mcpbeat Sign in

SEO Content Skill for Claude

Assess a draft or page for usefulness, search intent, factual support and experience/expertise signals. Use for SEO content audits or revisions.

745 tokens
context cost
SKILL.md, read when the skill is used
2
files
plus reference files
0
copies elsewhere
how many repositories repackaged it
834
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/AgriciDaniel/chatgpt-seo --skill seo-content

What comes with it

190 bytes besides the instruction
agents/openai.yaml

The instruction itself

7 sections, as written by the author

Content quality

Input

The actual content and its audience, goal and sources when provided.

Evidence and runtime

If a skill-resource reader fails to open a linked supporting file, try the

available file or execution tool using the installed plugin root returned by

the host or resolved from this skill's location. Do not hardcode a home folder,

version, or working directory. Distinguish a failed reader call from an absent

file, and files actually attempted from files not attempted. Report a resource

as unavailable only after the supported access paths have failed. If no file

or execution access is available, continue within the evidence you can read

and state that limit.

Read the operating contract when this

workflow is selected. Use runtime and data paths

when choosing a tool or handling missing data. Recheck relevant

search facts and primary sources

before date-sensitive claims. For a quantitative diagnostic, read

scoring; unavailable categories stay unknown.

Supporting resources

Read only the resources needed for the selected part of this task:

  • editorial and factual review.
  • section purpose.

Workflow

  • Read the main content, distinguish it from navigation and boilerplate, and identify the task a visitor should complete.
  • Evaluate who created it, how claims can be checked, why it exists, and which original examples, methods or experiences improve the answer.
  • Find unsupported statistics, vague expertise claims, stale prices or policies, and contradictions. Verify volatile claims against primary sources or mark them unresolved.
  • Assess completeness against the task and observed search intent. Do not use a universal word-count minimum, keyword-density target or AI detector as a quality verdict.
  • Propose the smallest useful improvements: source-backed passages, a clearer structure, evidence or examples, author accountability, and natural internal links.
  • When rewriting, retain the user's product facts and voice. Flag missing facts instead of inventing testimonials, experience or credentials.

Deliverable

A content diagnosis, a claim/evidence ledger and an edit plan. Supply the revised content only when requested, with unresolved facts clearly identified.

Boundary

E-E-A-T is a review framework here, not a directly measured ranking score. Originality claims require comparison evidence.

Adapted from the public Claude SEO seo-content workflow.

How to use it

Copy the folder

Take agricidaniel/seo-content from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.