CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

email-voice-profile

Build (or refresh) a voice profile of how the user writes email, from their own sent Gmail. The profile is what email-draft-in-voice consumes to ghostwrite email that sounds like them.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills-seed/email-voice-profile/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 tight, well-sequenced workflow with genuine validation and feedback loops, and excellent token efficiency. The main weaknesses are the unreferenced bundle script that duplicates step 1's instructions and the correspondingly vague corpus-pull direction.

Suggestions

Reference the bundle script in step 1, e.g. "Run `python3 scripts/fetch_sent.py` (token from $VAULT_TOKEN_GMAIL_GOOGLEAPIS_COM) to build voice/corpus/corpus.jsonl", falling back to the selected email access skill only if it is unavailable.

If the script is the intended path, trim the inline re-description of quote/signature stripping and internal/external tagging that the script already performs.

State when to prefer the script's --query/--limit flags (e.g., limiting to recent mail for a refresh) so the bundle is navigable from SKILL.md.

DimensionReasoningScore

Conciseness

The ~77-line body is lean and assumes competence: exact file names (voice/corpus/corpus.jsonl, email-voice-profile.md), thresholds ("fewer than ~50 usable emails"), and ready commands. The few explanatory asides ("Computers are replaced without notice...", "Gmail appends it on send") are single-line rationales for non-obvious rules, not padding of concepts Claude already knows, so it matches the 5-anchor rather than the 4-anchor's trimmable over-explanation.

5 / 5

Actionability

Mostly executable: concrete API calls with headers, an exact curl upload command, the exact profile filename and section structure, and a defined corpus format. It falls short of 5 because step 1 says only "Use the selected email access skill to retrieve up to 300 of the user's sent messages" while the bundle's scripts/fetch_sent.py — which implements exactly that fetch — is never invoked, leaving the corpus pull as high-level direction where a single command exists.

4 / 5

Workflow Clarity

Sections 0-5 give a clear sequence (check Files → pull corpus → study → write profile → validate → publish) with explicit validation steps and feedback loops: hold out 3 threads and tighten where drafts diverge, a small-corpus checkpoint that asks the user whether to continue, and user corrections folded in as hard rules. This matches the 5-anchor's explicit validation with error-recovery loops.

5 / 5

Progressive Disclosure

The body is well-sectioned, but scored against the actual bundle: the one bundle file (scripts/fetch_sent.py) is never referenced or signaled anywhere in SKILL.md, so the skill file is not a navigable map of its own bundle. It fits the 3-anchor (structure present, references not clearly signaled) better than 4, since the sole provided script is undiscoverable from the overview.

3 / 5

Total

17

/

20

Passed

Description

65%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 crisp, third-person description with a clear what and a well-delineated niche, but it omits any explicit "when to use" trigger guidance and misses some natural trigger phrasings. Adding a Use-when clause with the user-facing phrases already present in the body ("learn my voice", "study my sent mail") would lift it substantially.

Suggestions

Append a trigger clause such as: "Use when the user asks to learn their email voice, study their sent mail, or when email-draft-in-voice needs a profile that doesn't exist yet."

Fold the natural trigger phrases from the body ("learn my voice", "build my email voice profile") into the description itself so they are visible at skill-selection time.

Optionally name one more concrete capability (e.g., validating drafts against held-out threads) to broaden action coverage.

DimensionReasoningScore

Specificity

"Build (or refresh) a voice profile of how the user writes email, from their own sent Gmail" names the domain and 1-2 concrete actions with a specific data source, but does not list several distinct actions the way the 4-anchor requires. The consumer relationship ("email-draft-in-voice consumes") adds specificity of purpose, not additional capabilities.

3 / 5

Completeness

The "what" is clear (build/refresh a voice profile from the user's sent Gmail), but there is no "Use when..." clause or equivalent trigger guidance; the "when" is only weakly implied via the mention of the consuming skill, which per the judging guidelines caps completeness at 3. It is not 4 because the when is genuinely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural phrases like "voice profile", "how the user writes email", "sent Gmail", and "sounds like them" give good keyword coverage. A few natural terms users would say are missing ("learn my voice", "email style", "tone") — several of these appear in the body but not the description — so it does not reach comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

"The profile is what email-draft-in-voice consumes to ghostwrite email that sounds like them" carves out a clear niche (profiling the user's voice from their own sent mail) explicitly distinct from drafting skills themselves. Conflict risk with any other skill is minimal; it fits the clear-niche 5-anchor better than the 4-anchor's minor-overlap case.

5 / 5

Total

15

/

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

yc-software/qm

Path

skills-seed/email-voice-profile/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.