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

71

Quality

88%

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

77%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 well-structured, actionable planning skill with clear sequencing and validation checkpoints. Its main weaknesses are repetition of the scope/delegation message and reliance on external reference paths that are not present as bundle files, leaving substantial detail inline.

Suggestions

State the scope/delegation boundary once (e.g., in the intro or the Scope guard block) and reference it from later sections instead of repeating it in steps 6–7 and Next Best Skill; collapse the "Quality bar" list into the "Done when" criteria to remove duplication.

Move the detailed seven-step Instructions (or the rate-card and growth-loop modeling specifics) into a reference file under references/ and link to it, so SKILL.md stays a lean overview and progressive disclosure becomes one-level-deep with retrievable detail.

Verify the referenced paths (skill-contract.md, CONNECTORS.md, SECURITY.md, sibling SKILL.md files) resolve from the skill's shipped location, or note that they belong to the parent collection, so the signposted references are not dead links in isolation.

DimensionReasoningScore

Conciseness

The scope/delegation message ("does not compute EQS / run D1 / return math") recurs across the intro, the "Scope guard" block, steps 6–7, and Next Best Skill, and the closing "Quality bar" re-lists the "Done when" criteria. It is mostly efficient domain guidance but carries noticeable repetition, so it sits at score 2 rather than the lean score-3 level.

2 / 3

Actionability

Concrete formulas ("active × free-to-paid % × price", "active subscribers × open rate = the per-send impression base"), explicit rate-basis choices (CPM / CPC-flat / flat-per-send), the Measured/User-provided/Estimated labeling rule, decision gates, and a specific save path give copy-applicable guidance. Per the scoring notes, the absence of code in this instruction-only skill is not penalized because the guidance is actionable.

3 / 3

Workflow Clarity

Seven numbered steps are followed by a "Decision gate" (NEEDS_INPUT vs Continue silently), a "Quality bar before handoff" checklist, and explicit "Done when" criteria — a clear sequence with explicit validation checkpoints and feedback for D1/S2 flags. It is above score 2 because the checkpoints are explicit rather than implicit.

3 / 3

Progressive Disclosure

References (skill-contract.md, send-benchmark.md, CONNECTORS.md, SECURITY.md, sibling skills) are clearly signaled and one-level-deep, but no bundle files exist in references/scripts/assets and none of the referenced paths resolve in this context, while the seven-step Instructions carry heavy inline detail. Structure is present but core detail is not offloaded to retrievable files, so it lands at score 2 rather than 3.

2 / 3

Total

10

/

12

Passed

Description

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

A strong, third-person description that names concrete actions, supplies natural trigger phrasings, answers both what and when, and explicitly disambiguates from sibling skills. The trailing Chinese summary tag is slightly redundant but does not weaken the trigger clarity.

DimensionReasoningScore

Specificity

"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" lists multiple concrete actions, matching the score-3 anchor.

3 / 3

Completeness

It explicitly answers what ("produces a revenue model...") and when ("Use when the user asks to..."), with explicit triggers, matching the score-3 anchor. It is above score 2 because the 'when' is explicit, not implied.

3 / 3

Trigger Term Quality

"Use when the user asks to 'monetize my newsletter', 'build a sponsorship rate card', or 'model paid-subscription revenue'" gives natural, quotable phrasings a user would actually say. It is not the score-2 level because common variations are well covered rather than partially.

3 / 3

Distinctiveness Conflict Risk

"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" carves a clear niche and disambiguates from siblings, so it is unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

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.