Scraps Review
getsentry/sentry
Filter large Sentry Scraps design-system migration PRs for review by separating mechanical import-path changes, generated baseline updates, snapshot mocks, and pure renames from substantive…
Write or revise a GitHub issue (title and body) for this repository from notes, screenshots or a conversation.
Install Write Issue
$ npx skills add equinor/design-system --skill write-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install equinor/design-system 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/equinor/design-system.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/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/equinor/design-system/tree/main/.claude/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/equinor/design-system/tree/main/.claude/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 equinor/design-system --skill write-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install equinor/design-system write-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/equinor/design-system.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/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/equinor/design-system/tree/main/.claude/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 equinor/design-system --skill write-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install equinor/design-system write-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/equinor/design-system.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/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/equinor/design-system/tree/main/.claude/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/equinor/design-system.git --path .claude/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 equinor/design-system --skill write-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install equinor/design-system write-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/equinor/design-system.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/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/equinor/design-system/tree/main/.claude/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 equinor/design-system 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 equinor/design-system --skill write-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/equinor/design-system.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/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/equinor/design-system/tree/main/.claude/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 equinor/design-system --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 equinor/design-system write-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/equinor/design-system.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/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/equinor/design-system/tree/main/.claude/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
- 151
- Token cost
- ~362 tokens
- SKILL.md length
- 175 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write or revise a GitHub issue (title and body) for this repository from notes, screenshots or a conversation.
- Works in 5 steps: Gather the input: the notes, screenshots… → Separate what was observed from what is… → Pick the matching template in… → …
- Opening an issue
- Calls gh
- Running gh issue create
What it does
Write Issue is an agent skill from equinor/design-system. Write or revise a GitHub issue (title and body) for this repository from notes, screenshots or a conversation. Use whenever opening an issue, running gh issue create or gh issue edit, or when the user asks for an issue to be written.
Its SKILL.md is about 360 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 Frontend & Design, covering Design systems. It works with GitHub. The repository describes itself as: The Equinor design system. The licence is MIT.
When your agent uses it
- Opening an issue
- Running gh issue create
- The user asks for an issue to be written
Example prompts
- “/write-issue”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Gather the input: the notes, screenshots or conversation in $ARGUMENTS, plus any code or issues they point to. If $ARGUMENTS is empty, as…
- Separate what was observed from what is assumed. Ask the user about gaps instead of guessing.
- Pick the matching template in .github/ISSUE_TEMPLATE/, if any, and draft per § Issues in the canonical doc.
- Check the draft against § Before posting. Count the prose and cut until it is within 400 words.
- Show the draft to the user. Run gh issue create or gh issue edit only after they approve it.
What it can do on your machine
Read from SKILL.md and the folder at commit 35d1b25. 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 362 tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 175 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 equinor/design-system at commit 35d1b25, republished under its MIT licence (© equinor). 175 words, ~362 tokens.
Download SKILL.mdSave it as
.claude/skills/write-issue/SKILL.md (or your agent's skills folder).- name
- write-issue
- description
- Write or revise a GitHub issue (title and body) for this repository from notes, screenshots or a conversation. Use whenever opening an issue, running `gh issue create` or `gh issue edit`, or when the user asks for an issue to be written.
Write an issue
Explain a problem or proposed change clearly enough for someone to investigate it or decide what to do next.
Canonical reference:
documentation/agent-instructions/PR_AND_ISSUE_WRITING.md. Read it before drafting. It holds the word limit, the writing restrictions, the issue rules, an example and the checklist before posting.
Steps
- Gather the input: the notes, screenshots or conversation in
$ARGUMENTS, plus any code or issues they point to. If$ARGUMENTSis empty, as when the skill is applied from a request in the conversation, take the input from the conversation instead. Checkgh issue list --searchfor an existing issue on the same problem. - Separate what was observed from what is assumed. Ask the user about gaps instead of guessing.
- Pick the matching template in
.github/ISSUE_TEMPLATE/, if any, and draft per § Issues in the canonical doc. - Check the draft against § Before posting. Count the prose and cut until it is within 400 words.
- Show the draft to the user. Run
gh issue createorgh issue editonly after they approve it.
© equinor, 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 .claude/skills/write-issue of equinor/design-system.
Open the folder on GitHubat commit 35d1b25
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 skillequinor/design-system | 151 | — | ~362 | Automated safety check: Pass | MIT | |
| Scraps Reviewgetsentry/sentry | 45k | — | ~1.2k | Automated safety check: Notes | Custom licence | |
| Design SystemBuildGreatProducts/builder-os | 227 | — | ~4.8k | Automated safety check: Pass | MIT | |
| Mui Triagemui/mui-public | 106 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Ingest GitHubbluzir/claude-code-design | 106 | — | ~796 | Automated safety check: Pass | None | |
| Mui Releasemui/mui-public | 106 | — | ~749 | Automated safety check: Pass | MIT |
Similar skills
- Official
Design System
BuildGreatProducts/builder-os
Translates an image (or a set of image references — screenshots, mockups, Figma URLs, live websites) into two mirrored design-system artifacts: docs/design.md (YAML tokens + prose, following…
Mui Triage
mui/mui-public
Triage MUI GitHub issues from a mui/<repo/issues/<num URL or issue number - fetch context, classify state/type labels, prepare a durable summary comment, and emit a reviewable apply script without…
Ingest GitHub
bluzir/claude-code-design
Clone a GitHub repo and extract design tokens (colors, fonts, spacing) from its codebase.
Mui Release
mui/mui-public
Run or assist a release in any MUI repo, at any stage - release PR, npm publish, docs deploy, GitHub release.
Openforms Mui
BlackBeltTechnology/pi-agent-dashboard
Author, render, preview and debug OpenForms FormSchemaJSON form definitions as idiomatic, themed, accessible MUI (React).
More from equinor/design-system
Write PR Description
equinor/design-system
Write or revise a pull request description (title and body) for this repository.
Related
Works with
Categories
Questions about Write Issue
What does Write Issue do?
Write or revise a GitHub issue (title and body) for this repository from notes, screenshots or a conversation. Write Issue is an agent skill from equinor/design-system. Write or revise a GitHub issue (title and body) for this repository from notes, screenshots or a conversation.
When should I use Write Issue?
Write Issue fits situations like: opening an issue; running gh issue create; the user asks for an issue to be written.
How do I install Write Issue in Claude Code?
Run `npx skills add equinor/design-system --skill write-issue -a claude-code`. Or copy the skill folder (.claude/skills/write-issue in equinor/design-system) 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 equinor/design-system --skill write-issue -a codex`. Or copy the skill folder (.claude/skills/write-issue in equinor/design-system) 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 equinor/design-system --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 362 tokens (SKILL.md is roughly 1.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: Scraps Review (getsentry/sentry, 45k stars), Design System (BuildGreatProducts/builder-os, 227 stars), Mui Triage (mui/mui-public, 106 stars) and Ingest GitHub (bluzir/claude-code-design, 106 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Write Issue?
equinor (a GitHub organization) maintains it in equinor/design-system, which has 151 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 6, 2026.
Source: equinor/design-system on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.