SEO Setup
alisamadiii/Portfolio
Full SEO/metadata setup and audit for client websites (Astro, Next.js, any static site).
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…
Install Metadata Check
$ npx skills add jdevalk/skills --skill metadata-check -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jdevalk/skills metadata-check --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/metadata-check .claude/skills/metadata-check && 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 "metadata-check" agent skill from https://github.com/jdevalk/skills/tree/main/metadata-check into .claude/skills/metadata-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metadata-check", 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/metadata-checkType 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 metadata-check -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jdevalk/skills metadata-check --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/metadata-check .agents/skills/metadata-check && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "metadata-check" agent skill from https://github.com/jdevalk/skills/tree/main/metadata-check into .agents/skills/metadata-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metadata-check", 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 metadata-check -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jdevalk/skills metadata-check --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/metadata-check .cursor/skills/metadata-check && 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 "metadata-check" agent skill from https://github.com/jdevalk/skills/tree/main/metadata-check into .cursor/skills/metadata-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metadata-check", 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 metadata-check--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 metadata-check -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jdevalk/skills metadata-check --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/metadata-check .gemini/skills/metadata-check && 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 "metadata-check" agent skill from https://github.com/jdevalk/skills/tree/main/metadata-check into .gemini/skills/metadata-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metadata-check", 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 metadata-checkInstalls 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 metadata-check -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/metadata-check .github/skills/metadata-check && 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 "metadata-check" agent skill from https://github.com/jdevalk/skills/tree/main/metadata-check into .github/skills/metadata-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metadata-check", 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 metadata-check -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 metadata-check --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/metadata-check .opencode/skills/metadata-check && 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 "metadata-check" agent skill from https://github.com/jdevalk/skills/tree/main/metadata-check into .opencode/skills/metadata-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metadata-check", 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.
Facts
- Skill name
metadata-check- GitHub stars
- 104
- Token cost
- ~1k tokens
- SKILL.md length
- 405 words
- Files
- 2
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- The user asks to review metadata
- SKILL.md covers What to check, What to skip and Output format
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Proactively after generating any short string with audience-facing impact
What it does
Metadata Check is an agent skill from 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 paragraph-level readability checks don't apply. Checks front-loading, concreteness, filler, active voice, title/description duplication, difficult words, SERP-truncation fit, and one-idea-per-field. Use when the user asks to review metadata, a tagline, a bio, or SEO strings, or proactively after generating any short…
Its SKILL.md is about 1k 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 Positioning and messaging, Static sites and blogs and Plain language and style rules. It works with GitHub and 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.
When your agent uses it
- The user asks to review metadata
- Proactively after generating any short string with audience-facing impact
Example prompts
- “Use the metadata-check skill to review short high-value strings — page titles, meta descriptions, schema description fields, FAQ answers, GitHub…”
- “/metadata-check”
What it can do on your machine
Read from SKILL.md and the folder at commit 106fc68. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
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.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Metadata Check loads about 1k tokens when it runs. Until then it costs about 186 tokens; SKILL.md has 405 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from jdevalk/skills at commit 106fc68, republished under its MIT licence (© jdevalk). 405 words, ~1,022 tokens.
Download SKILL.mdSave it as
.claude/skills/metadata-check/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- metadata-check
- description
- 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 paragraph-level readability checks don't apply. Checks front-loading, concreteness, filler, active voice, title/description duplication, difficult words, SERP-truncation fit, and one-idea-per-field. Use when the user asks to review metadata, a tagline, a bio, or SEO strings, or proactively after generating any short string with audience-facing impact. Chained into by astro-seo, wp-readme-optimizer, github-repo, and github-profile for their metadata outputs. For multi-paragraph prose, use the `readability-check` skill instead.
Metadata check
Reviews short, high-value strings where every character counts — titles, meta descriptions, schema descriptions, FAQ answers, taglines, bios, and social-card copy. Flesch scoring and the ten-category readability rubric don't fit a 5–30 word string; this skill applies the checks that do.
Use this skill for anything in the metadata-string shape. For multi-paragraph prose (blog posts, READMEs, CONTRIBUTING files), use readability-check instead.
What to check
For each string, check these points. Every check is either ✓ (pass), ⚠ (needs work), or ✗ (problem).
- Front-load the distinguishing word. The most specific, searchable term sits near the start. "Astro SEO: the definitive guide" beats "The definitive guide to Astro SEO" — the reader's eye hits the topic first.
- Concrete over abstract. Names, numbers, specific claims. "Reduce LCP by 40%" beats "Improve performance significantly."
- Filler and hedging — aggressive. Every word costs shelf space. Cut really, just, very, actually, basically, simply, a bit, kind of, I think. In metadata these aren't style ticks, they're wasted SERP characters.
- Active voice unless the object is the subject. "Audit your GitHub profile" beats "Your GitHub profile can be audited."
- No title/description duplication. A meta description that restates the title burns ~60 of 200 characters for nothing. The description should promise what's inside the page, not re-announce what it is.
- Difficult words. Prefer the common synonym unless the domain term is what the user searches for. Between utilize and use, use use. Domain terms the target audience expects are fine (hydration, middleware, structured data).
- SERP and platform truncation. Know the limit for the surface:
- Google SERP: titles clipped around 55–65 characters, descriptions around 155–160.
- GitHub repo description: ~350 chars, but only the first ~100 show in search results and on profile cards.
- Twitter/X bio: 160 chars.
- Open Graph description: usually shown at ~200 chars. Anything past the cut should be disposable, not a key promise.
- One idea per field. Titles and descriptions that try to promise two things land fuzzy. Pick the sharpest one.
Show full SKILL.md (83 more words)Show less
What to skip
Don't run this skill on:
- URLs, schema
@idvalues, filenames, enum values, or any technical identifier. - Multi-paragraph prose — route that to
readability-check. - Strings the user did not write and cannot change (imported content, upstream defaults).
Output format
Per string, return:
### [Field name] — [length] chars
> [The string itself]
- Front-loading: [✓/⚠/✗] [one-line reason if not ✓]
- Concreteness: [✓/⚠/✗] [reason]
- Filler: [✓/⚠/✗] [reason]
- Active voice: [✓/⚠/✗] [reason]
- Duplication: [✓/⚠/✗] [reason]
- Word choice: [✓/⚠/✗] [reason]
- Truncation fit: [✓/⚠/✗] [reason] — platform: [SERP/GitHub/Twitter/OG]
- One idea: [✓/⚠/✗] [reason]
**Rewrite:** [only if any check failed — a concrete replacement string, not a suggestion]Keep the audit tight — metadata feedback should be actionable in seconds, and you're almost always running it across a batch of strings at once. If a string is already clean, don't pad the output; just mark all ✓ and move on.
© jdevalk, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in metadata-check of jdevalk/skills.
- SKILL.md
- README.md
Open the folder on GitHubat commit 106fc68
Compare with similar skills
Metadata Check 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 |
|---|---|---|---|---|---|---|
| Metadata Check this skilljdevalk/skills | 104 | — | ~1k | Automated safety check: Pass | MIT | |
| SEO Setupalisamadiii/Portfolio | 180 | — | ~1.7k | Automated safety check: Pass | None | |
| SEO Content Optimizationmagnus919/hermes-profiles | 278 | — | ~3.1k | Automated safety check: Pass | MIT | |
| SEOgridaco/grida | 2.7k | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Message House Builderaaron-he-zhu/aaron-marketing-skills | 2.9k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| SEO Autopilotkennyzir/7deer_skills | 322 | — | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
SEO Content Optimization
magnus919/hermes-profiles
Audit and optimize content sites for search — page title audits, schema injection (Organization, FAQ, LocalBusiness), meta description rewrites, URL hygiene, local landing pages, and measurement.
SEO
gridaco/grida
SEO best practices for the Grida project across Next.js pages, blog posts, and documentation.
Message House Builder
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "build a message house", "write a PR-FAQ for our launch", or "define the launch narrative and value pillars"; derives from the positioning canvas a…
SEO Autopilot
kennyzir/7deer_skills
全自动 SEO 内容新鲜度引擎。监听关键词研究报告目录，自动生成落地页和博客文章，运行 SEO 审计后推送更新。适用于任何需要定期更新内容以保持 Google 排名新鲜度的网站项目。支持 Next.js / Astro / Nuxt 等主流框架。
SEO Optimizer
secondsky/claude-skills
SEO optimization with keyword analysis, readability assessment, technical validation, content quality.
More from jdevalk/skills
All 9 skills in this repoWp Static Clone
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).
Astro SEO
jdevalk/skills
Audits and improves SEO for Astro sites. An agent skill from jdevalk/skills.
Content SEO
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…
Readability Check
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.
Static SEO
jdevalk/skills
Audits and improves SEO for static HTML sites. An agent skill from jdevalk/skills.
GitHub Profile
jdevalk/skills
Audits and optimizes GitHub profile pages — profile README, metadata fields, pinned repositories, stats widgets, and contribution visibility.
Related
Questions about Metadata Check
What does Metadata Check do?
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…. Metadata Check is an agent skill from 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 paragraph-level readability checks don't apply.
When should I use Metadata Check?
Metadata Check fits situations like: the user asks to review metadata; proactively after generating any short string with audience-facing impact.
How do I install Metadata Check in Claude Code?
Run `npx skills add jdevalk/skills --skill metadata-check -a claude-code`. Or copy the skill folder (metadata-check in jdevalk/skills) into .claude/skills/metadata-check in your project. Claude Code loads it when a task matches its description.
How do I install Metadata Check in Codex?
Run `npx skills add jdevalk/skills --skill metadata-check -a codex`. Or copy the skill folder (metadata-check in jdevalk/skills) into .agents/skills/metadata-check in your project. Codex loads it when a task matches its description.
Can I use Metadata Check in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jdevalk/skills --skill metadata-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/metadata-check, .gemini/skills/metadata-check, .github/skills/metadata-check and .opencode/skills/metadata-check in your project.
What does Metadata Check need to run?
SKILL.md names no scripts, command-line tools or credentials: Metadata Check is instructions for the agent only.
Does Metadata Check access the network?
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.
Is Metadata Check safe to install?
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.
What licence does Metadata Check use?
Metadata Check is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Metadata Check use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Metadata Check?
Skills that share tags, products or a category with Metadata Check: SEO Setup (alisamadiii/Portfolio, 180 stars), SEO Content Optimization (magnus919/hermes-profiles, 278 stars), SEO (gridaco/grida, 2.7k stars) and Message House Builder (aaron-he-zhu/aaron-marketing-skills, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Metadata Check?
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.