Capture
- 669 installs
- 1 repo stars
- Updated May 26, 2026
- camacho/ai-skills
capture is an AI agent skill that instantly turns a spoken or typed idea, bug report, or feature request into a properly labeled GitHub issue or local scratchpad fallback.
About
capture is a lightweight triage skill that parses free-text descriptions into GitHub issues with appropriate labels using the gh CLI. The skill classifies input by keywords: bug terms like error, crash, and regression receive triage and bug labels, while feature terms like add, new, and enhance receive triage and enhancement labels, defaulting to enhancement when unclear. Developers reach for capture when capturing ideas mid-debug, filing bugs from agent sessions, or avoiding context loss before formal planning. If GitHub issue creation is unavailable, capture falls back to a local scratchpad record while preserving the parsed title and body structure.
- Automatically classifies input as Bug or Feature using keyword detection
- Creates labeled GitHub Issue via gh CLI with concise title and full body
- Graceful fallback to ai-workspace/scratchpad.md when GitHub is unavailable
- Returns issue number and URL for immediate follow-up
- Handles edge cases: missing description, offline mode, no gh CLI
Capture by the numbers
- 669 all-time installs (skills.sh)
- Ranked #621 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/camacho/ai-skills --skill captureAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 669 |
|---|---|
| repo stars | ★ 1 |
| Security audit | 3 / 3 scanners passed |
| Last updated | May 26, 2026 |
| Repository | camacho/ai-skills ↗ |
How do you turn ideas into GitHub issues fast?
Instantly turn a spoken or typed idea, bug report, or feature request into a properly labeled GitHub issue or local scratchpad fallback.
Who is it for?
Developers who want frictionless issue intake from natural-language bug reports or feature ideas during coding sessions.
Skip if: Teams needing full sprint planning, estimation, or multi-issue epics should skip capture and use dedicated PM tooling instead.
When should I use this skill?
The user describes a bug, feature idea, or enhancement and wants a GitHub issue or scratchpad capture without manual triage formatting.
What you get
Draft GitHub issues with triage labels, concise titles, full bodies, or local scratchpad entries when GitHub is unavailable.
- Labeled GitHub issue draft
- Parsed issue title and body
- Local scratchpad fallback note
Files
Inputs
- Free-text description of an idea, bug, or feature request
Steps
1. Parse the description to detect type:
| Keywords | Type | Labels |
|---|---|---|
| error, crash, broken, fix, bug, fails, regression | Bug | triage, bug |
| add, want, should, new, feature, enhance, improve | Feature | triage, enhancement |
| Default | Feature | triage, enhancement |
2. Create GitHub Issue:
gh issue create \
--title "<concise title from description>" \
--body "<full description>" \
--label "triage" --label "<bug or enhancement>"3. Return the issue number and URL.
Fallback
If gh is not available or GitHub access fails: 1. Try GitHub MCP tools (if available) 2. If neither works → append to ai-workspace/scratchpad.md:
## Captured [date]
**Type**: [bug/feature]
**Description**: [text]
_Failed to create GitHub Issue — saved here as fallback._Inform the user that the capture was saved locally.
Edge Cases
- No description provided → ask the user to describe the idea/bug
- Offline / no GitHub access → scratchpad fallback (see above)
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
How does capture classify issues?
capture scans keywords in the description: error, crash, broken, fix, bug, fails, and regression map to triage and bug labels; add, want, new, feature, enhance, and improve map to triage and enhancement labels, with enhancement as the default.
What command does capture use for GitHub?
capture creates issues with gh issue create, passing a concise generated title, the full description as the body, and labels such as triage with bug or triage with enhancement depending on parsed type.
Is Capture safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.