SKILLEMALL.ai

AF c4-container

Expert C4 Container-level documentation specialist. Synthesizes Component-level documentation into Container-level architecture, mapping components to deployment units, documenting container interfaces as APIs, and creating container diagrams. Use when synthesizing components into deployment containers and documenting system deployment architecture.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 1 298 tokens Open the sourcegithub.com analyzed 2 d ago

Expert C4 Container-level documentation specialist.

As a process F 46/100 · Will not run — References files that are not bundled: c4-component-name.md

IntegrationKubernetesInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
81
Run on models
none yet
Process rating
F
46/100
Will not run
References files that are not bundled: c4-component-name.md
Tools and files w 18
0
Failures and branches w 10
0
Progress reporting w 2
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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: c4-component-name.md

Process rating: all ten parameters 46/100

Will not run. References files that are not bundled: c4-component-name.md
  • 0Tools and files. 1 referenced file(s) missing: c4-component-name.md
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 20 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 60Steps. 42 steps, 6 vague phrases
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1298 tokens
  • low 14 top-level sections: this looks like several domains in one skill

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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 351: enough signal without eating the budget
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 42 items
  • +3Output format is stated explicitly
  • +4Has examples (3 code blocks)

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