equinor/fusion-skill-self-report-bug
skills/.deprecated/fusion-skill-self-report-bug/SKILL.md
Capture Fusion skill workflow failure context and guide a draft-first bug reporting flow with explicit confirmation before any GitHub mutation.
testing
Updated Apr 17, 2026
$ install --global
skillsauthnpx skillsauth add equinor/fusion-skills fusion-skill-self-report-bugInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 12:23 PM20.6s4 files scanned
SKILL.md
- name:
- fusion-skill-self-report-bug
- description:
- Capture Fusion skill workflow failure context and guide a draft-first bug reporting flow with explicit confirmation before any GitHub mutation.
- license:
- MIT
- version:
- 0.1.2
- status:
- deprecated
- deprecated_at:
- 2026-03-21
- successor:
- fusion-skills
- owner:
- @equinor/fusion-core
Deprecated as of 2026-03-21. This skill has been superseded by the
wardenagent infusion-skills, which inlines the full bug reporting workflow and adds proactive frustration detection and skill smell inspection. Usefusion-skillsinstead.Install:
npx -y skills add equinor/fusion-skills fusion-skills
Self-report Fusion Skill Bugs
When to use
Use this skill when a Fusion skill workflow fails and you need a consistent, triage-ready bug report draft.
Treat this as the default failure handoff for any fusion-* skill execution.
Typical triggers:
- "a fusion-* skill failed"
- "this skill run failed"
- "self-report this skill error"
- "create a bug from this workflow failure"
- "capture this automation failure for triage"
When not to use
Do not use this skill for:
- Feature requests or roadmap planning
- General implementation tasks without observed failure
- Publishing GitHub changes without explicit user confirmation
Required inputs
Collect before drafting:
- Target repository for the bug report (default:
equinor/fusion-skills) - Failing command or workflow step
- Environment context (OS/shell/runtime/tooling versions if available)
- Observed output/error evidence
- Reproduction signal (exact steps or best-effort notes)
- Optional parent issue number for linking
Instructions
- Detect or confirm failure intent.
- If failure context is missing, ask for command used, expected behavior, actual behavior, and key error output.
- Capture failure context.
- Normalize context into: command, environment, observed error/output, reproducibility, and impact.
- Draft locally first.
- Write
.tmp/BUG-skill-failure-<context>.mdusingassets/issue-templates/skill-workflow-failure-bug.md. - Include reproducible steps and explicit observed/expected behavior.
- Write
- Propose issue metadata.
- Recommend issue type:
Bug. - Recommend labels for reliability/automation triage (for example
bug,automation,reliability), then validate labels against the target repository before mutation. - Ask assignee preference (
@me, specific user, or unassigned).
- Recommend issue type:
- Offer optional relationship linking.
- If parent issue is provided, prepare to link the new bug as a sub-issue after issue creation.
- Ask explicit publish confirmation.
- Do not run any GitHub mutation until the user explicitly confirms publish.
- Mutate only after confirmation.
- Create issue via MCP issue mutation.
- Apply labels/assignee.
- If parent issue was provided, link as sub-issue.
- If confirmation is not provided, stop after draft.
- Return status
No GitHub state changes made.
- Return status
Expected output
Return:
- Draft bug report file path under
.tmp/ - Captured failure-context summary (command, environment, observed output)
- Proposed title/body and reproduction steps
- Proposed issue type + labels + assignee plan
- Optional parent issue linking plan
- Explicit status:
Awaiting publish confirmationorNo GitHub state changes made - Created issue URL/number only after confirmed mutation
Safety & constraints
Never:
- Perform GitHub create/edit/comment/close actions without explicit confirmation
- Claim failure evidence that was not provided or observed
- Request or expose secrets/credentials
Always:
- Keep draft-first behavior
- Prefer minimal reproducible detail over long narrative
- Validate label existence in the target repository before applying
Related Skills
equinor/fusion-devtools
tools
VerifiedTrustedCommunity
Use Fusion DevTools CLI (fdev) for API testing, token acquisition, service discovery, and person lookup during development. USE FOR: calling Fusion REST APIs, getting access tokens as JSON, discovering services and environments, resolving persons, PIM role activation. DO NOT USE FOR: modifying backend service code, deploying services, infrastructure changes, CI/CD pipeline configuration, or Service Bus operations.
SKILL.mdUpdated May 30, 2026
equinor/fusion
testing
VerifiedTrustedCommunity
Main Copilot skill gate for the Fusion ecosystem — cross-domain router. USE FOR: routing between different Fusion domains (skills, issues, PRs, reviews) when the right domain skill is unclear; getting install guidance for missing skills. DO NOT USE FOR: skill lifecycle operations (use fusion-skills directly), tasks where a specific Fusion skill is already active.
SKILL.mdUpdated Apr 23, 2026
equinor/fusion-skills
tools
VerifiedTrustedCommunity
Entrypoint for all Fusion skill lifecycle operations. USE FOR: finding, installing, updating, syncing, or greenkeeping skills; setting up skill automation; creating or authoring a new skill; reporting a bug with a skill. DO NOT USE FOR: resolving GitHub issues, reviewing PRs, planning task breakdowns, or authoring GitHub issues — those are handled by other Fusion skills.
SKILL.mdUpdated Apr 23, 2026
equinor/fusion-skill-authoring
tools
VerifiedTrustedCommunity
Creates or modernizes repository skills with clear activation cues, purposeful support files, and practical review loops. USE FOR: creating a new skill, tightening an existing skill, improving discovery wording, and structuring references/assets/optional helper agents when they genuinely add value. DO NOT USE FOR: product-code changes, routine copy edits outside skills/, or documentation that should not become an installable skill.
SKILL.mdUpdated Apr 23, 2026