incremental-implementation

Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The skill is highly actionable with executable commands, code, and clear sequenced workflows, but it is somewhat verbose and ships a broken reference to a non-existent bundle file.

Suggestions

Create references/definition-of-done.md (or remove the See Also pointer) so the cited progressive-disclosure reference resolves to a real file.

Consolidate the overlapping Red Flags, Common Rationalizations, and Implementation Rules sections to reduce redundancy and tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of basic-concept padding, but it is verbose for a process skill with redundant sections (Red Flags, Common Rationalizations, and the Rules overlap) that could be tightened.	2 / 3
Actionability	It provides fully executable commands (npm test, npm run build, npx tsc --noEmit, npm run lint), complete TypeScript examples, concrete slicing walkthroughs, and a copy-paste agent prompt.	3 / 3
Workflow Clarity	The Increment Cycle is a clearly sequenced Implement→Test→Verify→Commit loop with explicit validation checkpoints, supported by an Increment Checklist and a final Verification checklist.	3 / 3
Progressive Disclosure	Sections are well organized, but the body references references/definition-of-done.md (and the git-workflow-and-versioning skill) while no references/ bundle directory exists, leaving a dangling reference, and material that could be split out remains inline.	2 / 3
	Total	10 / 12 Passed

Description

82%

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 states what the skill does and gives multiple natural "Use when..." triggers, but it stays somewhat abstract about concrete actions and risks overlapping with general coding-workflow skills.

Suggestions

Add one or two concrete actions (e.g., "slice work into buildable increments, verify each with tests, then commit") to lift specificity from 2 to 3.

Sharpen the distinctiveness by tying triggers to a narrower niche, such as multi-file or multi-step changes, to reduce overlap with general planning or refactoring skills.

Dimension	Reasoning	Score
Specificity	Names the domain and a core action ("Delivers changes incrementally") but does not list multiple distinct concrete actions the way the score-3 anchor does; it stops short of being comprehensive.	2 / 3
Completeness	Explicitly answers both what ("Delivers changes incrementally") and when (multiple "Use when..." clauses), so it is not subject to the missing-trigger cap.	3 / 3
Trigger Term Quality	Three explicit "Use when..." clauses map to natural user sentiments ("touches more than one file", "write a large amount of code at once", "a task feels too big to land in one step"), giving good coverage of phrasings users would actually say.	3 / 3
Distinctiveness Conflict Risk	It describes a general engineering discipline rather than a distinct domain niche, so it could overlap with other coding, refactoring, or planning skills rather than being clearly non-conflicting.	2 / 3
	Total	10 / 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: addyosmani/agent-skills
Commit: 70b7506

Reviewed: 3 days 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.