CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

learn-my-brand

Learn my brand once and stop asking me every time. Use when someone says learn my brand, set up my brand, here's our brand book, remember how we talk, what can we claim, can we say this, approve our claims, sign off our voice, our price or product changed, the client approved the claims, pick up where we left off, or check our claims are still current. Reads what GooseWorks already found about the brand, asks only the gaps as drafts to confirm, audits every claim (including ones research marked approved) and gets the ones that matter signed off with proof, scope and review date, turns the voice into rules the owner confirms, checks logo, colours and fonts, and saves it all as it goes so every other job loads it instead of asking. Ends with an unknowns list and a read-back. Not for who our customers are and what they say (use research-audience) or writing positioning from scratch (not covered yet).

Quality

96%

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

96%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.

An exceptionally dense, fully operational playbook: exact tool calls, gated approvals with explicit sign-off rules, save checkpoints, and a verify-from-fresh-read feedback loop. The only structural weakness is bundle navigation — one orphaned template file and several referenced paths that do not resolve in the bundle as provided.

Suggestions

Link references/brand-record-template.md from the record-output section (or step 7) — the template exists in references/ but is never referenced, leaving the record's structure described inline instead of pointing to the file.

Ship the referenced atoms/ sub-playbooks (claims-audit, voice-calibrate, brain-write-back) and tests/test-by-hand.md inside the skill bundle, or state where they live — as provided, those paths do not resolve.

The ../../../skills/marketing/* paths assume a fixed workspace layout; a one-line note on where these sibling skills live would make the skill's navigation self-contained.

DimensionReasoningScore

Conciseness

No concept explanations or padding; every line is operational detail Claude cannot know elsewhere — tool parameters ('brand_read sections: ["kit"], detail: "full"'), precedence order ('owner > owner's documents > owner's earlier rules > site > research'), triage budgets, and time-pressure fallbacks. Lean and efficient; every token earns its place.

5 / 5

Actionability

Fully concrete for an instruction-only skill: exact tool calls with parameters ('gooseworks:knowledge_import with url', 'brand_update patch.kit'), exact file paths ('brand/records/<YYYY-MM-DD>-v<N>.md, imported as a brand document'), a verbatim marker string to write, named sub-playbooks to run (atoms/claims-audit, atoms/brain-write-back), and copy-ready owner messages ('Connect GooseWorks first — I learn and save your brand through it.').

5 / 5

Workflow Clarity

Eight numbered steps with mode dispatch up front (full / resume / update / one claim / client sign-off back / sweep), save checkpoints after steps 3–5, and an explicit validation gate in step 8: 'Re-read fresh, not from this conversation … If a probe needs this conversation, fix the save', plus error handling ('Report anything that did not save'). Clear sequence with explicit validation steps and feedback loops for error recovery.

5 / 5

Progressive Disclosure

The body is a genuine overview pushing detail to one-level-deep, conditionally-loaded references ('if regulated, load references/category-rules.md') and all five referenced references/ files exist in the bundle. However, references/brand-record-template.md is present but never linked from the body (its content is re-described inline in 'Output and write-back'), and the referenced paths atoms/claims-audit, atoms/voice-calibrate, atoms/brain-write-back and tests/test-by-hand.md do not exist in the provided bundle — navigation gaps that keep this below the anchor-5 'easy navigation' bar.

4 / 5

Total

19

/

20

Passed

Description

95%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: explicit what and when, a dozen natural trigger phrases, and explicit scope exclusions that sharply delimit it from sibling skills. Its only rubric flaw is the first-person opening sentence, which breaks the required third-person voice and costs one specificity point.

Suggestions

Reword the opening in third person (e.g., "Learns the owner's brand once so no other job has to ask again") — 'Learn my brand once and stop asking me every time' reads as first person and cost a specificity point under the rubric's voice rule.

DimensionReasoningScore

Specificity

Names around six concrete actions ('audits every claim (including ones research marked approved) and gets the ones that matter signed off with proof, scope and review date', 'turns the voice into rules the owner confirms', 'checks logo, colours and fonts') — anchor-5 coverage. However, the first-person opener 'Learn my brand once and stop asking me every time' violates the third-person voice rule ('Learn my brand', 'stop asking me'), which the rubric penalizes by reducing specificity by 1.

4 / 5

Completeness

The 'what' is explicit (read existing research, ask only gaps, audit claims, confirm voice rules, check kit, save continuously) and the 'when' is an explicit 'Use when someone says …' clause with concrete trigger phrases, plus a 'Not for …' exclusion list. This matches the anchor-5 example pattern exactly.

5 / 5

Trigger Term Quality

Twelve natural user phrases — 'learn my brand', 'set up my brand', "here's our brand book", 'remember how we talk', 'what can we claim', 'can we say this', 'approve our claims', 'sign off our voice', 'our price or product changed', 'the client approved the claims', 'pick up where we left off', 'check our claims are still current' — exceed the anchor-5 example's synonym coverage; no common variation is missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche — owner sign-off of brand claims and voice within GooseWorks — with distinct triggers and explicit boundary guidance: 'Not for who our customers are and what they say (use research-audience) or writing positioning from scratch (not covered yet)'. This routes away sibling research skills, minimizing conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

gooseworks-ai/goose-skills

Path

drafts/marketing/learn-my-brand/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.