SKILLEMALL.ai

BD visual-recap

Turn a PR, branch, commit, or git diff into an interactive visual recap with diagrams, file maps, API/schema summaries, annotated diffs, and focused review notes.

BuilderIO/agent-native Agent Skills author: BuilderIO 4 files body ≈ 8 306 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Turn a PR, branch, commit, or git diff into an interactive visual recap with diagrams, file maps, API/schema summaries, annotated diffs, and focused review…

As a process D 47/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, execution cost

IntegrationGitHubDesignAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
76
Run on models
none yet
Process rating
D
47/100
Unfinished process
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

The same skill appears in 3 more places: agent-native, agent-native, agent-native

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 8306 tokens (recommended < 5000); move details to references/
  • note edit-residue the text marks something as outdated (lines 20, 225, 228, 306, 396): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 47/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. 34 mutating operations with no state check
  • 40Execution cost. Instruction body is 8306 tokens: crowds the task out of the window
  • 50When it triggers. No condition that starts the skill
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
  • 85Steps. 48 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 18 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (21 tags): a typed call is more reliable

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)
  • +3Output format is not stated: the model decides each time
  • -2localhost URLs: will not work for another user
  • +1No license
  • +2Single-language instructions
  • +3Description length 162: enough signal without eating the budget
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 48 items
  • +4Has examples (0 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)

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