CtrlK
BlogDocsLog inGet started
Tessl Logo

article-writing

Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.

68

Quality

84%

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

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.

A tight, well-structured instruction skill: lean and directive prose, clear sequenced process, and an explicit quality-gate checklist. Its main weakness is actionability — it is rule-based with no executable code, commands, or worked before/after examples to make the guidance copy-paste concrete.

Suggestions

Add one short worked example per structure type (Technical Guide / Essay / Newsletter) showing a before/after opening that applies the 'lead with the concrete thing' rule, to lift actionability above rule-only guidance.

Provide a tiny reusable outline template (e.g., a markdown skeleton with one-job-per-section placeholders) so Claude has an executable artifact rather than only directives.

Split the per-type Structure Guidance into a referenced file (e.g., STRUCTURES.md) and keep a one-line pointer per type in SKILL.md to demonstrate clearer progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout — 'Lead with the concrete thing', 'Explain after the example, not before', 'Use proof instead of adjectives' — with no padding and no explanation of concepts Claude already knows. Every line earns its place, matching the 'lean and efficient; every token earns its place' anchor above the 'minor instances of over-explanation' level (4).

5 / 5

Actionability

Guidance is concrete as directives (e.g., the explicit Banned Patterns list and the 'start sections with proof, artifact, conflict, or example' steps), but there are no executable code blocks, commands, or worked before/after examples — it instructs via rules rather than copy-paste artifacts. This fits the 'some concrete guidance but incomplete; missing key details' anchor, below the 'mostly executable guidance' level (4) which requires concrete code or commands.

3 / 5

Workflow Clarity

The Writing Process is a clear 5-step sequence and the Quality Gate is an explicit pre-delivery checklist acting as a validation checkpoint. It lacks a validate-fix-retry feedback loop, but this skill produces prose rather than destructive/batch operations, so the destructive-cap does not apply; minor checkpoint gaps place it at 'clear sequence with most checkpoints' rather than the full feedback-loop level (5).

4 / 5

Progressive Disclosure

Content is well-organized into clearly signaled sections (When to Activate, Core Rules, Voice Handling, Banned Patterns, Writing Process, Structure Guidance by type, Quality Gate) with the only cross-reference being a clearly signaled one-level pointer to the `brand-voice` skill. There are no bundle files present, so the structure is self-contained; it sits at 'good structure; most content appropriately placed' rather than a 5 because no detailed reference files exist to demonstrate one-level-deep splitting for the per-type guidance.

4 / 5

Total

16

/

20

Passed

Description

90%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, third-person description that names concrete output types, supplies natural trigger phrasing, and gives an explicit 'Use when...' clause covering both what and when. Its only mild gap is that the stated actions are output nouns rather than a richer set of distinct transformational verbs.

Suggestions

Add one or two concrete transformational verbs beyond 'Write' and 'matching' (e.g., 'tighten', 'restructure', 'voice-match') to lift specificity toward the comprehensive-action anchor.

Tighten the trigger clause so 'longer than a paragraph' is paired with an explicit length boundary (e.g., '>500 words') to further reduce overlap with short-form writing skills.

DimensionReasoningScore

Specificity

Lists several concrete output types (articles, guides, blog posts, tutorials, newsletter issues) plus a concrete action (matching an existing founder/operator/brand voice from examples), though it stops short of naming every long-form variant. It sits above '1-2 concrete actions' (3) but the actions are output nouns rather than distinct transformational verbs, so it does not reach the comprehensive multi-action level (5).

4 / 5

Completeness

It explicitly answers 'what' (write long-form content types derived from supplied examples/brand guidance) and 'when' (an explicit 'Use when the user wants polished written content longer than a paragraph...' clause with concrete triggers). This matches the anchor that clearly and explicitly answers both what and when with concrete trigger phrases, exceeding the level (4) where 'when' could be more explicit.

5 / 5

Trigger Term Quality

Covers natural user phrasing comprehensively — 'articles, guides, blog posts, tutorials, newsletter issues', 'polished written content longer than a paragraph', and 'voice consistency, structure, and credibility' — including the common synonyms users would say when asking for long-form content. It matches the comprehensive-synonym anchor rather than the 'a few natural terms missing' anchor (4).

5 / 5

Distinctiveness Conflict Risk

The long-form-content framing plus 'voice consistency/structure/credibility' carve a fairly distinct niche with minimal overlap risk, but it could still rub against a generic writing or summarizing skill, so it sits at 'mostly distinct; minor overlap' rather than the 'clear niche, minimal conflict' anchor (5).

4 / 5

Total

18

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.