c4-container

Expert C4 Container-level documentation specialist.

Install with Tessl CLI

npx tessl i github:sickn33/antigravity-awesome-skills --skill c4-container

What are skills?

2.75x

Review — 30%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Evaluation — 99%

↑ 2.75x

Agent success when using this skill

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

22%

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

This description is severely underdeveloped. It relies on vague role-based language ('specialist') rather than describing concrete capabilities, lacks any trigger guidance for when Claude should select this skill, and provides minimal actionable information for skill selection among many options.

Suggestions

Replace 'specialist' with specific actions: 'Creates C4 Container diagrams showing system boundaries, containers, and their interactions'

Add explicit trigger guidance: 'Use when the user asks about C4 diagrams, container architecture, system documentation, or mentions PlantUML/Structurizr'

Include natural trigger terms users would say: 'architecture diagrams', 'system containers', 'microservices documentation', 'C4 model'

Dimension	Reasoning	Score
Specificity	The description uses vague language ('Expert', 'specialist') without listing any concrete actions. It doesn't specify what the skill actually does - no verbs describing capabilities like 'creates', 'generates', 'documents', etc.	1 / 3
Completeness	The description only vaguely hints at 'what' (documentation) and completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent trigger guidance.	1 / 3
Trigger Term Quality	Contains 'C4' and 'Container-level' which are relevant technical terms users might search for, but misses common variations like 'architecture diagrams', 'system documentation', 'container diagram', or file extensions.	2 / 3
Distinctiveness Conflict Risk	'C4 Container-level' provides some specificity that distinguishes it from generic documentation skills, but 'documentation specialist' is broad enough to potentially conflict with other documentation-related skills.	2 / 3
	Total	6 / 12 Passed

Implementation

37%

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

This skill provides a comprehensive template structure for C4 container documentation but lacks actionable workflow guidance. It reads more like a documentation template than a skill teaching Claude how to create container-level documentation. The placeholder-heavy content adds token overhead without providing concrete, executable instructions.

Suggestions

Replace the generic placeholder templates with a concrete workflow: 1) Analyze deployment configs, 2) Identify container boundaries, 3) Document interfaces, 4) Generate diagrams, with validation steps between each phase

Move the OpenAPI and Mermaid templates to separate reference files and keep only a concise quick-start example in the main skill

Add specific validation criteria for container documentation (e.g., 'Verify each container has at least one interface documented', 'Confirm all inter-container relationships are bidirectionally documented')

Transform 'Example Interactions' into concrete input/output examples showing what source material looks like and what the resulting documentation should contain

Dimension	Reasoning	Score
Conciseness	The skill contains significant template boilerplate with placeholder text ([Container Name], [Description], etc.) that adds bulk without providing actionable guidance. While structured, it explains concepts Claude likely knows (what containers are, basic API specs) rather than focusing on unique workflow knowledge.	2 / 3
Actionability	Provides templates and examples (Mermaid diagrams, OpenAPI specs) but they are generic placeholders rather than executable, copy-paste ready content. The 'Instructions' section is vague ('Clarify goals, constraints') rather than providing concrete steps for creating C4 container documentation.	2 / 3
Workflow Clarity	No clear workflow sequence for creating container documentation. The skill lists what should be documented but not how to do it step-by-step. Missing validation checkpoints for verifying diagram correctness or API spec completeness. The 'Example Interactions' are prompts, not workflow steps.	1 / 3
Progressive Disclosure	References external file 'resources/implementation-playbook.md' appropriately, but the main content is a monolithic template dump. The structure exists (sections for Containers, Interfaces, Dependencies) but inline templates could be split into separate reference files for cleaner navigation.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Reviewed: 2 days 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.