CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./Skills/backend-platform/oak-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a compact, well-sectioned instruction-only skill with a clear workflow and an explicit validation feedback loop. Its weaknesses are a fully duplicated Avoid/Anti-Patterns section, validation gates named without runnable commands, and progressive-disclosure links that point outside the bundle while ignoring the reference files that actually ship with it.

Suggestions

Delete the 'Anti-Patterns' section (or 'Avoid') — they repeat the same three bullets verbatim.

Name the exact validation commands for 'Plugin Eval' and 'strict skill audit' (or link the script/eval file that defines them, e.g. references/evals.yaml) so the Validation section is executable.

Fix progressive-disclosure links: point to the bundle's actual reference files (contract.yaml, evals.yaml, task-profile.json) or verify the archived deferred-context path exists where this skill is deployed.

DimensionReasoningScore

Conciseness

The body is terse and sectioned with no concept explanations, but the 'Avoid' and 'Anti-Patterns' sections are verbatim duplicates of the same three bullets, a full redundant section that should be tightened away.

3 / 5

Actionability

Some concrete guidance exists ('Map content into explain -> practice -> check flows', the exact fail-fast message 'Missing inputs: age range, key stage, subject.'), but no actual endpoints, commands, or invocation instructions are given — 'Run Plugin Eval and strict skill audit' names gates without saying how to run them.

3 / 5

Workflow Clarity

The six-step workflow is clearly sequenced and a dedicated Validation section provides an explicit fail-fast feedback loop ('stop at the first failed gate, fix it, and rerun before continuing'); the minor gap is that the validation commands themselves are never specified.

4 / 5

Progressive Disclosure

Sections are well-organized and a deferred-context directory is signaled, but the referenced path 'Infrastructure/references/deferred-skill-context/backend-platform-oak-api/' does not exist in this bundle, while the actual bundle files (references/contract.yaml, evals.yaml, task-profile.json) are never referenced from the body — navigation does not match the real bundle structure.

3 / 5

Total

13

/

20

Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is third-person, concise, and explicitly covers both what the skill does and when to use it, with a clearly distinct niche. Its main weakness is thin capability coverage on the what-side and missing natural trigger synonyms (lessons, units, key stages) that users of this domain would say.

Suggestions

Expand the what-clause to list the skill's main actions, e.g. 'Map Oak endpoints, units, and quizzes into age-appropriate learning flows with compliance and attribution checklists.'

Add natural trigger synonyms users would actually say: lessons, units, quizzes, key stage, KS1/KS2/KS3/KS4, curriculum mapping.

State the child-safety angle as a concrete capability (age-fit checks, PII redaction) rather than only the qualifier 'safe'.

DimensionReasoningScore

Specificity

"Build safe Oak Curriculum API learning flows" names the domain and one concrete action, matching the anchor for 1-2 concrete actions without comprehensive coverage; endpoint mapping, quizzes, and compliance outputs named in the body are absent from the description.

3 / 5

Completeness

Both what ("Build safe Oak Curriculum API learning flows") and when ("Use this skill when Oak endpoints, curriculum maps, or child-facing Apps SDK guidance are needed") are explicitly present with concrete trigger areas, but the what-side covers a single action, falling short of the comprehensive multi-action 5 anchor.

4 / 5

Trigger Term Quality

"Oak endpoints, curriculum maps, or child-facing Apps SDK" provides relevant domain keywords, but common natural phrases the body itself uses (lessons, units, key stage, KS2, quizzes) are missing, matching the 'missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

"Oak Curriculum API" carves out a clear niche with distinct, domain-specific triggers; overlap with any other skill is minimal, matching the clear-niche anchor.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Skills/backend-platform/oak-api/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.