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

52%

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

63%Weight 40%Scale 1-5

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

The content is a thorough, well-structured instruction guide with concrete artifacts, procedures, and a validation checklist, scoring well on actionability and workflow clarity. It is held back by padding in the Benefits section and a monolithic single-file structure with no progressive disclosure via bundle files.

Suggestions

Trim or remove the Benefits section (Team Alignment, AI Consistency, Institutional Memory, Quality Assurance), which restates value Claude already knows without adding actionable guidance.

Move detailed artifact reference material, anti-patterns, and tool-integration guidance into reference files under ./references/ and link to them from SKILL.md to improve progressive disclosure.

Add explicit verification feedback loops (e.g., 'run the context validation checklist; if any item fails, update the artifact and re-validate before proceeding') to the workflow to reach full workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly well-organized reference material but includes sections that restate value Claude already knows (e.g., the Benefits section on Team Alignment, AI Consistency, Institutional Memory) and somewhat padded principle statements, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides concrete, specific guidance—named artifacts (product.md, tech-stack.md), numbered update procedures, the /conductor:setup command, a directory tree, and a validation checklist—with only minor gaps such as missing exact commands beyond /conductor:setup.	4 / 5
Workflow Clarity	The Context → Spec & Plan → Implement workflow, lifecycle, session continuity, and context validation checklist give a clear sequence with most checkpoints present, fitting 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	No bundle files exist and all ~400 lines live in a single SKILL.md with no external references signaled; content that could be split (artifact detail, anti-patterns, tool integration) is inlined, matching 'some structure but could be better organized; references present but not clearly signaled'.	3 / 5
	Total	14 / 20 Passed

Description

41%Weight 40%Scale 1-5

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 clearly conveys the skill's purpose but relies on abstract language and lacks an explicit 'Use when' trigger, weakening trigger quality and capping completeness. It is reasonably distinct from other skills.

Suggestions

Add an explicit 'Use when...' clause naming concrete scenarios (e.g., setting up a Conductor project, onboarding to an existing context, updating context artifacts before a work unit).

Replace abstract verbs ('implementing and maintaining', 'enabling') with concrete operations such as 'create, validate, and synchronize context artifacts (product.md, tech-stack.md, workflow.md)'.

Include natural trigger keywords users would actually say, such as 'Conductor setup', 'project context', or 'context-driven development'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('context as a managed artifact', 'structured project documentation') but the actions ('implementing and maintaining', 'enabling') are abstract rather than concrete operations, fitting the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states a clear 'what' (a guide for implementing and maintaining context) but provides no explicit 'when/Use when' trigger, and per the rubric a missing Use-when clause caps completeness at 3.	3 / 5
Trigger Term Quality	Terms like 'context', 'AI interactions', and 'team alignment' are conceptual jargon rather than the natural phrases a user would say when needing this skill, matching 'one or two generic keywords; missing the natural phrases users say'.	2 / 5
Distinctiveness Conflict Risk	The 'context as a managed artifact alongside code' framing carves a fairly specific niche with only minor overlap risk against adjacent documentation skills, fitting 'mostly distinct; minor overlap risk'.	4 / 5
	Total	11 / 20 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/agentic-awesome-skills
Path: skills/context-driven-development/SKILL.md
Commit: b1aebac

Reviewed: ~18 hours 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.