CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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/价值支柱/发布叙事

Quality

90%

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.

A dense, contract-driven instruction skill with a genuinely validated workflow: explicit input gates, an evidence-labeling scheme, a self-check loop, and precise handoff requirements. The main improvement levers are consolidating the repeated sibling-skill routing and inlining (or bundling) the banned-vocabulary list and a small output example that the core steps depend on.

Suggestions

Consolidate sibling-skill routing: launch-asset-packager and offer-claims-registry each appear in the Scope guard, Skill Contract, Reference Materials, and Next Best Skill sections — state the exclusions once and link from there to save tokens.

Bundle or inline the Output Voice banned-vocabulary list (currently only in the external skill-contract.md) so steps 2 and 7 are self-contained, since the referenced path does not resolve within this skill's directory.

Add one compact worked example (e.g., a single pillar with a labeled proof point and a two-line PR-FAQ excerpt in launch-day tense) so the output format is unambiguous without reading external references.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no explaining what a message house or PR-FAQ is; "empty-chair test" is defined in a single parenthetical) and stays operational throughout. However, sibling-skill routing (launch-asset-packager, offer-claims-registry, content-writer) recurs across the Scope guard, Skill Contract, Reference Materials, and Next Best Skill sections, which could be consolidated — this is minor tightening, not the unnecessary explanation of anchor 3.

4 / 5

Actionability

Guidance is mostly executable: exact output structures ("three value pillars, each traceable to a canvas value theme", "five external FAQs... five internal FAQs"), exact paths and tools (memory/launch/message-house-builder/YYYY-MM-DD-<topic>.md, registry-events.py), and copy-paste Quick Start prompts. Minor gaps keep it below 5: no worked example of a finished pillar/tagline, and the banned-vocabulary list that steps 2 and 7 depend on lives in an external reference file rather than inline.

4 / 5

Workflow Clarity

The seven numbered steps are clearly sequenced (verify inputs → roof → pillars → PR-FAQ → angle packs → claims sweep → banned-word check) with explicit validation: a stop-gate in step 1 ("if canon is absent... request an explicit exploratory fallback or stop"), a pre-check in step 2, and a validate-and-fix feedback loop in step 7 ("scan... and rewrite every hit"), plus a "Done when" checklist and blocked dependency status for unresolved claims. This matches the explicit-validation-with-feedback-loops anchor.

5 / 5

Progressive Disclosure

The body is a well-sectioned overview with clearly signaled, one-level-deep, annotated references (each Reference Materials entry states what it is for). It sits at anchor 4 rather than 5 because the Reference Materials and Next Best Skill sections partially duplicate the same sibling-skill routing, and key operational content (banned word list, handoff format) is delegated to external files that are not part of this skill's bundle.

4 / 5

Total

17

/

20

Passed

Description

100%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 exemplary description: it pairs literal user trigger phrases with a fully specified output inventory and explicit negative routing to four sibling skills, all in third person without fluff. Its only weakness is length, but every clause carries information, so it is dense rather than padded.

DimensionReasoningScore

Specificity

The description enumerates concrete deliverables — "tagline, one-liner, three value pillars, per-persona proof points (each labeled Measured / User-provided / [needs source])", "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)" — with comprehensive coverage of the skill's outputs. It matches the multiple-specific-concrete-actions anchor; it is not score 4 because there are no meaningful coverage gaps.

5 / 5

Completeness

Both questions are answered explicitly: "Use when the user asks to..." gives concrete 'when' triggers, and the derivation clause specifies exactly 'what' is produced (house structure, PR-FAQ spine, angle packs, evidence labels). It clearly matches the both-explicit-with-trigger-phrases anchor rather than the weaker-'when' anchor at 4.

5 / 5

Trigger Term Quality

It quotes the natural phrases users would say verbatim ("build a message house", "write a PR-FAQ for our launch", "define the launch narrative and value pillars") and covers synonyms — message house, PR-FAQ, value pillars, tagline, launch narrative — plus Chinese equivalents (消息屋/PR-FAQ/价值支柱/发布叙事). This is comprehensive natural-term coverage, exceeding the good-coverage-with-a-few-missing anchor at 4.

5 / 5

Distinctiveness Conflict Risk

It carves out a clear niche — the messaging layer between positioning and asset production — and explicitly de-conflicts with four adjacent skills ("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...; not for claim adjudication — use offer-claims-registry"). Minimal conflict risk; not the minor-overlap anchor at 4.

5 / 5

Total

20

/

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

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

launch/assemble/message-house-builder/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.