Converts conversations into well-structured GitHub issues with appropriate labels and priority.
Install
mkdir -p .claude/skills/capture-cyc-seattle && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19173" && unzip -o skill.zip -d .claude/skills/capture-cyc-seattle && rm skill.zipInstalls to .claude/skills/capture-cyc-seattle
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Capture a new GitHub issue for the isthmia repo with the correct type label, priority, and a clear Problem/Fix body. Use when the user wants to file an issue, log a bug, or record a TODO ("capture this", "file an issue", "make an issue for X").Key capabilities
- →Gather problem details from conversation or user description
- →Check for duplicate GitHub issues
- →Assign type labels (bug, enhancement, documentation, docker)
- →Assign priority labels (P0-P3) based on rubric
- →Write issue body using a specific template
- →Create GitHub issues and report issue number and URL
How it works
The skill systematically gathers problem details, checks for duplicates, assigns type and priority labels, formats the issue body, and creates a new GitHub issue in the specified repository.
Inputs & outputs
When to use capture
- →File a bug report
- →Log a new task
- →Capture an enhancement request
About capture
Checks for duplicates and creates issues with specific priority rubrics (P0-P3) and formatted descriptions.
Capture a new GitHub issue for the isthmia repo with the correct type label, priority, and a clear Problem/Fix body. Use when the user wants to file an issue, log a bug, or record a TODO ("capture this", "file an issue", "make an issue for X").
When not to use it
- →When filing issues for repositories other than cyc-seattle/isthmia
- →When inventing new labels without asking
- →When a problem is already covered by an existing issue and a new duplicate is not desired
Limitations
- →Issues are created for the isthmia repo
- →Labels must be chosen from existing types (bug, enhancement, documentation, docker)
- →Priority labels must adhere to the P0-P3 rubric
How it compares
This skill enforces a structured process for creating GitHub issues, including duplicate checks, priority rubrics, and a specific body template, unlike manual issue creation.
Compared to similar skills
capture side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| capture (this skill) | 0 | 3mo | No flags | Beginner |
| openspec-archive-change | 4 | 8mo | Review | Intermediate |
| session-wrap | 1 | 9mo | Review | Intermediate |
| semantic-commits | 0 | 7mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
openspec-archive-change
studyzy
归档实验性工作流中已完成的变更。当用户想要在实现完成后最终确定并归档变更时使用。
session-wrap
team-attention
This skill should be used when the user asks to "wrap up session", "end session", "session wrap", "/wrap", "document learnings", "what should I commit", or wants to analyze completed work before ending a coding session.
semantic-commits
lipkau
>-
tbd
jlevy
|-
preserve
markwharton
Preserve the most recently approved plan to docs/plans/
release-closeout-engineer
ThiagoGuislotti
Close out a completed workstream by updating README artifacts when needed, producing a commit message, and applying changelog-ready content when the work is ready for commit. Use after review when a stable checkpoint is ready.