Issue Brief

What it does

When your agent uses it

• A github.com issues/
• Discussions/ link is pasted
• The user says check / look at / verify / assess / analyse this issue
• What does this issue want

Example prompts

• “what are the cons”
• “explain that in simple terms”
• “/issue-brief”

Workflow steps

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

1. 1Fetch the thing
2. 2Answer in this order
3. 3Prose rules
4. 4"What are the cons?"
5. 5Worked example (issue 198, single-port proxy)
6. 6Don't

What it can do on your machine

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

Issue Brief loads about 1.5k tokens when it runs. Until then it costs about 223 tokens; SKILL.md has 741 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~223

When it runs · the whole SKILL.md, loaded when a task matches

~1.5k

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

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 VasiHemanth/tokentelemetry at commit 5eecfc4, republished under its MIT licence (© VasiHemanth). 741 words, ~1,513 tokens.

name

issue-brief

description

Explain a GitHub issue, discussion, or feature request in plain language before deciding whether to build it. Covers what the reporter actually wants, a numbered walkthrough of the failure using real hostnames/ports/endpoints, how the code behaves today with file:line anchors, what implementing it would take, and the traps (security regressions, open PRs touching the same files, older issues with the same root cause). Use whenever a github.com issues/ or discussions/ link is pasted, or the user says check / look at / verify / assess / analyse this issue, what does this issue want, is it worth doing, what would it take, or refers to one by number (issue 198, discussion 49). Also handles the follow-ups "what are the cons" and "explain that in simple terms". NOT for pull requests (use /review) and NOT for implementing. An issue-brief ends with the working tree untouched.

gh issue view <number-or-url> --json number,title,state,author,createdAt,closedAt,labels,body,comments

gh api graphql -f query='
{ repository(owner:"VasiHemanth", name:"tokentelemetry") {
    discussion(number: NNN) {
      number title url category{name} author{login} createdAt body
      comments(first:20){ nodes { author{login} body } }
    } } }'

© VasiHemanth, 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/issue-brief of VasiHemanth/tokentelemetry.

Open the folder on GitHubat commit 5eecfc4