report-issue · microsoft, process-intelligence — Claude Code skill: what it does, how to install
report-issue drafts Process Intelligence bug reports and support summaries for failed operations without exposing sensitive data.
MIT ★ 1,167 updated 2026-10-29
/plugin marketplace add microsoft/power-platform-skills
/plugin install process-intelligence@power-platform-skillsWhat report-issue does
The skill guides the creation of a Process Intelligence issue draft using details you provide directly. It tracks symptoms, reproduction steps, expected behavior and sanitized error codes. The workflow never runs shell commands, reads environment logs or inspects user credentials.
All output is stripped of access tokens, tenant identifiers, local file paths and internal URLs. The agent stops immediately after presenting the preview, because issue creation requires explicit manual confirmation.
What it helps with
- draft a clean bug report for a failed Process Intelligence run
- sanitize error descriptions by stripping tokens, tenant IDs and machine paths
- structure reproduction steps and expected outcomes for support
Example prompts for the agent
- Draft a Process Intelligence bug report for my failed pipeline run
- Help me summarize this error for support without including internal URLs
- Create an issue draft describing the unexpected behavior in Process Intelligence
How to install report-issue
1Plugin marketplace
/plugin marketplace add microsoft/power-platform-skills/plugin install process-intelligence@power-platform-skillsThis installs the whole process-intelligence plugin with all its skills
2Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill report-issue -a claude-code3Manually: put the files in place
~/.claude/skills/report-issue/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/report-issue/
1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill report-issue -a codex2Manually: put the files in place
.agents/skills/report-issue/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill report-issue -a cursor2Manually: put the files in place
.cursor/skills/report-issue/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install microsoft/power-platform-skills plugins/process-intelligence/skills/report-issue2Manually: put the files in place
.github/skills/report-issue/SKILL.md1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill report-issue -a gemini-cli2Platform CLI
gemini skills install https://github.com/microsoft/power-platform-skills --path plugins/process-intelligence/skills/report-issueManually: put the files in place
.devin/skills/report-issue/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.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 report-issue
How to install report-issue in Claude Code?
Run /plugin marketplace add microsoft/power-platform-skills, then execute /plugin install process-intelligence@power-platform-skills.
What does report-issue do?
It collects essential failure details from your input and drafts a sanitized support summary without reading system logs.
Does report-issue submit tickets automatically?
No, it stops at the draft stage. Submitting to an external repository requires explicit user consent and separate tooling.
Source text
SKILL.md · MIT
--- name: report-issue description: Use when the user wants a Process Intelligence bug-report draft or support summary for a failed operation. allowed-tools: AskUserQuestion --- # Draft a Process Intelligence issue **Draft first, do not submit by default.** There is no fixed destination repository. Use only the user's supplied information; this workflow performs no diagnostic collection. 1. Capture the symptom, reproduction, expected/actual behavior and sanitized error code. Include versions only when supplied. Ask one focused question at a time for missing essentials; do not ask again for supplied facts or invent missing details. 2. Do not collect or read logs, profiles, credentials, transcripts or unrelated environment data. Do not run authentication, credential checks, shell commands or business calls to prepare a report. Remove tokens, claims, usernames, tenant/environment/user identifiers, raw errors, tool inputs/results, business values, machine paths and internal URLs from the draft. 3. Show the full preview: intended destination and visibility, title, symptom, reproduction, expected/actual behavior, supplied versions and safe error codes. Include supplied session/request correlation IDs only after the user reviews them; a private destination is not permission to include sensitive data. Allow corrections. Missing evidence does not prove success, failure, cancellation or a hung backend. 4. Stop at the draft. Any later submission requires explicit approval of the exact destination and final content, through the host's supported issue-creation tool. Do not automatically submit, put the report in a URL query, upload files or silently check credentials.
© Microsoft · MIT · microsoft/power-platform-skills
Similar skills
All skills for Agent setup: memory, context, orchestration →report-issue by other authors comes first.