CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

acquisition-channel-advisor

Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/acquisition-channel-advisor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

Highly actionable and well-sequenced content with concrete formulas, thresholds, and templates, but it is notably verbose—re-explaining standard SaaS metrics and padding with redundant pitfalls—and inlines material that would benefit from being split into reference files.

Suggestions

Trim or remove definitions of standard SaaS metrics (CAC, LTV, payback, magic number, NRR) that Claude already knows; keep only the channel-specific thresholds and decision rules.

Collapse the 10 Common Pitfalls and the Anti-Patterns section into a short list, since they largely restate the decision matrix and recommendation guidance.

Move the four full recommendation-pattern templates and worked examples into separate reference files under references/ to reduce SKILL.md to a lean overview with one-level-deep pointers.

DimensionReasoningScore

Conciseness

The ~640-line body noticeably over-explains well-known SaaS concepts (CAC, LTV, payback, magic number, NRR) and pads with 10 redundant pitfall entries and repeated framework restatements across Key Concepts, Application steps, and recommendation patterns.

2 / 5

Actionability

Provides fully executable guidance: explicit formulas ('CAC = Monthly Spend / Customers Acquired per Month'), a threshold-based decision matrix, ✅/⚠️/🚨 flagging rules, and four copy-paste recommendation templates with worked numeric examples.

5 / 5

Workflow Clarity

Clear sequenced Steps 0-5 with per-step flagging checkpoints and a timeline-based feedback loop in the optimize pattern, though the main workflow uses assessment flags rather than explicit verify-and-retry validation checkpoints.

4 / 5

Progressive Disclosure

Section headers give some structure, but the bulk of templates, ten pitfalls, and examples are inlined into one large file, and the referenced 'examples/' folder is not present in the bundle.

3 / 5

Total

14

/

20

Passed

Description

87%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 strong, third-person description that clearly states both capability and trigger conditions with concrete, natural language. The main limitation is slightly conceptual rather than granular action wording and a few missing channel-type synonyms.

DimensionReasoningScore

Specificity

Names the domain ('Evaluate acquisition channels') and three concrete analytical dimensions ('unit economics, customer quality, and scalability'), listing several specific actions with only minor granularity gaps versus the fully comprehensive anchor.

4 / 5

Completeness

Explicitly answers both what ('Evaluate acquisition channels using unit economics, customer quality, and scalability') and when ('Use when deciding whether to scale, test, or kill a growth channel') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural PM phrases ('scale, test, or kill a growth channel', 'acquisition channels', 'growth channel') with good coverage, though a few synonyms like 'marketing channel' or 'paid channel' are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (financial evaluation of acquisition channels) with a distinct trigger ('scale, test, or kill a growth channel') and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (658 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

13

/

16

Passed

Repository

deanpeters/Product-Manager-Skills

Path

skills/acquisition-channel-advisor/SKILL.md

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.