CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

message-system-architect

Use when the user asks to "author our durable brand message hierarchy", "build the brand message house that seeds the canon", or "define the main narrative, three pillars, and tagline for the whole brand"; produces the DURABLE brand message system — main narrative, three value pillars, per-persona proof points (each labeled Measured / User-provided / '[needs source]'), and the tagline/one-liner — that seeds the narrative-registry canon and from which every per-launch house derives. Not for a single launch's message house or PR-FAQ — use message-house-builder; not for claim adjudication — use offer-claims-registry; not for the change-narrative arc itself — use strategic-narrative-designer. 品牌消息屋/主叙事/三支柱/标语/持久叙事 canon

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

73%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-sequenced, contract-driven workflow with strong validation checkpoints, feedback loops, and explicit write-authority boundaries, but it is noticeably repetitive (the authorized-proposal boilerplate appears five times) and defers all concrete output formats to external references. Tightening the repeated handoff rules and adding one worked example would lift both conciseness and actionability.

Suggestions

State the authorized proposal-path rule once in the Skill Contract and cross-reference it from steps 8-9 and Save Results, instead of repeating "via an authorized `operation: propose` request to `registry-events.py`" five times.

Add one compact worked example of the output — a mini message-house block showing the `canon_id`, version, hash, current-head, and `supersedes` binding — so the deliverable format is executable without opening external references.

Convert the long Scope Guard paragraph into a short bulleted exclusion list to remove the repeated "not X — use Y" sentence structures and reduce token cost.

DimensionReasoningScore

Conciseness

The body teaches no known concepts, but it is noticeably repetitive: "via an authorized `operation: propose` request to `registry-events.py`" appears five times (Writes, step 8, step 9, Save Results twice) and "[narrative-registry] is the sole writer" three times, and the intro/scope-guard both restate the reuse-vs-replace point. It fits anchor 3 (mostly efficient but could be tightened) rather than 4, where trimming would be minor; it is not 2 because there is no concept-explaining padding.

3 / 5

Actionability

Instructions carry concrete, executable specifics — exact paths (memory/narrative/message-system-architect/, memory/events/claims.ndjson), exact labels (Measured / User-provided / `[needs source]`), and explicit stop conditions ("stop with `NEEDS_INPUT`"). It is not 5 because every output format (handoff summary shape, propose-request structure, save template, banned-vocabulary list) is deferred to external files, so nothing is copy-paste ready from the body alone; it is not 3 because the steps themselves contain the key details needed to execute.

4 / 5

Workflow Clarity

Nine clearly sequenced steps with explicit validation checkpoints (input verification in step 1, canon re-version binding in step 2, banned-vocabulary and slop checks in step 6, internal-consistency pass in step 7, claims sweep in step 8) and error-recovery feedback loops ("An orphan pillar ... is a defect — cut it or send the gap back to positioning"; contradictions "resolved by sharpening the hierarchy"), plus a "Done when" checklist. It is not 4 because checkpoints are all present, not just most.

5 / 5

Progressive Disclosure

The body is a clear overview with a dedicated, annotated "Reference Materials" section of one-level-deep links, each with a one-line purpose note. It is not 5 because the skill ships no bundle of its own (no references/, scripts/, or assets/ exist here) and leans on ~11 cross-tree links that cannot be verified within this bundle, mixing detail files with cross-skill pointers; it is not 3 because structure and signaling are genuinely good, not buried.

4 / 5

Total

16

/

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: third-person voice, explicit "Use when" triggers with quoted natural phrases, a complete concrete inventory of outputs, and explicit negative boundaries that route the three most-confusable sibling skills away. No weaknesses surfaced against any anchor.

DimensionReasoningScore

Specificity

The description enumerates every concrete deliverable — "produces the DURABLE brand message system — main narrative, three value pillars, per-persona proof points (each labeled Measured / User-provided / '[needs source]'), and the tagline/one-liner" — which is comprehensive coverage of the skill's outputs, not a partial list. It is not 4 because there are no minor gaps: the full output inventory is explicitly named.

5 / 5

Completeness

Both halves are explicit: "Use when the user asks to..." gives concrete trigger phrases, and the "what" is the fully enumerated deliverable set (main narrative, three pillars, labeled proof points, tagline/one-liner) plus downstream role ("seeds the narrative-registry canon"). It is not 4 because the "when" is stated with quoted trigger phrases rather than being merely present or generic.

5 / 5

Trigger Term Quality

It quotes the exact natural phrases a user would say ("build the brand message house that seeds the canon", "define the main narrative, three pillars, and tagline for the whole brand") and covers synonyms (message house / message hierarchy, tagline / one-liner, three pillars / value pillars) plus bilingual terms (品牌消息屋/主叙事/三支柱/标语). It is not 4 because synonym coverage within this domain is comprehensive rather than missing a few natural terms.

5 / 5

Distinctiveness Conflict Risk

It explicitly disambiguates against the three most-confusable siblings — "Not for a single launch's message house or PR-FAQ — use message-house-builder; not for claim adjudication — use offer-claims-registry; not for the change-narrative arc itself — use strategic-narrative-designer" — carving a clear durable-brand-level niche. It is not 4 because conflict risk is actively minimized by the negative boundaries, not just reduced.

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

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

narrative/architect/message-system-architect/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.