c4-container

Expert C4 Container-level documentation specialist.

Quality

40%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/c4-container/SKILL.md

Quality

Content

43%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-sectioned but template-heavy placeholder document: it provides useful Mermaid and OpenAPI scaffolding yet leans on fill-in-the-blank text rather than executable guidance, has no sequenced workflow with validation, and references a non-existent implementation-playbook file. It reads more as a blank template than operational instructions.

Suggestions

Replace the generic "Instructions" bullets with a numbered, sequenced workflow that includes explicit validation checkpoints (e.g., verify Mermaid renders, validate OpenAPI with a linter before output).

Move the large Mermaid C4Container and OpenAPI templates into files under references/ and keep only a concise inline example in SKILL.md, fixing the broken "resources/implementation-playbook.md" reference to an actual bundle file.

Cut placeholder filler ([Container Name], [Description], etc.) and replace with a worked concrete example so the guidance is executable rather than a blank form.

Dimension	Reasoning	Score
Conciseness	The body does not over-explain concepts Claude already knows, but it carries substantial template placeholder padding (e.g. "[Container Name]", "[Description]", "[Short description of container purpose and deployment]") and inlined Mermaid/OpenAPI blocks that inflate tokens, matching the score-3 anchor (mostly efficient, could be tightened); it is not a 2 because it avoids concept over-explanation and not a 4 due to the volume of placeholder filler.	3 / 5
Actionability	Concrete reusable artifacts are present (a Mermaid C4Container diagram template and an OpenAPI YAML template), but the "Instructions" section is abstract ("Clarify goals... Apply relevant best practices and validate outcomes") and most content is fill-in-the-blank placeholders, matching the score-3 anchor (some concrete guidance but incomplete); it is not a 4 because key execution details remain placeholder-only.	3 / 5
Workflow Clarity	The "Instructions" list is a loose, unnumbered set of generic steps with no explicit sequence, validation checkpoints, or feedback loops, matching the score-2 anchor (rough sequence, steps poorly defined, validation absent); it is not a 3 because the steps are not clearly sequenced and not a 1 because a rough high-level flow is present.	2 / 5
Progressive Disclosure	Clear section headers provide structure, but large Mermaid and OpenAPI templates are inlined rather than split into reference files, and the sole reference ("resources/implementation-playbook.md") points to a path with no corresponding bundle file, matching the score-3 anchor (some structure, references not clearly signaled, content that should be separate is inline); it is not a 4 because of the broken reference and inlined bulk, and not a 2 because real structure exists.	3 / 5
	Total	11 / 20 Passed

Description

36%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a terse role label that names the C4 Container-level domain but provides no concrete actions, no natural trigger phrases beyond the domain term, and no explicit "use when" guidance. It is distinguishable within the C4 family only by the level qualifier, leaving meaningful overlap and trigger-discovery risk.

Suggestions

Rewrite in third-person action voice listing concrete actions, e.g. "Creates C4 Container-level diagrams and OpenAPI specs by mapping components to deployment units."

Add an explicit "Use when..." clause with natural trigger phrases (e.g., "Use when documenting container deployment architecture, container diagrams, or container APIs").

Include common synonyms and artifacts users mention (Mermaid C4Container, OpenAPI/Swagger specs, Dockerfiles, Kubernetes manifests) to improve trigger-term coverage and reduce sibling-skill overlap.

Dimension	Reasoning	Score
Specificity	The description "Expert C4 Container-level documentation specialist" names the domain clearly but states no concrete actions, describing a role persona rather than performed actions; it fits the score-2 anchor (names domain, minimal actions) better than score 1 because the domain is explicitly identified, but it is not a 3 since no concrete actions are listed.	2 / 5
Completeness	It offers only a vague role-based "what" ("documentation specialist") and entirely lacks a "when"/"Use when..." trigger clause, matching the score-2 anchor (vague what, no when); per guidelines the missing Use-when clause caps it at 3, and the what itself is too vague to reach 3.	2 / 5
Trigger Term Quality	"C4 Container" is a genuine natural term a user might say, but the description includes only that single keyword with no synonyms, variations, or file extensions, matching the score-3 anchor (some relevant keywords, missing common variations); it is not a 4 because coverage is thin and not a 2 because a real natural term is present.	3 / 5
Distinctiveness Conflict Risk	"C4 Container-level" denotes a reasonably distinct niche, but as part of a family of sibling C4-level skills (Context/Component/Code) it carries real overlap risk, matching the score-3 anchor (somewhat specific, could overlap); it is not a 4 because the bare role wording does not clearly disambiguate from those sibling skills.	3 / 5
	Total	10 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/c4-container/SKILL.md
Commit: 1f67c44

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.