CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

brand-writer

Write clear, developer-first copy for Zed — leading with facts, grounded in craft.

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./.factory/skills/brand-writer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 skill body is a strong instruction-only skill: a well-sequenced two-pass writing workflow with real validation loops, concrete [FACT]-marker protocol, and useful good/bad/fixed examples. Its weaknesses are a broken reference layer (three named bundle files do not exist) and duplicated illustrative content that inflates token cost without adding guidance.

Suggestions

Create the referenced `rubric.md`, `taboo-phrases.md`, and `voice-examples.md` files (or remove the 'load reference files' steps and keep their content inline) — the workflow currently depends on files that are not in the bundle.

Trim duplication: the 'Performance you can feel' passage is repeated verbatim as the Good example, the Avoid list restates Tone guidance, and the Phase 5 scorecard example with fabricated scores can be reduced to a template skeleton.

Move the Phase 5 output-format table and Review Mode diagnosis templates into a reference file so SKILL.md stays a lean overview, improving both conciseness and progressive disclosure.

DimensionReasoningScore

Conciseness

Most sections earn their place (principles, avoid list, workflow, good/bad/fixed examples), but there is noticeable duplication and padding: the "Performance you can feel" passage appears verbatim in Core Messages and again as the Good example, the Avoid list repeats Tone guidance, and Phase 5 embeds a full fabricated scorecard ("37/40", checkmark lines) that is illustrative filler. This fits 'Mostly efficient but includes some unnecessary explanation or could be tightened' — too much real value for a 2, not lean enough for a 4.

3 / 5

Actionability

The guidance is largely executable for an instruction-only skill: exact invocation syntax, a concrete [FACT]-tagging protocol with a worked example, an inline 8-criterion rubric table, line-referenced taboo scanning, per-context output formats, and good/bad/fixed transformation examples. It falls short of 5 because two operational inputs — the taboo-phrase list and the transformation patterns — are delegated to `taboo-phrases.md` and `voice-examples.md`, which are not present in the bundle, leaving 'Scan for taboo phrases' backed only by the short inline Avoid list.

4 / 5

Workflow Clarity

The five-phase workflow is clearly sequenced with explicit validation checkpoints and a genuine feedback loop: Pass 2 scores the draft on all 8 rubric criteria, Pass 3 rewrites anything scoring <4 and re-scores, with 'Repeat until all criteria score 4+', plus a Litmus Test checklist and a final scorecard gate. This matches the top anchor 'Clear sequence with explicit validation steps; feedback loops for error recovery; checklists for complex processes'.

5 / 5

Progressive Disclosure

The body claims reference files are 'auto-loaded from the skill folder' (`rubric.md`, `taboo-phrases.md`, `voice-examples.md`) and directs the workflow to load them, but none of these files exist in the bundle — broken navigation that undermines the one-level-deep reference design. Structure within SKILL.md itself is reasonable (clear sections, criteria inlined), but a 280-line body that inlines rubric criteria, templates, and examples while pointing to missing files fits 'Some structure but could be better organized; references present but not clearly signaled... content that should be separate is inline'.

3 / 5

Total

15

/

20

Passed

Description

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

The description is short, cleanly written, and correctly third-person imperative, with a clear 'what' anchored to a distinctive niche (Zed brand copy). Its main weaknesses are the complete absence of a 'when to use' clause and thin action coverage — the skill actually supports drafting multiple content formats and a --review mode, none of which is surfaced.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing or reviewing Zed marketing copy — homepage text, release notes, docs intros, announcements — or when the user mentions Zed's brand voice or tone."

Enumerate the concrete actions the skill performs (draft copy per context, review existing copy with --review, score against an 8-criterion rubric) instead of the single generic action "write copy".

Include natural synonym triggers users would actually say — "brand voice", "tone", "marketing copy", "announcement" — to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ("copy for Zed") but offers only a single generic action — "Write clear, developer-first copy" — matching the anchor 'Names the domain but actions are minimal or generic' (cf. "Processes PDF files"). "leading with facts, grounded in craft" is brand flavor rather than an additional concrete action, so it does not reach the 1-2-action anchor at 3, while it is clearly above the entirely-vague anchor at 1.

2 / 5

Completeness

The 'what' is clear (write developer-first copy for Zed), but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3, which is exactly the anchor 'Has a clear what but when is missing or only weakly implied'.

3 / 5

Trigger Term Quality

Relevant keywords like "copy", "Zed", and "developer-first" would naturally appear in a request, but common variations a user would actually say are missing: "brand voice", "tone", "marketing copy", "release notes", "announcement", "review copy". This lands on 'Some relevant keywords but missing common variations or synonyms' — better than the single-generic-keyword anchor (2), short of the good-coverage anchor (4).

3 / 5

Distinctiveness Conflict Risk

The Zed-specific niche ("copy for Zed", "developer-first") is mostly distinct with clear brand anchoring, matching 'Mostly distinct; minor overlap risk'. It is not a 5 because generic writing/copywriting terms like "copy" could collide with other writing or humanizer-style skills since no stronger disambiguating triggers (e.g., 'brand voice') are given; it is well above the broad-overlap anchors at 2-3.

4 / 5

Total

12

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

coumbassaabdoulaye01-del/borther-Code-by-code

Path

.factory/skills/brand-writer/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.