context-driven-development

tessl i github:sickn33/antigravity-awesome-skills --skill context-driven-development

Use this skill when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md, and workflow.md files.

48%

Overall

Validation — 88%

Implementation — 35%

Activation — 40%

SKILL.md

Review

Evals

Validation

88%

Warnings & errors only

Criteria	Description	Result
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
license_field	'license' field is missing	Warning

	Total	14 / 16 Passed

Implementation

35%

This skill is comprehensive but severely over-documented, explaining many concepts Claude already understands (what product documentation contains, basic git workflows, IDE usage). The content would benefit from aggressive trimming to focus on Conductor-specific patterns and decisions, with detailed reference material moved to linked files. The lack of executable examples and concrete commands reduces actionability.

Suggestions

Reduce content by 60-70% by removing explanations of obvious concepts (what product.md contains, basic git practices) and keeping only Conductor-specific decisions and patterns

Add executable code examples for key operations like running validation, updating artifacts, and using the /conductor:setup command with expected outputs

Move detailed sections (Anti-Patterns, Integration with Development Tools, Session Continuity) to separate referenced files, keeping only summaries in the main skill

Add explicit validation commands with expected outputs in the workflow sections, especially for the 'Verify Context Before Implementation' process

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~300 lines with significant redundancy. Explains obvious concepts Claude already knows (what product.md contains, basic git practices, IDE integration). Multiple sections repeat the same information (update triggers, validation checklists, best practices overlap heavily).	1 / 3
Actionability	Provides some concrete guidance like directory structure and checklists, but lacks executable code examples. Commands like '/conductor:setup' are mentioned but not demonstrated. Most content describes concepts rather than providing copy-paste ready instructions.	2 / 3
Workflow Clarity	The 'Context → Spec & Plan → Implement' workflow is stated but lacks explicit validation checkpoints. Session continuity and context validation sections list steps but don't include verification commands or feedback loops for error recovery.	2 / 3
Progressive Disclosure	References 'resources/implementation-playbook.md' for detailed examples, which is good. However, the main document is a monolithic wall of text that should be split into separate files (artifact reference, anti-patterns, integration guides). Content that belongs in referenced files is inline.	2 / 3
	Total	7 / 12 Passed

Activation

40%

This description provides a 'Use when' clause but lacks specificity about what concrete actions the skill enables. It relies heavily on proper nouns (Conductor) and file names without explaining what operations can be performed. The description tells Claude when to use it but not what it actually does.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Creates and updates product.md files, generates tech-stack.md documentation, maintains workflow.md processes'

Expand the 'what' portion to list 2-4 specific capabilities before the 'Use when' clause

Include natural trigger terms users might say, such as 'project setup', 'context files', 'development methodology', or 'project documentation'

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'working with' and 'managing' without listing concrete actions. It names file types but doesn't specify what operations can be performed on them.	1 / 3
Completeness	Has a 'Use when' clause addressing when to use the skill, but the 'what' portion is weak - it doesn't clearly explain what concrete actions or capabilities the skill provides beyond vague 'managing' and 'understanding'.	2 / 3
Trigger Term Quality	Includes some relevant terms like 'product.md', 'tech-stack.md', 'workflow.md', and 'context-driven development', but 'Conductor' is a proper noun that users may not naturally use, and common variations are missing.	2 / 3
Distinctiveness Conflict Risk	The specific file names (product.md, tech-stack.md, workflow.md) and 'Conductor' methodology provide some distinctiveness, but 'project context artifacts' is generic enough to potentially overlap with other project management skills.	2 / 3
	Total	7 / 12 Passed

Reviewed

19 days ago

Table of Contents

Validation Implementation Activation

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.