CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/oss-growth/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-organized instruction-only skill that respects the token budget and structures its few references cleanly, but it tells Claude what each surface needs without showing an example to calibrate output.

Suggestions

Add one short exemplar per surface type (e.g., a sample one-line hook + runnable example + next step for a README quickstart) to lift actionability from directive to copy-paste ready.

Show a one-line example of annotating a specialist finding with a growth implication so the "side-channel" rule is concrete rather than abstract.

DimensionReasoningScore

Conciseness

The body is a lean set of short bullets with no padding and no explanation of concepts Claude already knows; every line carries operational guidance, matching the score-3 anchor.

3 / 3

Actionability

Directives are concrete ("one-line hook, a runnable example, and a clear next step", "never stage or commit anything under WIP"), but no exemplars (sample hook, sample release announcement) are given, so the guidance is actionable yet incomplete per the score-2 anchor.

2 / 3

Workflow Clarity

This is a simple, single-purpose guidance skill under 50 lines; the "When to activate" and "Key rules" sections are clear and well-organized with unambiguous directives and no risky/batch operations requiring validation, so the simple-skill exception applies.

3 / 3

Progressive Disclosure

Under 50 lines with no bundle files needed; two well-organized sections plus a single clearly-signaled one-level external reference (the persona link) — no nested references — satisfying the score-3 anchor for simple skills.

3 / 3

Total

11

/

12

Passed

Description

75%Weight 40%Scale 1-3

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 has explicit activation triggers and a distinctive, well-scoped niche, but describes surfaces as nouns rather than concrete actions and blends natural terms with growth-hacker jargon.

Suggestions

Lead with concrete action verbs (e.g., "Convert READMEs, write quickstarts and release announcements, sharpen the contributor funnel") so capabilities read as actions, not just areas.

Pair jargon ("conversion surfaces", "contributor funnel") with plain-language equivalents a general user might say ("onboarding", "getting new contributors") to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ("OSS adoption work") and concrete surfaces ("README conversion surfaces, quickstart, templates, release announcements, contributor funnel, story angles"), but these are nouns/areas rather than explicit actions like the score-3 anchor's "extract... fill... merge"; not comprehensive on verbs.

2 / 3

Completeness

Provides explicit trigger guidance ("Activate for...") so it is not capped at 2, and addresses both what ("OSS adoption work") and when (the enumerated surfaces plus "any update to the maintained growth strategy at WIP/growth-strategy.md").

3 / 3

Trigger Term Quality

Includes natural terms users would say ("README", "quickstart", "templates", "release announcements"), but mixes in growth-hacker jargon ("conversion surfaces", "contributor funnel", "story angles") and lacks common plain-language variations, matching the score-2 anchor.

2 / 3

Distinctiveness Conflict Risk

A clear niche tied to a specific repo artifact ("WIP/growth-strategy.md") and a side-channel/CEO-escalation frame, with triggers unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

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.