Make Custom Agent
dotnet/efcore
Create custom GitHub Copilot agents. An agent skill from dotnet/efcore.
Capture the idea, concept, or bug being brainstormed in the current chat and file it as a GitHub issue in the current repository.
MITAuto-check passed
Install Capture As Gh Issue
$ npx skills add twentyTwo/vsc-ext-coding-time-tracker --skill capture-as-gh-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install twentyTwo/vsc-ext-coding-time-tracker capture-as-gh-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/twentyTwo/vsc-ext-coding-time-tracker.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/capture-as-gh-issue .claude/skills/capture-as-gh-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 "capture-as-gh-issue" agent skill from https://github.com/twentyTwo/vsc-ext-coding-time-tracker/tree/main/.claude/skills/capture-as-gh-issue into .claude/skills/capture-as-gh-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "capture-as-gh-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/twentyTwo/vsc-ext-coding-time-tracker/tree/main/.claude/skills/capture-as-gh-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 twentyTwo/vsc-ext-coding-time-tracker --skill capture-as-gh-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install twentyTwo/vsc-ext-coding-time-tracker capture-as-gh-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/twentyTwo/vsc-ext-coding-time-tracker.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/capture-as-gh-issue .agents/skills/capture-as-gh-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 "capture-as-gh-issue" agent skill from https://github.com/twentyTwo/vsc-ext-coding-time-tracker/tree/main/.claude/skills/capture-as-gh-issue into .agents/skills/capture-as-gh-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "capture-as-gh-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 twentyTwo/vsc-ext-coding-time-tracker --skill capture-as-gh-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install twentyTwo/vsc-ext-coding-time-tracker capture-as-gh-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/twentyTwo/vsc-ext-coding-time-tracker.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/capture-as-gh-issue .cursor/skills/capture-as-gh-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 "capture-as-gh-issue" agent skill from https://github.com/twentyTwo/vsc-ext-coding-time-tracker/tree/main/.claude/skills/capture-as-gh-issue into .cursor/skills/capture-as-gh-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "capture-as-gh-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/twentyTwo/vsc-ext-coding-time-tracker.git --path .claude/skills/capture-as-gh-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 twentyTwo/vsc-ext-coding-time-tracker --skill capture-as-gh-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install twentyTwo/vsc-ext-coding-time-tracker capture-as-gh-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/twentyTwo/vsc-ext-coding-time-tracker.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/capture-as-gh-issue .gemini/skills/capture-as-gh-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 "capture-as-gh-issue" agent skill from https://github.com/twentyTwo/vsc-ext-coding-time-tracker/tree/main/.claude/skills/capture-as-gh-issue into .gemini/skills/capture-as-gh-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "capture-as-gh-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 twentyTwo/vsc-ext-coding-time-tracker capture-as-gh-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 twentyTwo/vsc-ext-coding-time-tracker --skill capture-as-gh-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/twentyTwo/vsc-ext-coding-time-tracker.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/capture-as-gh-issue .github/skills/capture-as-gh-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 "capture-as-gh-issue" agent skill from https://github.com/twentyTwo/vsc-ext-coding-time-tracker/tree/main/.claude/skills/capture-as-gh-issue into .github/skills/capture-as-gh-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "capture-as-gh-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 twentyTwo/vsc-ext-coding-time-tracker --skill capture-as-gh-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 twentyTwo/vsc-ext-coding-time-tracker capture-as-gh-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/twentyTwo/vsc-ext-coding-time-tracker.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/capture-as-gh-issue .opencode/skills/capture-as-gh-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 "capture-as-gh-issue" agent skill from https://github.com/twentyTwo/vsc-ext-coding-time-tracker/tree/main/.claude/skills/capture-as-gh-issue into .opencode/skills/capture-as-gh-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "capture-as-gh-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
capture-as-gh-issue- GitHub stars
- 151
- Token cost
- ~1k tokens
- SKILL.md length
- 590 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
Capture the idea, concept, or bug being brainstormed in the current chat and file it as a GitHub issue in the current repository.
- Works in 5 steps: Find the concept → Check for duplicates → Draft → …
- The user asks to capture
- SKILL.md covers Step 1 — Find the concept, Step 2 — Check for duplicates, Step 3 — Draft and Step 4 — Show the draft, get…, plus 2 more sections
- Calls gh
What it does
Capture As Gh Issue is an agent skill from twentyTwo/vsc-ext-coding-time-tracker. Capture the idea, concept, or bug being brainstormed in the current chat and file it as a GitHub issue in the current repository. Use whenever the user asks to capture, file, log, save, or push something as a GitHub issue, wants to turn a discussion or concept into an issue, or says "make an issue for this" — even if they never say the word "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 works with GitHub and Visual Studio Code. The repository describes itself as: Simple Coding Time Tracker in Visual Studio Code. The licence is MIT.
When your agent uses it
- The user asks to capture
- Push something as a GitHub issue
- Wants to turn a discussion
- Concept into an issue
Example prompts
- “make an issue for this”
- “/capture-as-gh-issue”
Workflow steps
5 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 b88bb7d. 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
Capture As Gh Issue loads about 1k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 590 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 twentyTwo/vsc-ext-coding-time-tracker at commit b88bb7d, republished under its MIT licence (© twentyTwo). 590 words, ~1,049 tokens.
Download SKILL.mdSave it as
.claude/skills/capture-as-gh-issue/SKILL.md (or your agent's skills folder).- name
- capture-as-gh-issue
- description
- Capture the idea, concept, or bug being brainstormed in the current chat and file it as a GitHub issue in the current repository. Use whenever the user asks to capture, file, log, save, or push something as a GitHub issue, wants to turn a discussion or concept into an issue, or says "make an issue for this" — even if they never say the word "issue".
Capture as GitHub issue
Turn the outcome of a brainstorm in this conversation into a GitHub issue: distill the chat into a title and a structured body, show the draft, and create the issue only after the user approves it.
Creating an issue is public and effectively permanent — anyone watching the repo gets notified, and a mis-titled issue lingers in the tracker. That is why the flow stops at a draft first; treat the confirmation step as the point of the skill, not as friction.
Step 1 — Find the concept
Re-read the conversation and identify the thing being brainstormed: the problem or wish that started it, the shape of the solution that emerged, decisions made or rejected along the way, and questions left open. Write for a reader who was not in the chat — no "as we discussed", no pronouns without an antecedent, no references to "the conversation".
If the chat contains no discernible concept (the skill was invoked cold), ask what to file rather than inventing something. An empty catch-all issue is worse than none.
Step 2 — Check for duplicates
Before drafting, search the repo's open issues for the same idea:
gh issue list --state open --search "<key terms from the concept>"Filing a duplicate buries the original discussion. If a near-duplicate exists, show it and ask whether to add a comment to it instead of creating a new issue.
Step 3 — Draft
Title. One line, sentence case, imperative, roughly 50–72 characters, naming the outcome — "Add a microphone selector to Settings", not "Mic issue" and not "Issue: microphone selector feature".
Body. Three sections, in this order. Drop a heading only if its content is genuinely empty.
Problem — what is wrong or missing today, in terms a reader can verify.
Proposal — what to build or change. This is the distilled outcome of the brainstorm, including alternatives that were considered and rejected, and why. That rationale is the main thing the chat has that the repo does not; losing it is how issues get re-litigated months later.
Notes — open questions, constraints, links, and anything that did not fit above.
Example of the shape (abridged):
Title: Add a microphone selector to Settings
Problem Bolo records from the Windows default input device. Anyone with a headset and a webcam mic has to change the system default to change what Bolo hears.
Proposal Add a Microphone tab to Settings listing input devices. The discussion rejected per-app device profiles as out of scope for now.
Notes Needs a fallback when the selected device is unplugged.
Show full SKILL.md (181 more words)Show less
Step 4 — Show the draft, get approval
Show the full title and body in the chat and stop. Apply the edits the user asks for and re-show. Create the issue only on an explicit go-ahead — "yes", "looks good", "ship it". Silence, a new question, or a tangent is not approval.
Step 5 — Create the issue
Write the body to a temp file and pass --body-file. The body contains quotes,
backticks, and apostrophes; an inline --body "..." argument breaks on them
(especially through Windows shells), while a file sidesteps quoting entirely:
gh issue create --title "<title>" --body-file "<temp file>"Run it from the repo root so gh targets the workspace's repository; if the
user named a different repository when invoking the skill, add
--repo owner/name. Delete the temp file afterwards and report the issue URL
gh prints — that URL is the deliverable.
Prerequisites
ghmust be installed and authenticated. Ifgh auth statusfails, say so and offer the draft for manual filing instead of stopping silently.- The current directory must be a git repo with a GitHub remote. If it is not,
ask which
owner/nameto target rather than guessing.
© twentyTwo, 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/capture-as-gh-issue of twentyTwo/vsc-ext-coding-time-tracker.
Open the folder on GitHubat commit b88bb7d
Compare with similar skills
Capture As Gh 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 |
|---|---|---|---|---|---|---|
| Capture As Gh Issue this skilltwentyTwo/vsc-ext-coding-time-tracker | 151 | — | ~1k | Automated safety check: Pass | MIT | |
| Make Custom Agentdotnet/efcore | 15k | — | ~2.5k | Automated safety check: Pass | MIT | |
| ReleasePowerShell/vscode-powershell | 1.9k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Release Roslynatordotnet/roslynator | 3.5k | — | ~1k | Automated safety check: Pass | Custom licence | |
| Unicliolo-dot-io/Uni-CLI | 274 | — | ~3.8k | Automated safety check: Notes | Apache-2.0 | |
| Releasesignageos/vscode-sops | 122 | — | ~2.2k | Automated safety check: Notes | MIT |
Similar skills
- Official
Release
PowerShell/vscode-powershell
Guide for preparing a release of the PowerShell VS Code extension.
- Official
Release Roslynator
dotnet/roslynator
A skill your agent uses when shipping a roslynator release, rolling CHANGELOG.md [Unreleased], updating the VS Code extension changelog, creating a GitHub v release, or optionally tagging cli-v.
Unicli
olo-dot-io/Uni-CLI
Comprehensive guide to Uni-CLI — the open Agent-Computer Interface runtime for real software.
Release
signageos/vscode-sops
Releases the vscode-sops extension end-to-end: determines the next version from the bump history, updates CHANGELOG.md and package.json/package-lock.json, builds via vscode:prepublish, publishes to…
- Official
Review PR
microsoft/vscode-containers
Review a specific vscode-containers pull request on demand from the CLI (or any interactive agent), the way a Container Tools maintainer would.
Related
Works with
Questions about Capture As Gh Issue
What does Capture As Gh Issue do?
Capture the idea, concept, or bug being brainstormed in the current chat and file it as a GitHub issue in the current repository. Capture As Gh Issue is an agent skill from twentyTwo/vsc-ext-coding-time-tracker. Capture the idea, concept, or bug being brainstormed in the current chat and file it as a GitHub issue in the current repository.
When should I use Capture As Gh Issue?
Capture As Gh Issue fits situations like: the user asks to capture; push something as a GitHub issue; wants to turn a discussion; concept into an issue.
How do I install Capture As Gh Issue in Claude Code?
Run `npx skills add twentyTwo/vsc-ext-coding-time-tracker --skill capture-as-gh-issue -a claude-code`. Or copy the skill folder (.claude/skills/capture-as-gh-issue in twentyTwo/vsc-ext-coding-time-tracker) into .claude/skills/capture-as-gh-issue in your project. Claude Code loads it when a task matches its description.
How do I install Capture As Gh Issue in Codex?
Run `npx skills add twentyTwo/vsc-ext-coding-time-tracker --skill capture-as-gh-issue -a codex`. Or copy the skill folder (.claude/skills/capture-as-gh-issue in twentyTwo/vsc-ext-coding-time-tracker) into .agents/skills/capture-as-gh-issue in your project. Codex loads it when a task matches its description.
Can I use Capture As Gh 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 twentyTwo/vsc-ext-coding-time-tracker --skill capture-as-gh-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/capture-as-gh-issue, .gemini/skills/capture-as-gh-issue, .github/skills/capture-as-gh-issue and .opencode/skills/capture-as-gh-issue in your project.
What does Capture As Gh Issue need to run?
Going by SKILL.md and its folder, Capture As Gh Issue needs the command-line tools its instructions call (gh).
Does Capture As Gh 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 Capture As Gh 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 Capture As Gh Issue use?
Capture As Gh 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 Capture As Gh Issue use?
About 1k tokens (SKILL.md is roughly 4.2k 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 Capture As Gh Issue?
Skills that share tags, products or a category with Capture As Gh Issue: Make Custom Agent (dotnet/efcore, 15k stars), Release (PowerShell/vscode-powershell, 1.9k stars), Release Roslynator (dotnet/roslynator, 3.5k stars) and Unicli (olo-dot-io/Uni-CLI, 274 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Capture As Gh Issue?
twentyTwo (a GitHub user) maintains it in twentyTwo/vsc-ext-coding-time-tracker, which has 151 GitHub stars. The repository was last updated on October 7, 2026.
Source: twentyTwo/vsc-ext-coding-time-tracker on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.