oss-growth

Activate for OSS adoption work -- README conversion surfaces, quickstart, templates, release announcements, contributor funnel, story angles -- and any update to the maintained growth strategy at WIP/growth-strategy.md.

Quality

67%

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 ./.apm/skills/oss-growth/SKILL.md

Quality

Content

72%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 lean, well-structured, and gives concrete directives appropriate for an instruction-only persona skill, but it lacks an explicit activation workflow and worked examples that would make the guidance fully unambiguous.

Suggestions

Add a short explicit sequence: detect a conversion surface -> apply hook + runnable example + next step -> annotate growth implications -> escalate to the CEO.

Include one worked example (e.g., a sample README hero hook with a runnable command and next step) to make the 'every conversion surface' rule concrete.

Add a verification checkpoint such as confirming each touched surface has all three elements (hook, example, next step) before finishing.

Dimension	Reasoning	Score
Conciseness	The body is lean with well-scoped sections and no padding about concepts Claude already knows; the WIP/growth-strategy bullet is detailed but conveys repo-specific rules Claude could not infer, with only minor phrasing that could be trimmed, fitting 'efficient; minor instances that could be trimmed'.	4 / 5
Actionability	The rules give concrete, executable directives ('one-line hook, a runnable example, and a clear next step', 'Cut anything that dilutes it', 'annotate them with growth implications and escalate to the CEO'), but no worked examples of a hook or announcement copy are provided, leaving minor gaps.	4 / 5
Workflow Clarity	'When to activate' and 'Key rules' imply a decision flow (detect trigger, apply rules, annotate, escalate), but there is no explicit step sequence or validation checkpoint; the action bundle is somewhat ambiguous, so it sits at 'steps present but checkpoints implicit'.	3 / 5
Progressive Disclosure	The skill is under 50 lines, self-contained, and organized into clear 'When to activate' and 'Key rules' sections with a single one-level-deep, clearly-signaled reference (the persona link), meeting the simple-skill exception for a top score.	5 / 5
	Total	16 / 20 Passed

Description

62%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 carves out a clear, fairly distinctive niche and provides explicit activation guidance, but it lists surfaces rather than concrete actions and leans on specialized jargon over natural user phrasing.

Suggestions

Lead with concrete verbs instead of surface nouns, e.g. 'Rewrite README hero sections, draft quickstart examples, compose release announcements, and grow the contributor funnel.'

Add a 'Use when the user asks to improve a README, write release notes, or grow adoption' style phrase using language a user would actually say.

Include common synonyms (documentation, onboarding, launch posts) alongside the specialized terms to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('OSS adoption work') and lists several specific surfaces ('README conversion surfaces, quickstart, templates, release announcements, contributor funnel, story angles'), but the only verb is the generic 'Activate for' — the items are nouns/surfaces rather than concrete actions, matching the anchor that names the domain with minimal actions.	3 / 5
Completeness	It answers both 'what' (the listed conversion surfaces and the growth-strategy file) and 'when' ('Activate for OSS adoption work ... and any update to ... WIP/growth-strategy.md'), with explicit trigger guidance equivalent to 'Use when', so it is not capped at 3; the 'when' could be slightly more explicit, keeping it at 4 rather than 5.	4 / 5
Trigger Term Quality	Terms like 'README', 'quickstart', 'templates', and 'release announcements' are reasonably natural, but the phrasing ('Activate for OSS adoption work', 'contributor funnel', 'story angles') is persona-internal jargon rather than the phrases a user would naturally say, and common synonyms ('documentation', 'onboarding', 'marketing') are missing.	3 / 5
Distinctiveness Conflict Risk	The OSS-growth niche is clear and the anchor to 'WIP/growth-strategy.md' is distinctive, but 'README', 'quickstart', and 'templates' could overlap with a general documentation skill, so it is mostly distinct with minor overlap risk rather than minimal.	4 / 5
	Total	14 / 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: .apm/skills/oss-growth/SKILL.md
Commit: 71a877c

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