Name: apm-strategy
Rating: 65.60000000000001 (1 reviews)
Author: microsoft

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.

Quality

79%

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 ./.agents/skills/apm-strategy/SKILL.md

Quality

Content

80%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 body is an exceptionally concise, well-organized policy skill that assumes Claude's intelligence and gives concrete, specific directives. Its weakness is the absence of a sequenced workflow with an explicit validation checkpoint and a lack of runnable `gh` command examples.

Suggestions

Add a short sequenced workflow with an explicit validation checkpoint, e.g., '1. Gather `gh` evidence (stars, issues, PRs, releases). 2. Verify each claim cites a concrete artifact. 3. Only then approve or block.'

Include one or two copy-paste `gh` CLI commands (e.g., `gh issue list --state open --limit 20`) so actionability reaches 5.

Optionally show a minimal example CHANGELOG entry with its one-line migration note to make the breaking-change rule executable.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, never explaining what a README, CHANGELOG, or release workflow is. Every line carries a directive or a concrete file/rule, with no padding.	5 / 5
Actionability	Guidance is concrete and specific (ground claims in `gh` CLI evidence listing stars, issues, PRs, releases, traffic, contributors; every breaking change needs a CHANGELOG entry plus a one-line migration note). It is below 5 because no actual runnable `gh` commands or copy-paste examples are provided.	4 / 5
Workflow Clarity	'When to activate' and 'Key rules' are clearly grouped and unambiguous, but there is no sequenced multi-step workflow and no explicit validation checkpoint (e.g., confirm `gh` evidence exists before asserting a claim). The destructive/batch cap does not apply since this is a review/decision skill, so 3 rather than lower.	3 / 5
Progressive Disclosure	The skill is under 50 lines with no external bundle files, organized into clean 'When to activate' and 'Key rules' sections, and its one external link (the APM CEO persona) is a clearly signaled one-level-deep reference.	5 / 5
	Total	17 / 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.

The description is concise, specific, and clearly answers both what the skill does and when to activate it, with a well-scoped niche that minimizes conflict risk. Its main limitation is that triggers are listed as a flat set rather than elaborated into richer natural-language trigger phrases.

Suggestions

Add a few natural-language trigger phrasings (e.g., 'Use when reviewing a release CHANGELOG entry or drafting release notes') to lift completeness and trigger-term quality toward 5.

Optionally name the concrete actions the skill performs (e.g., 'Reviews, approves, and blocks...') so specificity is framed as actions rather than only activation contexts.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete trigger contexts (README, MANIFESTO, PRD, CHANGELOG, release workflows, issue templates, breaking-change decisions), with only minor coverage gaps. It falls short of 5 because the 'actions' are framed as activation triggers rather than the specific actions the skill performs.	4 / 5
Completeness	Explicitly answers both 'what' (activate for positioning, release communication, community artifacts, breaking-change decisions) and 'when' ('Triggers on README, MANIFESTO, PRD, CHANGELOG...'), satisfying the explicit-trigger-guidance requirement. It is below 5 because the trigger guidance is a single flat list rather than fully elaborated concrete trigger phrases.	4 / 5
Trigger Term Quality	Concrete artifact names users would naturally reference (README, MANIFESTO, PRD, CHANGELOG, issue templates) give good keyword coverage. It is below 5 because synonym/variation coverage is limited and there are no file extensions, though these matter less for a strategy skill.	4 / 5
Distinctiveness Conflict Risk	The niche is sharply defined (microsoft/apm strategic, release, and community-facing decisions) with distinct, named-file triggers and minimal overlap 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
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: microsoft/apm
Path: .agents/skills/apm-strategy/SKILL.md
Commit: 71a877c

Reviewed: ~1 hour 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.