CtrlK
BlogDocsLog inGet started
Tessl Logo

generate-voice-guide

Generate a personal voice guide for X (Twitter) and/or LinkedIn by scanning a user's past posts and iteratively refining with sample-and-feedback loops. Produces a structured markdown voice guide that sibling skills (create-x-content, create-linkedin-content) consume to draft in-voice posts. Different from brand-voice-extractor, which analyses company blogs/landing pages — this skill is for personal social voice.

65

Quality

79%

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 ./skills/brand/capabilities/generate-voice-guide/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 content is a strong, highly actionable agent-executed workflow with clear phases, an explicit feedback loop, and concrete tooling details. Its only real weakness is minor motivational redundancy and a missed opportunity to split the template skeleton / config schema into reference files.

DimensionReasoningScore

Conciseness

The body is well-organized and mostly lean, assuming Claude's competence, with only minor instances of motivational repetition (the '5+ iterations is the floor' point appears in both Phase 3 and Tips) that could be trimmed.

4 / 5

Actionability

For an instruction-only, agent-executed skill the guidance is exceptionally concrete: named Apify actors, the exact env var, default counts, exclusion rules, a section-ordered template skeleton, the config JSON schema, and a full CLI args table with defaults.

5 / 5

Workflow Clarity

Four phases are clearly sequenced with an explicit feedback loop in Phase 3 (sample → feedback → revise → repeat), a concrete stopping rule, error handling for a missing APIFY_API_TOKEN, and a fallback path — all checkpoints an agent can follow.

5 / 5

Progressive Disclosure

No bundle files exist, so the skill is self-contained with well-organized sections and clear navigation; the inline template skeleton and config schema could arguably live in separate reference files, leaving a minor organization gap.

4 / 5

Total

18

/

20

Passed

Description

70%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 concrete and strongly differentiated, clearly answering what the skill does and how it differs from a sibling skill. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a user wants a personal voice guide for X or LinkedIn, or when create-x-content / create-linkedin-content needs one that doesn't yet exist.'

Include a few more natural synonyms (e.g. 'writing style', 'tone profile') alongside 'voice guide' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'scanning a user's past posts', 'iteratively refining with sample-and-feedback loops', 'produces a structured markdown voice guide' — with only minor gaps in coverage.

4 / 5

Completeness

The 'what' is clearly stated but there is no explicit 'Use when...' trigger clause; per the judging guidelines a missing trigger clause caps completeness at 3 even though the what is strong.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('voice guide', 'X (Twitter)', 'LinkedIn', 'past posts', 'social voice') with good coverage, though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Explicitly carves a niche ('personal social voice') and differentiates from brand-voice-extractor by name, giving it a clear, low-conflict trigger surface.

5 / 5

Total

16

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
gooseworks-ai/goose-skills
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.