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.

referencesRESOURCES-FORMAT.md

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

RESOURCES.md Format

RESOURCES.md is the curated set of trusted sources for this topic. Knowledge for explainers should be drawn from here, not from parametric guesses. Wisdom comes from the communities listed here.

Structure

# {Topic} Resources

## Knowledge

- [Official API Documentation: `{Library/Framework}`](https://example.com/docs)
  Primary reference by the maintainers covering core architecture, API signatures, and lifecycle semantics. Use for: authoritative explanations of types, functions, and runtime behavior.
- [Official User Guide: `{Testing/Verification Tool}`](https://example.com/testing)
  Official documentation for automated testing and verification. Use for: designing high-signal test assertions and verification labs in every lesson.

## Wisdom (Communities)

- [`{org/repo}` GitHub Discussions](https://github.com/example/repo/discussions)
  Official Q&A and architecture forum monitored by maintainers and experienced practitioners. Use for: design review, performance tuning, and idiomatic patterns.
- [{Language/Framework} Users Forum](https://example.com/forum)
  High-signal, well-moderated forum for learners and experts alike. Use for: architectural questions and real-world debugging discussions.

Rules

  • High-trust only. Prefer primary sources, official documentation, recognised experts, peer-reviewed work, verified workspace skills (.agents/skills/*), and communities with strong moderation. If a resource is marketing dressed as education, leave it out.
  • Annotate every entry. A bare link is useless in three months. Add one line: what it covers and when to reach for it.
  • Group by Knowledge / Wisdom. Mirrors the philosophy in SKILL.md. It is fine for a resource to appear in only one group.
  • Surface gaps explicitly. If no good resource exists for an area the mission needs, write a ## Gaps section listing what is missing. This drives future search.
  • Prune ruthlessly. A resource that turned out to be wrong, shallow, or off-mission should be removed, not buried. Better five sharp sources than thirty mediocre ones.
  • Record community preferences. If the user has opted out of joining communities, note it here so future sessions don't keep proposing them.

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