SKILLEMALL.ai

DC bro

Re-explain the previous assistant message, or any text typed after the command, in a much simpler way. For when a reply made you go 'bro what'. Use /bro for a plain-language version of the last answer, or /bro <text> to simplify a pasted paragraph, error, email, or doc.

Not recommendedcritical or high security findings · low grade D
luchasarie/bro-skill Agent Skills author: luchasarie 9 files · 1 script body ≈ 489 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Re-explain the previous assistant message, or any text typed after the command, in a much simpler way.

As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency

Proceduretype and topics are labelled automatically from the skill text
JSON
Technical rating
D
74/100
safety, quality, tests
Safety 60%
72
Quality 40%
77
Run on models
none yet
Process rating
C
55/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Dangerous commands
If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 3

  • high Dangerous commands cmd-pipe-to-shell README.md:46
    Downloads and executes remote code from an unrecognised host (pipe to shell)
    bash <(curl -fsSL https://raw.githubusercontent.com/luchasarie/bro-skill/main/install.sh)
Medium and low: 2
  • medium Dangerous commands cmd-pipe-to-shell install.sh:11
    Downloads and executes remote code from an unrecognised host (pipe to shell) (code comment)
    # Resolve SKILL.md — local copy first, otherwise download (supports curl | bash)
    comment
  • medium Dangerous commands cmd-pipe-to-shell install.sh:43
    Downloads and executes remote code from an unrecognised host (pipe to shell) (code comment)
    # not cp: on the curl | bash path $SKILL is a mktemp file (0600) and that mode rides along
    comment

Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

✓ No remarks against the Agent Skills spec

Process rating: all ten parameters 55/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 1 mutating operations with no state check
  • 40Consistency. Frontmatter name (bro) differs from the folder (bro-skill)
  • 50When it triggers. No condition that starts the skill
  • 60Failures and branches. 2 branches
  • 100Tools and files. No external tools needed
  • 100Steps. 9 steps
  • 100Execution cost. Instruction body is 489 tokens

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +4Structure: 2 headings, hard to scan
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +2Single-language instructions
  • +3Description length 270: enough signal without eating the budget
  • +3Step-by-step instructions: 9 items
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.