Agent skill · writing content · aiskillstore
ki-register-use-case-documenter
Document AI use cases for EU AI Act governance, inspect code or interview users, then validate and submit confirmed manifests to KI-Register.
Why this skill is useful
Adds specific commands and workflows for documenting AI use cases under EU AI Act compliance that the AI wouldn't reliably generate on its own.
What it needs
Requires node installed locally. Requires kiregister account access. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
KI-Register Use Case Documenter Use this skill when an AI application, process, or workflow should become a structured KI-Register use case for EU AI Act-oriented governance, audit preparation, procurement, supplier requests, or internal review. The operating principle is simple: document first, validate the manifest, get explicit human confirmation, then submit to KI-Register when API credentials are available. Primary outputs docs/agent-workflows/<slug>/manifest.json docs/agent-workflows/<slug>/README.md The manifest is the canonical machine-readable source. The README is the human-readable review surface for operators, legal, compliance, product, and engineering teams. Setup and account flow 1. If the Agent Kit repository is present, use its CLI from the package root: node ./bin/studio-agent.mjs. 2. If the Agent Kit is vendored inside another repo as agent-kit/, use: node ./agent-kit/bin/studio-agent.mjs. 3. If no local onboarding exists, run studio-agent onboard or node ./bin/studio-agent.mjs onboard. 4. If the user does not have a KI-Register account or API key, send them to https://kiregister.com/developers/agent-kit or directly to https://kiregister.com/settings/agent-kit. They should sign in or create an account, create or choose the target register, create one scoped Agent Kit API key, and copy the generated command. 5. Keep KIREGISTERAPIKEY in the environment or a local secret store. Do not write API keys into Git, manifests, README files, logs, screenshots, or skill files. Capture modes Use the smallest mode that can produce a defensible use case record: Codebase inspection: When the user points at a repo, inspect README files, app routes, API routes, config, prompts, workflows, scripts, tests, and docs. Infer only facts that are supported by local evidence. Mark unclear areas as missing and ask targeted follow-up questions. Stakeholder interview: When the process is not visible from files, ask one sharp question at a time. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/ki-register-use-case-documenter