Index of every page on this site: llms.txt
All skills
Run it yourself

Interactive, stateful code-teaching workflow that builds self-contained HTML lessons (compiled from Markdown via build.py), printable reference sheets, learning records, and runnable per-lesson companion projects in ./apps/ verified with automated tests and linters. Use when the user asks to learn a programming language, framework, or engineering tool, build or extend an interactive coding course, create lessons or reference sheets, or invokes /teach-code or /teach.

Use this Skill: https://skilld.dev/gh/domesticmouse/skills/teach-code

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesMISSION-FORMAT.md

≈433 tokens on demand. Your agent reads this file only when SKILL.md points to it.

MISSION.md Format

MISSION.md lives at the root of the teaching workspace (. for dedicated course repos, or ./tutorial/ inside an existing project repo). It captures the reason the user is learning this topic. Every teaching decision (what to teach next, which resources to surface, which exercises to design) should trace back to this document.

Template

# Mission: {Topic}

## Why
{1-3 sentences. The concrete real-world goal the user is chasing. What changes in their life or work when they have this skill? Avoid abstract framings like "to understand X"; push for the underlying outcome.}

## Success looks like
- {A specific, observable thing the user will be able to do or ship}
- {Another specific thing}
- {…}

## Constraints
- {Time, budget, target platform, prior commitments, learning preferences, anything that bounds the approach}

## Out of scope
- {Adjacent topics the user explicitly does not want to chase right now, protecting the zone of proximal development}

Rules

  • One mission per workspace. If the user wants to learn two unrelated things, that is two workspaces.
  • Concrete over abstract. "Build and verify a desktop schematic reviewer in Rust" beats "learn GUI programming." "Ship a tested CLI tool to my team" beats "learn Python."
  • Push back on vagueness. If the user cannot articulate why, interview them (one question at a time) before writing anything. A bad mission is worse than no mission.
  • Revise when reality shifts. Missions change. When the user's goal moves, update this file: don't leave a stale mission steering future sessions.
  • Keep it short. If MISSION.md runs past a screen, it has stopped being a compass and started being a plan.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning3d3 checks · Risk SAFE
  • Gen Agent Trust Hub3d

    The teach-code skill provides a structured framework for generating interactive coding tutorials. It includes a utility script for synchronizing source code into lesson files, which incorporates safety checks to prevent path traversal. The workflow relies on standard development tools and well-known libraries for document processing.

  • Socket3d

    No alerts

  • Snyk3d

    Risk: MEDIUM · 1 issue

Signed by skilld at 606a5d5. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 4 days ago

README badge

README badge for domesticmouse/skills/teach-code