CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

message-test-designer

Use when the user asks to "test our messaging before we scale it", "design a message-market-fit panel", or "run a 5-second comprehension test on our new tagline"; produces a message-test design spec — hypothesis, panel and recruit criteria, comprehension / 5-second / message-market-fit (Wynter-style) protocols, stimulus set drawn from the canon, success thresholds, and a stop/revise decision rule — for the TALE Evaluate phase so the message is validated before any paid scale. It designs the test; it never runs the experiment or adjudicates a claim. Not for running the panel or A/B experiment — use send-experiment-designer or ad-test-designer; not for analyzing the results — use performance-analyzer; not for authoring the message itself — use message-system-architect. 消息测试/理解度测试/面板设计/五秒测试/消息市场契合

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 delivers an exceptionally clear, gated 8-step design workflow with concrete examples, exact paths, and an executable significance command, backed by a real one-level-deep reference file for the binding schema. Its weakness is token efficiency: scope guardrails and sibling routing are restated four to six times each, and the body carries contract detail that belongs in the reference file. Tightening the repetition would bring this to top-tier without losing clarity.

Suggestions

State the out-of-scope routing once (in the Scope guard) and remove its repeats from Data Sources, step 7, and Reference Materials — the same four sibling handoffs currently appear six times.

Move the artifact-semantics rules from step 8 and the Skill Contract (measurement-contract vs evidence-observation distinctions, 'never call the message validated') into references/stimulus-binding.md, keeping one summary sentence plus the link in the body.

Consolidate the 10-item Reference Materials list with the Next Best Skill section so each sibling skill is linked exactly once instead of appearing in both.

DimensionReasoningScore

Conciseness

No concept-teaching padding and every sentence carries information, but the same guardrails are repeated many times — the execution/analysis/authoring handoff routing appears in the intro, Scope guard, Data Sources, step 7, Reference Materials, and Next Best Skill, and "never call the message validated without a matching observation" appears three times. This is 'mostly efficient but could be tightened' rather than the minor-trim level of 4.

3 / 5

Actionability

For an instruction-only skill the guidance is fully actionable: three copy-paste Quick Start invocations, a concrete example hypothesis with a numeric bar ("≥70% of the target panel correctly restate the core benefit unaided after 5 seconds"), a concrete panel-size heuristic labeled Estimated, exact save paths (memory/narrative/message-test-designer/YYYY-MM-DD-<topic>.md), and an executable keyless command ("python3 \"${CLAUDE_PLUGIN_ROOT}/scripts/connectors/experiment.py\" proportion --control <pref_A> <n> --variant <pref_B> <n>"). Specific examples cover the common cases (tagline, hero headline, three positioning statements).

5 / 5

Workflow Clarity

Eight steps are clearly sequenced with explicit validation gates and feedback loops: step 1 stops with NEEDS_INPUT and routes away if no candidate message exists, step 5 scans every claim and tags unapproved ones [needs source], step 6 defines automatic failure routing (a failed test routes back to message-system-architect, not more spend), and the Skill Contract's 'Done when' clause acts as a final checklist. This is a design-and-handoff skill, so no destructive/batch cap applies.

5 / 5

Progressive Disclosure

Good structure: the body is a sectioned overview, and the one real bundle reference (references/stimulus-binding.md — verified to exist) holds the detailed binding schema, well-signaled in step 5, the 'Done when' clause, and a Reference Materials entry with a one-line description. It falls short of 5 because the body is denser than a pure overview (contract semantics and artifact-type rules in step 8 could partly live in the reference file) and ~10 relative links point outside the bundle to sibling skills and repo-level files, which is a minor navigation/organization gap.

4 / 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.

A strong description: concrete deliverables, verbatim natural-language triggers, explicit what/when, and positive routing to siblings for everything out of scope. The only gap is a few missing synonym trigger terms (copy/concept/value-proposition testing) that would push trigger coverage to the top anchor. Voice is correctly third person.

Suggestions

Add common synonym triggers such as "copy testing", "concept test", or "value proposition test" to the trigger phrase list so users phrasing the need those ways also land on this skill.

DimensionReasoningScore

Specificity

The description enumerates the full deliverable set concretely: "produces a message-test design spec — hypothesis, panel and recruit criteria, comprehension / 5-second / message-market-fit (Wynter-style) protocols, stimulus set drawn from the canon, success thresholds, and a stop/revise decision rule" — six-plus specific concrete outputs with comprehensive coverage, matching the top anchor rather than the 'minor gaps' level below.

5 / 5

Completeness

Both halves are explicit: 'what' is the enumerated test-design-spec deliverables and 'when' opens with literal "Use when the user asks to..." trigger phrases. This is a direct match for the anchor-5 example pattern ('Extract text and tables... Use when working with PDF files'); a 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

It quotes natural user phrasings verbatim ("test our messaging before we scale it", "run a 5-second comprehension test on our new tagline") plus bilingual keywords (消息测试/五秒测试/消息市场契合), giving good coverage. It falls short of the top anchor because common synonyms like "copy test", "concept test", or "value proposition test" are absent — 'a few natural terms missing' fits the 4 anchor.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche and explicitly de-conflicts four sibling skills ("Not for running the panel or A/B experiment — use send-experiment-designer or ad-test-designer; not for analyzing the results — use performance-analyzer; not for authoring the message itself — use message-system-architect"), giving minimal conflict risk; nothing generic remains that would trigger the wrong skill.

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

narrative/evaluate/message-test-designer/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.