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...

Install with Tessl CLI

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

What are skills?

1.05x

Quality

37%

Does it follow best practices?

Impact

91%

1.05x

Average score across 3 eval scenarios

Optimize this skill with Tessl

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

SKILL.md

Review

Evals

Quality

Discovery

40%

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 suffers from vagueness and apparent truncation. While it attempts to establish when to use the skill and mentions specific artifacts, it fails to articulate concrete actions Claude can perform. The methodology-specific terminology provides some distinctiveness but the overall lack of specificity weakens its utility for skill selection.

Suggestions

Complete the truncated description and list specific concrete actions (e.g., 'Creates product.md files, updates tech-stack.md, generates context summaries')

Add natural trigger terms users might say (e.g., 'project setup', 'documentation structure', 'context files')

Specify what 'managing project context artifacts' actually means in terms of actionable operations

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'working with' and 'managing' without listing concrete actions. It mentions artifacts (product.md, tech-stack.md) but doesn't specify what operations can be performed on them.	1 / 3
Completeness	Has a 'Use when' clause which addresses when to use it, but the 'what' is weak - it only vaguely describes 'managing project context artifacts' and 'understanding the relationship' without concrete capabilities. The truncation ('and...') also indicates incompleteness.	2 / 3
Trigger Term Quality	Includes some relevant terms like 'Conductor', 'context-driven development', 'product.md', 'tech-stack.md' that users might mention, but these are fairly technical/specific and the description is truncated, potentially missing common variations.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Conductor' methodology and specific file names (product.md, tech-stack.md) provides some distinctiveness, but 'managing project context' is generic enough to potentially overlap with other project management or documentation skills.	2 / 3
	Total	7 / 12 Passed

Implementation

35%

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

This skill suffers from significant verbosity, explaining concepts Claude already understands (what product.md contains, basic git workflows, IDE configuration). The content would benefit from being 70% shorter with the detailed artifact descriptions and integration guides moved to referenced files. While the structure is logical, the lack of executable examples and concrete commands reduces actionability.

Suggestions

Reduce content by 60-70% by removing explanations of obvious concepts (what each artifact contains, basic git practices) and moving detailed sections to referenced files

Add concrete, executable examples for key operations like running validation, updating artifacts, and using /conductor:setup with actual command output

Split into multiple files: keep SKILL.md as a concise overview (~50 lines) with links to ARTIFACTS.md, WORKFLOWS.md, INTEGRATION.md for details

Add explicit validation commands with expected outputs in the workflow sections rather than just checklist items

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 relationships, anti-patterns, integration guides could each be separate documents).	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: 1 day 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.