{
  "markdown": "# 🤖 Fusion Skills\n\nThis is Fusion’s shared catalog of GitHub Copilot **Agent Skills** — reusable, versioned “mini playbooks” that help you run common workflows consistently.\n\nSkills are designed to be:\n- 🧭 **Actionable**: they guide you through a specific task (not generic chat)\n- 📎 **Concrete**: they state what the agent will produce (files/commands/summary)\n- 🔒 **Safer by default**: they call out constraints and avoid risky automation\n\nIf you just want to use the skills, start with **Quick start**.\n\n## 🚀 Quick start\n\nFor Fusion issue-authoring with GitHub Copilot, use the explicit agent-targeted install command:\n\n```bash\nnpx skills add equinor/fusion-skills \\\n\t--skill fusion-issue-authoring \\\n\t--agent github-copilot \\\n\t-y\n```\n\nFor GitHub Copilot project installs, skills are placed in `.agents/skills`.\nSee https://skills.sh for CLI behavior and agent support details.\n\n### Install a complete developer profile with APM\n\n[APM](https://microsoft.github.io/apm/) installs a composed profile containing skills, custom agents, scoped instructions, and Fusion MCP configuration. Install the [APM CLI](https://microsoft.github.io/apm/getting-started/quick-start/), then choose one profile:\n\n```bash\n# Shared issue, PR review, research, validation, and reporting workflows\napm install equinor/fusion-skills/apm/fusion-developer#<release-tag> --target copilot\n\n# Shared workflows plus Fusion Framework React development\napm install equinor/fusion-skills/apm/fusion-developer-app#<release-tag> --target copilot\n\n# Shared workflows plus Fusion backend service development\napm install equinor/fusion-skills/apm/fusion-developer-services#<release-tag> --target copilot\n\n# Combined Fusion application and backend service development\napm install equinor/fusion-skills/apm/fusion-developer-fullstack#<release-tag> --target copilot\n```\n\nReplace `<release-tag>` with a repository release containing the packages, for example `v1.7.0` (the first release to include `fusion-developer-fullstack`). See [APM packages](apm/README.md) for profile contents and composition.\n\n### Project-first workflow (recommended)\n\n> [!TIP]\n> Use project installs as the default for team sharing and reproducible onboarding.\n\n| Step | Command | Scope | Typical use |\n| --- | --- | --- | --- |\n| Discover | `npx skills add equinor/fusion-skills --list` | Project | See available skills |\n| Install | `npx skills add equinor/fusion-skills` | Project | Add skills to the repo |\n| Restore | `npx skills experimental_install` | Project | Rehydrate from `skills-lock.json` (fresh clones/CI) |\n| Remove | `npx skills remove` | Project | Remove installed skills |\n\n<details>\n<summary><strong>Optional: global install and global update checks</strong></summary>\n\nInstall for your user (local experimentation):\n\n```bash\nnpx skills add equinor/fusion-skills -g\n```\n\nCheck if global updates are available:\n\n```bash\nnpx skills check\n```\n\nUpdate globally installed skills:\n\n```bash\nnpx skills update\n```\n\n</details>\n\n> [!NOTE]\n> `npx skills check` and `npx skills update` currently read the global lock file (`~/.agents/.skill-lock.json`).\n\n## 🔄 Automated skill updates\n\nThis repository provides a **GitHub Actions workflow** you can copy into your repo for automated skill updates — like Dependabot for GitHub Copilot Agent Skills.\n\n> [!IMPORTANT]\n> Current CLI lock scope differs by command:\n> - `npx skills experimental_install` restores from project `skills-lock.json`\n> - `npx skills check` and `npx skills update` read the global lock file (`~/.agents/.skill-lock.json`)\n\nThe workflow automatically:\n- Detects available skill updates from this skills catalog (`equinor/fusion-skills`)\n- Creates a pull request only when skills actually change\n- Includes per-skill changelog summaries in the PR description\n\n### Setup in your repository\n\nIn your repository's `.github/workflows/` directory, create a workflow file (e.g., `skills-update.yml`):\n\n```yaml\nname: Upgrade Agent Skills\n\non:\n  schedule:\n    # Run weekdays at 8 AM UTC\n    - cron: '0 8 * * 1-5'\n  workflow_dispatch:  # Allow manual trigger\n\npermissions:\n  contents: write\n  pull-requests: write\n\njobs:\n  upgrade:\n    uses: equinor/fusion-skills/.github/workflows/skills-update.yml@main\n```\n\n### Configuration notes\n\n- **Schedule**: Adjust the cron expression to your preferred frequency. Examples:\n  - `0 2 * * 1` — Every Monday at 2 AM UTC\n  - `0 0 * * 0` — Every Sunday at midnight UTC\n  - `0 9 * * 1-5` — Every weekday at 9 AM UTC\n\n- **Version pinning**: Replace `@main` with a specific release tag to pin to a version:\n  ```yaml\n  uses: equinor/fusion-skills/.github/workflows/skills-update.yml@v1.0.0\n  ```\n\n- **Manual-only updates**: If you prefer manual-only triggers, remove the `schedule:` section and keep only `workflow_dispatch:`.\n\n- **Permissions**: The workflow requires write access to:\n  - `contents` — to commit skill updates\n  - `pull-requests` — to create and manage pull requests\n\n- **Concurrency**: This workflow does not use concurrency limits. If you run multiple concurrent updates (e.g., from both scheduled and manual triggers), they may update the same PR. This is safe—later commits will overwrite earlier ones on the branch. If you prefer stricter control, add a concurrency block at the job level:\n  ```yaml\n  concurrency:\n    group: skills-upgrade\n    cancel-in-progress: true\n  ```\n\n## 🆕 Automated new-skill discovery (one PR per skill)\n\nThis repository also provides a separate reusable workflow for discovering **new** skills and creating **one PR per skill**.\n\nThe workflow compares:\n- `npx skills add --list equinor/fusion-skills`\n- `npx skills add --list .`\n\nThen it filters ignored skills from `.github/skills-ignore.json`, and opens one branch/PR per remaining skill.\n\n### Setup in your repository\n\nCreate `.github/workflows/skills-discovery.yml`:\n\n```yaml\nname: Discover New Agent Skills\n\non:\n  schedule:\n    - cron: '0 8 * * 1-5'\n  workflow_dispatch:\n\npermissions:\n  contents: write\n  pull-requests: write\n\njobs:\n  discover:\n    uses: equinor/fusion-skills/.github/workflows/skills-discovery.yml@main\n```\n\nOptional inputs:\n\n```yaml\njobs:\n  discover:\n    uses: equinor/fusion-skills/.github/workflows/skills-discovery.yml@main\n    with:\n      source: equinor/fusion-skills\n      ignore-file: .github/skills-ignore.json\n      draft-prs: false\n      skip-if-rejected-pr-exists: true\n```\n\nOptional ignore list in your repository at `.github/skills-ignore.json`:\n\n```json\n{\n  \"ignored\": [\n    \"fusion-example-skill\"\n  ]\n}\n```\n\nIf the ignore file exists, the workflow validates this shape before continuing.\n\nIf a skill already has an open PR from branch `chore/skills-discovery/<skill>`, the workflow updates that PR.\n\n`skip-if-rejected-pr-exists` blocks re-proposing skills where a previous PR from that skill branch was closed without merge.\n\n## 🗑️ Automated deprecation cleanup\n\nThe update workflow also scans installed skills for `metadata.status: deprecated` or `archived` in their SKILL.md frontmatter. For each such skill it creates a separate removal PR that:\n\n- Removes the skill via `npx skills remove`\n- Includes successor recommendation and migration guidance when available\n- Respects previously-rejected removal PRs (won't re-propose)\n\nThis runs automatically as part of the update workflow above. To customize or disable:\n\n```yaml\njobs:\n  upgrade:\n    uses: equinor/fusion-skills/.github/workflows/skills-update.yml@main\n    with:\n      skip-deprecation-cleanup: false  # set true to disable\n      draft-deprecation-prs: false     # set true for draft PRs\n      skip-if-rejected-pr-exists: true # respect rejected PRs\n```\n\n## 🤌 What you get\n\nThis repo contains reusable skills for common workflows (planning, triage, reviews, runbooks, etc.).\n\nEach skill should tell you:\n- when to use it (and when not to),\n- what it will produce (files/commands/summary),\n- what inputs it needs,\n- and what safety constraints apply.\n\n## 📦 What’s in the repo\n\nSkills live under `skills/`. The structure inside a skill is intentionally flexible, but most skills have an entry file:\n\n`skills/fusion-<skill-name>/SKILL.md`\n\n### Available skills\n\nIn this repository, use `fusion-<skill-name>` as the default skill naming convention.\n\n- `skills/` 👍 default, generally available skills\n- `skills/.experimental/` 🧪 preview / in-development skills\n- `skills/.curated/` 👌 curated, broadly reusable skills\n- `skills/.system/` ⚙️ internal/system skills and shared building blocks\n\n<!-- skills-table:start -->\n**⚙️ [`equinor-design-system@0.1.0`](skills/.system/equinor-design-system/SKILL.md)**\n\nAuthoritative, machine-readable EDS design rules for color tokens, typography, spacing, elevation, icons, and page layout zones. USE FOR: looking up correct EDS CSS custom properties, typography variant names, spacing tokens, shadow/elevation tokens, icon usage rules, and Fusion Portal page layout conventions. This is a lookup reference consumed by other skills and agents — it has no standalone workflow. DO NOT USE FOR: React component props or usage examples (use fusion-research + mcp_fusion_search_eds), general Copilot coding tasks, or Fusion Framework API questions.\n\n---\n\n**👍 [`fusion@0.1.0`](skills/fusion/SKILL.md)**\n\nMain 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.\n\n---\n\n**👍 [`fusion-backend-dev@0.1.2`](skills/fusion-backend-dev/SKILL.md)**\n\nGuides 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).\n\n---\n\n**⚙️ [`fusion-code-conventions@0.1.4`](skills/.system/fusion-code-conventions/SKILL.md)**\n\nApplies and explains code conventions across TypeScript, React, C#, and Markdown. Enforces naming rules, file naming patterns, TSDoc and XML doc standards, inline comment intent (the *why*, not the *what*), code structure, error handling, async patterns, and dead code policy. Also enforces ADR and contributor doc decisions, and flags decisions that appear stale or misaligned with current tooling. USE FOR: convention questions, code review against project standards, applying naming rules, auditing intent comments, checking TSDoc completeness, enforcing recorded ADR decisions, and flagging stale architectural decisions. DO NOT USE FOR: security vulnerability scanning, performance profiling, runtime debugging, or generating net-new code without a review target.\n\n---\n\n**🧪 [`fusion-core-services@0.0.2`](skills/.experimental/fusion-core-services/SKILL.md)**\n\nGuides 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.\n\n---\n\n**🧪 [`fusion-dependency-review@0.1.4`](skills/.experimental/fusion-dependency-review/SKILL.md)**\n\nReview dependency PRs with structured research, existing-PR-discussion capture, multi-lens analysis (security, code quality, impact), and a repeatable verdict template. USE FOR: dependency update PRs, Renovate/Dependabot PRs, library upgrade reviews, \"review this dependency PR\", \"should we merge this update\". DO NOT USE FOR: feature PRs, application code reviews, dependency automation/bot configuration, or unattended merge without confirmation.\n\n---\n\n**🧪 [`fusion-design@0.1.2`](skills/.experimental/fusion-design/SKILL.md)**\n\nLooks up Fusion Design Guidelines and applies them to any frontend code in the Fusion ecosystem. USE FOR: layout, spacing, component usage, interaction patterns, any UI implementation decision. DO NOT USE FOR: backend changes, CI/CD, skill authoring, data layer logic.\n\n---\n\n**👍 [`fusion-developer-app@0.4.0`](skills/fusion-developer-app/SKILL.md)**\n\nGuides feature development in Fusion Framework React apps, including app-scoped framework research, test authoring, and test-time mocking needed to choose and verify the right integration patterns. USE FOR: building features, components, pages, hooks, services, API integrations, module configuration, and their tests. DO NOT USE FOR: issue authoring, skill authoring, CI/CD configuration, backend service changes, or general Fusion documentation unrelated to app implementation.\n\n---\n\n**👍 [`fusion-developer-portal@0.0.2`](skills/fusion-developer-portal/SKILL.md)**\n\nGuides 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.\n\n---\n\n**👍 [`fusion-devtools@0.1.1`](skills/fusion-devtools/SKILL.md)**\n\nUse 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.\n\n---\n\n**🧪 [`fusion-framework-mocking@0.1.0`](skills/.experimental/fusion-framework-mocking/SKILL.md)**\n\nGuides seeding deterministic Fusion Framework module state in tests — mockFramework, mockAppModules, and module-owned enableXMock helpers (msal, service-discovery, context, bookmark, feature-flag, analytics, telemetry, http, app) — while keeping each module''s real configurator, provider, validation, and lifecycle. USE FOR: signing in a mock user, seeding context/bookmarks/feature-flags, faking HTTP/OpenAPI responses, choosing a mock boundary, adding a mock for a custom module. DO NOT USE FOR: configuring vitest.config.ts, rendering React components/hooks, or Vitest Browser Mode setup (use fusion-framework-testing); dev-server-time API mocking/proxying in dev-server.config.ts (use fusion-developer-app); backend/service-repo mocking.\n\n---\n\n**🧪 [`fusion-framework-testing@0.1.0`](skills/.experimental/fusion-framework-testing/SKILL.md)**\n\nGuides writing and running Vitest tests for Fusion Framework React apps with @equinor/fusion-framework-vitest-plugin-react-app — choosing a testing layer, configuring vitest.config.ts and Browser Mode, rendering with test/render/renderAppHook/renderAppComponent/testApp fixtures, and troubleshooting or migrating a suite. USE FOR: writing a new app/component/hook test, setting up vitest.config.ts for a Fusion app, choosing between app/framework/module/HTTP test layers, composing or overriding test fixtures, diagnosing a failing Fusion app test. DO NOT USE FOR: seeding module-specific mock state (auth, context, bookmarks, feature flags, HTTP) — use fusion-framework-mocking; dev-server-time API mocking/proxying (use fusion-developer-app); non-Fusion test suites; backend/service-repo tests.\n\n---\n\n**🧪 [`fusion-github-review-resolution@0.1.8`](skills/.experimental/fusion-github-review-resolution/SKILL.md)**\n\nResolves 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 (#pullrequestreview-...), fix the review comments, close the open threads, address PR feedback. DO NOT USE FOR: summarizing feedback without code changes, creating new PRs, or read-only branches.\n\n---\n\n**👍 [`fusion-help-api@0.0.3`](skills/fusion-help-api/SKILL.md)**\n\nGuides 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.\n\n---\n\n**👍 [`fusion-help-docs@0.0.2`](skills/fusion-help-docs/SKILL.md)**\n\nGuides 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.\n\n---\n\n**👍 [`fusion-help-integration@0.0.2`](skills/fusion-help-integration/SKILL.md)**\n\nWires 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.\n\n---\n\n**👍 [`fusion-infra-cli@0.0.1`](skills/fusion-infra-cli/SKILL.md)**\n\nProvision and migrate Fusion databases using the fusion-infra-cli (finf). USE FOR: provision a database for a service, run SQL migrations, provision PR-specific ephemeral databases, check database state. DO NOT USE FOR: application code changes, service deployments, role management, or infrastructure other than databases.\n\n---\n\n**👍 [`fusion-issue-authoring@0.3.5`](skills/fusion-issue-authoring/SKILL.md)**\n\nClassify issue type, activate the matching agent mode for type-specific drafting, and enforce shared safety gates before GitHub mutation.\n\n---\n\n**🧪 [`fusion-issue-solving@0.1.7`](skills/.experimental/fusion-issue-solving/SKILL.md)**\n\nHandles GitHub issue resolution end-to-end for prompts like \"solve #123\", \"lets solve #123\", \"work on #123\", \"work on https://github.com/owner/repo/issues/123\", or by pasting a direct GitHub issue URL as the request. USE FOR: solve #123, continue work on issue #123, work on https://github.com/owner/repo/issues/123, paste a GitHub issue URL for implementation work. DO NOT USE FOR: issue drafting only, PR review only, or non-implementation research.\n\n---\n\n**🧪 [`fusion-issue-task-planning@0.1.6`](skills/.experimental/fusion-issue-task-planning/SKILL.md)**\n\nPlan and break down user-story issues into ordered, traceable task issue drafts with explicit publish gates.\n\n---\n\n**🧪 [`fusion-mcp@1.0.2`](skills/.experimental/fusion-mcp/SKILL.md)**\n\nExplain what Fusion MCP is and guide users through setting it up when they need Fusion-aware MCP capabilities in Copilot workflows.\n\n---\n\n**🧪 [`fusion-package-scribe@0.0.2`](skills/.experimental/fusion-package-scribe/SKILL.md)**\n\nSystematically 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.\n\n---\n\n**🧪 [`fusion-pm-mcp@0.1.0`](skills/.experimental/fusion-pm-mcp/SKILL.md)**\n\nExplain what Fusion PM MCP is and guide setup of the hosted HTTP+OAuth server for its GitHub project-management retrieval tools. USE FOR: setting up or troubleshooting Fusion PM MCP, understanding its issue/PR/milestone tools, filing a setup bug. DO NOT USE FOR: implementing changes to the fusion-pm-mcp service itself, GitHub issue authoring/triage workflows, or general Fusion Framework/docs/EDS retrieval — use `fusion-mcp` for that.\n\n---\n\n**⚙️ [`fusion-research@0.4.1`](skills/.system/fusion-research/SKILL.md)**\n\nSource-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.\n\n---\n\n**👍 [`fusion-roles-cli@0.0.1`](skills/fusion-roles-cli/SKILL.md)**\n\nDeploy and manage Fusion Roles V2 configuration using the fusion-roles-cli (froles). USE FOR: deploy role config from a JSON file, create roles/bindings/assignments, export current role state, inspect role assignments. DO NOT USE FOR: database provisioning, application code changes, Azure AD group management outside role bindings, or Roles V1 management.\n\n---\n\n**⚙️ [`fusion-rule-author@0.1.1`](skills/.system/fusion-rule-author/SKILL.md)**\n\nSupport skill providing the workflow, templates, and references for AI coding assistant rule authoring. Invoked by fusion-rules gateway agents — not intended for direct use.\n\n---\n\n**👍 [`fusion-rules@0.1.1`](skills/fusion-rules/SKILL.md)**\n\nEntrypoint 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.\n\n---\n\n**👍 [`fusion-skill-authoring@0.3.5`](skills/fusion-skill-authoring/SKILL.md)**\n\nCreates 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.\n\n---\n\n**👍 [`fusion-skills@0.0.0`](skills/fusion-skills/SKILL.md)**\n\nEntrypoint 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.\n<!-- skills-table:end -->\n\n## 🔖 Versioning\n\nFor predictable consumer upgrades with `npx skills add|update`:\n\n- Use git tags with semantic versioning for releases (`vMAJOR.MINOR.PATCH`)\n- Treat `main` as latest stable-ish; use prerelease tags for experiments (`v1.3.0-beta.1`)\n- Pin production installs to a tag: `npx skills add equinor/fusion-skills@v1.2.3`\n\nSee `CHANGELOG.md` for release notes.\n\nIf you are developing or maintaining skills in this repository, use `CONTRIBUTING.md` for changesets, release automation, and validation workflows.\n\n<details>\n\t<summary>Where do skills get installed?</summary>\n\n- For GitHub Copilot project installs, skills land in `.agents/skills/` in the current repo.\n- Personal installs use your Copilot user-level skills location.\n\n</details>\n\n## 🔒 Safety & security\n\n> [!CAUTION]\n> - Never paste secrets (tokens/keys/credentials) into prompts, logs, or docs\n> - Only install skills from sources you trust; skills may include executable commands or scripts\n> - Treat `skills/**/scripts/` as security-sensitive code; review and verify before execution\n> - Confirm side effects before running commands (especially destructive operations)\n\nFor details and reporting guidance, see `SECURITY.md`.\n\n> [!WARNING]\n> - This is __NOT__ a general Fusion documentation site (keep long-form docs in the relevant product repos)\n> - This is __NOT__ a place for secrets, tokens, or environment-specific configuration\n> - This is __NOT__ a dumping ground for one-off prompts — skills should be owned and maintained\n\n---\n\nWant to contribute or review changes? See `CONTRIBUTING.md`.\n\nAre you an agent making changes in this repo? See `AGENTS.md`.\n",
  "bytes": 25576,
  "sha": "10eb0136df7ae2a758729d11c73cc3a6761182e8bc911e543155998f44cad0b9",
  "repo_slug": "equinor/fusion-skills",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/skl_equinor_fusion_skills_fusion_research_fd9305a8/readme"
}