Equinor
30 skills
fusion-issue-authoring
Passed all 3 security checks
Classify issue type, activate the matching agent mode for type-specific drafting, and enforce shared safety gates before GitHub mutation.
·01.3k
fusion-issue-solving
Passed all 3 security checks
·01k
fusion-github-review-resolution
Passed all 3 security checks
Resolves unresolved GitHub PR review threads end-to-end: evaluates whether each review comment is correct, applies a targeted fix when valid, replies with rationale when not, commits, and resolves the thread. USE FOR: unresolved review threads, PR review feedback, changes requested PRs, PR review URLs (
·01k
fusion-mcp
Passed all 3 security checks
Explain what Fusion MCP is and guide users through setting it up when they need Fusion-aware MCP capabilities in Copilot workflows.
·0924
fusion-skill-authoring
Passed all 3 security checks
'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.'
·0916
fusion-issue-task-planning
Passed all 3 security checks
Plan and break down user-story issues into ordered, traceable task issue drafts with explicit publish gates.
·0880
fusion-dependency-review
Passed all 3 security checks
·0787
fusion-code-conventions
Passed all 3 security checks
'Applies and explains code conventions across TypeScript, React, C
·0736
fusion-skills
Passed all 3 security checks
'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.'
·0531
fusion-research
Passed all 3 security checks
'Source-backed research orchestrator for the Fusion ecosystem. Routes to the correct research agent based on question type. Returns source-backed evidence only; will not invent Framework behavior, component APIs, skill catalog relationships, platform guidance, or backend implementation details. USE FOR: any research question needing source-backed evidence about Fusion Framework APIs, EDS components, the Fusion skill catalog, Fusion platform documentation, or backend service implementation. DO NOT USE FOR: implementing code changes, installing or editing skills, MCP setup or troubleshooting, or inventing Fusion behavior without evidence.'
·0504
fusion-issue-author-task
Passed all 3 security checks
DEPRECATED: Use fusion-issue-authoring instead. Previously: Draft and update task issues with checklist-first decomposition and dependency-aware sequencing.
·022
fusion-issue-author-user-story
Passed all 3 security checks
DEPRECATED: Use fusion-issue-authoring instead. Previously: Draft and update user-story issues with role-action-value framing and workflow scenarios.
·019
fusion-issue-author-feature
Passed all 3 security checks
DEPRECATED: Use fusion-issue-authoring instead. Previously: Draft and update feature issues with clear problem framing and scoped requirements.
·019
fusion-issue-author-bug
Passed all 3 security checks
DEPRECATED: Use fusion-issue-authoring instead. Previously: Draft and update bug issues using a bug-focused structure.
·018
fusion-skill-self-report-bug
Passed all 3 security checks
Capture Fusion skill workflow failure context and guide a draft-first bug reporting flow with explicit confirmation before any GitHub mutation.
·017
fusion-discover-skills
Passed all 3 security checks
'DEPRECATED: Use fusion-skills instead. This skill has been superseded by fusion-skills, which provides discover, sync, and author modes in a single orchestrator.'
·014
fusion-rules
Passed all 3 security checks
'Entrypoint for AI coding assistant rule authoring across GitHub Copilot, Cursor, and Claude Code. USE FOR: setting up rules, reviewing existing rules, scaffolding instruction files, or asking which editor format to use. DO NOT USE FOR: authoring skills (SKILL.md), agent definitions (.agent.md), or CI enforcement of rule files.'
·013
fusion-package-scribe
Passed all 3 security checks
'Systematically improves TSDoc and README documentation across packages in a TypeScript monorepo. Discovers public API surfaces, generates or improves TSDoc on all exports, rewrites READMEs to a consistent retrieval-friendly structure, and commits each package independently. USE FOR: monorepo-wide documentation passes, single-package doc improvements, TSDoc generation on public exports, README standardization, review council quality checks. DO NOT USE FOR: runtime code changes, security scanning, API reference site generation, non-TypeScript languages.'
·012
fusion-devtools
Passed all 3 security checks
'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.'
·012
fusion-rule-author
Passed all 3 security checks
'Support skill providing the workflow, templates, and references for AI coding assistant rule authoring. Invoked by fusion-rules gateway agents — not intended for direct use.'
·012
fusion-framework-feature-toggling
Passed all 3 security checks
'Guides developers using Fusion Framework feature flags with MCP-backed framework retrieval first and bundled public-source fallback assets when MCP is unavailable. USE FOR: helping with `enableFeatureFlag`, `enableFeatureFlagging`, `useFeature`, rollout/cleanup guidance, and finding Fusion Framework feature-flag examples. DO NOT USE FOR: generic SaaS flag platforms, backend-only rollout systems, or inventing framework APIs.'
·011
fusion-help-integration
Passed all 3 security checks
'Wires Fusion Help Center into app pages — creates article slug constants, adds useHelpCenter hook, and connects PageLayout props so users can open contextual help articles. USE FOR: add help button to page, wire useHelpCenter, create helpArticles constants, integrate Fusion Help in app, connect PageLayout to help center, add openHelpArticle to page. DO NOT USE FOR: authoring markdown help articles (use fusion-help-docs), direct Help REST API calls (use fusion-help-api), modifying @fra/ui shared components.'
·011
fusion-core-services
Passed all 3 security checks
'Guides integrations across Fusion Core service APIs from a single installable skill. USE FOR: service discovery across apps, people, context, roles, notifications, reports, tasks, and other Fusion Core APIs; cross-service integration planning; choosing the right endpoint/model guidance for a workflow. DO NOT USE FOR: modifying Fusion backend source code, non-Fusion APIs, or generic cloud architecture work without a Fusion service integration target.'
·011
fusion-app-react-dev
Passed all 3 security checks
'DEPRECATED — use fusion-developer-app instead. Guides feature development in Fusion Framework React apps.'
·011
fusion-help-api
Passed all 3 security checks
'Guides developers and admins through direct interaction with the Fusion Help REST API — reading articles, FAQs, release notes, searching content, and managing help documentation programmatically. USE FOR: fetch help articles from API, integrate help content in app, search help content, manage help documentation via API, automate help content, build help tooling. DO NOT USE FOR: using the fhelp CLI tool (use fusion-help-docs skill), modifying Fusion.Services.Help backend code, or non-help-API tasks.'
·010
fusion-backend-dev
Passed all 3 security checks
'Guides consumption and understanding of Fusion backend services, APIs, and patterns for frontend/client developers, integrators, and architects. Shows reference implementations, explains architectural decisions, and clarifies contracts. USE FOR: understanding Fusion backend APIs, learning implementation patterns, exploring reference code, choosing the right integration point, and understanding authorization/validation/async patterns. DO NOT USE FOR: modifying backend services, creating new endpoints, database changes, or backend-specific development (use fusion-services-develop or backend service repo instead).'
·010
fusion-help-docs
Passed all 3 security checks
'Guides app teams through authoring, structuring, and publishing help documentation (articles, release notes, FAQs) using the fusion-help-cli. USE FOR: write help articles, create release notes, set up help docs, publish documentation, sync articles, configure help config file, maintain app help content. DO NOT USE FOR: building the CLI itself, modifying Fusion.Services.Help internals, or non-documentation tasks.'
·010
fusion-developer-app
Passed all 3 security checks
'Guides feature development in Fusion Framework React apps, including app-scoped framework research needed to choose the right hooks, modules, packages, and integration patterns before implementation. USE FOR: building new features, adding components or pages, creating hooks and services, wiring up API endpoints, extending Fusion module configuration, and answering app implementation questions about which Fusion Framework surface to use. DO NOT USE FOR: issue authoring, skill authoring, CI/CD configuration, backend service changes, or general Fusion documentation that is not tied to app implementation.'
·010
fusion-developer-portal
Passed all 3 security checks
'Guides development of Fusion portal shells — scaffolding, module configuration, app loading, routing, header/context integration, analytics, and deployment using the Fusion Framework CLI portal commands. USE FOR: create portal, scaffold portal, configure portal modules, portal app loading, portal routing, portal header, context selector, portal analytics, portal telemetry, portal manifest, ffc portal dev, portal deployment, embed apps in portal. DO NOT USE FOR: app-level feature development (use fusion-app-react-dev), backend service changes, Fusion Help Center integration, skill authoring.'
·010
Route your request to the right tool
Passed all 3 security checks
When you're not sure which skill handles code reviews, PRs, issues, or skills themselves, this asks clarifying questions and routes you to the right place with setup help.
Engineering / workflow-sprint-structuremetafor-engineers
·08