Release Blog Drafter
obot-platform/obot
Drafts a release announcement blog post for an obot release as a Markdown file, with an optional WordPress draft through MCP and no live publishing without confirmation.
Groom a single GitHub issue — produce an implementation spec and optionally post the grooming summary as a GitHub comment.
$ npx skills add wp-media/wp-rocket --skill groom -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install wp-media/wp-rocket groom --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/wp-media/wp-rocket.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/groom .claude/skills/groom && 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 "groom" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/groom into .claude/skills/groom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "groom", 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/wp-media/wp-rocket/tree/develop/.claude/skills/groomType 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 wp-media/wp-rocket --skill groom -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install wp-media/wp-rocket groom --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/groom .agents/skills/groom && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "groom" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/groom into .agents/skills/groom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "groom", 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 wp-media/wp-rocket --skill groom -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install wp-media/wp-rocket groom --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/groom .cursor/skills/groom && 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 "groom" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/groom into .cursor/skills/groom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "groom", 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/wp-media/wp-rocket.git --path .claude/skills/groom--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 wp-media/wp-rocket --skill groom -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install wp-media/wp-rocket groom --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/groom .gemini/skills/groom && 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 "groom" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/groom into .gemini/skills/groom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "groom", 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 wp-media/wp-rocket groomInstalls 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 wp-media/wp-rocket --skill groom -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/groom .github/skills/groom && 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 "groom" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/groom into .github/skills/groom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "groom", 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 wp-media/wp-rocket --skill groom -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install wp-media/wp-rocket groom --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/groom .opencode/skills/groom && 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 "groom" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/groom into .opencode/skills/groom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "groom", 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.
groomGroom a single GitHub issue — produce an implementation spec and optionally post the grooming summary as a GitHub comment.
Groom is an agent skill from wp-media/wp-rocket. Groom a single GitHub issue — produce an implementation spec and optionally post the grooming summary as a GitHub comment. Standalone entry point for the grooming-agent.
Its SKILL.md is about 690 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with GitHub and WordPress. The repository describes itself as: Performance optimization plugin for WordPress. The licence is GPL-2.0.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 3a96b66. 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.
Shell commands in SKILL.md call:
ghbashFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
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.
Groom loads about 685 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 294 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 wp-media/wp-rocket at commit 3a96b66, republished under its GPL-2.0 licence (© wp-media). 294 words, ~685 tokens.
.claude/skills/groom/SKILL.md (or your agent's skills folder).Standalone grooming for a single issue. Runs the full grooming analysis and writes the spec to disk. Posting to GitHub is your choice — you are prompted at the end.
This skill targets wp-media/wp-rocket. The issue and spec files live at the wp-rocket
temp convention:
.TemporaryItems/Issues/wp-rocket/issues/<N>.md.TemporaryItems/Issues/wp-rocket/issues/<N>-spec.mdEnsure the issue file exists at .TemporaryItems/Issues/wp-rocket/issues/<N>.md. Run:
bash .claude/skills/issue-workflow/scripts/issue-sync.sh <N>If the file already exists and is recent (less than 5 minutes old), skip the sync.
Invoke the grooming-agent sub-agent with the following invocation context:
Issue number:
<N>Issue file path:.TemporaryItems/Issues/wp-rocket/issues/<N>.mdRepo:wp-media/wp-rocketcomplexity_signal: derive from the issue content yourselfSTANDALONE MODE — two differences from the normal pipeline run:
- Skip Step 5 (posting to GitHub). Instead, include the full comment body you would have posted in a section titled
## Grooming Comment Draftat the end of your response. Use exactly the same format the pipeline would post (including the<!-- ai-pipeline:grooming-plan -->marker), so it is ready to post as-is.- Skip the StructuredOutput JSON return. Return a short human-readable summary instead: effort, risk, complexity, and any open questions.
The spec file is still written to .TemporaryItems/Issues/wp-rocket/issues/<N>-spec.md as normal.
After the agent responds, display its ## Grooming Comment Draft to the user, then ask:
Post this as a comment on issue #<N>? Reply
yesto post as-is,noto finish without posting, or paste edited text to post a modified version.
If yes — check for an existing grooming comment first (dedup):
EXISTING_ID=$(gh api repos/wp-media/wp-rocket/issues/<N>/comments \
--jq '[.[] | select(.body | contains("<!-- ai-pipeline:grooming-plan -->"))] | last | .id // empty')Update with gh api --method PATCH repos/wp-media/wp-rocket/issues/comments/$EXISTING_ID if found, otherwise post a new comment.
If no — confirm the spec was written to .TemporaryItems/Issues/wp-rocket/issues/<N>-spec.md and finish.
If edited — use the user-provided text as the comment body and post.
© wp-media, GPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/groom of wp-media/wp-rocket.
Open the folder on GitHubat commit 3a96b66
Groom 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 |
|---|---|---|---|---|---|---|
| Groom this skillwp-media/wp-rocket | 767 | — | ~685 | Automated safety check: Pass | GPL-2.0 | |
| Release Blog Drafterobot-platform/obot | 1.1k | — | ~4.6k | Automated safety check: Pass | MIT | |
| Wp 71 Dev Note IssuesWordPress/Documentation-Issue-Tracker | 109 | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Deploy To Hostinghostinger/api-mcp-server | 159 | — | ~2.7k | Automated safety check: Notes | MIT | |
| Wjs Converting Wp To Hugojianshuo/claude-skills | 131 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Wporg Forum Triageduracelltomi/gtm4wp | 174 | — | ~6.1k | Automated safety check: Warn | GPL-2.0-or-later |
obot-platform/obot
Drafts a release announcement blog post for an obot release as a Markdown file, with an optional WordPress draft through MCP and no live publishing without confirmation.
WordPress/Documentation-Issue-Tracker
Create missing WordPress 7.1 Dev Note and Field Guide tracking issues from 7-1-dev-notes/tickets.json in WordPress/Documentation-Issue-Tracker.
hostinger/api-mcp-server
Deploy an existing project to a website on Hostinger web hosting (Shared, Cloud or Agency plans) and keep it deployed: picks the right deploy for static sites, Node.js apps (Next.js, Nuxt, Express…
jianshuo/claude-skills
A skill your agent uses when migrating a WordPress site to a Hugo static site on GitHub Pages from a WXR export (.xml) plus the wp-content/uploads folder — preserving /archives/<id/ URLs, localizing…
duracelltomi/gtm4wp
Triage GTM4WP support topics and reviews on the wordpress.org forum — read a topic (or a batch), work out whether it is already fixed in a released version, classify it, screen for security…
joseconti/declaracion-renta-espana
A skill your agent uses for ANY new software project from idea to release — websites, WordPress/WooCommerce plugins, MCP servers, web apps, components, or libraries.
wp-media/wp-rocket
Read and refresh wp-rocket's pre-built dependency graph at .claude/graph/dependency-graph.json.
wp-media/wp-rocket
A skill your agent uses when modifying templates, admin UI, output, hooks, plugin metadata, sanitization, escaping, or any code that must remain compliant with WordPress.org and repository PHPCS…
wp-media/wp-rocket
A skill your agent uses when changing service structure, Subscribers, ServiceProviders, Container wiring, bootstrapping, Context classes, or any code that may affect the core caching engine in WP…
wp-media/wp-rocket
Adversarially review a grooming spec before implementation starts.
wp-media/wp-rocket
Check a change against WordPress.org plugin rules and PHPCS standards.
wp-media/wp-rocket
Update developer-facing documentation to reflect code changes on the current branch.
Groom a single GitHub issue — produce an implementation spec and optionally post the grooming summary as a GitHub comment. Groom is an agent skill from wp-media/wp-rocket. Groom a single GitHub issue — produce an implementation spec and optionally post the grooming summary as a GitHub comment.
Run `npx skills add wp-media/wp-rocket --skill groom -a claude-code`. Or copy the skill folder (.claude/skills/groom in wp-media/wp-rocket) into .claude/skills/groom in your project. Claude Code loads it when a task matches its description.
Run `npx skills add wp-media/wp-rocket --skill groom -a codex`. Or copy the skill folder (.claude/skills/groom in wp-media/wp-rocket) into .agents/skills/groom 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 wp-media/wp-rocket --skill groom -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/groom, .gemini/skills/groom, .github/skills/groom and .opencode/skills/groom in your project.
Going by SKILL.md and its folder, Groom needs the command-line tools its instructions call (gh and bash).
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. 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.
Groom is published under the GPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 685 tokens (SKILL.md is roughly 2.7k 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 Groom: Release Blog Drafter (obot-platform/obot, 1.1k stars), Wp 71 Dev Note Issues (WordPress/Documentation-Issue-Tracker, 109 stars), Deploy To Hosting (hostinger/api-mcp-server, 159 stars) and Wjs Converting Wp To Hugo (jianshuo/claude-skills, 131 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
wp-media (a GitHub organization) maintains it in wp-media/wp-rocket, which has 767 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 8, 2026.
Source: wp-media/wp-rocket on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.