CtrlK
BlogDocsLog inGet started
Tessl Logo

apm-strategy

Activate for changes to project positioning, release communication, community-facing artifacts, or breaking-change decisions in microsoft/apm. Triggers on README, MANIFESTO, PRD, CHANGELOG, release workflows, and issue templates.

68

Quality

82%

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

86%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 tight, well-structured review skill that delivers concrete policy guidance with excellent token efficiency and clear navigation. Adding example gh commands and an explicit verification step for grounding claims would round out actionability and workflow clarity.

Suggestions

Add 1-2 example gh commands (e.g., 'gh issue list --state open' or 'gh release list') to make the 'ground every claim in gh CLI evidence' rule directly executable.

Include a brief verification checkpoint, such as confirming each strategic claim cites a gh evidence item before signing off, to support the arbiter role.

DimensionReasoningScore

Conciseness

Lean bullet lists with no padding and no explanation of concepts Claude already knows; every line carries actionable guidance and assumes Claude's competence.

5 / 5

Actionability

Concrete, specific policy guidance (named files, named reviewers, 'ground every claim in gh CLI evidence', 'one-line migration note'); it is instruction-only so code is not required, but example gh commands would make the evidence-gathering step fully executable.

4 / 5

Workflow Clarity

Clearly organized into 'When to activate' and 'Key rules' with a single, unambiguous purpose; it lacks explicit validation checkpoints for its consequential review/arbiter role, which keeps it just below a 5 but above the destructive/batch cap of 3.

4 / 5

Progressive Disclosure

Under 50 lines, well-organized into clear sections, with one well-signaled one-level-deep reference (the APM CEO persona link); meets the simple-skill exception for top marks.

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 focused, well-scoped description that pairs explicit activation triggers with concrete artifact names and a clear repository niche. The main gap is that the skill's actual capability ('what it does once activated') is only weakly implied relative to its strong 'when' guidance.

Suggestions

Add a brief 'what it does' clause (e.g., 'Reviews and enforces positioning/release policy for microsoft/apm') so the capability is as explicit as the trigger guidance.

Include common synonyms a user might say ('release notes', 'contributing guide', 'deprecation') to broaden natural-term coverage.

DimensionReasoningScore

Specificity

Names concrete trigger domains ('project positioning, release communication, community-facing artifacts, breaking-change decisions') and specific artifacts (README, MANIFESTO, PRD, CHANGELOG, release workflows, issue templates); it enumerates targets rather than distinct capability actions, so it sits just below a comprehensive 5.

4 / 5

Completeness

Both 'what' (strategy/release-positioning decisions) and 'when' are present, with explicit trigger guidance via 'Activate for' and 'Triggers on'; the 'when' is concrete while the 'what' is only moderately explicit, keeping it just below a 5.

4 / 5

Trigger Term Quality

Includes natural terms a user or reviewer would say ('README', 'MANIFESTO', 'PRD', 'CHANGELOG', 'release workflows', 'issue templates', 'breaking-change') with good coverage, though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Scoped to microsoft/apm with distinctive artifacts (MANIFESTO, PRD, APPROACH), giving it a clear niche with minimal conflict risk against other skills.

5 / 5

Total

17

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
microsoft/apm
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.