Reproduce Chat States
different-ai/openwork
Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.
A skill your agent uses when the user wants to report a bug, file an issue, submit a bug report, or report any problem with the mobile-app plugin.
Install Report Issue
$ npx skills add microsoft/power-platform-skills --skill report-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install microsoft/power-platform-skills report-issue --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/microsoft/power-platform-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/mobile-apps/skills/report-issue .claude/skills/report-issue && 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 "report-issue" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/mobile-apps/skills/report-issue into .claude/skills/report-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "report-issue", 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/microsoft/power-platform-skills/tree/main/plugins/mobile-apps/skills/report-issueType 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 microsoft/power-platform-skills --skill report-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install microsoft/power-platform-skills report-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/power-platform-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/mobile-apps/skills/report-issue .agents/skills/report-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "report-issue" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/mobile-apps/skills/report-issue into .agents/skills/report-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "report-issue", 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 microsoft/power-platform-skills --skill report-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install microsoft/power-platform-skills report-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/power-platform-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/mobile-apps/skills/report-issue .cursor/skills/report-issue && 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 "report-issue" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/mobile-apps/skills/report-issue into .cursor/skills/report-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "report-issue", 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/microsoft/power-platform-skills.git --path plugins/mobile-apps/skills/report-issue--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 microsoft/power-platform-skills --skill report-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install microsoft/power-platform-skills report-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/power-platform-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/mobile-apps/skills/report-issue .gemini/skills/report-issue && 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 "report-issue" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/mobile-apps/skills/report-issue into .gemini/skills/report-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "report-issue", 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 microsoft/power-platform-skills report-issueInstalls 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 microsoft/power-platform-skills --skill report-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/microsoft/power-platform-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/mobile-apps/skills/report-issue .github/skills/report-issue && 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 "report-issue" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/mobile-apps/skills/report-issue into .github/skills/report-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "report-issue", 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 microsoft/power-platform-skills --skill report-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install microsoft/power-platform-skills report-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/power-platform-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/mobile-apps/skills/report-issue .opencode/skills/report-issue && 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 "report-issue" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/mobile-apps/skills/report-issue into .opencode/skills/report-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "report-issue", 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
report-issue- GitHub stars
- 967
- Token cost
- ~1.8k tokens
- SKILL.md length
- 494 words
- Files
- 1
- Skills in repo
- 87
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when the user wants to report a bug, file an issue, submit a bug report, or report any problem with the mobile-app plugin.
- Works in 5 steps: Capture user description → Detect project context → Collect diagnostics → …
- The user wants to report a bug
- SKILL.md covers Workflow and Notes
- Calls node, npx and npm
What it does
Report Issue is an agent skill from microsoft/power-platform-skills, published by the product's own GitHub organization. Use when the user wants to report a bug, file an issue, submit a bug report, or report any problem with the mobile-app plugin.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering QA and bug reports. It works with Power Automate. The repository describes itself as: A plugin marketplace for GitHub Copilot and other AI agents that provides Power Platform development plugins, including reusable skills, agents, and commands for building and… The licence is MIT.
When your agent uses it
- The user wants to report a bug
- Submit a bug report
- Report any problem with the mobile-app plugin
Example prompts
- “/report-issue”
Requirements
- Node.js
- Pre-approved tools (allowed-tools): Read, Bash, Glob, Grep, AskUserQuestion
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 5ef4e4f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashGlobGrepAskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
nodenpxnpmazjavagit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, npm, az and git, which can reach the network depending on how they are called.
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
Report Issue loads about 1.8k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 494 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:119
- Contents of `.env` or any file matching `.env*` - NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion
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 microsoft/power-platform-skills at commit 5ef4e4f, republished under its MIT licence (© microsoft). 494 words, ~1,814 tokens.
Download SKILL.mdSave it as
.claude/skills/report-issue/SKILL.md (or your agent's skills folder).- name
- report-issue
- description
- Use when the user wants to report a bug, file an issue, submit a bug report, or report any problem with the mobile-app plugin.
- allowed-tools
- Read, Bash, Glob, Grep, AskUserQuestion
- user-invocable
- true
- argument-hint
- [optional: brief description of the bug]
- model
- haiku
Plugin check: Run
node "${PLUGIN_ROOT}/scripts/check-version.js"- if it outputs a message, show it to the user before proceeding.
📋 Shared instructions: shared-instructions.md — read this first.
Report Issue — mobile-app
Generates a fully-populated GitHub issue body for the microsoft/power-platform-skills repo, scoped to the mobile-app plugin. Read-only — no project modifications.
Workflow
- Capture user description → 2. Detect project context → 3. Collect diagnostics → 4. Render issue body → 5. Print URL
Step 1 — Capture user description
Telemetry checkpoint: capture_issue_description
If $ARGUMENTS contains a description, use it. Otherwise prompt:
"What's the issue? Briefly describe what you expected vs. what happened. (You can paste error output if helpful.)"
Then ask via AskUserQuestion:
"Issue category? (a) Bug — something broke (b) Unexpected behavior — wrong output but no error (c) Documentation — docs are wrong / missing (d) Feature request (e) Question / discussion"
"How blocking is this? (a) Blocking — can't proceed at all (b) Workaround exists — but painful (c) Annoying — non-critical (d) Polish — nice-to-have"
Step 2 — Detect project context
Read-only checks:
test -f power.config.json && echo "in_project=true" || echo "in_project=false"
pwd
node --version
npm --version
node scripts/resolve-environment.js "$(node -e \"console.log(require('./power.config.json').environmentId)\")" 2>/dev/null || true
az --version 2>/dev/null | head -1
npx expo --version 2>/dev/null
uname -srmIf in a project:
node -e "console.log(require('./package.json').name, require('./package.json').version)" 2>/dev/null
node -e "console.log(JSON.stringify({env: require('./power.config.json').environmentId, name: require('./power.config.json').displayName}))"
test -f memory-bank.md && echo "memory_bank=present"
test -f native-app-plan.md && echo "plan=present"
ls src/generated/services/ 2>/dev/null | head -10If the description names a package matching @microsoft/power-apps-native-*, collect its declared and lockfile-resolved versions from package.json and package-lock.json. Do not read package source or metadata from node_modules/.
node - <<'NODE'
const fs = require('node:fs');
const manifest = JSON.parse(fs.readFileSync('package.json', 'utf8'));
const lockfile = fs.existsSync('package-lock.json')
? JSON.parse(fs.readFileSync('package-lock.json', 'utf8'))
: null;
const dependencies = { ...manifest.dependencies, ...manifest.devDependencies };
for (const [name, declared] of Object.entries(dependencies)) {
if (!name.startsWith('@microsoft/power-apps-native-')) continue;
const resolved = lockfile?.packages?.[`node_modules/${name}`]?.version ?? 'unknown';
console.log(`${name}\tdeclared=${declared}\tresolved=${resolved}`);
}
NODEFor native-build issues also capture:
[ "$(uname)" = "Darwin" ] && xcode-select -p
[ "$(uname)" = "Darwin" ] && pod --version 2>/dev/null
java -version 2>&1 | head -1
echo "ANDROID_HOME=$ANDROID_HOME"Step 3 — Collect diagnostics
Telemetry checkpoint: collect_issue_diagnostics
Run npx expo doctor and capture the text output verbatim.
Ask for the affected workflow's Support ID when available. Use the telemetry
helper's read-only --report mode from the affected project to inspect only its
allowlisted timeline. Include the Support ID and relevant step/error category in
the issue body, not environment, tenant, or organization IDs. Do not
upload the telemetry directory or raw timing/authentication files.
If the user pasted an error, capture verbatim. Otherwise look for recent failure signals:
- Last 50 lines of any Metro / Gradle / Xcode log if user mentions a build failure
git status --shortif in a git repo (to show modified files — sanitize for secrets first)- Output of
npx tsc --noEmitif relevant
Show full SKILL.md (178 more words)Show less
Do NOT capture:
- Contents of
src/playerConfig.ts(contains tenantId / clientId — sensitive) - Contents of
.envor any file matching.env* - Connection IDs unless the user explicitly opted in (PII / can map to tenant)
- Anything under
node_modules/ - Package source excerpts, patched package contents, or proposed fork code
- Tenant/environment/organization IDs in a public issue, even though verified IDs can exist in access-controlled telemetry
Step 4 — Render issue body
Telemetry checkpoint: render_issue_report
Print this block — user copies into a new issue:
### Description
<user's description>
### Category
<Bug / Unexpected behavior / Docs / Feature / Question>
### Severity
<Blocking / Workaround / Annoying / Polish>
### Environment
| | |
|---|---|
| Plugin | mobile-app |
| Plugin version | <from .plugin/plugin.json, or legacy .claude-plugin/plugin.json fallback, or "unknown"> |
| OS | <uname output> |
| Node | <version> |
| npm | <version> |
| Power Apps CLI | <version> |
| Expo CLI | <version> |
| Xcode | <if macOS> |
| JDK | <if android> |
| ANDROID_HOME set | <yes/no> |
### Project context
<if in project>
- Mobile project detected: yes
- Support ID: `<affected workflow run GUID, or unavailable>`
- Failed step / error category: `<registered step and fixed category, or unknown>`
- Memory bank present: <yes/no>
- Plan present: <yes/no>
- Connector count: <count, not generated service or business-table names>
</if>
<if not in project>
Not run inside a mobile-app project.
</if>
### Affected native package
<include only when the issue concerns @microsoft/power-apps-native-*>
- Package: `<package name>`
- Declared version: `<package.json range>`
- Resolved version: `<package-lock.json version or unknown>`
- Platform: `<iOS / Android>`
- Ownership evidence: <why the documented caller contract is satisfied and the failure is package-internal>
### Reproduction steps
1.
2.
3.
### Expected
<what should have happened>
### Actual
<what happened>
### Logs / errors
<paste verbatim — sensitive values redacted>
### Notes
<anything else>Step 5 — Print URL
Telemetry checkpoint: generate_issue_submission_url
Tell the user:
Open this URL to file the issue:
https://github.com/microsoft/power-platform-skills/issues/new?labels=plugin%3Amobile-app
Paste the block above into the body. Review for any sensitive values before submitting.
If the user wants to open it, suggest open <url> (macOS) / xdg-open <url> (Linux) / start <url> (Windows). Do not auto-open without confirmation.
Notes
- This skill never modifies any file or invokes mutating commands. Pure diagnostic.
- For diagnosing connection-specific failures, suggest the user run
/list-connectionsfirst and paste that output into the issue. - For diagnosing build failures, suggest they include the full Metro/Gradle/Xcode log (not truncated).
© microsoft, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/mobile-apps/skills/report-issue of microsoft/power-platform-skills.
Open the folder on GitHubat commit 5ef4e4f
Compare with similar skills
Report Issue 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 |
|---|---|---|---|---|---|---|
| Report Issue this skillmicrosoft/power-platform-skills | 967 | — | ~1.8k | Automated safety check: Notes | MIT | |
| Reproduce Chat Statesdifferent-ai/openwork | 24k | — | ~673 | Automated safety check: Pass | Custom licence | |
| Dynamo Jira TicketDynamoDS/Dynamo | 2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Minimal Run And Auditlllllllama/RigorPilot-Skills | 497 | 2 repos | ~691 | Automated safety check: Pass | MIT | |
| Moav E2EMotherofallVPNs/MoaV | 448 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Creating A Coral TaskHuman-Agent-Society/CORAL | 1k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Dynamo Jira Ticket
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
Minimal Run And Audit
lllllllama/RigorPilot-Skills
Rigor Run skill for README-first deep learning repo reproduction.
Moav E2E
MotherofallVPNs/MoaV
Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.
Creating A Coral Task
Human-Agent-Society/CORAL
Author a new CORAL task — the three pieces that must line up (task.yaml, seed/, a packaged grader/), the coral init → coral validate → smoke-test loop, and how to pick a grader pattern (stdout…
Launch Rl
marin-community/marin
Define, validate, submit, or restart a Marin SkyRL experiment through its artifact main.
More from microsoft/power-platform-skills
All 87 skills in this repo- Official
Manage Firewall
microsoft/power-platform-skills
Inspects and configures the web application firewall (WAF) in front of a Power Pages production site.
- Official
Manage Headers
microsoft/power-platform-skills
Inspects and configures the security headers a Power Pages site sends to browsers — Content Security Policy, frame and clickjacking protection, cross-origin sharing, cookie behavior, and related…
- Official
Scan Code
microsoft/power-platform-skills
Scans a Power Pages site project for security issues in source code and dependencies.
- Official
Scan Site
microsoft/power-platform-skills
Runs a security scan on a deployed Power Pages site, fetches the latest scan report, and produces a plain-language summary.
- Official
Setup Datamodel
microsoft/power-platform-skills
Creates Dataverse tables, columns, and relationships for a Power Pages site based on a data model proposal.
- Official
Add Server Logic
microsoft/power-platform-skills
Creates, edits, and manages Power Pages Server Logic files — server-side JavaScript that runs securely on the Power Pages runtime.
Related
Works with
Categories
Questions about Report Issue
What does Report Issue do?
A skill your agent uses when the user wants to report a bug, file an issue, submit a bug report, or report any problem with the mobile-app plugin. Report Issue is an agent skill from microsoft/power-platform-skills, published by the product's own GitHub organization. Use when the user wants to report a bug, file an issue, submit a bug report, or report any problem with the mobile-app plugin.
When should I use Report Issue?
Report Issue fits situations like: the user wants to report a bug; submit a bug report; report any problem with the mobile-app plugin.
How do I install Report Issue in Claude Code?
Run `npx skills add microsoft/power-platform-skills --skill report-issue -a claude-code`. Or copy the skill folder (plugins/mobile-apps/skills/report-issue in microsoft/power-platform-skills) into .claude/skills/report-issue in your project. Claude Code loads it when a task matches its description.
How do I install Report Issue in Codex?
Run `npx skills add microsoft/power-platform-skills --skill report-issue -a codex`. Or copy the skill folder (plugins/mobile-apps/skills/report-issue in microsoft/power-platform-skills) into .agents/skills/report-issue in your project. Codex loads it when a task matches its description.
Can I use Report Issue 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 microsoft/power-platform-skills --skill report-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/report-issue, .gemini/skills/report-issue, .github/skills/report-issue and .opencode/skills/report-issue in your project.
What does Report Issue need to run?
Going by SKILL.md and its folder, Report Issue needs the command-line tools its instructions call (node, npx, npm, az, java and git). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Bash, Glob, Grep, AskUserQuestion.
Does Report Issue access the network?
SKILL.md contains no URLs. Its commands use npx, npm and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Report Issue safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file; pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Report Issue use?
Report Issue is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Report Issue use?
About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Report Issue?
Skills that share tags, products or a category with Report Issue: Reproduce Chat States (different-ai/openwork, 24k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars), Minimal Run And Audit (lllllllama/RigorPilot-Skills, 497 stars) and Moav E2E (MotherofallVPNs/MoaV, 448 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Report Issue?
microsoft (a GitHub organization, an official publisher) maintains it in microsoft/power-platform-skills, which has 967 GitHub stars. The repository holds 87 skills in this directory. The repository was last updated on October 6, 2026.
Source: microsoft/power-platform-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.