CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

content-and-copy

Write or edit website copy, blog content, and editorial pieces with attention to voice, structure, and goal. Use this skill whenever the user wants to write an article, draft website copy, edit existing content for clarity or voice, write a blog post, or produce general editorial content. Triggers on write a blog post, draft an article, write copy for, edit this, rewrite this, write content, write a guide, draft a how-to, write web copy. Also triggers when content has been outlined and now needs to be written, or when existing content needs voice or clarity edits.

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

The canonical home for this skill is content-and-copy in rampstackco/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

86%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-structured instruction skill: concrete examples, two clearly sequenced workflows with checkpoints, a copy-paste output template, and clean progressive disclosure into two real, well-signaled reference files. The only notable weaknesses are mild redundancy between the five-dimensions section and the Failure patterns section, and a few implicit rather than explicit validation loops in the workflows.

Suggestions

Trim the Failure patterns section to only the failure modes not already covered by the five dimensions (e.g. keep "Edit by adding" and "Ignoring the headers", cut restatements of weak hooks, padding, and no-closing).

Add an explicit validation loop in the new-piece workflow, e.g. after drafting: "Re-read the brief. Does each section serve the stated reader and goal? If not, fix before voice editing".

Consider moving the quoted example bank (strong/weak hooks and closings) into a reference file if the skill grows, keeping SKILL.md to the framework and workflows.

DimensionReasoningScore

Conciseness

The body is dense and example-driven with no tutorials on concepts Claude already knows (no "what is a blog post" padding), and every quoted example ("By the end, you'll know exactly which X to pick") earns its place. It is not a 5 because the Failure patterns section ("Burying the lead... Padding to hit word count... No closing") substantially mirrors the five dimensions section in negative form and could be trimmed.

4 / 5

Actionability

Fully concrete guidance throughout: quoted strong/weak hook and closing examples, a 7-step new-piece workflow, a 5-step edit workflow with explicit edit-by-priority ordering, and a copy-paste-ready output template with a markdown skeleton and YAML frontmatter. For an instruction-only skill this matches the top anchor: specific examples cover the common cases.

5 / 5

Workflow Clarity

Both workflows are clearly numbered sequences with explicit checkpoints ("If the brief is vague, do not write yet", "Do not edit on first read", "Pre-publish checks. Headers in order, no skipped levels, internal links present") and an external edit checklist. Not a 5 because some validation is implicit — e.g. there is no explicit loop back to verify the draft against the brief or the hook after drafting.

4 / 5

Progressive Disclosure

The body is an overview of the framework and workflows, with detailed materials correctly split into real one-level-deep references: "references/content-brief-template.md - The brief that should exist before any content is written" and "references/content-edit-checklist.md - Pre-publish editing checklist", both verified to exist and each signaled with a link and a one-line description. Easy to navigate, no buried or nested references.

5 / 5

Total

18

/

20

Passed

Description

75%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 that explicitly answers both what and when with a concrete natural-language trigger list, in proper third-person voice. Its weaknesses are limited action-verb coverage in the what-statement and generic triggers ("edit this", "write content") that create overlap risk with closely related sibling skills.

Suggestions

Broaden the action verbs in the what-statement to cover the skill's actual scope, e.g. "Write, edit, outline, and restructure website copy, blog posts, and editorial pieces, adapting them to a defined brand voice".

Add a brief exclusion clause to reduce conflict risk, e.g. "For landing pages or email sequences, use the dedicated skills instead".

Add a few missing natural trigger variations such as "proofread this", "write a help article", or "write a knowledge base article" to cover the how-to/help-center use cases named in the body.

DimensionReasoningScore

Specificity

"Write or edit website copy, blog content, and editorial pieces" names the domain clearly but provides only two action verbs (write, edit), matching the anchor for naming a domain with 1-2 concrete actions. It is not a 4 because the body covers additional concrete actions (outlining, restructuring, adapting brand voice) that the description omits.

3 / 5

Completeness

Both questions are answered explicitly: the what ("Write or edit website copy, blog content, and editorial pieces with attention to voice, structure, and goal") and the when ("Use this skill whenever the user wants to write an article... Triggers on write a blog post, draft an article...") with a concrete trigger-phrase list. Matches the anchor for a clear, explicit what AND when with concrete trigger phrases.

5 / 5

Trigger Term Quality

"Triggers on write a blog post, draft an article, write copy for, edit this, rewrite this, write content, write a guide, draft a how-to, write web copy" gives good coverage of natural phrases users would say. Not a 5 because common variations like "proofread", "help article", "knowledge base", or "tighten this up" are missing.

4 / 5

Distinctiveness Conflict Risk

Triggers like "edit this", "rewrite this", and "write content" are broad and overlap with sibling skills (email-sequences, landing-page-copy, brand-voice), and the description carries no exclusion carve-outs. It is somewhat specific (editorial/web content niche) but still risks firing for the wrong skill, matching the middle anchor; not 4 because the exclusions only exist in the body, not the description.

3 / 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

rampstackco/claude-skills

Path

dist/codex/.agents/skills/content-and-copy/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.