Internal Comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use …
Transform messy input (error logs, voice notes, screenshots) into clean, actionable GitHub issues.
## Summary
[One-line description of the issue]
## Environment
- **Product/Service**:
- **Region/Version**:
- **Browser/OS**: (if relevant)
## Reproduction Steps
1. [Step]
2. [Step]
3. [Step]
## Expected Behavior
[What should happen]
## Actual Behavior
[What actually happens]
## Error Details
[Error message/code if applicable]
## Visual Evidence
[Reference to attached screenshots/GIFs]
## Impact
[Severity: Critical/High/Medium/Low + brief explanation]
## Additional Context
[Any other relevant details]
Create issues as markdown files in /issues/ directory at the repo root. Use naming convention: YYYY-MM-DD-short-description.md
Be crisp: No fluff. Every word should add value.
Extract structure from chaos: Voice dictation and raw notes often contain the facts buried in casual language. Pull them out.
Infer missing context: If user mentions "same project" or "the dashboard", use context from conversation or memory to fill in specifics.
Placeholder sensitive data: Use [PROJECT_NAME], [USER_ID], etc. for anything that might be sensitive.
Match severity to impact: - Critical: Service down, data loss, security issue - High: Major feature broken, no workaround - Medium: Feature impaired, workaround exists - Low: Minor inconvenience, cosmetic
Image/GIF handling: Reference attachments inline. Format: 
Input (voice dictation):
so I was trying to deploy the agent and it just failed silently no error nothing the workflow ran but then poof gone from the list had to refresh and try again three times
Output:
## Summary
Agent deployment fails silently - no error displayed, agent disappears from list
## Environment
- **Product/Service**: Azure AI Foundry
- **Region/Version**: westus2
## Reproduction Steps
1. Navigate to agent deployment
2. Configure and deploy agent
3. Observe workflow completes
4. Check agent list
## Expected Behavior
Agent appears in list with deployment status, errors shown if deployment fails
## Actual Behavior
Agent disappears from list. No error message. Requires page refresh and retry.
## Impact
**High** - Blocks agent deployment workflow, no feedback on failure cause
## Additional Context
Required 3 retry attempts before successful deployment
Input (error paste):
Error: PERMISSION_DENIED when publishing to Teams channel. Code: 403. Was working yesterday.
Output:
## Summary
403 PERMISSION_DENIED error when publishing to Teams channel
## Environment
- **Product/Service**: Copilot Studio → Teams integration
- **Region/Version**: [REGION]
## Reproduction Steps
1. Configure agent for Teams channel
2. Attempt to publish
## Expected Behavior
Agent publishes successfully to Teams channel
## Actual Behavior
Returns `PERMISSION_DENIED` with code 403
## Error Details
Error: PERMISSION_DENIED Code: 403
## Impact
**High** - Blocks Teams integration, regression from previous working state
## Additional Context
Was working yesterday - possible permission/config change or service regression
Source: Microsoft · MIT · SHA-256 shown alongside the download.
License file included. A license and checksum are not a security certification. Review package instructions and scripts before running them.
microsoft-github-issue-creator/SKILL.md3762 bytesAn adaptation record is bundled. Inspect the declared changes and archived original before use. Review adaptation and original-file hashes →
Machine-readable installation guide →Source and packaging checks recorded on 2026-10-03. These notes are not safety certification or measured task performance.
A workspace where Markdown drafts can be written; optional screenshots or logs.
This workflow drafts files. Publishing to GitHub is a separate action; redact credentials and personal information first. Core frontmatter was adapted by BB Skills for the existing namespace directory; unchanged original SKILL.md is archived. This does not imply client execution was tested.
Upstream commit: 84d8eaa8ae95930f55cdceb3e27196c795dab038
Runtime status: not tested by this catalog. Configure your client and test the skill in your own environment.
Records are supplied by the site administrator and bound to a specific package. They are not third-party safety certification. This page does not execute skills.
No published scenario records yet. Resource availability and download counts do not imply measured task performance.
Be the first to share your experience.
Sign in to leave a review →A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use …
Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to au…
Find GGUF models, compare quantization choices, and plan llama.cpp inference for your own hardware.
Read Hugging Face paper pages and retrieve structured links to models, datasets, code, and arXiv papers.