CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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变现/赞助刊例/付费订阅测算

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

70%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, highly actionable planning workflow with explicit validation gates and feedback loops. Its weaknesses are duplicated passages (scope guard vs. intro; quality bar vs. done-when) and a progressive-disclosure structure that depends entirely on external files not present in the bundle.

Suggestions

Deduplicate the workflow text: fold the 'Scope guard' paragraph into the intro (they repeat the same three handoff boundaries), and merge the 'Quality bar' list into the 'Done when' list instead of restating the same four checks twice.

Ship the essential referenced content in the bundle or inline the critical templates: the handoff-summary and Save Results formats live in skill-contract.md, which is not part of the bundle, so the skill cannot stand alone as provided.

Add one small worked example of the output artifacts (e.g. a two-row rate-card table with a labeled fill-rate assumption, or one projection milestone row) to close the actionability gap and make the Measured/User-provided/Estimated labeling concrete.

DimensionReasoningScore

Conciseness

Mostly dense and efficient, but there is real duplication: the intro paragraph and the "Scope guard" paragraph both state the same three delegation boundaries (email-quality-auditor for EQS/D1, roi-calculator for return math, landing-optimizer for the post-click page), and the four "Done when" items are restated nearly verbatim as the four "Quality bar" items. This fits 'mostly efficient but could be tightened' rather than 4, where only minor trims would be needed.

3 / 5

Actionability

Concrete, executable guidance throughout for an instruction-only skill: exact formulas ("active × free-to-paid % × price", "active subscribers × open rate = the per-send impression base"), explicit rate-basis choices ("CPM … CPC/flat by click, or flat per send"), named projection milestones ("current list, +25%, +50%"), a concrete save path, and the `[needs source]` convention. Not a 5 because there is no worked example of the output artifacts (e.g. a sample rate-card table or projection layout), leaving minor gaps.

4 / 5

Workflow Clarity

A clearly sequenced 7-step instruction list with an explicit decision gate ("Stop and ask (NEEDS_INPUT) — when none of list size, open rate, or a price/revenue target is provided") and a validation feedback loop ("If any item fails, fix it or report it in the handoff — do not ship silently") plus checklists. This matches the anchor: explicit validation steps, error-recovery loops, and checklists for a complex process.

5 / 5

Progressive Disclosure

Section structure is good and references are clearly annotated (Reference Materials lists each file with its purpose), but the bundle contains no files at all — every referenced path ([skill-contract.md](../../../references/skill-contract.md), [CONNECTORS.md](../../../CONNECTORS.md), [SECURITY.md], [state-model.md], seven sibling SKILL.md links) points outside the skill directory and none can be verified as present. The disclosure architecture rests entirely on unshipped files, which is more than the 'minor organization gaps' of a 4.

3 / 5

Total

15

/

20

Passed

Description

92%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 description: concrete capabilities, explicit quoted triggers, and unusually good negative-boundary disambiguation against sibling skills. The only weakness is slightly incomplete synonym coverage for trigger terms and a redundant trailing duplicate summary line.

DimensionReasoningScore

Specificity

The description lists multiple concrete deliverables — "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" — matching the comprehensive-coverage anchor. It is not a 4 because there are no meaningful gaps: each revenue line and each output artifact is named with its sub-components.

5 / 5

Completeness

It explicitly answers both questions with concrete trigger phrases: what ("produces a revenue model … a list-growth ↔ revenue projection, and honest-offer / disclosure checks for the SEND-D lever") and when ("Use when the user asks to 'monetize my newsletter'…"), matching the anchor-5 example pattern. Not a 4 because the 'when' is fully explicit with quoted trigger phrases rather than merely serviceable.

5 / 5

Trigger Term Quality

Trigger phrases are natural user phrasings — '"monetize my newsletter", "build a sponsorship rate card", "model paid-subscription revenue"" — giving good keyword coverage. It falls short of 5 because common variations users would say (e.g. "newsletter pricing", "how much to charge sponsors", "sponsor rates", "paid newsletter tiers") are not covered, and the trailing CJK summary duplicates tokens without adding new triggers.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche and actively disambiguates siblings: "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." This is stronger than the 4 anchor's 'minor overlap risk' — the negative boundaries make wrong-skill triggering unlikely.

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.

Validation — 13 / 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

Path

email/nurture/newsletter-monetization-planner/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.