k-ID Agent Skills
Agent Skills for integrating k-ID — age-appropriate compliance as a service —
into your app, game, or platform. These skills cover the full range of
jurisdictional regimes a k-ID integration can be configured for:
- COPPA (US)
- GDPR-Kids (EU)
- UK AADC and the UK Online Safety Act (highly effective age assurance for 18+ features)
- Brazil ECA Digital (loot-boxes and targeted ads at 18, direct marketing at 12)
- Australia Online Safety Act (social media minimum age)
- Other regional regimes configured in k-ID Compliance Studio
They follow the open Agent Skills specification
and work with 35+ AI coding agents including Claude Code, Cursor, OpenAI
Codex, GitHub Copilot, Gemini CLI, and others.
Canonical reference for API shapes and endpoints remains
docs.k-id.com. These skills encode integration
patterns, compliance invariants, and known pitfalls — not API documentation.
Two integration shapes
The skills cover both k-ID integration shapes. Use whichever matches
your product.
- Shape A — Full sessioned integration. Age gate → session →
(consent | verification | threshold) → permissions. For games,
social platforms, and multi-feature apps that need persistent
per-user state and multiple gated features.
- Shape B — Standalone AgeKit+. One call to the age-verification
endpoint, no session, no permission-management UI. For 18+ sites
(UK OSA), age-restricted downloads, AU social-media minimum-age
checks, or any single age-proof decision.
The router skill detects which shape applies from the user's request.
Two UI approaches within Shape A
Within Shape A, there is a second choice: custom UX workflows
(build the UI, call the APIs) or widgets (pre-built k-ID iframes).
- Custom UX workflows (the default). Build the age gate and
consent UI yourself and call
/age-gate/check,
/challenge/send-email, etc. directly. Produces the best-looking,
most brand-integrated experience, renders inline (no iframe), and
works on every platform k-ID supports — including Unity WebGL,
consoles, and native desktop apps where iframes aren't practical.
Recommended for production integrations.
- Widgets (fast-path fallback). k-ID publishes drop-in widgets
for the age gate, the end-to-end flow (age gate + parental consent
- data notices + permissions + preferences), manage-permissions
upgrades, and data notices. They carry built-in
jurisdiction-appropriate age collection, initiate parental-consent
challenges automatically, and emit DOM events
(
Widget.AgeGate.Result, Widget.AgeGate.Challenge) to the parent
window. Choose when the integration must be small, simple, and as
fast as possible to ship — proofs of concept, internal tools,
early-stage games.
The k-id-age-gate and k-id-consent-and-challenges skills cover
both approaches — the router picks the right pattern from the user's
intent. See
Choose integration
for the canonical comparison.
What's in here
Eight skills, designed to work together:
| Skill | Purpose |
|---|
k-id-integration | Router. Picks the right shape and sibling skill(s) based on the user's request. |
k-id-age-gate | Entry point for Shape A — /age-gate/check, jurisdiction detection, correct age-appropriate defaults. |
k-id-consent-and-challenges | Shape A only — GUARDIAN-managed parental consent flow for minors (QR + OTP + email) and challenge polling. |
k-id-age-verification | Age verification and assurance for both shapes — standalone AgeKit+ (Pattern 1), unverified-adult in a session (Pattern 2), and per-permission threshold (Pattern 3, UK OSA 18+, Brazil ECA Digital, Australia social media age). |
k-id-sessions-and-permissions | Shape A only — live permission propagation, /session/upgrade, permission-gated UI controls, verifiedAgeThreshold handling. |
k-id-webhooks | Webhook signature verification and event handling. Relevant to both shapes. |
k-id-server-trust-boundary | Companion skill: API key placement, server proxy, pre-flight checks. Required for both shapes. |
k-id-mobile-native | Companion skill: iOS/Android/Unity platform age signals and deep links. |
Neimo MCP skills (prefix neimo-)
A separate family of skills that orchestrate the Neimo MCP rather than the k-ID API. Use these when the agent needs to research children's-digital-safety regulation across multiple markets (COPPA, GDPR Art. 8, UK OSA, Brazil ECA Digital, AU social-media min-age, etc.) before or after touching k-ID itself.
