SKILLEMALL.ai

BF readme-badger

Badge design and selection knowledge base for shields.io badges in README files. Use when writing or updating READMEs, choosing badge layouts, selecting badge styles, adding project health indicators, or picking Simple Icons logo slugs. Covers shields.io URL encoding rules, static vs dynamic badge selection, style variants (flat/flat-square/for-the-badge/social/plastic), layout patterns (two-tier/inline/centered), project-type badge sets for Python/JS/Rust/Claude plugins, color reference, non-obvious logo slugs, and common anti-patterns to avoid.

Jamie-BitFlight/claude_skills Agent Skills author: Jamie-BitFlight MIT 6 files body ≈ 3 813 tokens Open the sourcegithub.com↗ analyzed 8 d ago

Badge design and selection knowledge base for shields.io badges in README files. Use when writing or updating READMEs, choosing badge layouts, selecting badge…

As a process F 33/100 · No process to follow — References files that are not bundled: img

ReferenceGitHubDockerSoftware developmentDesigntype and topics are labelled automatically from the skill text
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
99
Quality 40%
82
Run on models
none yet
Process rating
F
33/100
No process to follow
References files that are not bundled: img
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Secrets in code secret-high-entropy-token SKILL.md:39
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    4. Assemble path: `Clau…757`
    quoted

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: img
  • note edit-residue the text marks something as outdated (lines 61): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 33/100

Will not run. References files that are not bundled: img
  • 0Tools and files. 1 referenced file(s) missing: img
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 3 mutating operations with no state check
  • 100Steps. 17 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3813 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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 552: enough signal without eating the budget
  • +4Structure: 24 headings
  • +3Step-by-step instructions: 17 items
  • +4Has examples (15 code blocks)
  • +4Reference files are cited in the instructions (5 of 5)

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