Ingest
coreyhaines31/makerskills
When you paste raw human input — a call transcript (Grain, Zoom, Granola, Fathom), a text or email from a client/partner/friend, a voice-memo dump, or meeting notes — and want it converted into…
Create well-structured GitHub issues from any source: meeting notes, transcriptions, conversation context, informal descriptions, or direct requests.
Install Issue From Notes
$ npx skills add AxonIQ/AxonFramework --skill issue-from-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AxonIQ/AxonFramework issue-from-notes --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/AxonIQ/AxonFramework.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/issue-from-notes .claude/skills/issue-from-notes && 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 "issue-from-notes" agent skill from https://github.com/AxonIQ/AxonFramework/tree/main/.claude/skills/issue-from-notes into .claude/skills/issue-from-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-from-notes", 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/AxonIQ/AxonFramework/tree/main/.claude/skills/issue-from-notesType 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 AxonIQ/AxonFramework --skill issue-from-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AxonIQ/AxonFramework issue-from-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AxonIQ/AxonFramework.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/issue-from-notes .agents/skills/issue-from-notes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "issue-from-notes" agent skill from https://github.com/AxonIQ/AxonFramework/tree/main/.claude/skills/issue-from-notes into .agents/skills/issue-from-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-from-notes", 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 AxonIQ/AxonFramework --skill issue-from-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AxonIQ/AxonFramework issue-from-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AxonIQ/AxonFramework.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/issue-from-notes .cursor/skills/issue-from-notes && 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 "issue-from-notes" agent skill from https://github.com/AxonIQ/AxonFramework/tree/main/.claude/skills/issue-from-notes into .cursor/skills/issue-from-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-from-notes", 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/AxonIQ/AxonFramework.git --path .claude/skills/issue-from-notes--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 AxonIQ/AxonFramework --skill issue-from-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AxonIQ/AxonFramework issue-from-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AxonIQ/AxonFramework.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/issue-from-notes .gemini/skills/issue-from-notes && 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 "issue-from-notes" agent skill from https://github.com/AxonIQ/AxonFramework/tree/main/.claude/skills/issue-from-notes into .gemini/skills/issue-from-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-from-notes", 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 AxonIQ/AxonFramework issue-from-notesInstalls 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 AxonIQ/AxonFramework --skill issue-from-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AxonIQ/AxonFramework.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/issue-from-notes .github/skills/issue-from-notes && 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 "issue-from-notes" agent skill from https://github.com/AxonIQ/AxonFramework/tree/main/.claude/skills/issue-from-notes into .github/skills/issue-from-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-from-notes", 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 AxonIQ/AxonFramework --skill issue-from-notes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install AxonIQ/AxonFramework issue-from-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AxonIQ/AxonFramework.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/issue-from-notes .opencode/skills/issue-from-notes && 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 "issue-from-notes" agent skill from https://github.com/AxonIQ/AxonFramework/tree/main/.claude/skills/issue-from-notes into .opencode/skills/issue-from-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-from-notes", 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
issue-from-notes- GitHub stars
- 3.6k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 469 words
- Files
- 2 (incl. references)
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Create well-structured GitHub issues from any source: meeting notes, transcriptions, conversation context, informal descriptions, or direct requests.
- Works in 5 steps: Determine Issue Type → Read the Matching Template → Fill Out the Template → …
- The user says create a github issue
- SKILL.md covers Workflow, Quality Checklist and References
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Issue From Notes is an agent skill from AxonIQ/AxonFramework. Create well-structured GitHub issues from any source: meeting notes, transcriptions, conversation context, informal descriptions, or direct requests. Use when the user says "create a github issue", "create issue from notes", "write up an issue", "turn these notes into an issue", "file a bug", "file a bug from meeting notes", "create enhancement from discussion", "make an issue for", "open an issue about", "create a follow-up issue", or any variation of creating a structured GitHub issue — whether the input comes…
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/examples.md`).
It sits in Productivity & Automation, covering Meeting notes and agendas, Transcription and Domain-driven design. It works with GitHub and Java. The repository describes itself as: Framework for Evolutionary Message-Driven Microservices on the JVM. The licence is Apache-2.0.
When your agent uses it
- The user says create a github issue
- Create issue from notes
- Write up an issue
- Turn these notes into an issue
Example prompts
- “create a github issue”
- “create issue from notes”
- “write up an issue”
- “/issue-from-notes”
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 acb0b5f. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 From Notes loads about 1.1k tokens when it runs, and up to ~2.7k if it reads all its reference files. Until then it costs about 148 tokens; SKILL.md has 469 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 AxonIQ/AxonFramework at commit acb0b5f, republished under its Apache-2.0 licence (© AxonIQ). 469 words, ~1,144 tokens.
Download SKILL.mdSave it as
.claude/skills/issue-from-notes/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- issue-from-notes
- description
- Create well-structured GitHub issues from any source: meeting notes, transcriptions, conversation context, informal descriptions, or direct requests. Use when the user says "create a github issue", "create issue from notes", "write up an issue", "turn these notes into an issue", "file a bug", "file a bug from meeting notes", "create enhancement from discussion", "make an issue for", "open an issue about", "create a follow-up issue", or any variation of creating a structured GitHub issue — whether the input comes from notes, conversation context, or a direct description.
Issue From Notes
Transform unstructured meeting notes, transcriptions, or descriptions into well-structured GitHub issue bodies matching the project's issue templates.
Workflow
1. Determine Issue Type
Based on the input, classify as one of:
- Bug report - something broken or not working as expected
- Enhancement request - improvement to an existing feature
- Feature request - entirely new functionality
- Documentation change - docs need updating
If ambiguous, ask the user.
2. Read the Matching Template
Read the corresponding template from the project's .github/ISSUE_TEMPLATE/ directory:
| Type | Template file |
|---|---|
| Feature | .github/ISSUE_TEMPLATE/1_feature_request.md |
| Enhancement | .github/ISSUE_TEMPLATE/2_enhancement_request.md |
| Bug | .github/ISSUE_TEMPLATE/3_bug_report.md |
| Documentation | .github/ISSUE_TEMPLATE/4_documentation_change.md |
3. Fill Out the Template
Parse the user's notes and map information to the template sections. Follow these rules:
- Keep it short - focus on the most important parts; remove noise, filler, and tangents
- Split when needed - if the notes cover multiple distinct issues, create a separate file for each
- Extract and restructure - do not just copy-paste raw notes; reorganize into coherent sections
- Preserve technical details - keep code snippets, class names, error messages, version numbers exactly as mentioned
- Class name references - always format class names in backticks without spaces:
EventHandlingComponent,AccessSerializingRepository,CommandBus - Research mentioned classes - if class names are mentioned in the discussion, read their source code and javadoc to produce an accurate, comprehensive description in the issue
- Add code blocks - wrap any code, stack traces, or configuration in proper markdown fenced blocks
- Fill every section - if the notes lack info for a section, write a reasonable placeholder or note
N/Arather than leaving it blank - Capture decisions - if meeting notes contain resolution decisions or action items, include them
Show full SKILL.md (212 more words)Show less
4. Compose the Title and File Name
Propose a concise, descriptive title (under 80 chars). Patterns:
- Bug: describe the symptom, e.g. "Polymorphic
@EventSourcedEntity- doesn't evolve immutable entities" - Enhancement: describe the desired outcome, e.g. "Allow usage of the
AccessSerializingRepository" - Feature: describe the capability, e.g. "Support dead letter queue for failed event handlers"
Derive a kebab-case file name from the title, e.g.:
- Title: "Polymorphic
@EventSourcedEntity- doesn't evolve immutable entities" ->polymorphic-event-sourced-entity-doesnt-evolve-immutable-entities.md - Title: "Allow usage of the
AccessSerializingRepository" ->allow-usage-of-access-serializing-repository.md
Present the proposed title to the user before writing the file.
5. Write to File
Structure the output file as:
# <Issue Title>
<filled template body>The title goes as an # H1 header at the top, followed by the filled-in template sections.
Write the file to: .ai/temp/skills/issue-from-notes/<file-name>.md
Create the directory if it doesn't exist. Print the file path after writing.
Quality Checklist
Before writing the file, verify:
- All template sections are filled
- The
#H1 header contains the issue title - Code snippets have proper syntax highlighting (
java,kotlin, etc.) - Technical terms and class names are accurate to what was mentioned
- The title is concise and descriptive
- No raw meeting artifacts remain (filler words, off-topic tangents, speaker labels)
References
For real-world examples of well-written issues in this project, see references/examples.md. Consult these examples to match the tone, depth, and structure expected in this project's issues.
© AxonIQ, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in .claude/skills/issue-from-notes of AxonIQ/AxonFramework.
- SKILL.md
- references/examples.md
Open the folder on GitHubat commit acb0b5f
Compare with similar skills
Issue From Notes 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 |
|---|---|---|---|---|---|---|
| Issue From Notes this skillAxonIQ/AxonFramework | 3.6k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Ingestcoreyhaines31/makerskills | 844 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Scribe Meeting Notesooiyeefei/ccc | 494 | — | ~876 | Automated safety check: Pass | MIT | |
| FeedgrabiBigQiang/feedgrab | 613 | — | ~2k | Automated safety check: Pass | MIT | |
| GitHub Issue CreatorbenjaminasterA/antigravity-awesome-skills | 364 | — | ~922 | Automated safety check: Pass | MIT | |
| Qv Daily Work Updatetetherto/qvac | 674 | — | ~1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Scribe Meeting Notes
ooiyeefei/ccc
Turns meeting recordings into notes with a chain of custody from audio to claim, auditing transcripts for gaps and low-confidence numbers and names.
Feedgrab
iBigQiang/feedgrab
Universal content grabber — fetch any URL and return structured Markdown.
GitHub Issue Creator
benjaminasterA/antigravity-awesome-skills
Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports.
Qv Daily Work Update
tetherto/qvac
Generate a concise end-of-day work update from local diary, GitHub activity, PR queue state, and optional Asana config.
Standup
haacked/dotfiles
Generate standup notes from GitHub PR activity. An agent skill from haacked/dotfiles.
More from AxonIQ/AxonFramework
Dynamic Consistency Boundaries
AxonIQ/AxonFramework
Explain and reason about Dynamic Consistency Boundaries (DCB) and how Axon Framework 5 and Axon Server implement them.
Migration Path
AxonIQ/AxonFramework
Create a new Axon Framework 4→5 migration path documentation page.
Related
Questions about Issue From Notes
What does Issue From Notes do?
Create well-structured GitHub issues from any source: meeting notes, transcriptions, conversation context, informal descriptions, or direct requests. Issue From Notes is an agent skill from AxonIQ/AxonFramework. Create well-structured GitHub issues from any source: meeting notes, transcriptions, conversation context, informal descriptions, or direct requests.
When should I use Issue From Notes?
Issue From Notes fits situations like: the user says create a github issue; create issue from notes; write up an issue; turn these notes into an issue.
How do I install Issue From Notes in Claude Code?
Run `npx skills add AxonIQ/AxonFramework --skill issue-from-notes -a claude-code`. Or copy the skill folder (.claude/skills/issue-from-notes in AxonIQ/AxonFramework) into .claude/skills/issue-from-notes in your project. Claude Code loads it when a task matches its description.
How do I install Issue From Notes in Codex?
Run `npx skills add AxonIQ/AxonFramework --skill issue-from-notes -a codex`. Or copy the skill folder (.claude/skills/issue-from-notes in AxonIQ/AxonFramework) into .agents/skills/issue-from-notes in your project. Codex loads it when a task matches its description.
Can I use Issue From Notes 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 AxonIQ/AxonFramework --skill issue-from-notes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-from-notes, .gemini/skills/issue-from-notes, .github/skills/issue-from-notes and .opencode/skills/issue-from-notes in your project.
What does Issue From Notes need to run?
SKILL.md names no scripts, command-line tools or credentials: Issue From Notes is instructions for the agent only.
Does Issue From Notes access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Issue From Notes 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 Issue From Notes use?
Issue From Notes is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Issue From Notes use?
About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.
What are the alternatives to Issue From Notes?
Skills that share tags, products or a category with Issue From Notes: Ingest (coreyhaines31/makerskills, 844 stars), Scribe Meeting Notes (ooiyeefei/ccc, 494 stars), Feedgrab (iBigQiang/feedgrab, 613 stars) and GitHub Issue Creator (benjaminasterA/antigravity-awesome-skills, 364 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Issue From Notes?
AxonIQ (a GitHub organization) maintains it in AxonIQ/AxonFramework, which has 3,622 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.
Source: AxonIQ/AxonFramework on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.