c4-architecture-c4-architecture

Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.

Quality

61%

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-architecture-c4-architecture/SKILL.md

Quality

Content

65%

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

The body delivers highly actionable, concrete subagent prompts and a clear multi-phase workflow, but it is padded with boilerplate and redundancy, lacks explicit validation checkpoints for its batch operations, and carries a dangling reference instead of a real bundle.

Suggestions

Remove boilerplate (generic 'Use/Do not use this skill when', placeholder Instructions, 'Extended thinking') and de-duplicate Success Criteria/Coordination Notes to tighten conciseness.

Add explicit validation gates between phases (e.g., a checklist verifying all c4-code-*.md files exist and link correctly before starting Phase 2 synthesis) to lift workflow clarity.

Either create the referenced 'resources/implementation-playbook.md' bundle file or remove the dangling reference, and move the verbose per-subagent prompt templates into separate reference files for cleaner progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The workflow is detailed and largely purposeful, but includes filler (generic 'Use this skill when'/'Do not use this skill when' boilerplate, placeholder Instructions, an 'Extended thinking' block restating the overview, and redundant Coordination Notes/Success Criteria) that could be tightened.	2 / 3
Actionability	Subagent prompts specify exact output paths (e.g., 'C4-Documentation/c4-code-[directory-name].md'), exact subagent_type values, full section structures, and OpenAPI 3.1+ requirements — copy-paste ready and fully executable.	3 / 3
Workflow Clarity	The four-phase bottom-up sequence is clearly laid out, but for a batch operation that processes every directory and synthesizes across levels, validation gates (e.g., verify all c4-code-*.md exist before Phase 2) are only implied in Coordination Notes rather than explicit checkable checkpoints, capping it at 2.	2 / 3
Progressive Disclosure	Sections are clearly organized, but the ~390-line body is largely a monolithic inline wall of text and its only signaled reference ('resources/implementation-playbook.md') does not exist as a bundle file, so references are not cleanly backed by the bundle structure.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 conveys a clear, distinctive purpose but stops short of listing multiple concrete actions and omits any explicit "Use when..." trigger guidance, capping completeness and trigger-term coverage at 2.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when documenting an existing codebase's architecture, generating C4 diagrams, or mapping system context/containers/components').

Enumerate multiple concrete actions (e.g., 'Generate context, container, component, and code-level C4 diagrams with OpenAPI specs') to lift specificity to 3.

Dimension	Reasoning	Score
Specificity	Names a concrete domain and action ("Generate comprehensive C4 architecture documentation") plus the approach ("bottom-up analysis"), but lists only one main action rather than multiple specific concrete actions, so it is not a 3.	2 / 3
Completeness	It clearly answers "what" (generate C4 architecture docs via bottom-up analysis) but provides no "when" / "Use when" clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	"C4 architecture documentation" and "repository/codebase" are natural terms a user would say, but common variations (diagrams, system context, container/component diagrams) and an explicit "Use when..." trigger are missing, so coverage is incomplete.	2 / 3
Distinctiveness Conflict Risk	"C4 architecture documentation" is a clear, specialized niche with distinct triggers unlikely to overlap with unrelated skills.	3 / 3
	Total	9 / 12 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-architecture-c4-architecture/SKILL.md
Commit: a3068b7

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