oak-api
/oak-api
Build safe Oak Curriculum API learning flows. Use this skill when Oak endpoints, curriculum maps, or child-facing Apps SDK guidance are needed.
- Author
- jscraik ↗
- Repository
- Agent-Skills ↗
- Licence
- Apache-2.0
- Last repository change
- 10.10.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Build safe Oak Curriculum API learning flows. Use this skill when Oak endpoints, curriculum maps, or child-facing Apps SDK guidance are needed.
Original author description
Build safe Oak Curriculum API learning flows. Use this skill when Oak endpoints, curriculum maps, or child-facing Apps SDK guidance are needed.
How it works
- Philosophy
- When To Use
- Avoid
- Inputs
- Outputs
- Workflow
- Constraints
- Validation
- Anti-Patterns
- Examples
SKILL.md preview
--- name: oak-api description: Build safe Oak Curriculum API learning flows. Use this skill when Oak endpoints, curriculum maps, or child-facing Apps SDK guidance are needed. metadata: skill-type: library_api_reference risk: medium --- # Oak API ## Philosophy Learner safety, age fit, and compliance come before product cleverness. ## When To Use - The task depends on Oak API subjects, units, lessons, quizzes, search, or endpoint mapping. - The user wants Oak content turned into a learner-facing flow or implementation plan. - A child-facing app needs age fit, attribution, API-key handling, and rate-limit reminders. ## Avoid - Do not create generic educational content with no Oak data dependency. - Do not dump Oak lesson material verbatim. - Do not imply Oak endorsement or skip licensing and rate-limit reminders. ## Inputs - User request and target repo or artifact. - Evidence source such as files, diffs, issues, releases, or existing workflow state. - Any safety, privacy, compliance, or approval constraints. ## Outputs - Schema-bound outputs include `schema_version`. - Age-appropriate learning flow or endpoint map. - Compliance checklist and attribution. - Implementation guidance when requested. ## Workflow 1. Collect age range, key stage, subject, learning goal, interaction style, and constraints. 2. Confirm no learner PII and restore age/compliance context if the task drifts. 3. Load only the archived Oak reference needed for the current request. 4. Map content into explain -> practice -> check flows. 5. Include required age, flow, compliance, attribution, pagination, and rate-limit markers when relevant. 6. Use authenticated fetch tooling only when explicitly needed and keep keys in environment variables. ## Constraints - Redact secrets, API keys, and learner details by default. - Use Oak endpoint claims only from archived references or live verified docs. - Do not log credentials or imply Oak endorsement. - Fail fast with `Missing inputs: age range, key stage, subject.` when core context is absent. ## Validation - Run Plugin Eval and strict skill audit after editing this skill. - Report exact validation commands and pass/fail outcomes. - Fail fast: stop at the first failed gate, fix it, and rerun before continuing. ## Anti-Patterns - Do not create generic educational content with no Oak data dependency. - Do not dump Oak lesson material verbatim. - Do not imply Oak endorsement or skip licensing and rate-limit reminders. ## Examples - "Turn a KS2 maths unit into an Oak-backed practice flow." - "Build the Oak flow, but age range and subject are missing." ## Progressive Disclosure - Archived full context: `Infrastructure/references/deferred-skill-context/backend-platform-oak-api/`. - Load archived references only when the active workflow needs that exact detail. - Keep the active path compact; do not remove important context for budget trimming. ## See Also | Skill | When to use together | |---|---| | [[verification-before-completion]] | Confirm gate outcomes and report deterministic pass/fail evidence before closeout | | [[project-brain]] | Capture durable repo learnings and route updates into the canonical memory surface |
Files in this package (4)
- SKILL.md 3 KB
- references/contract.yaml 1 KB
- references/evals.yaml 2 KB
- references/task-profile.json 1 KB
Versions
The database has no other skills named oak-api.
Database snapshot: 13.11.2026 · package version 8d4729bf0db4 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100curriculum
Build a learning track from a project plan, spec, design doc, claude.ai artifact or plain topic: phases, topics, prerequisites, and a concrete 'ready when' per topic, mapped to what the learner will build. Use when the user says 'make a curriculum for X', 'what do I need to… - 95oak-backend
Use this skill when building Oak backend applications — Deno native HTTP framework, middleware context, composable middleware. This skill enforces: middleware composition, proper context usage, Deno permissions, type-safe routing. Do NOT use for: Node.js Express projects, Hono… - 100oak
Oak Deno middleware framework inspired by Koa. Covers routing, middleware, context, WebSocket, and static files. Use for Koa-like Deno APIs. USE WHEN: user mentions "Oak", "oak", "Deno middleware", "Koa for Deno", asks about "Deno web framework", "Deno API server",… - 90oak-commit
Use when the user asks to commit or open a pull request, or when /autonomous reaches delivery - produces atomic commits that stage explicit paths only, with messages and a pull-request body written from the actual diff. - 95oak-design
Use this skill to generate well-branded, accessible (WCAG 2.2 AA), themable interfaces and assets for Oak National Academy — production or throwaway prototypes/mocks/decks/worksheets. Contains tokens, a component class library, compiled React components, templates, fonts, icons,… - 100place-based-curriculum-orchestrator
Present pathway options and orchestrate place-based curriculum design from a local place, curriculum requirement, or community issue. Use when place should become a primary text for learning.