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

73%

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

Quality

Content

76%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 policy skill that respects token budget and gives concrete directives, supported by clearly signaled one-level references. Its gaps are the absence of a sequenced workflow with validation checkpoints and the lack of concrete artifact examples (a sample hook or template).

Suggestions

Add a short worked example of a conversion surface (one-line hook + runnable example + next step) so the central rule is immediately actionable.

Provide a lightweight sequenced workflow for a typical growth task (e.g., review change -> identify affected surfaces -> apply hook/example/next-step pattern -> annotate and escalate) with a verification/escalation checkpoint.

Clarify or relocate the persona reference (the ../../../.apm/agents/... path resolves outside the skill bundle); consider bundling a short persona summary inline or under references/ so the skill is self-contained.

Dimension	Reasoning	Score
Conciseness	The body is lean and operational with no padding or explanation of concepts Claude already knows; every line (the gitignored WIP rule, the hook/example/next-step requirement, the framing and escalation rules) earns its place, matching the 'lean and efficient; every token earns its place' anchor.	5 / 5
Actionability	Guidance is concrete and specific for an instruction-only skill ("one-line hook, a runnable example, and a clear next step", "Never stage or commit anything under WIP/", "annotate them with growth implications and escalate to the CEO"), but it states requirements rather than giving an example hook/template, leaving minor gaps versus fully copy-paste-ready direction.	4 / 5
Workflow Clarity	Structure exists ("When to activate" trigger list plus "Key rules" policies) but there is no sequenced multi-step workflow or validation checkpoint; the skill spans several surfaces rather than a single unambiguous action, so it does not reach the clear-sequence-with-checkpoints anchors.	3 / 5
Progressive Disclosure	The body is a concise overview with well-signaled one-level-deep references (the persona link and the WIP/growth-strategy.md source of truth) and clean sectioning, fitting the 'good structure; references mostly clear' anchor; the persona reference is a deep relative path with no bundle file present and the strategy file is gitignored/may-not-exist, leaving minor organization gaps versus the top anchor.	4 / 5
	Total	16 / 20 Passed

Description

70%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, trigger-rich description for a narrow OSS-growth niche that clearly signals when to activate and stays free of fluff. Its main weakness is enumerating surfaces rather than concrete actions, and the 'when' could be a more explicit 'Use when...' clause.

Suggestions

Lead with concrete verbs (e.g., 'Convert READMEs, draft release announcements and quickstarts, shape starter templates') instead of listing surface nouns after 'Activate for'.

Add an explicit 'Use when ...' clause naming the most common user phrasings (README rewrite, launch post, contributor onboarding) to lift completeness and trigger quality.

Include a synonym or two for internal jargon (e.g., 'contributor funnel / onboarding', 'story angles / messaging hooks') so natural user terms map more directly.

Dimension	Reasoning	Score
Specificity	Names the OSS-growth domain and enumerates concrete 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/areas rather than concrete actions, matching the 'names domain and 1-2 concrete actions' anchor and falling below the 'several specific actions' level.	3 / 5
Completeness	It states what (OSS adoption work across the listed surfaces) and gives explicit trigger guidance via "Activate for ... and any update to the maintained growth strategy at WIP/growth-strategy.md", satisfying the 'has both what and when' anchor; the 'when' is explicit but phrased as 'Activate for' rather than a crisp 'Use when...' with concrete trigger phrases, keeping it just below the top anchor.	4 / 5
Trigger Term Quality	Good natural-term coverage with "README", "quickstart", "templates", and "release announcements" that users would actually say, plus a file path trigger; some terms ("conversion surfaces", "contributor funnel", "story angles") lean internal and synonyms/extensions are sparse, so it sits at 'good coverage, a few natural terms missing' rather than the comprehensive level.	4 / 5
Distinctiveness Conflict Risk	The niche is specific (OSS adoption/growth tied to a named persona and a WIP/growth-strategy.md source of truth) with distinct triggers, so it is mostly distinct with only minor overlap against general docs/marketing skills; it lacks the razor-sharp single-format focus of the top anchor.	4 / 5
	Total	15 / 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/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.