CtrlK
BlogDocsLog inGet started
Tessl Logo

pricing-packaging-planner

Use when the user asks to "plan launch pricing", "design pricing tiers / packaging", or "set up a launch discount / early-bird offer"; produces a launch pricing and packaging plan — tier structure and naming, a value-to-price map aligned to the message house, a launch-offer ladder with a true deadline reason, beta / early-adopter pricing with a post-launch graduation path, and guarantee / refund terms — with every price claim and offer term submitted to memory/events/claims.ndjson. Not for the canonical offer / claim record — use offer-claims-registry; not for paid-newsletter subscription economics — use newsletter-monetization-planner; not for ad bidding — use bid-strategy-planner. 发布定价/梯度打包/早鸟优惠/保证设计

72

Quality

92%

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

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 well-structured, actionable instruction skill with a clear sequenced workflow and clean progressive disclosure through signaled references. Its main weakness is repetition — the claim-submission protocol phrase and scope-guard exclusions are restated multiple times, which pads the token budget.

Suggestions

Define the claim-submission protocol ('via an authorized operation: propose request to registry-events.py to memory/events/claims.ndjson') once in a short 'Claim submission' subsection and reference it from steps 4–6 and Save Results, instead of repeating the full phrase verbatim five times.

Consolidate the 'not for X — use Y' exclusion list into the single Scope guard section; the intro, Skill Contract, and Reference Materials each restate overlapping exclusions that can be pointed to once.

Remove the duplicated trailing Chinese summary string from the description field since it already appears in the summary field, eliminating redundant tokens in a frequently-loaded field.

DimensionReasoningScore

Conciseness

Mostly information-dense and earns its place, but the phrase 'via an authorized operation: propose request to registry-events.py' repeats verbatim across steps 4, 5, 6 and Save Results, and the scope-guard / 'not for X — use Y' exclusions recur in the intro, the Scope guard section, and Reference Materials — tightening would remove padding.

2 / 3

Actionability

Concrete guidance throughout — tier heuristics at 'roughly 1x / 2.2x / 5x', the 'DIY / Done-With-You / Done-For-You' naming pattern, named destinations (memory/launch/pricing-packaging-planner/, memory/events/claims.ndjson), and explicit validation rules; for an instruction-only skill this is actionable without code.

3 / 3

Workflow Clarity

An 8-step numbered Instructions sequence with explicit checkpoints ('Validate either heuristic against the user's actual cost and value structure', 'Flag any pillar with no home', 'Label every number') plus a 'Done when' completion checklist gives a clear, validated flow.

3 / 3

Progressive Disclosure

Well-organized sections (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) with clearly signaled one-level-deep links to sibling skills and reference docs; no local bundle directories exist, so references are the disclosure mechanism and they are cleanly labeled.

3 / 3

Total

11

/

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 states concrete capabilities, gives natural 'Use when…' triggers, and disambiguates from three sibling skills via explicit exclusions. The only blemish is the trailing duplicated Chinese summary string that also appears in the summary field.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'tier structure and naming, a value-to-price map aligned to the message house, a launch-offer ladder with a true deadline reason, beta / early-adopter pricing with a post-launch graduation path, and guarantee / refund terms' — rather than vague language.

3 / 3

Completeness

Explicitly answers both: 'Use when the user asks to…' (when) and 'produces a launch pricing and packaging plan' (what), satisfying the what-and-when requirement with explicit triggers.

3 / 3

Trigger Term Quality

Quotes natural phrasings a user would actually say — 'plan launch pricing', 'design pricing tiers / packaging', 'set up a launch discount / early-bird offer' — with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche and explicitly excludes adjacent skills ('Not for the canonical offer / claim record — use offer-claims-registry; not for paid-newsletter… use newsletter-monetization-planner; not for ad bidding — use bid-strategy-planner'), making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

Passed

Validation

75%

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

Validation12 / 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: 27 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

12

/

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.