New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Groom Issue

by yamcodes in yamcodes/arkenv

Groom a poorly written issue by grilling the user to clarify requirements, updating the issue on GitHub via the gh cli, and utilizing the triage skill to apply the correct label and add an agent…

MITAuto-check passedAgent Workflows

Install Groom Issue

skills CLI
$ npx skills add yamcodes/arkenv --skill groom-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install yamcodes/arkenv groom-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/groom-issue .claude/skills/groom-issue && rm -rf skills-src

Use ~/.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/

Facts

Skill name
groom-issue
GitHub stars
145
Token cost
~1k tokens
SKILL.md length
467 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

Groom a poorly written issue by grilling the user to clarify requirements, updating the issue on GitHub via the gh cli, and utilizing the triage skill to apply the correct label and add an agent…

  • Works in 4 steps: Context gathering & initial assessment → Grilling / requirement clarification (if… → Fleshing out the issue on GitHub → …
  • The user wants to groom
  • SKILL.md covers Trigger and Workflow
  • Calls gh

What it does

Groom Issue is an agent skill from yamcodes/arkenv. Groom a poorly written issue by grilling the user to clarify requirements, updating the issue on GitHub via the gh cli, and utilizing the triage skill to apply the correct label and add an agent brief if necessary. Use when the user wants to groom, flesh out, or clarify a poorly written issue.

Its SKILL.md is about 1k 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 Agent Workflows, covering Requirements gathering. It works with GitHub. The repository describes itself as: ⛯ Typesafe environment variables with ArkType, Zod, or Valibot. The licence is MIT.

When your agent uses it

  • The user wants to groom
  • Clarify a poorly written issue

Example prompts

  • “/groom-issue”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Context gathering & initial assessment
  2. Grilling / requirement clarification (if needed)
  3. Fleshing out the issue on GitHub
  4. Triage & agent brief

What it can do on your machine

Read from SKILL.md and the folder at commit 74b3732. 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

Groom Issue loads about 1k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 467 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~77
When it runs · the whole SKILL.md, loaded when a task matches
~1k

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

The full file from yamcodes/arkenv at commit 74b3732, republished under its MIT licence (© yamcodes). 467 words, ~1,029 tokens.

Download SKILL.mdSave it as .claude/skills/groom-issue/SKILL.md (or your agent's skills folder).
name
groom-issue
description
Groom a poorly written issue by grilling the user to clarify requirements, updating the issue on GitHub via the gh cli, and utilizing the triage skill to apply the correct label and add an agent brief if necessary. Use when the user wants to groom, flesh out, or clarify a poorly written issue.
metadata.internal
true

Groom issue

This skill takes a poorly written, ambiguous, or incomplete issue, conducts an interactive grilling session with the user to clarify requirements, updates the issue on GitHub using the GitHub CLI (gh), and utilizes the existing /triage skill workflow to apply the correct canonical labels and post an authoritative agent brief.

Trigger

Use this skill whenever the user says /groom-issue <number> or asks to "groom", "clarify", "flesh out", or "improve" a poorly written issue.

Workflow

1. Context gathering & initial assessment

Before asking any questions, you MUST examine the current state of the issue and the surrounding codebase.

  1. Retrieve Issue Details: Fetch the issue context, including title, body, comments, and labels using the GitHub CLI:
    bash
    gh issue view <issue-number> --json title,body,labels,comments
  2. Analyze Requirements: Evaluate the issue description and existing comments. Identify gaps, ambiguities, missing edge cases, unclear desired behavior, or lacking acceptance criteria.
  3. Explore Codebase: Explore the repository to understand the domain model and existing implementations relevant to the issue. Refer to the project's domain glossary (docs/CONTEXT.md), ADRs (docs/adr/), and prior rejections (.out-of-scope/*.md).
2. Grilling / requirement clarification (if needed)

If the issue is vague, poorly written, or lacks concrete acceptance criteria, conduct a rigorous interview session with the user (following the principles of /grill-with-docs):

  1. Ask One Question at a Time: Interview the user relentlessly about every aspect of the issue until reaching a shared understanding.
  2. Wait for Feedback: Present your recommended answer/approach for each question and wait for the user's confirmation before proceeding to the next question.
  3. Probe Specifics: Challenge fuzzy language, establish clear boundaries between domain concepts, and explore concrete edge cases and error conditions.
Show full SKILL.md (222 more words)Show less
3. Fleshing out the issue on GitHub

Once the requirements are fully clarified and agreed upon:

  1. Synthesize Refined Specification: Format the clarified requirements into a clean, comprehensive issue body. Ensure it includes:
    • A clear problem statement
    • Detailed desired behavior
    • Concrete, testable acceptance criteria
  2. Update Issue on GitHub: Use the GitHub CLI to update the issue body (and title if appropriate):
    bash
    gh issue edit <issue-number> --body "<refined-issue-body>"
4. Triage & agent brief

At the end of the grooming process, you MUST utilize the existing /triage skill workflow (refer to skills/triage/SKILL.md and skills/triage/AGENT-BRIEF.md) to properly classify and prepare the issue:

  1. Determine Triage Roles: Identify the correct category role (bug or enhancement) and state role (ready-for-agent, ready-for-human, needs-info, wontfix, etc.) based on the triage skill guidelines.
  2. Apply Triage Labels: Use the GitHub CLI to apply the correct canonical labels to the issue:
    bash
    gh issue edit <issue-number> --add-label "<category-role>,<state-role>"
    (Note: Remove any conflicting or outdated triage state labels if necessary).
  3. Post Agent Brief (If Applicable): If the issue is transitioned to ready-for-agent or ready-for-human, generate a durable, behavioral agent brief following the principles and template in skills/triage/AGENT-BRIEF.md. Post it as a comment on the issue:
    bash
    gh issue comment <issue-number> --body "<agent-brief-content>"
    (If transitioned to needs-info or wontfix, follow the corresponding comment or closing procedures defined in the triage skill).

© yamcodes, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/groom-issue of yamcodes/arkenv.

Open the folder on GitHubat commit 74b3732

Compare with similar skills

Groom Issue 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.

Groom Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Groom Issue this skillyamcodes/arkenv145—~1kAutomated safety check: PassMIT
Agentic Workflow Designerdotnet/Open-XML-SDK4.6k2 repos~3.5kAutomated safety check: PassMIT
DBS Skill Makerdontbesilent2025/dbskill11k—~1.2kAutomated safety check: PassCustom licence
Ask NavigatorYeachan-Heo/oh-my-claudecode40k—~4.1kAutomated safety check: PassMIT
Readoutwarpdotdev/common-skills608—~2kAutomated safety check: PassMIT
Ouroboros Command ReferenceQ00/ouroboros6.2k—~1.8kAutomated safety check: PassMIT

Similar skills

  • Agentic Workflow Designer

    dotnet/Open-XML-SDK

    Official

    Interviews you one question at a time about goal, trigger, permissions and data needs, then drafts a single agentic workflow markdown file.

    4.6k GitHub starsUsed in 2 repos~3.5k tokens
    Agent WorkflowsAuto-check passed

  • DBS Skill Maker

    dontbesilent2025/dbskill

    Turns a problem you keep running into into a single installable, tested skill, and prepares a GitHub repository only when you ask to share it.

    11k GitHub stars~1.2k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Ask Navigator

    Yeachan-Heo/oh-my-claudecode

    Charts a foggy effort into a map of decision tickets on the repo's issue tracker and works through them one per session, producing decisions rather than deliverables.

    40k GitHub stars~4.1k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Readout

    warpdotdev/common-skills

    Produce a polished, self-contained HTML "readout" document under ~/.readouts (with an auto-maintained index page), either by snapshotting the findings accumulated in the current conversation or —…

    608 GitHub stars~2k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Ouroboros Command Reference

    Q00/ouroboros

    Reference guide to the Ouroboros commands and agents, covering interviews, seed specs, evaluation, lateral-thinking personas and the evolutionary loop.

    6.2k GitHub stars~1.8k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Dev Request

    FHIR/fhir-codegen

    Drafts and iterates on local-development feature requests in the role of a staff-level Product Manager.

    154 GitHub stars~3.8k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from yamcodes/arkenv

All 20 skills in this repo

  • Hallmark

    yamcodes/arkenv

    Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots.

    145 GitHub starsUsed in 4 repos~18k tokens
    Auto-check passed

  • Bulletproof React

    yamcodes/arkenv

    Bulletproof React architecture patterns for scalable, maintainable applications.

    145 GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Arkenv

    yamcodes/arkenv

    Answer questions about ArkEnv and help implement environment variable validation.

    145 GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Code Review

    yamcodes/arkenv

    Fetch, analyze, and address code reviews and comments on GitHub, or perform a code review on changes in the workspace.

    145 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Forward Port

    yamcodes/arkenv

    Manually forward-ports merged dev (v0) changes to the v1 branch, adapting code to v1's package layout and changeset names.

    145 GitHub stars~970 tokensUpdated today
    Auto-check passed

  • Internalize Skill

    yamcodes/arkenv

    Move newly installed skills from '.agents/skills/' to the project's root 'skills/' directory, with options to rename and attribute them, and mark them as internal.

    145 GitHub stars~750 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Groom Issue

What does Groom Issue do?

Groom a poorly written issue by grilling the user to clarify requirements, updating the issue on GitHub via the gh cli, and utilizing the triage skill to apply the correct label and add an agent…. Groom Issue is an agent skill from yamcodes/arkenv. Groom a poorly written issue by grilling the user to clarify requirements, updating the issue on GitHub via the gh cli, and utilizing the triage skill to apply the correct label and add an agent brief if necessary.

When should I use Groom Issue?

Groom Issue fits situations like: the user wants to groom; clarify a poorly written issue.

How do I install Groom Issue in Claude Code?

Run `npx skills add yamcodes/arkenv --skill groom-issue -a claude-code`. Or copy the skill folder (skills/groom-issue in yamcodes/arkenv) into .claude/skills/groom-issue in your project. Claude Code loads it when a task matches its description.

How do I install Groom Issue in Codex?

Run `npx skills add yamcodes/arkenv --skill groom-issue -a codex`. Or copy the skill folder (skills/groom-issue in yamcodes/arkenv) into .agents/skills/groom-issue in your project. Codex loads it when a task matches its description.

Can I use Groom Issue 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 yamcodes/arkenv --skill groom-issue -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-issue, .gemini/skills/groom-issue, .github/skills/groom-issue and .opencode/skills/groom-issue in your project.

What does Groom Issue need to run?

Going by SKILL.md and its folder, Groom Issue needs the command-line tools its instructions call (gh).

Does Groom Issue 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 Groom Issue 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 Groom Issue use?

Groom Issue is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Groom Issue use?

About 1k tokens (SKILL.md is roughly 4.1k 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 Groom Issue?

Skills that share tags, products or a category with Groom Issue: Agentic Workflow Designer (dotnet/Open-XML-SDK, 4.6k stars), DBS Skill Maker (dontbesilent2025/dbskill, 11k stars), Ask Navigator (Yeachan-Heo/oh-my-claudecode, 40k stars) and Readout (warpdotdev/common-skills, 608 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Groom Issue?

yamcodes (a GitHub user) maintains it in yamcodes/arkenv, which has 145 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 8, 2026.

Source: yamcodes/arkenv on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.