GitHub Issue Triage
duracelltomi/gtm4wp
Triage and manage GTM4WP GitHub issues — read an issue (or a batch), classify it, check for duplicates/already-fixed, screen for security disclosures, and draft a polite reply plus proposed labels.
Create missing WordPress 7.1 Dev Note and Field Guide tracking issues from 7-1-dev-notes/tickets.json in WordPress/Documentation-Issue-Tracker.
Install Wp 71 Dev Note Issues
$ npx skills add WordPress/Documentation-Issue-Tracker --skill wp-71-dev-note-issues -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install WordPress/Documentation-Issue-Tracker wp-71-dev-note-issues --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/WordPress/Documentation-Issue-Tracker.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/wp-71-dev-note-issues .claude/skills/wp-71-dev-note-issues && 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 "wp-71-dev-note-issues" agent skill from https://github.com/WordPress/Documentation-Issue-Tracker/tree/main/.github/skills/wp-71-dev-note-issues into .claude/skills/wp-71-dev-note-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-71-dev-note-issues", 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/WordPress/Documentation-Issue-Tracker/tree/main/.github/skills/wp-71-dev-note-issuesType 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 WordPress/Documentation-Issue-Tracker --skill wp-71-dev-note-issues -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install WordPress/Documentation-Issue-Tracker wp-71-dev-note-issues --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WordPress/Documentation-Issue-Tracker.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/wp-71-dev-note-issues .agents/skills/wp-71-dev-note-issues && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wp-71-dev-note-issues" agent skill from https://github.com/WordPress/Documentation-Issue-Tracker/tree/main/.github/skills/wp-71-dev-note-issues into .agents/skills/wp-71-dev-note-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-71-dev-note-issues", 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 WordPress/Documentation-Issue-Tracker --skill wp-71-dev-note-issues -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install WordPress/Documentation-Issue-Tracker wp-71-dev-note-issues --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WordPress/Documentation-Issue-Tracker.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/wp-71-dev-note-issues .cursor/skills/wp-71-dev-note-issues && 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 "wp-71-dev-note-issues" agent skill from https://github.com/WordPress/Documentation-Issue-Tracker/tree/main/.github/skills/wp-71-dev-note-issues into .cursor/skills/wp-71-dev-note-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-71-dev-note-issues", 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/WordPress/Documentation-Issue-Tracker.git --path .github/skills/wp-71-dev-note-issues--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 WordPress/Documentation-Issue-Tracker --skill wp-71-dev-note-issues -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install WordPress/Documentation-Issue-Tracker wp-71-dev-note-issues --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WordPress/Documentation-Issue-Tracker.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/wp-71-dev-note-issues .gemini/skills/wp-71-dev-note-issues && 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 "wp-71-dev-note-issues" agent skill from https://github.com/WordPress/Documentation-Issue-Tracker/tree/main/.github/skills/wp-71-dev-note-issues into .gemini/skills/wp-71-dev-note-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-71-dev-note-issues", 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 WordPress/Documentation-Issue-Tracker wp-71-dev-note-issuesInstalls 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 WordPress/Documentation-Issue-Tracker --skill wp-71-dev-note-issues -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/WordPress/Documentation-Issue-Tracker.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/wp-71-dev-note-issues .github/skills/wp-71-dev-note-issues && 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 "wp-71-dev-note-issues" agent skill from https://github.com/WordPress/Documentation-Issue-Tracker/tree/main/.github/skills/wp-71-dev-note-issues into .github/skills/wp-71-dev-note-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-71-dev-note-issues", 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 WordPress/Documentation-Issue-Tracker --skill wp-71-dev-note-issues -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install WordPress/Documentation-Issue-Tracker wp-71-dev-note-issues --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WordPress/Documentation-Issue-Tracker.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/wp-71-dev-note-issues .opencode/skills/wp-71-dev-note-issues && 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 "wp-71-dev-note-issues" agent skill from https://github.com/WordPress/Documentation-Issue-Tracker/tree/main/.github/skills/wp-71-dev-note-issues into .opencode/skills/wp-71-dev-note-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-71-dev-note-issues", 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
wp-71-dev-note-issues- GitHub stars
- 109
- Token cost
- ~1.6k tokens
- SKILL.md length
- 719 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Create missing WordPress 7.1 Dev Note and Field Guide tracking issues from 7-1-dev-notes/tickets.json in WordPress/Documentation-Issue-Tracker.
- Works in 5 steps: Confirm the current repository is… → Confirm GitHub CLI is authenticated with… → Confirm these repository labels exist → …
- Asked to import
- SKILL.md covers Source files, Eligible tickets, Authentication and repository… and Find existing issues, plus 5 more sections
- Calls gh
What it does
Wp 71 Dev Note Issues is an agent skill from 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. Use when asked to import, sync, or create GitHub issues for triaged WordPress 7.1 Trac tickets.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Issue triage. It works with WordPress and GitHub. The repository describes itself as: Issue Tracker for the WordPress Documentation team.
When your agent uses it
- Asked to import
- Create GitHub issues for triaged WordPress 7.1 Trac tickets
Example prompts
- “/wp-71-dev-note-issues”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Confirm the current repository is WordPress/Documentation-Issue-Tracker.
- Confirm GitHub CLI is authenticated with gh auth status.
- Confirm these repository labels exist
- Do not create, rename, or delete labels automatically.
- If any required label is missing, stop before creating issues and report it.
What it can do on your machine
Read from SKILL.md and the folder at commit 4377e0a. 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
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
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.
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
Wp 71 Dev Note Issues loads about 1.6k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 719 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 719 words (~1,622 tokens).
“Use this skill only in the WordPress/Documentation-Issue-Tracker repository.”
- name
- wp-71-dev-note-issues
Files
Just SKILL.md in .github/skills/wp-71-dev-note-issues of WordPress/Documentation-Issue-Tracker.
Open the folder on GitHubat commit 4377e0a
Compare with similar skills
Wp 71 Dev Note Issues 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 |
|---|---|---|---|---|---|---|
| Wp 71 Dev Note Issues this skillWordPress/Documentation-Issue-Tracker | 109 | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| GitHub Issue Triageduracelltomi/gtm4wp | 174 | — | ~4.7k | Automated safety check: Warn | GPL-2.0-or-later | |
| Setup Matt Pocock Skillsbestofjs/bestofjs | 3.1k | 20 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Windows App SDK Issue Triage Reportmicrosoft/WindowsAppSDK | 4.7k | — | ~3.4k | Automated safety check: Pass | Apache-2.0 | |
| Exposed Bug Fix WorkflowJetBrains/Exposed | 9.3k | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Pre-Release PR Triagejamiepine/voicebox | 57k | — | ~3.1k | Automated safety check: Pass | MIT |
Similar skills
Setup Matt Pocock Skills
bestofjs/bestofjs
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.
- Official
Windows App SDK Issue Triage Report
microsoft/WindowsAppSDK
Generates GitHub Feature Area Status reports for the Windows App SDK repository, scoring issues so teams can see what needs attention in each area.
- Official
Exposed Bug Fix Workflow
JetBrains/Exposed
Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.
Pre-Release PR Triage
jamiepine/voicebox
Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.
- Official
WinAppSDK Triage Meeting Prep
microsoft/WindowsAppSDK
Prepares the triage meeting summary for WinAppSDK Needs-Triage issues, with research-backed area suggestions, draft replies and a diff since the last triage.
More from WordPress/Documentation-Issue-Tracker
Wp 71 Release Metadata
WordPress/Documentation-Issue-Tracker
Populate or refresh 7-1-dev-notes/release-metadata.json from every JSON file in 7-1-dev-notes/components/ and validate it against release-metadata.schema.json.
Related
Categories
Questions about Wp 71 Dev Note Issues
What does Wp 71 Dev Note Issues do?
Create missing WordPress 7.1 Dev Note and Field Guide tracking issues from 7-1-dev-notes/tickets.json in WordPress/Documentation-Issue-Tracker. Wp 71 Dev Note Issues is an agent skill from WordPress/Documentation-Issue-Tracker.json in WordPress/Documentation-Issue-Tracker.
When should I use Wp 71 Dev Note Issues?
Wp 71 Dev Note Issues fits situations like: asked to import; create GitHub issues for triaged WordPress 7.1 Trac tickets.
How do I install Wp 71 Dev Note Issues in Claude Code?
Run `npx skills add WordPress/Documentation-Issue-Tracker --skill wp-71-dev-note-issues -a claude-code`. Or copy the skill folder (.github/skills/wp-71-dev-note-issues in WordPress/Documentation-Issue-Tracker) into .claude/skills/wp-71-dev-note-issues in your project. Claude Code loads it when a task matches its description.
How do I install Wp 71 Dev Note Issues in Codex?
Run `npx skills add WordPress/Documentation-Issue-Tracker --skill wp-71-dev-note-issues -a codex`. Or copy the skill folder (.github/skills/wp-71-dev-note-issues in WordPress/Documentation-Issue-Tracker) into .agents/skills/wp-71-dev-note-issues in your project. Codex loads it when a task matches its description.
Can I use Wp 71 Dev Note Issues 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 WordPress/Documentation-Issue-Tracker --skill wp-71-dev-note-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wp-71-dev-note-issues, .gemini/skills/wp-71-dev-note-issues, .github/skills/wp-71-dev-note-issues and .opencode/skills/wp-71-dev-note-issues in your project.
What does Wp 71 Dev Note Issues need to run?
Going by SKILL.md and its folder, Wp 71 Dev Note Issues needs the command-line tools its instructions call (gh).
Does Wp 71 Dev Note Issues access the network?
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.
Is Wp 71 Dev Note Issues 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 Wp 71 Dev Note Issues use?
Wp 71 Dev Note Issues has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Wp 71 Dev Note Issues use?
About 1.6k tokens (SKILL.md is roughly 6.5k 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 Wp 71 Dev Note Issues?
Skills that share tags, products or a category with Wp 71 Dev Note Issues: GitHub Issue Triage (duracelltomi/gtm4wp, 174 stars), Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars), Windows App SDK Issue Triage Report (microsoft/WindowsAppSDK, 4.7k stars) and Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wp 71 Dev Note Issues?
WordPress (a GitHub organization) maintains it in WordPress/Documentation-Issue-Tracker, which has 109 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on July 22, 2026.
Source: WordPress/Documentation-Issue-Tracker on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.