agentleFS
leafyoungleafyoung/shared_skills/slides-teach/SKILL.md

slides-teach

Skill2 starsChanged 2 months agoNo licenceView on GitHub

Build a full study course from static source material — slide decks (PDF, PPTX), documents (DOCX, PDF), or spreadsheets (XLSX) — laid out as one workspace: one git repo, one `uv` project, one folder per course unit (`unitN_<slug>/`) holding the original source, extracted page captures with an authoritative pages/README.md index (plus extracted speaker notes when the format has them), resource snapshots, marimo notebooks, and teach-skill lessons authored into an mdBook at the repo root. Use when the user asks to "build a course from these slides", "turn this deck/document into lessons", "make a course from this PDF/textbook chapter", or otherwise wants the slides→index→lessons→resources→notebooks pipeline over static files — no audio/video, hence no download or transcription step. Pairs with `teach` (pedagogy, workspace layout, lessons, resources, verification gates), `teach-marimo` (companion notebooks), and `mdbook-authoring` (book mechanics); the sibling for lecture-video sources is `video-teach`.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.