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

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/context-driven-development/SKILL.md

Quality

Content

62%

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

The body is well-organized with clear workflows and strong validation checklists, but it is over-long for a SKILL.md, padded with conceptual material, and its one external reference is a dangling path to a non-existent file.

Suggestions

Move the detailed artifact contents, anti-patterns, and benefits into separate reference files (e.g., references/artifacts.md, references/anti-patterns.md) and link to them one level deep, keeping SKILL.md a lean overview.

Either create the referenced `resources/implementation-playbook.md` or remove the dangling reference, and verify all linked paths resolve to real bundle files.

Trim conceptual padding ('Core Philosophy', 'Benefits', 'Key principles') and replace the vague 'Instructions' boilerplate with concrete first steps tied to the workflow phases.

Dimension	Reasoning	Score
Conciseness	The body is mostly structured and useful (artifact contents, update triggers, checklists) but is padded with conceptual sections Claude already knows ('Core Philosophy', 'Benefits', 'Key principles') and generic boilerplate ('Apply relevant best practices and validate outcomes'), so it could be tightened considerably.	2 / 3
Actionability	There are concrete elements (the `/conductor:setup` command, directory structure, validation checklist, the `[~]` status marker), but the core 'Instructions' section is vague ('Clarify goals, constraints, and required inputs') and much of the artifact guidance is descriptive rather than directly executable, fitting the score-2 anchor.	2 / 3
Workflow Clarity	The Context → Spec & Plan → Implement workflow is clearly sequenced and backed by explicit validation steps ('Verify Context Before Implementation') and a detailed 'Context Validation Checklist', matching the score-3 anchor of clear sequence with checkpoints and checklists.	3 / 3
Progressive Disclosure	The skill is a monolithic ~400-line document with content that could be split out, and its single reference to `resources/implementation-playbook.md` points to a file that does not exist in any bundle directory, so references are present but not clearly signaled or backed by real files.	2 / 3
	Total	9 / 12 Passed

Description

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is in third person and identifies a clear domain, but it stays abstract and omits any explicit 'Use when...' trigger guidance. It reads more like a definition than an activation prompt.

Suggestions

Add an explicit 'Use when...' clause listing concrete trigger situations (e.g., setting up a Conductor project, onboarding to an existing context-driven project, deciding when to update context artifacts).

Replace abstract phrasing ('managed artifact', 'structured project documentation') with concrete actions users would recognize (e.g., 'Create and maintain product.md, tech-stack.md, workflow.md, and tracks.md context files').

Include natural trigger keywords users would actually say, such as 'context files', 'Conductor setup', 'project context', or 'onboarding'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('context as a managed artifact alongside code') and actions ('implementing and maintaining'), but the actions are abstract ('managed artifact', 'structured project documentation') rather than a list of concrete capabilities, matching the score-2 anchor.	2 / 3
Completeness	It clearly states what the skill does but provides no 'Use when...' clause or explicit trigger guidance in the description, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like 'context-driven development', 'AI interactions', 'team alignment', and 'project documentation' are relevant but somewhat jargon-heavy and miss common natural variations a user would actually say, fitting the score-2 anchor.	2 / 3
Distinctiveness Conflict Risk	The framing around context-as-artifact and AI alignment gives it a niche, but it could still overlap with general documentation or project-setup skills, matching the score-2 anchor.	2 / 3
	Total	8 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/context-driven-development/SKILL.md
Commit: 7962275

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.