No Comments
cursor/plugins
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
Fetches a Drupal.org issue with all its comments and analyses whether the "Proposed resolution" in the issue summary matches the current discussion consensus.
No licenceAuto-check passed
Install Drupalorg Issue Summary Update
$ npx skills add mglaman/drupalorg-cli --skill drupalorg-issue-summary-update -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mglaman/drupalorg-cli drupalorg-issue-summary-update --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/mglaman/drupalorg-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skill-data/drupalorg-issue-summary-update .claude/skills/drupalorg-issue-summary-update && 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 "drupalorg-issue-summary-update" agent skill from https://github.com/mglaman/drupalorg-cli/tree/main/skill-data/drupalorg-issue-summary-update into .claude/skills/drupalorg-issue-summary-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "drupalorg-issue-summary-update", 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/mglaman/drupalorg-cli/tree/main/skill-data/drupalorg-issue-summary-updateType 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 mglaman/drupalorg-cli --skill drupalorg-issue-summary-update -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mglaman/drupalorg-cli drupalorg-issue-summary-update --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mglaman/drupalorg-cli.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skill-data/drupalorg-issue-summary-update .agents/skills/drupalorg-issue-summary-update && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "drupalorg-issue-summary-update" agent skill from https://github.com/mglaman/drupalorg-cli/tree/main/skill-data/drupalorg-issue-summary-update into .agents/skills/drupalorg-issue-summary-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "drupalorg-issue-summary-update", 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 mglaman/drupalorg-cli --skill drupalorg-issue-summary-update -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mglaman/drupalorg-cli drupalorg-issue-summary-update --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mglaman/drupalorg-cli.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skill-data/drupalorg-issue-summary-update .cursor/skills/drupalorg-issue-summary-update && 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 "drupalorg-issue-summary-update" agent skill from https://github.com/mglaman/drupalorg-cli/tree/main/skill-data/drupalorg-issue-summary-update into .cursor/skills/drupalorg-issue-summary-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "drupalorg-issue-summary-update", 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/mglaman/drupalorg-cli.git --path skill-data/drupalorg-issue-summary-update--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 mglaman/drupalorg-cli --skill drupalorg-issue-summary-update -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mglaman/drupalorg-cli drupalorg-issue-summary-update --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mglaman/drupalorg-cli.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skill-data/drupalorg-issue-summary-update .gemini/skills/drupalorg-issue-summary-update && 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 "drupalorg-issue-summary-update" agent skill from https://github.com/mglaman/drupalorg-cli/tree/main/skill-data/drupalorg-issue-summary-update into .gemini/skills/drupalorg-issue-summary-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "drupalorg-issue-summary-update", 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 mglaman/drupalorg-cli drupalorg-issue-summary-updateInstalls 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 mglaman/drupalorg-cli --skill drupalorg-issue-summary-update -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mglaman/drupalorg-cli.git skills-src && mkdir -p .github/skills && cp -r skills-src/skill-data/drupalorg-issue-summary-update .github/skills/drupalorg-issue-summary-update && 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 "drupalorg-issue-summary-update" agent skill from https://github.com/mglaman/drupalorg-cli/tree/main/skill-data/drupalorg-issue-summary-update into .github/skills/drupalorg-issue-summary-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "drupalorg-issue-summary-update", 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 mglaman/drupalorg-cli --skill drupalorg-issue-summary-update -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mglaman/drupalorg-cli drupalorg-issue-summary-update --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mglaman/drupalorg-cli.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skill-data/drupalorg-issue-summary-update .opencode/skills/drupalorg-issue-summary-update && 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 "drupalorg-issue-summary-update" agent skill from https://github.com/mglaman/drupalorg-cli/tree/main/skill-data/drupalorg-issue-summary-update into .opencode/skills/drupalorg-issue-summary-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "drupalorg-issue-summary-update", 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
drupalorg-issue-summary-update- GitHub stars
- 168
- Token cost
- ~986 tokens
- SKILL.md length
- 475 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- None found
At a glance
Fetches a Drupal.org issue with all its comments and analyses whether the "Proposed resolution" in the issue summary matches the current discussion consensus.
- Works in 4 steps: Detect issue type → Fetch issue with comments → Draft updated summary → …
- SKILL.md covers Instructions and Notes
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Drupalorg Issue Summary Update is an agent skill from mglaman/drupalorg-cli. Fetches a Drupal.org issue with all its comments and analyses whether the "Proposed resolution" in the issue summary matches the current discussion consensus. Drafts an updated summary for the user to paste back.
Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: A command line tool for interfacing with Drupal.org.
Example prompts
- “Proposed resolution”
- “Use the drupalorg-issue-summary-update skill to fetch a Drupal.org issue with all its comments and analyses whether the "Proposed resolution" in the…”
- “/drupalorg-issue-summary-update”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Detect issue type
- Fetch issue with comments
- Draft updated summary
- Guide the user to apply the update
What it can do on your machine
Read from SKILL.md and the folder at commit 9b085ab. 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 bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
drupal.org
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
Drupalorg Issue Summary Update loads about 986 tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 475 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 475 words (~986 tokens).
“Purpose: Ensure a Drupal.org issue summary's "Proposed resolution" reflects the latest discussion in the comments.”
- name
- drupalorg-issue-summary-update
Files
Just SKILL.md in skill-data/drupalorg-issue-summary-update of mglaman/drupalorg-cli.
Open the folder on GitHubat commit 9b085ab
Compare with similar skills
Drupalorg Issue Summary Update 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 |
|---|---|---|---|---|---|---|
| Drupalorg Issue Summary Update this skillmglaman/drupalorg-cli | 168 | — | ~986 | Automated safety check: Pass | None | |
| No Commentscursor/plugins | 10k | 7 repos | ~640 | Automated safety check: Pass | None | |
| Commentsanthropics/claude-for-legal | 9.6k | 1 repos | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Clean Up Commentsthedaviddias/Front-End-Checklist | 74k | — | ~435 | Automated safety check: Pass | MIT | |
| Comment Checkercode-yeongyu/oh-my-openagent | 70k | — | ~160 | Automated safety check: Pass | Custom licence | |
| Writing Commentswithastro/astro | 63k | — | ~2.7k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
- Official
Comments
anthropics/claude-for-legal
Review open NPRM comment periods, log decisions, track deadlines.
Clean Up Comments
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Remove comments and debug code in production.
Comment Checker
code-yeongyu/oh-my-openagent
A skill your agent uses when Codex needs to understand or respond to automatic comment-checker feedback emitted after an edit-like PostToolUse hook.
- Official
Writing Comments
withastro/astro
How to write JSDoc (/ /) and inline (//) comments in the Astro codebase, for contributors reading the source — not end users.
- Official
PR Review State Fetch
prisma/orm
Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.
More from mglaman/drupalorg-cli
Drupalorg CLI
mglaman/drupalorg-cli
CLI for Drupal.org issue lifecycle management. An agent skill from mglaman/drupalorg-cli.
Drupalorg Work On Issue
mglaman/drupalorg-cli
Agentic workflow for contributing to a Drupal.org issue via GitLab MR.
Drupalorg Issue Search
mglaman/drupalorg-cli
Search for Drupal.org issues by keyword. An agent skill from mglaman/drupalorg-cli.
Questions about Drupalorg Issue Summary Update
What does Drupalorg Issue Summary Update do?
Fetches a Drupal.org issue with all its comments and analyses whether the "Proposed resolution" in the issue summary matches the current discussion consensus. Drupalorg Issue Summary Update is an agent skill from mglaman/drupalorg-cli.org issue with all its comments and analyses whether the "Proposed resolution" in the issue summary matches the current discussion consensus.
How do I install Drupalorg Issue Summary Update in Claude Code?
Run `npx skills add mglaman/drupalorg-cli --skill drupalorg-issue-summary-update -a claude-code`. Or copy the skill folder (skill-data/drupalorg-issue-summary-update in mglaman/drupalorg-cli) into .claude/skills/drupalorg-issue-summary-update in your project. Claude Code loads it when a task matches its description.
How do I install Drupalorg Issue Summary Update in Codex?
Run `npx skills add mglaman/drupalorg-cli --skill drupalorg-issue-summary-update -a codex`. Or copy the skill folder (skill-data/drupalorg-issue-summary-update in mglaman/drupalorg-cli) into .agents/skills/drupalorg-issue-summary-update in your project. Codex loads it when a task matches its description.
Can I use Drupalorg Issue Summary Update 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 mglaman/drupalorg-cli --skill drupalorg-issue-summary-update -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/drupalorg-issue-summary-update, .gemini/skills/drupalorg-issue-summary-update, .github/skills/drupalorg-issue-summary-update and .opencode/skills/drupalorg-issue-summary-update in your project.
What does Drupalorg Issue Summary Update need to run?
SKILL.md names no scripts, command-line tools or credentials: Drupalorg Issue Summary Update is instructions for the agent only.
Does Drupalorg Issue Summary Update access the network?
SKILL.md names 1 domain. As links in the text: drupal.org. This is read from the text; nothing was executed.
Is Drupalorg Issue Summary Update 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 Drupalorg Issue Summary Update use?
No licence was found for Drupalorg Issue Summary Update or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Drupalorg Issue Summary Update use?
About 986 tokens (SKILL.md is roughly 3.9k 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 Drupalorg Issue Summary Update?
Skills that share tags, products or a category with Drupalorg Issue Summary Update: No Comments (cursor/plugins, 10k stars), Comments (anthropics/claude-for-legal, 9.6k stars), Clean Up Comments (thedaviddias/Front-End-Checklist, 74k stars) and Comment Checker (code-yeongyu/oh-my-openagent, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Drupalorg Issue Summary Update?
mglaman (a GitHub user) maintains it in mglaman/drupalorg-cli, which has 168 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 22, 2026.
Source: mglaman/drupalorg-cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.