Create strict JSON flashcard decks for active-recall study.
64
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Create one /workspace/<slug>.json file. JSON is the canonical deck; do not
write a separate Markdown summary.
Use exactly this closed version-one shape:
{
"schema_version": 1,
"title": "Deck title",
"cards": [
{
"front_text": "One focused recall prompt",
"back_text": "A sufficient, concise answer",
"hint_text": "Optional hint with inline math: \\(x^2\\)"
}
]
}\(...\) for inline math or \[...\] for display math. Escape each
backslash as \\ in JSON. Keep delimiters and braces balanced; do not nest
math delimiters.hint_text when no useful hint exists; never use null.schema_version, duplicate fronts, or use raw
HTML or Markdown in card content.Call:
verify_artifact(path="/workspace/<slug>.json", format="flashcards")Fix all blocking findings together, rewrite the JSON once, and reverify the exact path. If a blocker remains, stop and explain it instead of looping.
After verification returns status="verified", call:
save_artifact(path="/workspace/<slug>.json", title="...")Do not pass markdown_representation; the backend derives trusted Markdown
from the exact receipt-bound JSON.
For revisions, edit the restored JSON from primary_path, write the complete
deck to expected_output_path, verify that path as flashcards, and save with
the returned artifact_id and expected_generation. Do not edit the derived
markdown_path or reconstruct the deck with vision.
MODSetter/SurfSense
176aed2
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.