How do I install the Navikt Sokos Skattekort Ktor REST API skill?

Run npx skillmds@latest add tomevault-io/navikt-sokos-skattekort-ktor-rest-api in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Navikt Sokos Skattekort Ktor REST API skill do?

Ktor REST API It is listed under Integrations & APIs on SkillMD.

Is Navikt Sokos Skattekort Ktor REST API safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Navikt Sokos Skattekort Ktor REST API?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Navikt Sokos Skattekort Ktor REST API free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Navikt Sokos Skattekort Ktor REST API?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Navikt Sokos Skattekort Ktor REST API by tomevault-io

Name: Navikt Sokos Skattekort Ktor REST API
Author: tomevault-io

File contents

Ktor REST API

REST patterns for this codebase — both the Ktor server routes and outgoing HTTP clients. Detailed examples live in the sub-files — load them on demand.

Quick reference

Server-side (incoming requests)

Concept	Implementation
Route definition	Extension functions on `Route` (`fun Route.myApi(...)`)
Route mounting	Inside `authenticate(providerName) { ... }` block in `RoutingConfig`
Serialization	`kotlinx.serialization` with `@Serializable` data classes
Request validation	`RequestValidation` plugin with `validate<T>` blocks
Error responses	`StatusPages` plugin mapping exceptions → `ApiError` JSON
Access control	`call.requirePermission()` / `requireScope()` / `requireRole()` per endpoint
Swagger	`swaggerUI()` per API version, backed by OpenAPI YAML specs in `resources/openapi/`
API versioning	Path-based: `/api/v1/...`, `/api/v2/...`
JSON config	Shared `jsonConfig` (`prettyPrint`, `ignoreUnknownKeys`, `encodeDefaults`, `explicitNulls = false`)

Client-side (outgoing requests)

Concept	Implementation
HTTP engine	Ktor `HttpClient(Apache5)` with proxy and keep-alive
Resilience	Resilience4j `CircuitBreaker` wrapping suspend functions
Retry	Ktor `HttpRequestRetry` plugin with exponential backoff
Auth	`bearerAuth()` with Azure AD or Maskinporten tokens
Content negotiation	`ContentNegotiation` with `kotlinx.serialization` JSON
Named dependencies	`@Named("clientName")` for URL and token client injection

Sub-files

server-routes.md — route extension functions, DTOs, request validation, Swagger UI
http-client.md — HttpClient config, circuit breaker, token auth, retry
error-handling.md — StatusPages, ApiError, exception-to-HTTP mapping

Boundaries

Always

Extension functions on Route for API definitions — never inline routes in Application.module()
@Serializable data classes for request/response bodies
Shared jsonConfig for consistent JSON behavior across server and client
StatusPages for centralized error handling — never catch-and-respond in individual routes
Circuit breaker on every outgoing HTTP client
Bearer auth via AzuredTokenClient (M2M) or MaskinportenTokenClient (external)
OpenAPI YAML specs in src/main/resources/openapi/ — Swagger UI is auto-mounted
Access control on every authenticated endpoint

Never

Return raw exceptions to the client — always go through StatusPages
Build HTTP clients without retry and circuit breaker
Use expectSuccess = true on clients where non-2xx is a valid business response
Hardcode URLs — always inject via @Named string constants from PropertiesConfig
Skip access control on authenticated routes

Source: navikt/sokos-skattekort — distributed by TomeVault.

---name: navikt-sokos-skattekort-ktor-rest-apidescription: Ktor REST API---# Ktor REST APIREST patterns for this codebase — both the Ktor server routes and outgoing HTTP clients. Detailed examples live in the sub-files — load them on demand.## Quick reference### Server-side (incoming requests)| Concept | Implementation ||---|---|| Route definition | Extension functions on `Route` (`fun Route.myApi(...)`) || Route mounting | Inside `authenticate(providerName) { ... }` block in `RoutingConfig` || Serialization | `kotlinx.serialization` with `@Serializable` data classes || Request validation | `RequestValidation` plugin with `validate<T>` blocks || Error responses | `StatusPages` plugin mapping exceptions → `ApiError` JSON || Access control | `call.requirePermission()` / `requireScope()` / `requireRole()` per endpoint || Swagger | `swaggerUI()` per API version, backed by OpenAPI YAML specs in `resources/openapi/` || API versioning | Path-based: `/api/v1/...`, `/api/v2/...` || JSON config | Shared `jsonConfig` (`prettyPrint`, `ignoreUnknownKeys`, `encodeDefaults`, `explicitNulls = false`) |### Client-side (outgoing requests)| Concept | Implementation ||---|---|| HTTP engine | Ktor `HttpClient(Apache5)` with proxy and keep-alive || Resilience | Resilience4j `CircuitBreaker` wrapping suspend functions || Retry | Ktor `HttpRequestRetry` plugin with exponential backoff || Auth | `bearerAuth()` with Azure AD or Maskinporten tokens || Content negotiation | `ContentNegotiation` with `kotlinx.serialization` JSON || Named dependencies | `@Named("clientName")` for URL and token client injection |## Sub-files- [server-routes.md](server-routes.md) — route extension functions, DTOs, request validation, Swagger UI- [http-client.md](http-client.md) — HttpClient config, circuit breaker, token auth, retry- [error-handling.md](error-handling.md) — StatusPages, ApiError, exception-to-HTTP mapping## Boundaries### Always- Extension functions on `Route` for API definitions — never inline routes in `Application.module()`- `@Serializable` data classes for request/response bodies- Shared `jsonConfig` for consistent JSON behavior across server and client- `StatusPages` for centralized error handling — never catch-and-respond in individual routes- Circuit breaker on every outgoing HTTP client- Bearer auth via `AzuredTokenClient` (M2M) or `MaskinportenTokenClient` (external)- OpenAPI YAML specs in `src/main/resources/openapi/` — Swagger UI is auto-mounted- Access control on every authenticated endpoint### Never- Return raw exceptions to the client — always go through `StatusPages`- Build HTTP clients without retry and circuit breaker- Use `expectSuccess = true` on clients where non-2xx is a valid business response- Hardcode URLs — always inject via `@Named` string constants from `PropertiesConfig`- Skip access control on authenticated routes---> Source: [navikt/sokos-skattekort](https://github.com/navikt/sokos-skattekort) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Navikt Sokos Skattekort Ktor REST API