CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

launch-feedback-synthesizer

Use when the user asks to "triage launch feedback", "cluster reviews, comments, and board posts into themes", or "set up a you asked, we shipped loop"; produces a feedback theme digest (frequency, severity, representative quotes per theme), an open→planned→started→completed/declined status loop with duplicate-merge and notification rules, shipped-change announcement material, and a compliant social-proof harvest protocol (never incentivized store reviews). Not for repurposing or amplifying the harvested proof — use content-amplifier; not for executing testimonial outreach threads — use outreach-manager. 反馈分诊/状态环/社证收割/评测合规

Quality

81%

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

67%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 with genuinely specific, actionable rules (status transitions, notification semantics, compliance matrix, harvest red lines) and a clear sequenced workflow with a done-when checklist. Its main weaknesses are repetition — the registry-propose phrasing and sibling-skill handoffs are restated several times — and the absence of any example output templates or error-recovery guidance.

Suggestions

State the registry-submission mechanism ('via an authorized operation: propose request to registry-events.py') once in the Skill Contract and reference it elsewhere as 'submit per the contract' — it currently appears three times, and each sibling-skill handoff link appears up to four times.

Add a minimal example of the theme digest entry and the review ask message (the two outputs users will judge the skill by) to lift actionability from described to copy-paste ready.

Add a short failure-handling note after step 2 (e.g., exports with mismatched windows or malformed formats: re-request, label frequencies Estimated, or exclude the surface) so the workflow has an explicit error-recovery checkpoint.

DimensionReasoningScore

Conciseness

The body is mostly efficient but visibly repetitious: 'via an authorized operation: propose request to registry-events.py' appears three times, the content-amplifier and outreach-manager handoff links each appear four times, and 'It works one lever and hands off' is stated twice in consecutive paragraphs (lines 18 and 20). This is more than the minor trims of the 4 anchor, though far from the concept-explaining padding of the 2 anchor.

3 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: a severity taxonomy ('blocks-usage / degrades / cosmetic'), precise rules ('Duplicates are merged with votes transferred, never closed'; 'notifies all subscribers of the item minus the actor... an edit that does not change status sends nothing'), and a specified compliance-matrix shape ('platform → incentive allowed? → disclosure required?'). It falls short of the 5 anchor because no example theme digest, changelog entry, or review-ask message is shown — outputs are described, not templated.

4 / 5

Workflow Clarity

The eight numbered steps are clearly sequenced (inventory surfaces → pull exports → cluster → spec loop → build shipped-loop → spec harvest → route roadmap themes → metrics/snapshot) and the 'Done when' contract provides an explicit completion checklist with gated writes ('ask before writing'). It is not the 5 anchor because there is no error-recovery guidance — e.g., what to do with malformed exports or non-comparable feedback windows after step 2 records them.

4 / 5

Progressive Disclosure

Sections are well organized (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials) and every reference is a clearly signaled, one-level-deep markdown link; no bundle files exist to inline. It stops short of the 5 anchor because content that plausibly belongs in a reference file — the long scope-guard paragraph and the repeatedly inlined handoff rules — is kept in SKILL.md.

4 / 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: explicit what-and-when with concrete trigger phrases, specific deliverables, and explicit routing boundaries to sibling skills. The only weakness is mild verbosity — the trailing duplicated Chinese keyword summary adds tokens without new information, and a few natural trigger synonyms are absent.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete deliverables — 'feedback theme digest (frequency, severity, representative quotes per theme)', 'open→planned→started→completed/declined status loop with duplicate-merge and notification rules', 'shipped-change announcement material', and 'compliant social-proof harvest protocol (never incentivized store reviews)' — with no vague filler. This matches the comprehensive-coverage anchor; the 4 anchor would require minor coverage gaps, and none are present.

5 / 5

Completeness

Both halves are explicit: an 'Use when the user asks to...' clause with concrete quoted trigger phrases, and a clear 'what' listing the four outputs. This is a direct match for the 5 anchor; the 4 anchor's weaker/'could be more explicit' when-clause does not apply.

5 / 5

Trigger Term Quality

Natural quoted triggers ('triage launch feedback', 'cluster reviews, comments, and board posts into themes', 'set up a you asked, we shipped loop') plus synonyms like reviews, testimonials, and social proof give good coverage. A few plausible user phrasings (e.g. 'summarize feedback', 'customer feedback themes', 'review collection') are missing, keeping it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The niche (launch-window feedback triage) is distinct and the description adds explicit negative boundaries — 'Not for repurposing or amplifying the harvested proof — use content-amplifier; not for executing testimonial outreach threads — use outreach-manager' — minimizing wrong-skill triggering. Clear match for the 5 anchor.

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: 3 missing, 3 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

launch/prove/launch-feedback-synthesizer/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.