CtrlK
BlogDocsLog inGet started
Tessl Logo

newsletter-monetization-planner

Use when the user asks to "monetize my newsletter", "build a sponsorship rate card", or "model paid-subscription revenue"; produces a revenue model (paid tiers, ad/sponsorship inventory + CPM/flat rate card, referral/boost loops), a list-growth ↔ revenue projection, and honest-offer / disclosure checks for the SEND-D lever. Not for scoring the whole program or running D1 — use email-quality-auditor; not for the return math — use roi-calculator; not for the post-click page — use landing-optimizer. 邮件newsletter变现/赞助刊例/付费订阅测算

68

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 a well-sequenced, actionable planning skill with strong validation checkpoints and clear handoff routing. Conciseness dips slightly from restated scope boundaries, and progressive disclosure is solid though it relies on external references with no local bundle to verify.

DimensionReasoningScore

Conciseness

The body is largely efficient with tight contract/read/write/done-when structure and minimal concept re-explanation, though sections like Data Sources and the repeated scope-guard/handoff language restate boundaries already covered in the description and intro.

4 / 5

Actionability

Concrete executable guidance abounds — explicit formulas ('active × free-to-paid % × price', 'CPM price per 1,000 opens'), labeled Measured/Estimated tagging rules, and exact save paths — with only minor gaps like missing worked numeric examples in the quick start.

4 / 5

Workflow Clarity

The 7-step Instructions sequence is clearly ordered with explicit checkpoints: a NEEDS_INPUT decision gate, a 'Done when' completion checklist, a Quality bar verification before handoff, and a termination/visited-set rule for the routing chain.

5 / 5

Progressive Disclosure

Well-organized sections with one-level-deep sibling/reference links and clear navigation; no bundle files exist alongside the skill, so cross-references like send-benchmark.md and skill-contract.md live outside this directory, keeping the SKILL.md a proper overview with minor signaling gaps.

4 / 5

Total

17

/

20

Passed

Description

88%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 concrete, trigger-rich, and explicitly bounds both its scope and its handoffs, making it highly specific and unlikely to fire for the wrong skill. Trigger term coverage is strong but slightly shy of comprehensive synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across three revenue lines — 'paid tiers', 'ad/sponsorship inventory + CPM/flat rate card', 'referral/boost loops', 'list-growth ↔ revenue projection', and 'honest-offer / disclosure checks' — with comprehensive coverage of the skill's outputs.

5 / 5

Completeness

Explicitly answers both 'what' (revenue model, rate card, growth projection, disclosure checks) and 'when' ('Use when the user asks to...'), plus negative boundary guidance on when not to use it and which sibling skill to use instead.

5 / 5

Trigger Term Quality

Includes natural user phrases like 'monetize my newsletter', 'build a sponsorship rate card', and 'model paid-subscription revenue', though it is missing a few common synonyms such as 'sponsor pricing' or 'paid newsletter tiers'.

4 / 5

Distinctiveness Conflict Risk

A clear owned-audience monetization niche with explicit carve-outs (not email-quality-auditor, not roi-calculator, not landing-optimizer) that minimize overlap with sibling skills.

5 / 5

Total

19

/

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 32 suspicious

Warning

Total

13

/

16

Passed

Repository
aaron-he-zhu/aaron-marketing-skills
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.