This repository collects agent skills that improve your GitHub presence, WordPress plugins, EmDash plugins, Astro sites, and the readability of your writing. You can audit and improve GitHub repos and profile pages, set up CI/CD pipelines for WordPress and EmDash plugins, rewrite WordPress.org readme files for better search rankings, audit Astro site SEO end-to-end, and run a readability pass on drafts. Each skill is a structured, score-based workflow that produces drop-in replacements.
Install a single skill or all of them via the skills CLI:
# One skill
npx skills add jdevalk/skills --skill astro-seo
# All skills in this repo
npx skills add jdevalk/skillsThe CLI supports Claude Code, Cursor, Cline, GitHub Copilot, and 20+ other agents. Use --agent to pick which ones.
# Update all installed skills
npx skills update
# Update a single skill
npx skills update astro-seoOptional: auto-check on session start. Add a SessionStart hook to your Claude Code settings.json so stale skills are flagged before you hit them:
{
"hooks": {
"SessionStart": [
{
"type": "command",
"command": "npx skills update -g -y 2>/dev/null"
}
]
}
}This runs outside the context window on every session start, /clear, and compaction — zero token cost. If the latency bothers you on /clear, scope it to startup only by checking the source field in the hook input.
Audits a GitHub repository against best practices and generates the files that make a repo look professional: README, CONTRIBUTING.md, SECURITY.md, issue/PR templates, and more. Scores six categories out of 60 and produces drop-in replacements for anything that's missing or weak.
Trigger phrases: "improve my repo", "set up issue templates", "make my GitHub project look professional"
Sources
- Joost de Valk — How to create a healthy GitHub repository
- GitHub Docs — About READMEs
- GitHub Docs — Setting guidelines for repository contributors
- GitHub Docs — Creating a default community health file
- GitHub Docs — Configuring issue templates for your repository
- GitHub Docs — About rulesets
- GitHub Docs — Customizing your repository's social media preview
Reviews a GitHub profile page — bio, pinned repos, profile README, stats widgets, contribution visibility — and generates an optimized profile README. Works for both personal and organization profiles.
Trigger phrases: "make my GitHub look good", "create a profile README", "optimize my developer profile"
Sources
- Joost de Valk — Good-looking GitHub profile pages
- GitHub Docs — Managing your profile README
- GitHub Docs — About your profile
- GitHub Docs — Customizing your organization's profile
- GitHub Docs — Contributions on your profile
Sets up a complete GitHub Actions CI/CD pipeline for WordPress plugins. The skill analyzes your plugin's structure — Composer, JS/CSS assets, tests, WordPress.org listing — and picks the workflows you need. Coverage includes:
- Coding standards (WPCS/PHPCS)
- PHP and JS/CSS linting
- PHPUnit testing and PHPStan static analysis
- Composer security scanning
- WordPress Playground PR previews
- Automated deployment to WordPress.org
Trigger phrases: "add CI to my WordPress plugin", "set up GitHub Actions for my plugin", "deploy my plugin to WordPress.org automatically"
Sources
- Joost de Valk — GitHub Actions to keep your WordPress plugin healthy
- 10up/wpcs-action — WordPress Coding Standards GitHub Action
- 10up/action-wordpress-plugin-deploy — Deploy to WordPress.org
- WordPress/action-wp-playground-pr-preview — Playground PR previews
- WordPress Developer Blog — How to add automated unit tests to your WordPress plugin
Sets up GitHub Actions CI/CD workflows for EmDash plugins. The skill analyzes your plugin's structure — TypeScript source, React admin UI, tests, npm publishing — and picks the workflows you need. Coverage includes:
- TypeScript type-checking with
emdashtypes - ESLint linting
- Vitest testing
- npm security auditing
- Automated npm publishing on release
Trigger phrases: "add CI to my EmDash plugin", "set up GitHub Actions for my EmDash plugin", "publish my EmDash plugin to npm automatically"
Sources
- EmDash CMS — Full-stack TypeScript CMS based on Astro
- GitHub Docs — Publishing Node.js packages
- TypeScript Docs — Compiler Options
Reviews a WordPress.org plugin readme.txt with a structured audit, scores each section, and produces a fully rewritten version optimized for search visibility and install conversion.
Trigger phrases: "optimize my readme", "review my plugin listing", "make my plugin page better"
Sources
- Matt Cromwell — How I Optimize Plugin README's for Better Search Results
- Freemius — Outrank Competitors' SEO on the WordPress.org Plugin Repository
- Freemius — A Guide to Optimizing Your Plugin's WordPress.org Page
- WordPress Plugin Handbook — How Your Plugin Assets Work
- SitePoint — How To Create an Awesome WordPress Page for Your Plugin
Audits and improves SEO for Astro sites across nine categories: the <Seo> component and head metadata, linked JSON-LD graphs, content-collection Zod schemas, auto-generated Open Graph images, per-collection sitemaps with git-based lastmod, IndexNow submission, schema endpoints and schema maps for agent discovery, redirects and FuzzyRedirect, and performance defaults. The stack is opinionated and routes most fixes through @jdevalk/astro-seo-graph.
Trigger phrases: "audit my Astro SEO", "set up SEO for my Astro site", "add structured data to my Astro blog"
Sources
- Joost de Valk — Astro SEO: the definitive guide
@jdevalk/astro-seo-graph— the<Seo>component, schema endpoints, IndexNow, FuzzyRedirect, build validation@astrojs/sitemap— per-collection sitemaps- IndexNow — active indexing protocol
- NLWeb — agent discovery protocol
Runs a readability audit on a blog post draft, calibrated for readers who read English as a second language. The skill checks nine categories:
- Paragraph structure and lead sentences
- Opening paragraph strength
- Tiered sentence length
- Passive voice
- Difficult words (judged by L2 conversational use, not syllable count)
- Filler and hedging
- Transitions
- Variation
- Heading hierarchy
Output combines a Flesch Reading Ease score (with target bands) and a per-category status. Each issue quotes the problem text with a concrete fix, and specific passages that work get called out too. In technical posts, the skill holds non-technical paragraphs — intros, context, conclusions — to a stricter L2 standard than the technical sections.
Trigger phrases: "check readability", "is this readable", "readability pass"
Sources
- Yoast — Readability analysis in Yoast SEO
- Rudolf Flesch — Flesch Reading Ease formula
- Hemingway Editor — sentence-length tiering
Reviews short high-value strings — page titles, meta descriptions, schema description fields, FAQ answers, GitHub repo taglines, profile bios, social-card copy — where Flesch scoring and paragraph-level readability checks don't apply. Per string, the skill checks:
- Front-loading (most specific word near the start)
- Concreteness (names, numbers, specific claims)
- Aggressive filler and hedging removal
- Active voice
- No title/description duplication
- Difficult-word substitution
- Platform truncation fit (Google SERP, GitHub description, Twitter bio, OG)
- One idea per field
Output is per-string: the original, length, a ✓/⚠/✗ per check, and a concrete rewrite when something fails. Chained into by astro-seo, wp-readme-optimizer, github-repo, and github-profile for their metadata outputs.
Trigger phrases: "check my metadata", "review my tagline", "is this bio any good"
This project is licensed under the MIT License.