Altinn

Norsk tekstforfatter og redaktør for Digdir: klarspråk, AI-markører, anglisismer, fagtermer, mikrotekst.

Rebase a stacked PR onto main after its parent was squash-merged, using `git rebase --onto` to skip already-merged commits. Use when rebasing a stacked or dependent PR, handling a squash-merged parent PR, or recovering from empty commits or spurious conflicts after `git rebase main`.

Skill for reviewing text content - error messages, labels, help texts and tone of voice. Use this skill only when directly invoked.

Manage the workflow engine's Docker Compose stack. Use when starting, stopping, rebuilding containers, or resetting the database.

Format C# files with CSharpier and verify the build passes. Use when formatting code, fixing build errors from formatting, or before committing changes.

Run k6 load tests against the workflow engine. Use when performance testing, stress testing, or benchmarking.

Manage EF Core database migrations. Use when adding, listing, or removing migrations for the workflow engine.

Write and run tests for the workflow engine. Use when creating tests, adding test coverage, scaffolding test files, or running the test suite.

Explore Altinn access packages — search them, inspect a package's metadata, the resources it contains, and the group/area hierarchy they are organised in. Use for questions about access packages themselves (e.g. "what is the X package", "which packages exist for skatt", "what resources are in package Y", "list the package areas"). Uses the `altinn` MCP server.

Answer questions about Altinn services, resources, access packages and roles using the `altinn` MCP server. Use for any question about who can access a service, what a role or access package grants access to, finding services by name/owner/type, or exploring the Altinn access model. This is the entry point — it explains the data model and routes to the focused altinn-* skills.

Find who or what has access to a specific Altinn service/resource — the access packages and roles granted in its policy. Use for questions like "which access packages have access to <service>", "which roles can use <service>", or "who has access to <service>". Uses the `altinn` MCP server.

Find and describe Altinn services/resources — search by name, owner, type or keyword, and show details such as description, owner, status, resource type, delegable rights and security level. Use for questions about services themselves (e.g. "find services from Skatteetaten", "what is service X", "which MaskinportenSchema resources exist", "what rights does service Y have"). Uses the `altinn` MCP server.

Explore Altinn roles — search roles by name/code, inspect a role's metadata, and list the access packages and resources a role carries. Use for questions about roles themselves (e.g. "what is the DAGL role", "which roles exist", "what packages does daglig leder have", "what can regnskapsfører do"). Uses the `altinn` MCP server.

Find what an Altinn access package or role can access — the list of services/resources it grants. Use for questions like "what services does <access package> have access to", "what can <role> access", or "which resources does tilgangsstyrer grant". Uses the `altinn` MCP server.

Sjekker begrepsbruk på tvers av Altinn-produkter og lager faktagrunnlag for beslutninger.

Norsk tekstforfatter og redaktør. Klarspråk, AI-markører, anglisismer, fagtermer, mikrotekst. Aktiver skill når brukeren ber deg gjennomgå/se gjennom/vurdere en tekstendring.

Scaffold a new vertical-slice endpoint in oed-admin.Server following the Features/<Area>/<Operation>/ convention, and register it in Features/Endpoints.cs with an authorization policy. Use when adding an API route to the admin backend.

Set up or repair a local development environment for oed-admin — dev certificates, the two PostgreSQL databases, user secrets, and client environment variables.

Create and configure Altinn DIS platform custom resources as GitOps-ready Kubernetes manifests — PostgreSQL Database and DatabaseServer, Azure Key Vault, and ApplicationIdentity. Use this whenever the user wants to provision or wire up DIS infrastructure for an Altinn app: creating a database, standing up a postgres server (dedicated or shared), requesting a key vault or secret store, or creating an application / managed identity — even when they don't name the CRD or the operator. Do NOT use this for developing the dis-* operators themselves (controller/reconciler code, regenerating CRD manifests).

Norsk tekstforfatter og redaktør: klarspråk, AI-markører, anglisismer, fagtermer, mikrotekst.

Scaffolds a new EF Core migration for oed-authz, reviews it for safety, and optionally applies it to the local dev database.