CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

brand-writer

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

Quality

68%

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 ./docs/.conventions/brand-voice/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 body presents a well-sequenced, genuinely actionable brand-writing workflow with an explicit diagnose-rewrite-re-score feedback loop and useful worked examples. Its two real weaknesses are duplicated anti-marketing guidance across several sections and a validation system that depends on reference files absent from the bundle. Shipping those files or inlining their essentials would close the largest gaps.

Suggestions

Ship rubric.md, taboo-phrases.md, and voice-examples.md (e.g., in a references/ directory) or inline their essential content — the validation workflow currently depends on files that are not in the bundle.

Consolidate the anti-hype guidance repeated across Core Voice/Tone, Writing Principle 6, Avoid, and Structure into a single section.

Trim the Phase 4 full-scorecard template and the Review Mode output examples down to the essential structure.

DimensionReasoningScore

Conciseness

The brand-specific material (Core Messages, voice rules, good/bad/fixed examples) is knowledge Claude does not already have, but the anti-hype guidance is restated across four sections (Core Voice/Tone, Writing Principle 6, Avoid, Structure) and the Phase 4 scorecard template plus Review Mode output examples are padded. Mostly efficient with real tightening opportunities — not the minor-trimming level of 4.

3 / 5

Actionability

The guidance is concrete and executable: a [FACT]-marker system with a worked example, a named 8-criterion scoring table, per-context output formats, and transformation examples. It falls short of fully executable (5) because the criteria definitions, taboo list, and transformation patterns are delegated to reference files (rubric.md, taboo-phrases.md, voice-examples.md) that are not present in the bundle.

4 / 5

Workflow Clarity

Four phases are explicitly sequenced (understand → gather → draft → validate) with a genuine feedback loop — "For any criterion scoring <4 or any taboo phrase found: identify, rewrite, verify [FACT] markers survived, re-score. Repeat until all criteria score 4+" — plus fact-survival checks and checklists (Litmus Test, final scorecard). This matches the top anchor: explicit validation steps, error-recovery loops, and checklists.

5 / 5

Progressive Disclosure

Sections are well organized and the three references are clearly signaled with one-line descriptions, but rubric.md, taboo-phrases.md, and voice-examples.md do not exist in the bundle (no references/ directory), so the promised detail is inaccessible and the "auto-loaded from skill folder" claim is broken. The dangling references are a major gap that rules out 4 despite good internal structure.

3 / 5

Total

15

/

20

Passed

Description

53%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 conveys a clear, well-targeted "what" — Zed-specific, developer-first copywriting — but omits any "when to use" guidance, and its trigger vocabulary is thin relative to the contexts the skill itself supports (homepage, release notes, review mode). Low conflict risk thanks to the Zed niche. A use-when clause plus trigger synonyms would lift the weakest dimensions.

Suggestions

Add a trigger clause, e.g., "Use when writing or reviewing copy for Zed — homepage, product pages, release notes, docs, or social — or when the user mentions Zed's brand voice or tone."

Include the natural trigger synonyms users would say: "brand voice", "tone", "marketing copy", "announcement", "zed.dev content".

Mention the review capability ("--review existing copy for brand fit") so the description covers both invocation modes.

DimensionReasoningScore

Specificity

"Write clear, developer-first copy for Zed" names the domain and one concrete action, with "leading with facts, grounded in craft" adding style framing rather than capabilities. It is not comprehensive — the skill's review mode is absent — so it sits at anchor 3, above the generic-action level of 2 but below the several-specific-actions level of 4.

3 / 5

Completeness

The "what" is clear ("Write clear, developer-first copy for Zed"), but there is no "when" — no "Use when..." clause or equivalent trigger guidance anywhere, which caps completeness at 3 per the judging guidelines. It is above 2 because the "what" half is concrete and specific.

3 / 5

Trigger Term Quality

Natural terms like "write", "copy", "Zed", and "developer" are present, but common variations a user would actually say — "brand voice", "tone", "marketing copy", "release notes", "homepage" — are missing. This matches "some relevant keywords but missing common variations or synonyms" rather than the good coverage of 4.

3 / 5

Distinctiveness Conflict Risk

The "for Zed" niche makes it mostly distinct from other writing skills, with only minor overlap risk against generic copywriting or brand-voice skills. Not 5 because the description lacks the distinct trigger vocabulary (brand voice, zed.dev) that would eliminate that overlap.

4 / 5

Total

13

/

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

docs/.conventions/brand-voice/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.