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.
Install with Tessl CLI
npx tessl i github:Dicklesworthstone/pi_agent_rust --skill context-driven-development62
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/skillValidation for skill structure
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 focuses heavily on 'when' triggers but fails to explain 'what' the skill actually does. It relies on proper nouns and file names for distinctiveness but lacks concrete action verbs describing capabilities. The vague language ('working with', 'managing', 'understanding') provides little insight into the skill's actual functionality.
Suggestions
Replace vague verbs with specific actions (e.g., 'Creates and updates product.md files, generates tech-stack.md documentation, maintains workflow.md processes').
Add concrete capabilities that explain what 'context-driven development methodology' means in practice (e.g., 'tracks project requirements, documents architectural decisions, defines development workflows').
Include natural trigger terms users might say, such as 'project setup', 'documentation structure', 'project context', or 'development workflow'.
| 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 explain what the skill actually does beyond vague 'working with' and 'managing' language. | 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 'managing project context artifacts' is generic enough to overlap with other project management skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive conceptual guidance for context-driven development with good workflow structure and validation checklists. However, it's verbose with explanatory content Claude doesn't need, lacks concrete executable examples (no actual code, configs, or command outputs), and could benefit from splitting into a concise overview with referenced detail files.
Suggestions
Remove explanatory sections like 'Core Philosophy' and 'Benefits' that explain concepts Claude already understands - focus on the actionable 'how'
Add concrete examples: show actual product.md content, demonstrate a real tech-stack.md update, provide sample git hook code
Split into SKILL.md overview with references to separate files for checklists (VALIDATION.md), anti-patterns (ANTI-PATTERNS.md), and integration guides (INTEGRATION.md)
Replace the 'Integration with Development Tools' section with actual configuration snippets or remove it entirely if no concrete examples exist
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably organized but includes explanatory material Claude already knows (e.g., explaining what 'living documentation' means, benefits sections that state obvious advantages). Several sections could be significantly tightened without losing actionable value. | 2 / 3 |
Actionability | Provides good structural guidance and checklists, but lacks concrete executable examples. Commands like '/conductor:setup' are mentioned but not demonstrated. The 'Integration with Development Tools' section describes what to do conceptually but provides no actual code or configuration examples. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced (Context → Spec & Plan → Implement) with explicit validation checklists. The 'Context Validation Checklist' provides clear checkpoints, and the 'Session Continuity' section includes explicit steps for starting, ending, and handling interruptions. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but this is a monolithic document that could benefit from splitting detailed content (like the full validation checklist, anti-patterns, and integration guides) into separate referenced files. The directory structure suggests a multi-file approach that isn't reflected in this skill's own organization. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%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
Table of Contents
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.