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.
27
10%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/context-driven-development/SKILL.mdQuality
Discovery
0%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 is highly abstract and reads like marketing copy rather than a functional skill description. It lacks concrete actions, natural trigger terms, explicit 'when to use' guidance, and any distinguishing specificity that would help Claude select it from a pool of skills.
Suggestions
Replace abstract language with concrete actions, e.g., 'Creates and updates CONTEXT.md files that document project structure, conventions, and AI interaction guidelines.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about creating context files, setting up AI-friendly project documentation, CONTEXT.md, or establishing conventions for AI coding assistants.'
Include specific file types or artifacts this skill produces (e.g., 'CONTEXT.md', 'CLAUDE.md', '.context/' directory) to make it clearly distinguishable from generic documentation skills.
| 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 (no concrete actions listed) and there is no 'when' clause or explicit trigger guidance at all. The description fails to answer either question clearly. | 1 / 3 |
Trigger Term Quality | The description lacks natural keywords a user would say. Terms like 'managed artifact', 'structured project documentation', and 'consistent AI interactions' are abstract jargon. A user would more likely say things like 'context file', 'CONTEXT.md', 'project docs for AI', or 'Claude context'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so generic — 'structured project documentation', 'team alignment' — that it could easily overlap with any documentation, project management, or AI workflow skill. Nothing distinguishes it as a specific, unique capability. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is extremely verbose and largely descriptive rather than actionable. It reads more like a conceptual guide or README for a documentation methodology than an instruction set for Claude. The content explains many things Claude already knows (what product vision is, benefits of documentation, what anti-patterns are) while failing to provide concrete, executable guidance like templates, code examples, or specific commands.
Suggestions
Replace descriptive artifact sections with concrete templates showing exactly what each file (product.md, tech-stack.md, etc.) should contain, with example content that can be copy-pasted and adapted.
Cut the 'Benefits', 'Core Philosophy', and 'Common Anti-Patterns' sections entirely—Claude understands these concepts and they consume tokens without adding actionable value.
Move detailed content (artifact relationships, integration guidance, session continuity) into separate reference files and keep SKILL.md as a concise overview with clear links.
Add executable examples: show a concrete `/conductor:setup` interaction, a sample completed product.md, or a specific validation script rather than abstract descriptions of what to do.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Much of the content explains concepts Claude already understands (what product vision is, what brand voice means, benefits of documentation). Sections like 'Benefits', 'Core Philosophy', and 'Common Anti-Patterns' are largely things Claude knows. The artifact descriptions read like a documentation template rather than actionable instructions. | 1 / 3 |
Actionability | Despite its length, the skill contains zero executable code, no concrete commands (references to `/conductor:setup` but no actual implementation), no specific examples of what context artifacts should look like, and no copy-paste ready templates. Guidance is almost entirely abstract and descriptive rather than instructive. | 1 / 3 |
Workflow Clarity | There is a clear sequence (Context → Spec & Plan → Implement) and the Context Validation Checklist provides explicit checkpoints. However, the workflow lacks concrete validation commands or tools, and the steps are largely procedural descriptions without feedback loops for error recovery. The session continuity section has reasonable sequencing. | 2 / 3 |
Progressive Disclosure | There is one reference to `resources/implementation-playbook.md` for detailed examples, which is good. However, the massive amount of inline content (artifact descriptions, anti-patterns, best practices, integration guidance, session continuity) should be split into separate reference files. The skill is essentially a monolithic wall of text that would benefit greatly from offloading sections. | 2 / 3 |
Total | 6 / 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 | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
93c57b2
- 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.