SKILLEMALL.ai

BF c4-diagramming

Create and review C4 software-architecture diagrams using Mermaid or Structurizr. Use when teams need a communication-ready system context, container, component, or code-level view, including audience, narrative, hierarchy, labels, legends, accessibility, and uncertainty. Do not use for Mermaid syntax/rendering work without C4 modeling, architecture decisions, or full accessibility conformance reviews.

magnus919/agent-skills Agent Skills author: magnus919 MIT 8 files body ≈ 1 805 tokens Open the sourcegithub.com↗ analyzed 27 h ago

Create and review C4 software-architecture diagrams using Mermaid or Structurizr.

As a process F 41/100 · Will not run — References files that are not bundled: ../mermaid-diagrams/references/c4-to-flowchart.md

AnalyzerGitHubSoftware developmentMarketingtype and topics are labelled automatically from the skill text
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
85
Run on models
none yet
Process rating
F
41/100
Will not run
References files that are not bundled: ../mermaid-diagrams/references/c4-to-flowchart.md
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
  • 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: 7. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../mermaid-diagrams/references/c4-to-flowchart.md

Process rating: all ten parameters 41/100

Will not run. References files that are not bundled: ../mermaid-diagrams/references/c4-to-flowchart.md
  • 0Tools and files. 1 referenced file(s) missing: ../mermaid-diagrams/references/c4-to-flowchart.md
  • 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. 4 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 20 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1805 tokens
  • low 10 top-level sections: this looks like several domains in one skill
  • low No test case covers injection arriving through data

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
  • +3Output format is not stated: the model decides each time
  • -2localhost URLs: will not work for another user
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 405: enough signal without eating the budget
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 20 items
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (4 of 5)
  • +1License stated

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