Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
equinor avatar

Fusion Core Services

  • 758 installs
  • 1 repo stars
  • Updated August 4, 2026
  • equinor/fusion-skills

fusion-core-services is a Claude Code skill that gives coding agents reliable access to Equinor Fusion platform services for developers who integrate enterprise Fusion APIs without rewriting connection glue each time.

About

fusion-core-services is an Equinor Fusion platform integration skill from equinor/fusion-skills, listed on Skills.sh with 425 installs and rank 18 in its catalog. It standardizes how Claude and Cursor agents call Fusion core services so developers avoid repeating bespoke API client setup. The skill targets teams building against Equinor's internal Fusion ecosystem who need consistent service discovery, authentication patterns, and endpoint usage from agent sessions. Developers reach for fusion-core-services when agent workflows must read or mutate Fusion-backed data during feature development. It assumes familiarity with Equinor Fusion—not a general-purpose REST client generator.

  • Provides pre-built MCP tools for Fusion Core Services including project, context, and data access patterns
  • Official skill from equinor/fusion-skills repository with 425 installs
  • Enables agents to call real Fusion platform endpoints securely
  • Reduces boilerplate when building internal tools or automation on top of Equinor data platforms

Fusion Core Services by the numbers

  • 758 all-time installs (skills.sh)
  • Ranked #1,361 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/equinor/fusion-skills --skill fusion-core-services

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs758
repo stars1
Last updatedAugust 4, 2026
Repositoryequinor/fusion-skills

How do agents integrate Equinor Fusion core services?

Give their Claude or Cursor agents reliable access to Equinor Fusion platform services without writing custom API glue each time.

Who is it for?

Developers building on Equinor Fusion who want agent-assisted access to core platform services without custom glue code.

Skip if: Developers outside the Equinor Fusion ecosystem or projects needing generic OAuth REST client scaffolding.

When should I use this skill?

A developer working in Equinor Fusion asks an agent to query, update, or orchestrate Fusion core platform services.

What you get

Configured Fusion API calls, service endpoint mappings, and agent-ready integration snippets.

  • Fusion API integration patterns
  • Agent-callable service endpoints

By the numbers

  • 425 installs on Skills.sh
  • Rank 18 in equinor/fusion-skills catalog

Files

SKILL.mdMarkdownGitHub ↗

Fusion Core Services

When to use

Use when the task involves one or more Fusion Core service APIs and the agent needs to identify the right service guidance without requiring separate skill installs.

Typical triggers:

  • implement a Fusion API client
  • wire a Fusion backend service integration
  • figure out which Fusion Core service owns a workflow
  • solve a cross-service task such as context plus people, roles plus notifications, or apps plus service messages

When not to use

  • Modifying code inside fusion-core-services
  • Non-Fusion APIs or generic Microsoft Graph / Power BI work with no Fusion service layer
  • Standalone product workflows already covered by another dedicated skill outside Fusion Core services

Required inputs

  • target workflow or user goal
  • target consumer shape (react, typescript client, csharp httpclient, backend service, or other)
  • known service hints, if any
  • versioning or authorization expectations when relevant

Instructions

1. Scope the request first.

  • Identify whether the workflow touches one service or multiple.
  • If service is ambiguous, use agents/service-router.md to map the workflow to likely services before producing implementation guidance.

2. Read only the relevant service references.

  • Start with Combined API surface.
  • Then open the matching per-service reference file.
  • Pull in the endpoint catalog and model asset for only the services that materially affect the answer.

3. Preserve source-grounded guidance.

  • Prefer controller-backed endpoint and model notes already captured in bundled references.
  • Call out any route or model area that still requires direct source confirmation before shipping.

4. Handle capabilities explicitly.

  • If a service exposes OPTIONS or other access-probe routes, use them to drive capability-aware UI or mutation logic.
  • If a service does not expose stable probes, document conservative client behavior and treat 403 Forbidden as the fallback capability signal.

5. Treat subscriptions as backend-only unless the reference says otherwise.

  • The /subscriptions/... routes are for application-token event registration and CloudEvent-style change handling, not normal frontend CRUD flows.

6. Return consumer-ready guidance.

  • For frontend consumers, return TypeScript-friendly DTOs and a minimal client/hook pattern.
  • For .NET consumers, return a typed HttpClient plan plus DTO record suggestions.
  • For cross-service tasks, explain the service sequence and data handoff between services.

Service catalog

  • Apps: reference, endpoint catalog, models
  • Bookmarks: reference, endpoint catalog, models
  • Context: reference, endpoint catalog, models
  • Contract Personnel: reference, endpoint catalog, models
  • Mail: reference, endpoint catalog, models
  • Notification: reference, endpoint catalog, models
  • People: reference, endpoint catalog, models
  • Portal Config: reference, endpoint catalog, models
  • Reports: reference, endpoint catalog, models
  • RolesV2: reference, endpoint catalog, models
  • Service Messages: reference, endpoint catalog, models
  • Tasks: reference, endpoint catalog, models

Expected output

Return headings in this order: 1. Scope check 2. Service selection 3. Endpoint mapping 4. Model mapping 5. Consumer implementation plan 6. Integration code sketch 7. Validation and test notes 8. Risks and assumptions

Safety & constraints

Never:

  • invent service ownership, routes, or DTO fields
  • answer from generic SaaS/API assumptions when the bundled Fusion references are specific
  • treat backend subscription routes as normal frontend interaction flows

Always:

  • keep cross-service reasoning explicit when more than one service is involved
  • call out capability-probe behavior when the service exposes OPTIONS
  • prefer the narrowest set of service references needed for the user’s workflow

Related skills

FAQ

What platform does fusion-core-services integrate?

fusion-core-services connects coding agents to Equinor Fusion core platform services, standardizing API access so developers skip rewriting connection glue for each agent session.

How popular is fusion-core-services on Skills.sh?

fusion-core-services shows 425 installs and rank 18 on Skills.sh under equinor/fusion-skills, indicating active use among Fusion platform developers.

AI & Agent Buildingagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.