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.
Pick the option that matches your setup.
Download the .skill file for the skill you want from the latest release and open it — Claude installs it automatically.
.skill files are plain zip archives. Two ways to install the skill folder:
-
From a release. Download the
.skillfrom the latest release, unzip it, and move the resulting folder into your agent's skills directory (for Claude Code that's~/.claude/skills/). -
From the repo. Clone the repo and copy or symlink the skill folder:
git clone https://github.com/jdevalk/skills.git cp -r skills/astro-seo ~/.claude/skills/ # or, to stay in sync with upstream: ln -s "$(pwd)/skills/astro-seo" ~/.claude/skills/astro-seo
Each skill is self-contained: the folder holds a SKILL.md plus any referenced assets. If your agent uses a different skills directory, substitute that path.
Every skill carries a version: field in its frontmatter. On invocation, each skill fetches versions.json at the repo root and compares its own version to the manifest. If it's behind, the skill tells you and offers to update itself: with your consent, it downloads the matching .skill from the latest release and unpacks it over the installed skill directory. The unpack target is resolved from where the running skill actually lives, so this works for any agent — not just Claude Code — as long as its skills directory is writable. Decline and the skill continues on the current version; the check never blocks execution. CI validates that every SKILL.md's version: matches the versions.json entry for its directory, so the manifest and the shipped skills can't drift.
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
This project is licensed under the MIT License.