email-to-issue — Claude Code skill: what it does, how to install
The email-to-issue Claude Code skill turns Outlook threads into GitHub issues or comments. It processes flagged mail or threads selected by subject.
no license 723 installs updated 2026-11-16
npx skills add clhbid/agent-context --skill email-to-issue -a claude-codeWhat email-to-issue does
The skill gathers matching Outlook threads into one proposal table, then suggests a new GitHub issue or a comment on an open issue for each. It searches with several phrasings and waits for approval row by row; GitHub stays unchanged until approval. New issues go to Backlog.
After filing, the agent replies in each thread with the issue link, then asks separately which threads to unflag and archive. Replies go only to the signed-in user. For public repositories, email details are paraphrased without customer names, contact details or pricing. The setup needs a Microsoft 365 connector and the gh, issue-tracker and sending-emails-with-outlook tools. Without mail-writing tools, the user handles the final mail actions manually.
What it helps with
- create a GitHub issue from a flagged Outlook thread
- add an email update to an existing open issue
- link a thread to its issue with a reply
- review several email-to-issue proposals before filing
Example prompts for the agent
- Run
/email-to-issueon my flagged Outlook threads and propose an action for each. - Process the Outlook threads with subject “Export failure” and suggest issues or comments.
- Turn these Outlook messages into GitHub issues, showing me the proposal table first.
How to install email-to-issue
1Skills CLI (Vercel)
npx skills add clhbid/agent-context --skill email-to-issue -a claude-code2Manually: put the files in place
~/.claude/skills/email-to-issue/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/email-to-issue/
1Skills CLI (Vercel)
npx skills add clhbid/agent-context --skill email-to-issue -a codex2Manually: put the files in place
.agents/skills/email-to-issue/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add clhbid/agent-context --skill email-to-issue -a cursor2Manually: put the files in place
.cursor/skills/email-to-issue/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install clhbid/agent-context skills/email-to-issue2Manually: put the files in place
.github/skills/email-to-issue/SKILL.md1Skills CLI (Vercel)
npx skills add clhbid/agent-context --skill email-to-issue -a gemini-cli2Platform CLI
gemini skills install https://github.com/clhbid/agent-context --path skills/email-to-issueManually: put the files in place
.devin/skills/email-to-issue/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add clhbid/agent-context --skill email-to-issue -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about email-to-issue
How do I install email-to-issue in Claude Code?
Run npx skills add clhbid/agent-context --skill email-to-issue -a claude-code. The skill file is installed at ~/.claude/skills/email-to-issue/SKILL.md.
What does email-to-issue do?
It matches selected or flagged Outlook threads against open GitHub issues. After approval, it creates an issue or comment and links the thread to the issue with a reply.
What does email-to-issue need to run?
It needs a Microsoft 365 connector with mail-reading and search tools, GitHub CLI gh, and the issue-tracker and sending-emails-with-outlook skills. Replying and archiving also require mail-writing and move tools; without them, those steps are manual.