Agentic Workflow Designer
dotnet/Open-XML-SDK
Interviews you one question at a time about goal, trigger, permissions and data needs, then drafts a single agentic workflow markdown file.
Write a new issue from scratch by grilling the user to clarify requirements, creating the issue on GitHub via the gh cli, and utilizing the triage skill to apply the correct label and add an agent…
Install Write Issue
$ npx skills add yamcodes/arkenv --skill write-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install yamcodes/arkenv write-issue --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/yamcodes/arkenv.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/write-issue .claude/skills/write-issue && 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 "write-issue" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/write-issue into .claude/skills/write-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-issue", 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/yamcodes/arkenv/tree/v1/skills/write-issueType 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 yamcodes/arkenv --skill write-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install yamcodes/arkenv write-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/write-issue .agents/skills/write-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-issue" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/write-issue into .agents/skills/write-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-issue", 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 yamcodes/arkenv --skill write-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install yamcodes/arkenv write-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/write-issue .cursor/skills/write-issue && 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 "write-issue" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/write-issue into .cursor/skills/write-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-issue", 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/yamcodes/arkenv.git --path skills/write-issue--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 yamcodes/arkenv --skill write-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install yamcodes/arkenv write-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/write-issue .gemini/skills/write-issue && 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 "write-issue" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/write-issue into .gemini/skills/write-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-issue", 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 yamcodes/arkenv write-issueInstalls 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 yamcodes/arkenv --skill write-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/write-issue .github/skills/write-issue && 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 "write-issue" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/write-issue into .github/skills/write-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-issue", 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 yamcodes/arkenv --skill write-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install yamcodes/arkenv write-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/write-issue .opencode/skills/write-issue && 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 "write-issue" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/write-issue into .opencode/skills/write-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-issue", 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
write-issue- GitHub stars
- 145
- Token cost
- ~1k tokens
- SKILL.md length
- 472 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write a new issue from scratch by grilling the user to clarify requirements, creating 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 & creating it on… → …
- The user wants to write
- SKILL.md covers Trigger and Workflow
- Calls gh
What it does
Write Issue is an agent skill from yamcodes/arkenv. Write a new issue from scratch by grilling the user to clarify requirements, creating 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 write, create, draft, open, or file a new issue on GitHub.
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 write
- File a new issue on GitHub
Example prompts
- “/write-issue”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
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
Write Issue loads about 1k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 472 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
The full file from yamcodes/arkenv at commit 74b3732, republished under its MIT licence (© yamcodes). 472 words, ~1,010 tokens.
Download SKILL.mdSave it as
.claude/skills/write-issue/SKILL.md (or your agent's skills folder).- name
- write-issue
- description
- Write a new issue from scratch by grilling the user to clarify requirements, creating 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 write, create, draft, open, or file a new issue on GitHub.
- metadata.internal
- true
Write issue
This skill takes a user request to create a new issue, conducts an interactive grilling session with the user to clarify requirements, creates 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 /write-issue or /create-issue or asks to "write", "create", "draft", "open", or "file" a new issue on GitHub.
Workflow
1. Context gathering & initial assessment
Before asking any questions, you MUST examine the codebase to understand the domain and potential files/implementations relevant to the user's intent.
- Explore Codebase: Explore the repository to understand the domain model and existing implementations relevant to the user's request. Refer to the project's domain glossary (
docs/CONTEXT.md), ADRs (docs/adr/), and prior rejections (.out-of-scope/*.md). - Determine Initial Scope: Formulate a mental model of the feature/bug area, likely dependencies, and potential technical boundaries.
2. Grilling / requirement clarification (if needed)
If the user's initial description is vague or lacks concrete acceptance criteria, conduct a rigorous interview session with the user (following the principles of /grill-with-docs):
- Ask One Question at a Time: Interview the user relentlessly about every aspect of the new issue until reaching a shared understanding.
- Wait for Feedback: Present your recommended answer/approach for each question and wait for the user's confirmation before proceeding to the next question.
- Probe Specifics: Challenge fuzzy language, establish clear boundaries between domain concepts, and explore concrete edge cases, error conditions, and out-of-scope items.
Show full SKILL.md (240 more words)Show less
3. Fleshing out the issue & creating it on GitHub
Once the requirements are fully clarified and agreed upon:
- Synthesize Refined Specification: Format the clarified requirements into a clean, comprehensive issue body. Ensure it includes:
- A clear problem statement / summary
- Detailed current behavior (or status quo)
- Detailed desired behavior
- Concrete, testable acceptance criteria
- Specific out-of-scope items
- Confirm with User: Present the drafted title and body of the issue to the user for final approval before creation.
- Create Issue on GitHub: Use the GitHub CLI to create the issue:
bash gh issue create --title "<issue-title>" --body "<issue-body>" - Extract Issue Number: Retrieve the newly created issue number from the output of the create command.
4. Triage & agent brief
At the end of the issue creation 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:
- Determine Triage Roles: Identify the correct category role (
bugorenhancement) and state role (ready-for-agent,ready-for-human,needs-info,wontfix, etc.) based on the triage skill guidelines. - 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>" - Post Agent Brief (If Applicable): If the issue is transitioned to
ready-for-agentorready-for-human, generate a durable, behavioral agent brief following the principles and template inskills/triage/AGENT-BRIEF.md. Post it as a comment on the issue:bash gh issue comment <issue-number> --body "<agent-brief-content>"
© 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/write-issue of yamcodes/arkenv.
Open the folder on GitHubat commit 74b3732
Compare with similar skills
Write 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Write Issue this skillyamcodes/arkenv | 145 | — | ~1k | Automated safety check: Pass | MIT | |
| Agentic Workflow Designerdotnet/Open-XML-SDK | 4.6k | 2 repos | ~3.5k | Automated safety check: Pass | MIT | |
| DBS Skill Makerdontbesilent2025/dbskill | 11k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Ask NavigatorYeachan-Heo/oh-my-claudecode | 40k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Readoutwarpdotdev/common-skills | 608 | — | ~2k | Automated safety check: Pass | MIT | |
| Ouroboros Command ReferenceQ00/ouroboros | 6.2k | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
- Official
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.
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.
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 —…
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.
Dev Request
FHIR/fhir-codegen
Drafts and iterates on local-development feature requests in the role of a staff-level Product Manager.
More from yamcodes/arkenv
All 20 skills in this repoHallmark
yamcodes/arkenv
Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots.
Bulletproof React
yamcodes/arkenv
Bulletproof React architecture patterns for scalable, maintainable applications.
Arkenv
yamcodes/arkenv
Answer questions about ArkEnv and help implement environment variable validation.
Code Review
yamcodes/arkenv
Fetch, analyze, and address code reviews and comments on GitHub, or perform a code review on changes in the workspace.
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.
Groom Issue
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…
Related
Works with
Categories
Questions about Write Issue
What does Write Issue do?
Write a new issue from scratch by grilling the user to clarify requirements, creating the issue on GitHub via the gh cli, and utilizing the triage skill to apply the correct label and add an agent…. Write Issue is an agent skill from yamcodes/arkenv. Write a new issue from scratch by grilling the user to clarify requirements, creating 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 Write Issue?
Write Issue fits situations like: the user wants to write; file a new issue on GitHub.
How do I install Write Issue in Claude Code?
Run `npx skills add yamcodes/arkenv --skill write-issue -a claude-code`. Or copy the skill folder (skills/write-issue in yamcodes/arkenv) into .claude/skills/write-issue in your project. Claude Code loads it when a task matches its description.
How do I install Write Issue in Codex?
Run `npx skills add yamcodes/arkenv --skill write-issue -a codex`. Or copy the skill folder (skills/write-issue in yamcodes/arkenv) into .agents/skills/write-issue in your project. Codex loads it when a task matches its description.
Can I use Write 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 write-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/write-issue, .gemini/skills/write-issue, .github/skills/write-issue and .opencode/skills/write-issue in your project.
What does Write Issue need to run?
Going by SKILL.md and its folder, Write Issue needs the command-line tools its instructions call (gh).
Does Write 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 Write 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 Write Issue use?
Write 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 Write Issue use?
About 1k tokens (SKILL.md is roughly 4k 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 Write Issue?
Skills that share tags, products or a category with Write 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 Write 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.