ce-strategy

Create or update STRATEGY.md. Use when starting a product, adding a strategy doc to an existing repo, changing direction or roadmap, or when ce-ideate, ce-brainstorm, or ce-plan need upstream product grounding.

Quality

80%

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

Quality

Content

78%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.

A well-structured, instruction-oriented skill body with a clear phased workflow, concrete actionable guidance, and exemplary progressive disclosure that offloads detail to four real reference files. The main improvement lever is tightening the dense Boundaries prose and the repeated reference re-listings.

Suggestions

Tighten the Boundaries paragraph (line 21): split it into short bullet points so the ownership test and author-approved marker rules are scannable rather than buried in one long sentence.

Reduce repetition of the reference filenames across phases by introducing them once and referring back by short name, trimming token cost without losing the load-before-use signal.

Add one explicit post-write verification step (e.g., re-read STRATEGY.md to confirm sections and frontmatter match the template) to lift workflow_clarity to the top anchor.

Dimension	Reasoning	Score
Conciseness	The body is information-dense and assumes Claude's competence without explaining basic concepts, but the long Boundaries paragraph (line 21) and repeated re-listing of reference files add some prose that could be trimmed, keeping it just below the lean anchor.	4 / 5
Actionability	Concrete, specific guidance is present throughout (ordered interview steps, "Show the model in chat before the first question: three to five lines", "Ask one question at a time through the host's blocking question tool"), with the only gap being that pushback rules and anti-pattern examples live in references rather than inline.	4 / 5
Workflow Clarity	The four phases and the numbered 1-9 interview order give a clear sequence with checkpoints (show model and invite correction, present draft and offer edits, two-round pushback cap), but explicit post-write verification of the written file is only implied, leaving it just short of the top anchor.	4 / 5
Progressive Disclosure	SKILL.md is a clear overview pointing to four well-signaled one-level-deep references (grounding.md, interview.md, strategy-template.md, update-run.md), all of which exist, with content appropriately split and easy navigation, matching the top anchor.	5 / 5
	Total	17 / 20 Passed

Description

82%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.

A strong description that explicitly answers both what it does and when to use it with concrete, natural trigger phrases and a clear niche. Specificity is the only relative weak spot, as it lists only the two generic actions create/update rather than enumerating the broader set of concrete actions the skill performs.

Dimension	Reasoning	Score
Specificity	"Create or update STRATEGY.md" names the domain artifact and two concrete actions, matching the anchor that names a domain with 1-2 concrete actions; it does not list the multiple specific actions needed for a 4 or 5.	3 / 5
Completeness	It explicitly states both what ("Create or update STRATEGY.md") and when ("Use when starting a product, adding a strategy doc... changing direction or roadmap, or when ce-ideate, ce-brainstorm, or ce-plan need upstream product grounding") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases are present ("starting a product", "adding a strategy doc", "changing direction or roadmap", "upstream product grounding") plus the named artifact STRATEGY.md, giving good keyword coverage with synonyms, though a few natural variations are absent.	4 / 5
Distinctiveness Conflict Risk	The STRATEGY.md artifact, product-strategy niche, and named downstream skills give it a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	17 / 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: EveryInc/compound-engineering-plugin
Path: skills/ce-strategy/SKILL.md
Commit: 26bf5b1

Reviewed: 4 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.