CtrlK
BlogDocsLog inGet started
Tessl Logo

message-house-builder

Use when the user asks to "build a message house", "write a PR-FAQ for our launch", or "define the launch narrative and value pillars"; derives from the positioning canvas a message house — tagline, one-liner, three value pillars, per-persona proof points (each labeled Measured / User-provided / [needs source]) — plus a working-backwards PR-FAQ narrative spine (launch-day tense, empty-chair test, five external + five internal FAQs) and per-channel message angle packs (angles, not finished copy). Not for the positioning canvas itself — use positioning-mapper; not for finished blog posts or pages — use content-writer; not for ad or email units — use each discipline creative builder; not for claim adjudication — use offer-claims-registry. 消息屋/PR-FAQ/价值支柱/发布叙事

78

Quality

100%

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

100%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 instruction skill: a numbered workflow with validation gates, concrete per-step rules, and a clean Reference Materials section that routes depth to one-level-deep files. Minor redundancy between the scope guard and the banned-word steps (2 and 7) is the only tightening opportunity.

DimensionReasoningScore

Conciseness

The body is dense and purposeful — 'tagline and one-liner derived from the canvas value themes', 'the empty-chair test (would the named ICP reader care about each sentence?)' — assuming Claude's competence with no concept-tutorial padding; only mild redundancy between the scope guard and steps 2/7 keeps it from being perfectly lean.

3 / 3

Actionability

Gives concrete executable rules — 'Label every proof point Measured (own analytics/export), User-provided, or [needs source]', 'the press release in launch-day tense... numbers over adjectives', 'cite the official App Store Connect / Play Console docs and mark verify current' — instruction-only yet highly actionable.

3 / 3

Workflow Clarity

A clear 7-step sequence with explicit validation checkpoints and feedback loops: 'If canon is absent... request an explicit exploratory fallback or stop', 'Run both against the Output Voice banned-vocabulary list... before presenting', and a 'Done when' checklist — matching the validation-and-recovery anchor.

3 / 3

Progressive Disclosure

The body is a concise overview with well-signaled one-level-deep references (Reference Materials listing ramp-benchmark.md, skill-contract.md, and sibling skills with one-line purposes); no nested chains, and no bundle files are present requiring deeper structure.

3 / 3

Total

12

/

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 highly specific, well-triggered description that clearly delimits what the skill does and routes overlapping work to sibling skills via explicit negatives. It satisfies all four anchors at the top level without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'a message house — tagline, one-liner, three value pillars, per-persona proof points', 'a working-backwards PR-FAQ narrative spine', and 'per-channel message angle packs' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what (derives a message house, PR-FAQ spine, angle packs) and when ('Use when the user asks to...'), satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Opens with natural user phrasing — 'build a message house', 'write a PR-FAQ for our launch', 'define the launch narrative and value pillars' — terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

A clear niche reinforced by explicit negatives — 'Not for the positioning canvas itself... use positioning-mapper', 'not for finished blog posts... use content-writer', 'not for claim adjudication — use offer-claims-registry' — making mis-triggering unlikely.

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: 21 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.