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.

Quality

67%

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

50%

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 usable template with concrete Mermaid and OpenAPI examples, but it leans heavily on placeholder scaffolding, generic boilerplate instructions, and a dead reference link, leaving workflows unsequenced and guidance only partially actionable.

Suggestions

Replace the generic 'Instructions' boilerplate with a concrete numbered synthesis workflow (gather component docs -> group into deployment containers -> document interfaces -> render diagram) with explicit validation checkpoints.

Resolve or remove the placeholder link to ./c4-component-name.md since no references/ bundle exists, or create the referenced file.

Provide at least one fully worked, non-placeholder example container to lift actionability from template scaffolding to copy-paste-ready guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly a lean template without long concept explanations, but the generic 'Instructions' section ('Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes.') is filler Claude already knows, matching the level-2 anchor of mostly efficient with some unnecessary content.	2 / 3
Actionability	Provides a concrete Mermaid C4Container example and an OpenAPI template, but most scaffolding is placeholder-laden ('[Container Name]', '[Description]') rather than copy-paste ready, matching the level-2 anchor of some concrete guidance but incomplete.	2 / 3
Workflow Clarity	The 'Instructions' section is generic boilerplate with no sequenced workflow or validation checkpoints for the multi-step container-synthesis task, matching the level-2 anchor of steps present but checkpoints missing or implicit.	2 / 3
Progressive Disclosure	Sections are reasonably well-organized, but at ~160 lines the content is monolithic, the link to ./c4-component-name.md points to a non-existent placeholder file, and no actual reference files are bundled, matching the level-2 anchor of some structure with references not clearly signaled.	2 / 3
	Total	8 / 12 Passed

Description

85%

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 specific, complete, and well-scoped with an explicit 'Use when' trigger and concrete actions in third-person voice. Its main weakness is trigger-term naturalness, leaning on C4 process-jargon rather than the everyday terms a user might actually say.

Suggestions

Add concrete deployment terms a user would naturally say (e.g., Docker, Kubernetes, deployment diagrams, microservices) to the 'Use when' clause to broaden trigger coverage.

Reword 'synthesizes Component-level documentation into Container-level architecture' into more natural trigger phrasing to reduce process-jargon.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Synthesizes Component-level documentation into Container-level architecture', 'mapping components to deployment units', 'documenting container interfaces as APIs', and 'creating container diagrams', matching the level-3 anchor for several distinct actions.	3 / 3
Completeness	Clearly answers both what (synthesizes/maps/documents/creates) and when via the explicit 'Use when synthesizing components into deployment containers and documenting system deployment architecture' clause, matching the level-3 anchor for explicit what-and-when triggers.	3 / 3
Trigger Term Quality	Includes relevant C4-domain terms ('container diagrams', 'deployment containers', 'system deployment architecture') but the phrasing 'synthesizes Component-level documentation into Container-level architecture' is process-jargon and common variations like Docker/Kubernetes/deployment manifests are absent, matching the level-2 anchor of some relevant keywords missing common variations.	2 / 3
Distinctiveness Conflict Risk	Scoped specifically to 'C4 Container-level' deployment architecture, which is a clear niche distinct from sibling C4 context/component/code levels and unlikely to trigger for unrelated skills, matching the level-3 anchor.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/c4-container/SKILL.md
Commit: e63f7dd

Reviewed: about 5 hours 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.