CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ce-strategy

Create or update STRATEGY.md. Use when starting a product, adding a strategy doc, or changing direction or roadmap.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%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, interview-driven instruction skill with excellent workflow sequencing, explicit user-confirmation checkpoints before writes, and exemplary progressive disclosure that pushes detail into four purpose-labeled reference files loaded at the right phase. The only weakness is moderate redundancy between the body and the references, which costs tokens without adding guidance.

DimensionReasoningScore

Conciseness

The body is densely operational with no explanation of concepts Claude already knows, but there is duplication between it and the references (the repo-model wording and show-in-chat instructions appear in both SKILL.md Phase 0 and grounding.md, and the ownership rules are stated in the body while also delegated to update-run.md), and the 'Meaning is the contract' boundary bullet is a ~150-word paragraph that could be trimmed.

4 / 5

Actionability

Guidance is highly concrete for an instruction-only skill: an exact 9-section interview order, quoted routing announcements ("Strategy doc not found - let's write it."), a file-state decision rule, timed non-optional reference loads, and an explicit done-state; the interview question wording, pushback rules, and quality bar are deferred to references rather than given inline, leaving minor gaps.

4 / 5

Workflow Clarity

Phases 0-3 are clearly sequenced with a deterministic routing rule and explicit validation checkpoints: the repo model is shown and corrected before the first question, the full draft is presented with an edit round before any write, the question tool has an error fallback, and a two-round cap with explicit recovery ('a completed run, not a blocked one') prevents stalls.

5 / 5

Progressive Disclosure

A ~50-line overview routes to four real, one-level-deep references (grounding.md, interview.md, strategy-template.md, update-run.md), each clearly signaled with its purpose and load timing ('non-optional load', 'required read before you edit an existing file'); the split keeps interview, template, and update detail out of the main context until the phase that needs them.

5 / 5

Total

18

/

20

Passed

Description

78%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 concise, well-structured description that clearly answers both what the skill does and when to use it, with explicit and natural trigger phrases and low conflict risk. Its main gap is capability breadth: only two actions (create, update) are stated, leaving the fuller capability set unmentioned.

Suggestions

Add one or two more concrete capabilities to the what-clause (e.g., 'interviews the user to capture purpose, positioning, and metrics, then stress-tests the direction') to lift specificity beyond two bare actions.

Include a common synonym such as 'product strategy' or 'vision' in the when-clause to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

"Create or update STRATEGY.md" names the domain and exactly two concrete actions on a specific artifact, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; it does not list several specific actions (e.g., interviewing, stress-testing direction, maintaining sections) that would justify a 4.

3 / 5

Completeness

It explicitly answers both questions with concrete trigger phrases: the what ("Create or update STRATEGY.md") and an explicit when ("Use when starting a product, adding a strategy doc, or changing direction or roadmap"), matching the top anchor's structure; the 4 anchor's condition ('when' could be more explicit) does not apply since three specific scenarios are named.

5 / 5

Trigger Term Quality

"Use when starting a product, adding a strategy doc, or changing direction or roadmap" provides good natural-phrase coverage across creation, update, and direction-change scenarios (plus the STRATEGY.md filename as an artifact trigger), but misses common synonyms such as "product strategy", "vision", or "mission", so it falls short of the comprehensive-synonym 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The named artifact and "adding a strategy doc" trigger give it a clear niche, but "starting a product" and "roadmap" are phrases that ideation or planning skills could also claim, giving minor overlap risk with closely related skills; it is more distinct than the 3 anchor but not the minimal-conflict 5 anchor.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.