Site Architecture
AvdLee/RocketSimApp
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking.
Audits a blog post draft or page copy for content-level SEO: search intent fit, focus keyphrase placement, E-E-A-T signals (experience, expertise, authoritativeness, trustworthiness), helpfulness…
$ npx skills add jdevalk/skills --skill content-seo -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jdevalk/skills content-seo --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jdevalk/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/content-seo .claude/skills/content-seo && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "content-seo" agent skill from https://github.com/jdevalk/skills/tree/main/content-seo into .claude/skills/content-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-seo", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jdevalk/skills/tree/main/content-seoType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jdevalk/skills --skill content-seo -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jdevalk/skills content-seo --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jdevalk/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/content-seo .agents/skills/content-seo && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "content-seo" agent skill from https://github.com/jdevalk/skills/tree/main/content-seo into .agents/skills/content-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-seo", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jdevalk/skills --skill content-seo -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jdevalk/skills content-seo --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jdevalk/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/content-seo .cursor/skills/content-seo && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "content-seo" agent skill from https://github.com/jdevalk/skills/tree/main/content-seo into .cursor/skills/content-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-seo", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jdevalk/skills.git --path content-seo--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jdevalk/skills --skill content-seo -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jdevalk/skills content-seo --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jdevalk/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/content-seo .gemini/skills/content-seo && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "content-seo" agent skill from https://github.com/jdevalk/skills/tree/main/content-seo into .gemini/skills/content-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-seo", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jdevalk/skills content-seoInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jdevalk/skills --skill content-seo -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jdevalk/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/content-seo .github/skills/content-seo && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "content-seo" agent skill from https://github.com/jdevalk/skills/tree/main/content-seo into .github/skills/content-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-seo", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jdevalk/skills --skill content-seo -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jdevalk/skills content-seo --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jdevalk/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/content-seo .opencode/skills/content-seo && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "content-seo" agent skill from https://github.com/jdevalk/skills/tree/main/content-seo into .opencode/skills/content-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-seo", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
content-seoAudits a blog post draft or page copy for content-level SEO: search intent fit, focus keyphrase placement, E-E-A-T signals (experience, expertise, authoritativeness, trustworthiness), helpfulness…
Content SEO is an agent skill from jdevalk/skills. Audits a blog post draft or page copy for content-level SEO: search intent fit, focus keyphrase placement, E-E-A-T signals (experience, expertise, authoritativeness, trustworthiness), helpfulness and originality, content freshness, and internal linking. Use when the user asks "will this rank", "SEO check this post", "content SEO audit", or "optimize this post for search" — or proactively after a readability pass on a post that's meant to rank. For how the prose reads, use the readability-check skill; for titles…
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).
It sits in Marketing & SEO, covering On-page SEO, Technical SEO and Static sites and blogs. It works with Astro. The repository describes itself as: Agent skills for GitHub repos and profiles, WordPress and EmDash plugins, Astro SEO, and content readability. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 106fc68. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Content SEO loads about 2.3k tokens when it runs. Until then it costs about 169 tokens; SKILL.md has 1,211 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from jdevalk/skills at commit 106fc68, republished under its MIT licence (© jdevalk). 1,211 words, ~2,292 tokens.
.claude/skills/content-seo/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Audit a post or page draft for whether it earns a ranking — not how it reads. This skill covers the content-level questions: does the post match a real search intent, does it use the words searchers use, does it demonstrate experience and trustworthiness, and does it give the searcher a reason to stay.
This is the third pass in the writing-quality chain. Run readability-check first (how the prose reads), metadata-check on the title and meta description, and this skill on the question of whether the content deserves the click. Technical SEO — sitemaps, structured data, canonicals, performance — belongs to astro-seo or static-seo.
You need two facts. If the user hasn't supplied them, derive them and state your assumption — a wrong assumption flagged is better than a silent one:
The reader decides what quality is, not the writer. Every check below reduces to one question: does this content serve the person who typed the query better than what's already ranking?
Read the full post, then report on each criterion below. For every issue, quote the specific text, reference its location, explain the problem, and suggest a concrete fix.
Searchers arrive with one of four intents, and the content type must match:
Checks:
The keyphrase confirms to the searcher — and to the search engine — that this page answers their query. It should appear naturally in the places both of them weight most:
And the inverse checks:
Search quality raters assess experience, expertise, authoritativeness, and trustworthiness. These aren't abstract virtues — each one is visible (or absent) in the text:
The people-first test: would this post exist if search engines didn't?
A post doesn't rank in isolation — it ranks as part of a site:
Per-category status — for each of the 6 checks above, assign one of:
Overall verdict — one of three:
## Content SEO audit: [post title]
### Target
- Focus keyphrase: [phrase] ([stated by user / derived — assumption])
- Intent: [informational / commercial / transactional / navigational]
- Verdict: [Ready / Fixable / Wrong content for the query]
- Per-category: 1. ✓ 2. ⚠ 3. ✓ 4. ✗ 5. ✓ 6. ⚠
### Summary
[One paragraph: what query this post serves, how well it serves it, and the one or two changes that would move it most.]
### Issues found
[Grouped by category. For each: location, quoted text, why it's a problem, concrete fix.]
### What's working
[Specific elements that earn the ranking — a genuinely first-hand example, a complete answer placed early, a well-linked cornerstone reference. Quote them so the writer can calibrate.]© jdevalk, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in content-seo of jdevalk/skills.
Open the folder on GitHubat commit 106fc68
Content SEO next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Content SEO this skilljdevalk/skills | 104 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Site ArchitectureAvdLee/RocketSimApp | 802 | 10 repos | ~3.3k | Automated safety check: Pass | Custom licence | |
| SEO Audit with Search Consolenowork-studio/notfair-plugin | 3.9k | 1 repos | ~15k | Automated safety check: Warn | MIT | |
| SEO Optimizerailabs-393/ai-labs-claude-skills | 454 | 1 repos | ~3.2k | Automated safety check: Pass | MIT | |
| SEO Setupalisamadiii/Portfolio | 180 | — | ~1.7k | Automated safety check: Pass | None | |
| SEO Auditfreekmurze/dotfiles | 1k | 33 repos | ~2.2k | Automated safety check: Pass | None |
AvdLee/RocketSimApp
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking.
nowork-studio/notfair-plugin
Runs a full SEO audit that combines Google Search Console, URL Inspection, PageSpeed Insights and a technical crawl, then ranks quick wins and a 30-day plan.
ailabs-393/ai-labs-claude-skills
This skill should be used when analyzing HTML/CSS websites for SEO optimization, fixing SEO issues, generating SEO reports, or implementing SEO best practices.
alisamadiii/Portfolio
Full SEO/metadata setup and audit for client websites (Astro, Next.js, any static site).
freekmurze/dotfiles
When the user wants to audit, review, or diagnose SEO issues on their site.
AgriciDaniel/claude-seo
Hub for site-wide SEO work: audits, technical checks, schema, content quality, local, hreflang and AI-search readiness, run through slash commands.
jdevalk/skills
Clones a live WordPress (or other CMS-driven) site into a static HTML site deployable on any static host (Cloudflare Pages, Netlify, Vercel, S3+CloudFront, plain Apache/nginx).
jdevalk/skills
Audits and improves SEO for Astro sites. An agent skill from jdevalk/skills.
jdevalk/skills
Reviews short high-value strings — page titles, meta descriptions, schema description fields, FAQ answers, GitHub repo taglines, profile bios, social-card copy, and other metadata where Flesch and…
jdevalk/skills
Runs a readability audit on a blog post draft or other multi-paragraph prose, calibrated for readers who read English as a second language.
jdevalk/skills
Audits and improves SEO for static HTML sites. An agent skill from jdevalk/skills.
jdevalk/skills
Audits and optimizes GitHub profile pages — profile README, metadata fields, pinned repositories, stats widgets, and contribution visibility.
Works with
Categories
Audits a blog post draft or page copy for content-level SEO: search intent fit, focus keyphrase placement, E-E-A-T signals (experience, expertise, authoritativeness, trustworthiness), helpfulness…. Content SEO is an agent skill from jdevalk/skills. Audits a blog post draft or page copy for content-level SEO: search intent fit, focus keyphrase placement, E-E-A-T signals (experience, expertise, authoritativeness, trustworthiness), helpfulness and originality, content freshness, and internal linking.
Content SEO fits situations like: the user asks will this rank; SEO check this post; content SEO audit; optimize this post for search —.
Run `npx skills add jdevalk/skills --skill content-seo -a claude-code`. Or copy the skill folder (content-seo in jdevalk/skills) into .claude/skills/content-seo in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jdevalk/skills --skill content-seo -a codex`. Or copy the skill folder (content-seo in jdevalk/skills) into .agents/skills/content-seo in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jdevalk/skills --skill content-seo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/content-seo, .gemini/skills/content-seo, .github/skills/content-seo and .opencode/skills/content-seo in your project.
SKILL.md names no scripts, command-line tools or credentials: Content SEO is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Content SEO is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.3k tokens (SKILL.md is roughly 9.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Content SEO: Site Architecture (AvdLee/RocketSimApp, 802 stars), SEO Audit with Search Console (nowork-studio/notfair-plugin, 3.9k stars), SEO Optimizer (ailabs-393/ai-labs-claude-skills, 454 stars) and SEO Setup (alisamadiii/Portfolio, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jdevalk (a GitHub user) maintains it in jdevalk/skills, which has 104 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on July 5, 2026.
Source: jdevalk/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.