CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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. 发布定价/梯度打包/早鸟优惠/保证设计

Quality

86%

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

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

A well-structured instruction skill: lean sequencing, concrete heuristics with explicit provenance labels (Measured/Estimated), a defined output contract with done-when criteria, and clean one-level reference navigation. The main improvable spots are the repeated registry-routing clause and the absence of feedback loops for claim-submission outcomes.

Suggestions

State the registry routing rule once (e.g., a single line in the Skill Contract: 'all claim/term submissions go to memory/events/claims.ndjson via an authorized operation: propose request to registry-events.py') and reference it from steps 4–6 instead of repeating the full clause verbatim, saving ~15 lines.

Add a feedback loop to step 8: what to do when a registry proposal is rejected or returns a validation error (fix the term and re-propose, or surface the conflict to the user) before handoff.

Show one concrete claim-candidate record example (fields for claim text, type, source label, deadline rationale) so the registry-events.py submission step is executable without loading an external protocol file.

DimensionReasoningScore

Conciseness

The body is dense and instructional with no explanation of concepts Claude already knows, matching 'efficient; minor instances of over-explanation that could be trimmed'. The trimmable part is the identical routing clause 'via an authorized `operation: propose` request to `registry-events.py`' repeated verbatim ~6 times across the Skill Contract, Instructions, and Save Results sections — it could be stated once as a global rule. Not a 3 because everything else earns its tokens.

4 / 5

Actionability

The guidance is concretely executable for an instruction-only skill: specific heuristics ('3-tier ladder at roughly 1x / 2.2x / 5x', 'DIY / Done-With-You / Done-For-You'), exact paths ('memory/launch/pricing-packaging-planner/YYYY-MM-DD-<product-or-offer>.md'), and copy-paste Quick Start prompts. It stops short of 5 because the actual claim-submission payload format for `registry-events.py` is never shown and lives in files outside this bundle, leaving a gap in executing the core routing step.

4 / 5

Workflow Clarity

The 8 numbered steps are clearly sequenced with an explicit 'Done when' checklist and ask-before-write checkpoints, matching 'clear sequence with most checkpoints present'. It is not a 5 because there are no feedback loops — e.g., what to do if a registry proposal is rejected or a pillar cannot be mapped — and the pillar-mapping validation in step 3 is stated as a flag but not as an explicit verify-then-proceed gate.

4 / 5

Progressive Disclosure

The skill is a clear overview with well-signaled one-level-deep references: the Reference Materials section lists each cross-skill/protocol doc with a one-line description of what it provides, no reference points to another pointer file, and all process content is appropriately inlined. No bundle files exist in references/, scripts/, or assets/, so nothing is misplaced; this matches the anchor 'clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation'.

5 / 5

Total

17

/

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.

An excellent description: explicit trigger phrases, a comprehensively enumerated output contract, third-person voice, and explicit de-scoping against three sibling skills. The only weakness is a slightly incomplete set of natural trigger synonyms, and a trailing Chinese summary line ('发布定价/梯度打包/早鸟优惠/保证设计') that adds mild padding.

DimensionReasoningScore

Specificity

The description enumerates comprehensive concrete actions: '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' plus 'every price claim and offer term submitted to memory/events/claims.ndjson'. This matches the anchor 'lists multiple specific concrete actions; comprehensive coverage' and exceeds the score-4 anchor's 'minor gaps in coverage'.

5 / 5

Completeness

It 'clearly and explicitly answers both what AND when with concrete trigger phrases': the 'Use when the user asks to...' clause lists three concrete triggers, and the 'what' is a fully enumerated output plan. The 'when' is explicit with quoted phrases, matching the score-5 example pattern exactly.

5 / 5

Trigger Term Quality

Natural quoted triggers like "plan launch pricing", "design pricing tiers / packaging", and "set up a launch discount / early-bird offer" cover the main asks plus synonyms (early-bird, packaging), matching 'good keyword coverage; a few natural terms missing'. It falls short of the 5 anchor because common phrasings such as 'how much should we charge', 'price our product', or 'set our price points' are not covered.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (launch pricing/packaging) with distinct triggers and adds explicit negative boundaries — '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' — giving minimal conflict risk, which exceeds the 4 anchor's 'minor overlap risk'.

5 / 5

Total

19

/

20

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.

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

Path

launch/assemble/pricing-packaging-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.