meta-description — Claude Code skill for writing and auditing meta
A skill for writing, auditing, and optimizing meta descriptions. Use it when a specific page needs a snippet candidate, not a sitewide template rewrite.
npx skills add kostja94/marketing-skills --skill meta-description -a claude-code
npx skills add kostja94/marketing-skills --skill description -a claude-codeWhat meta-description does
The skill owns the rules for <meta name="description">. It reads root contextus.md when present and asks for page type, search intent, locale, verified page facts, current description, body coverage, and sibling-page descriptions before writing.
The Swap Test is the sharpest rule here: if a description can move to a sibling page unchanged, it is not specific enough. Length is a warning, not a hard gate. Google has no fixed limit and truncates snippets per device and context, so the skill flags descriptions that are too short to explain value or padded with filler.
It makes no promises about CTR, rankings, or traffic: a meta description is not a direct ranking control. Output is a recommended description, a non-binding length warning, a rationale, and a body-coverage flag when the page cannot substantiate the claim. For the sitewide metadata lifecycle with implementation and production validation, use page-metadata instead.
What it helps with
- Write a meta description for a specific page
- Catch sibling-page description duplication
- Flag descriptions the page text cannot substantiate
- Judge description length without a fixed character limit
- Localize a description from target-market query language
Example prompts for the agent
- Audit the meta description for this page and suggest a replacement
- Check sibling page descriptions for duplication
- Rewrite this meta description for the Spanish market without translating literally
How to install meta-description
1Skills CLI (Vercel)
npx skills add kostja94/marketing-skills --skill meta-description -a claude-codenpx skills add kostja94/marketing-skills --skill description -a claude-code2Manually: put the files in place
~/.claude/skills/description/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/description/
1Skills CLI (Vercel)
npx skills add kostja94/marketing-skills --skill description -a codex2Manually: put the files in place
.agents/skills/description/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add kostja94/marketing-skills --skill description -a cursor2Manually: put the files in place
.cursor/skills/description/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install kostja94/marketing-skills description2Manually: put the files in place
.github/skills/description/SKILL.md1Skills CLI (Vercel)
npx skills add kostja94/marketing-skills --skill description -a gemini-cli2Platform CLI
gemini skills install https://github.com/kostja94/marketing-skills --path skills/seo/on-page/descriptionManually: put the files in place
.devin/skills/description/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add kostja94/marketing-skills --skill description -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about meta-description
How do I install meta-description in Claude Code?
Run npx skills add kostja94/marketing-skills --skill meta-description -a claude-code. The skill lands in ~/.claude/skills/description/SKILL.md. The alias form is npx skills add kostja94/marketing-skills --skill description -a claude-code.
What is the difference between meta-description and page-metadata?
meta-description handles one page: write, audit, rewrite its description. page-metadata covers the sitewide metadata lifecycle, including implementation and production validation.
Does a meta description have a hard length limit?
The skill treats length as a warning, not a hard gate. Google has no fixed meta-description length limit and truncates snippets as needed for the device and result context. It flags descriptions that are too short to explain value or too long because of filler.
Source text
SKILL.md · MIT
--- name: meta-description description: When the user wants to write, audit, or optimize a meta description, SEO description, SERP snippet candidate, duplicate description, description length, or description rewrite issue. For a sitewide metadata lifecycle including implementation and production validation, use page-metadata. metadata: version: 2.0.0 --- # SEO On-Page: Meta Description Owns writing and review rules for `<meta name="description">`. It is a candidate source for search snippets, not a guarantee of the text Google will display. ## Inputs Read root `contextus.md` when present. Confirm page type, primary search intent, locale, verified page-specific facts, current description, body coverage, sibling-page descriptions, and the intended next action when one exists. ## Rules - Write an accurate, useful summary or pitch for the specific page. - Lead with information that distinguishes this page from sibling pages. - Use query-relevant language naturally, without a keyword list. - Length is a warning, not a hard gate. Google has no fixed meta-description length limit and truncates snippets as needed for the device and result context. - A description may exceed traditional character guidance when it remains concise and useful. Flag descriptions too short to explain value or too long because of filler, repetition, or boilerplate. - Use a CTA only when it suits the page task. Do not force marketing CTAs into legal, documentation, status, or informational pages. - Include price, author, date, availability, or compatibility only when present and current on the page. - Apply the **Swap Test**: if a description can move unchanged to a sibling page, it is not specific enough. - Localize from the target market's query language and intent; do not translate and truncate. - Google primarily creates snippets from page content and may show different text for different queries. Ensure the H2/body can substantiate the description's promise. - Do not claim a fixed CTR, ranking, or traffic increase. A meta description is not a direct ranking control. ## Output - Recommended description and a non-binding length warning when useful. - Brief rationale tied to intent and page-specific facts. - Body-coverage warning if the page cannot substantiate the proposed description. - Sibling duplication or cannibalization warning when applicable; do not restructure pages. ## Primary reference - [Google: snippets and meta descriptions](https://developers.google.com/search/docs/appearance/snippet) ## Related Skills - **page-metadata**, **title-tag**, **heading-structure** - **localization-strategy**, **translation**, **google-search-console**
© kostja94 · MIT · kostja94/marketing-skills
