CtrlK
BlogDocsLog inGet started
Tessl Logo

content-writer

Generate high-quality written content for any platform with AI-powered drafting and editing.

56

Quality

62%

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 ./apps/desktop/electron/default-skills/content-writer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 is well-structured, concise, and gives genuinely actionable writing guidance with a clear before-draft-output sequence. Main residual is minor stylistic padding in the intro and no explicit feedback loop, though none is strictly needed here.

DimensionReasoningScore

Conciseness

The guidance sections are tight and assume Claude's competence, with only minor stylistic flourishes in the intro ('not a generic content mill', 'throat-clearing') that could be trimmed, fitting the efficient-with-minor-trimmable-instances anchor.

4 / 5

Actionability

Gives concrete, specific direction (short scannable paragraphs + strong hook for social, clear H2 structure for long-form, one focused ask per email, vary hook/angle/structure for variants) rather than vague advice, with only minor gaps; absence of code is fine for an instruction-only skill.

4 / 5

Workflow Clarity

A clear sequenced flow (Before you write -> How to draft -> Variations and editing -> Output format) with most checkpoints present; no explicit validate-fix-retry loop, but none is required for non-destructive content generation, so it stays at 4 rather than 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into clearly signaled sections, so the simple-skill exception lets progressive disclosure score 5 on well-organized sections alone.

5 / 5

Total

17

/

20

Passed

Description

46%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 the skill's purpose but relies on buzzword fluff and lacks explicit trigger guidance, leaving it indistinguishable from generic writing tools. It needs concrete 'Use when...' phrasing and platform-specific trigger terms.

Suggestions

Replace 'high-quality' and 'AI-powered' with concrete deliverables (e.g., 'blog posts, landing pages, ad copy, email sequences, social captions').

Add an explicit trigger clause such as 'Use when drafting or substantially reworking net-new copy for blogs, email, social, or landing pages.'

Narrow 'any platform' to the specific platforms/formats the skill targets to reduce overlap with adjacent writing skills.

DimensionReasoningScore

Specificity

Names the domain ('written content for any platform') and two actions ('drafting and editing'), but 'high-quality' and 'AI-powered' are vague fluff and coverage is not comprehensive, matching the names-domain-with-1-2-actions anchor.

3 / 5

Completeness

It states a clear 'what' (generate/draft/edit content) but provides no 'Use when...' trigger guidance; per the guidelines a missing explicit trigger clause caps completeness at 3, and it is not below since the 'what' is clear.

3 / 5

Trigger Term Quality

Terms like 'written content', 'drafting and editing', and 'any platform' are somewhat relevant, but the description omits the natural phrases users actually say (e.g., 'blog post', 'email', 'caption', 'copywriting'), matching the some-keywords-but-missing-variations anchor.

3 / 5

Distinctiveness Conflict Risk

'Any platform' plus broad writing verbs makes this very broad with high overlap risk against many writing/copy skills, fitting the very-broad/high-overlap anchor rather than the somewhat-specific anchor above.

2 / 5

Total

11

/

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
holaboss-ai/holaOS
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.