context-driven-development

Guide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation.

Quality

13%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/context-driven-development/SKILL.md

Quality

Content

27%

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

This skill reads more like comprehensive documentation or a methodology guide than a concise, actionable skill for Claude. It is extremely verbose, explaining many concepts Claude already knows (what documentation is, why consistency matters, what anti-patterns are), while lacking concrete executable examples or commands. The content would benefit enormously from aggressive trimming and splitting into referenced sub-files.

Suggestions

Reduce the content by at least 60%—remove the 'Benefits' section entirely, collapse artifact descriptions into a brief table, and eliminate explanations of obvious concepts like 'Stale Context: Problem: Context documents become outdated and misleading.'

Add concrete, executable examples: show actual file content snippets for product.md, tech-stack.md, etc., and provide real commands or code for validation steps rather than abstract descriptions.

Split detailed content (anti-patterns, IDE/CI integration, session continuity, artifact relationship details) into separate referenced files and keep SKILL.md as a concise overview with clear navigation links.

Integrate validation checkpoints directly into the workflow steps rather than listing them as a separate section, and add explicit feedback loops (e.g., 'if context validation fails → update artifacts → re-validate → proceed').

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~300+ lines, with extensive sections explaining concepts Claude already understands (what product.md is, benefits of documentation, anti-patterns descriptions, IDE integration tips). The 'Benefits' section, 'Core Philosophy', and much of the artifact descriptions are conceptual padding that don't add actionable value. The content reads more like a blog post or whitepaper than a concise skill instruction.	1 / 3
Actionability	The skill provides structured checklists and step sequences (e.g., 'Verify Context Before Implementation', 'Context Validation Checklist'), which are somewhat actionable. However, there are no concrete code examples, no executable commands (references to `/conductor:setup` are vague), and much of the guidance is descriptive rather than instructive. The reference to 'resources/implementation-playbook.md' for detailed examples is good but the playbook isn't provided.	2 / 3
Workflow Clarity	The workflow is outlined (Context → Spec & Plan → Implement) with some sequencing in sections like 'Session Continuity' and 'Greenfield vs Brownfield'. However, validation checkpoints are presented as a separate checklist rather than integrated into the workflow steps, and there are no explicit feedback loops for error recovery. The 'Context Maintenance Principles' section lists steps but lacks concrete validation/verification mechanisms.	2 / 3
Progressive Disclosure	The skill references 'resources/implementation-playbook.md' but no bundle files are provided, making this reference unverifiable and potentially broken. The content is a monolithic wall of text with everything inline—artifact descriptions, anti-patterns, best practices, IDE integration, CI/CD integration, session continuity—all of which could be split into separate referenced files. There's no clear hierarchy or navigation structure.	1 / 3
	Total	6 / 12 Passed

Description

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 reads like marketing copy rather than a functional skill description. It relies heavily on abstract buzzwords ('managed artifact', 'team alignment', 'consistent AI interactions') without specifying concrete actions or when the skill should be triggered. It would be very difficult for Claude to distinguish this skill from other documentation or project management skills.

Suggestions

Replace abstract language with concrete actions, e.g., 'Creates and updates CONTEXT.md files that document project architecture, conventions, and AI interaction guidelines.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about setting up context files, project documentation for AI assistants, CONTEXT.md, or maintaining project context.'

Differentiate from generic documentation skills by naming the specific artifact type (e.g., CONTEXT.md) and the specific use case (e.g., providing context to AI coding assistants).

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language like 'implementing and maintaining context', 'managed artifact', 'consistent AI interactions', and 'team alignment'. No concrete actions are listed — it reads more like a mission statement than a capability description.	1 / 3
Completeness	The 'what' is vague (implementing and maintaining context as a managed artifact) and there is no 'when' clause or explicit trigger guidance at all. The absence of a 'Use when...' clause caps this at 2, but the weak 'what' brings it to 1.	1 / 3
Trigger Term Quality	The description lacks natural keywords a user would say. Terms like 'managed artifact', 'structured project documentation', and 'team alignment' are abstract buzzwords. A user needing this skill would more likely say things like 'context file', 'CONTEXT.md', 'AI project context', or 'project documentation for Claude'.	1 / 3
Distinctiveness Conflict Risk	The description is so generic — 'structured project documentation', 'team alignment', 'consistent AI interactions' — that it could easily overlap with any documentation, project management, or AI workflow skill. Nothing clearly carves out a distinct niche.	1 / 3
	Total	4 / 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

Repository: sickn33/antigravity-awesome-skills
Commit: 88d1e11

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