CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

write-like-me

Use this skill when the user asks to "draft this email in my voice", "rewrite this message like me", "sound like me", "learn my writing style", "update my voice profile", or "inspect my writing voice". Covers personal writing style emulation, tone calibration, and profile maintenance. Do NOT use this skill for filing notes or organizing vaults (use `para-vault`) or raw file operations (use `manage-file-operations`).

Quality

81%

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

The canonical home for this skill is write-like-me in NyssaAI/agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

60%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-organized orchestrator body with a clean triage matrix, sensible invariants, and an explicit verification checklist — concise and mostly clear. Its effectiveness is undermined by broken bundle integration: both workflow links point to non-existent files, and four of the five reference files are never linked, so the routing and progressive disclosure do not actually lead anywhere.

Suggestions

Fix the broken workflow links: either create workflows/draft.md and workflows/maintain.md or repoint the Triage Matrix at the files that actually exist (e.g., references/drafting-and-review.md for drafting, references/calibration.md plus references/learning-from-edits.md for profile maintenance).

Make the orphaned reference files discoverable by referencing references/calibration.md, references/learning-from-edits.md, and references/storage.md from the Triage Matrix or a short References section, so SKILL.md works as a real index of the bundle.

Trim the Scope Directive callout, which repeats the frontmatter description's boundaries and the Triage Matrix's routing, and replace the LaTeX '$\rightarrow$' arrows in invariant 4 with plain '→' or '>' so scope precedence renders correctly.

DimensionReasoningScore

Conciseness

The ~44-line body is lean, assumes Claude's competence, and explains nothing the model already knows — no filler or concept explanations. It sits just below anchor 5 because the 'Scope Directive' callout substantially repeats the routing and negative-scope information already carried by the Triage Matrix (e.g., the para-vault/manage-file-operations boundaries appear in both), and invariant 4 uses LaTeX arrows ('$\rightarrow$') that render as literal text in markdown, slightly padding presentation.

4 / 5

Actionability

The triage table gives concrete intent-based routing and invariant 4 names concrete config paths ('.nyssa-ai/agent-skills/writing-voice/', '~/.nyssa-ai/agent-skills/writing-voice/'), but the two primary executable targets — '[workflows/draft.md](workflows/draft.md)' and '[workflows/maintain.md](workflows/maintain.md)' — do not exist in the bundle, so an agent following the instructions hits missing files at the first step. This is the anchor-3 pattern of concrete-but-incomplete guidance with key details missing, not anchor 4's 'minor gaps'.

3 / 5

Workflow Clarity

The two-branch sequence is explicit (triage table: intent → runbook) and the Verification section provides a real checkpoint checklist before completion (facts preserved, files saved in authorized scope, no leakage, schema conformance), matching anchor 4's clear sequence with most checkpoints present. It is not anchor 5 because the detailed per-workflow steps live in the linked runbooks, which are absent from the bundle, leaving the middle of each workflow undefined.

4 / 5

Progressive Disclosure

Scored against the actual bundle: the body's two most prominent links ('workflows/draft.md', 'workflows/maintain.md') are broken — no workflows/ directory exists — and 4 of the 5 files in references/ (calibration.md, drafting-and-review.md, learning-from-edits.md, storage.md) are never mentioned anywhere in SKILL.md, making them undiscoverable; only references/profile-schema.md is both real and referenced. The section structure itself is good, but with the core navigation broken and most of the bundle orphaned, references are effectively buried rather than clearly signaled, fitting anchor 2 better than anchor 3.

2 / 5

Total

13

/

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.

A strong description: explicit use-when triggers with natural synonyms, a clear capability statement, and explicit negative scoping against neighboring skills. The only minor weakness is that the 'what' is phrased as capability areas ('tone calibration', 'profile maintenance') rather than fully concrete operations.

DimensionReasoningScore

Specificity

The 'what' is stated as three concrete capability areas — 'personal writing style emulation, tone calibration, and profile maintenance' — and the trigger quotes ('draft this email in my voice', 'update my voice profile') make the operations tangible. It falls short of anchor 5 because the actions are named as functional areas rather than fully concrete operations (e.g., it never mentions drafting concrete artifact types or updating profile files like VOICE.md/STYLE.md), and above anchor 3 because more than 1-2 specific capabilities are covered.

4 / 5

Completeness

Both halves are explicit: what it does ('Covers personal writing style emulation, tone calibration, and profile maintenance') and when to use it ('Use this skill when the user asks to...') with concrete trigger phrases. Negative triggers ('Do NOT use this skill for filing notes... or raw file operations') add disambiguation, satisfying the anchor-5 example of clearly answering both what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Six natural, verbatim user phrasings with synonyms are given: 'draft this email in my voice', 'rewrite this message like me', 'sound like me', 'learn my writing style', 'update my voice profile', 'inspect my writing voice'. This comprehensively covers how a user would naturally request this skill, matching the anchor-5 pattern of natural terms plus synonyms; nothing obvious is missing.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (personal writing voice emulation) with distinct triggers, and explicitly redirects two adjacent domains to other skills ('use `para-vault`' for vault filing, 'use `manage-file-operations`' for raw file operations). This active de-confliction matches the anchor-5 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

19

/

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

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

NyssaAI/agent-skills

Path

.agents/plugins/agent-skills/skills/write-like-me/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.