fusion-core-services
Skill2 starsChanged 2 months agoMITView on GitHub
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.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- caveman-compressSkill
- fusion-dependency-reviewSkill
- fusion-designSkill
- fusion-framework-mockingSkill
- fusion-framework-testingSkill
- fusion-github-review-resolutionSkill
- fusion-issue-solvingSkill
- fusion-issue-task-planningSkill
- fusion-mcpSkill
- fusion-package-scribeSkill
- fusion-pm-mcpSkill
- fusion-backend-devSkill
- fusion-developer-appSkill
- fusion-developer-portalSkill
- fusion-devtoolsSkill
- fusion-help-apiSkill
- fusion-help-docsSkill
- fusion-help-integrationSkill
- fusion-infra-cliSkill
- fusion-issue-authoringSkill
- fusion-roles-cliSkill
- fusion-rulesSkill
- fusion-skill-authoringSkill
- fusionSkill
- fusion-skillsSkill
- equinor-design-systemSkill
- fusion-code-conventionsSkill
- fusion-researchSkill
- fusion-rule-authorSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 11 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Use when the task involves one or more Fusion Core service APIs and the agent needs to identify the right service guidance without …
- Very specific: line 49
If service is ambiguous, use agents/service-router.md to map the workflow to likely services before producing implementation guidance.
- Distinctive: line 51
Read only the relevant service references.
- Distinctive: line 52
Start with Combined API surface.
- Very specific: line 57
Every Fusion Core service publishes its current OpenAPI document publicly, with no JWT required: …
- Distinctive: line 67
If you cannot fetch the live OpenAPI document (no web-fetch tool or network access), explicitly state that limitation, treat bundled …
- Distinctive: line 70
If the subdomain isn't already known from the service catalog below, resolve it via Fusion service discovery rather than guessing, per the …
- Distinctive: line 75
Prefer the live OpenAPI document over the bundled reference's own "suggested model" lists when they disagree — the live document is always …
- Distinctive: line 77
Call out any route or model area that still requires direct source confirmation before shipping.
- Very specific: line 80
If a service exposes OPTIONS or other access-probe routes, use them to drive capability-aware UI or mutation logic.
- Very specific: line 81
If a service does not expose stable probes, document conservative client behavior and treat 403 Forbidden as the fallback capability signal.
- Distinctive: line 83
Treat subscriptions as backend-only unless the reference says otherwise.
- Distinctive: line 125
treat backend subscription routes as normal frontend interaction flows
- Distinctive: line 130
keep cross-service reasoning explicit when more than one service is involved
- Very specific: line 131
call out capability-probe behavior when the service exposes OPTIONS
- Distinctive: line 132
prefer the narrowest set of service references needed for the user’s workflow
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- Scope the request first.
- Identify whether the workflow touches one service or multiple.
- If service is ambiguous, use
agents/service-router.mdto map the workflow to likely services before producing implementation guidance.
- 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.
- Fetch the live OpenAPI document before trusting exact names or shapes.
- Every Fusion Core service publishes its current OpenAPI document publicly, with no JWT required:
https://{service}.api.fusion.equinor.com/openapi/api-v{version}.json(e.g.https://people.api.fusion.equinor.com/openapi/api-v3.json,https://context.api.fusion.equinor.com/openapi/api-v1.json). - The bundled reference files are a curated index of which services/controllers exist and how to
approach them — not the source of truth for exact schema/type names, which drift as services
change. Fetch the live document for the target service(s) and read
components.schemasfor the real type names — responses are commonlyApi{Entity}and request bodies a plain{Verb}{Entity}Requestname, but the live document's exact name always wins over any pattern; never invent aDto-suffixed name that isn't actually incomponents.schemas. - If you cannot fetch the live OpenAPI document (no web-fetch tool or network access), explicitly state that limitation, treat bundled references/assets as best-effort, and avoid asserting exact schema/type names or required fields.
- If the subdomain isn't already known from the service catalog below, resolve it via Fusion service discovery rather than guessing, per the platform-wide rule of never hardcoding service addresses.
- Preserve source-grounded guidance.
- Prefer the live OpenAPI document over the bundled reference's own "suggested model" lists when they disagree — the live document is always current, the bundled file may not be.
- Call out any route or model area that still requires direct source confirmation before shipping.
- Handle capabilities explicitly.
- If a service exposes
OPTIONSor 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 Forbiddenas the fallback capability signal.
- 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.
- Return consumer-ready guidance.
- For frontend consumers, return TypeScript-friendly models (named after the real schema, not
Dto-suffixed) and a minimal client/hook pattern. - For .NET consumers, return a typed
HttpClientplan that deserializes directly into the real schema type from the live document (commonlyApi{Entity}, but use whatevercomponents.schemasactually names it) rather than a hand-rolled shadow record, where one is published. - 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:
- Scope check
- Service selection
- Endpoint mapping
- Model mapping
- Consumer implementation plan
- Integration code sketch
- Validation and test notes
- Risks and assumptions
Safety & constraints
Never:
- invent service ownership, routes, or model fields
- invent a
Dto-suffixed type name, or any name not actually present in the live OpenAPI document'scomponents.schemas— use the exact real name, whatever pattern it follows - answer from generic SaaS/API assumptions when the bundled Fusion references are specific
- treat backend subscription routes as normal frontend interaction flows
Always:
- fetch the live OpenAPI document for the target service(s) before naming a type — the bundled reference files can drift out of date, the live document cannot
- 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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

