report-issue
Use when the user wants a Process Intelligence bug-report draft or support summary for a failed operation.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.1k
- Forks
- 232
01 前言 Front Matter
- 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
03 SKILL.md 正文
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.
- 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.
- 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.
- 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.
- 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.
04 同仓库更多 Skills
compare-site-configurations
Compare Power Pages site configurations between two environments, such as dev, test and production, or between a local download and the live site, and explain which differences change site behavior. Use when a site works in one environment but not another (for example, works in dev but fails in test), to check configuration drift before promoting or deploying, or to see what changed between two sites. Produces a shareable HTML report and a JSON file that VS Code can import.
setup
Use when Process Intelligence needs building, explicit cloud/account/environment configuration, sign-in, connection diagnostics, or recovery from an authentication error.
investigate-process
Use when a broad Process Mining business question, observed pattern or competing explanation needs investigation across analytical perspectives.
derive-metric
Use when a requested measure is missing, a saved custom metric needs reuse, or an ephemeral formula or derived scalar is needed.
compare-cohorts
Use when comparing process cohorts, departments, periods or before-and-after results under matched definitions.
analyze-variants
Use when investigating common or slow variants, repeated work, unusual paths, or a specific Process Mining case.