Schups skills collection
Personal Claude Code skills collection.
Plugins
The repo hosts two plugins, installable independently:
| Plugin | Skills | Install when you want |
|---|
family-skills | kids-contents, kids-school-exercises | Educational content and exercises for the kids |
technology-skills | dev-guidelines | Structured coding discipline for development sessions |
Installation
Step 1 — Add the marketplace
claude plugin marketplace add https://github.com/schuups/skills
Step 2 — Install a plugin
# Family-oriented skills
claude plugin install --scope project family-skills@schups-skills
# Technology-oriented skills
claude plugin install --scope project technology-skills@schups-skills
Updating
claude plugin marketplace update schups-skills
claude plugin update family-skills@schups-skills
# or
claude plugin update technology-skills@schups-skills
Uninstalling
claude plugin uninstall family-skills@schups-skills
# and/or
claude plugin uninstall technology-skills@schups-skills
Skills
kids-contents
Generates multi-layered audio stories, discussion guides, and reading lists for a specific child (Quentin, age 9, Zurich). Content is calibrated to his interests in space, physics, and mathematics. The quality target is Feynman-grade engagement: captivating enough to listen to for hours on a roadtrip, interesting for both the child and the parent alongside him.
When it triggers:
- A movie, museum visit, or question sparked curiosity
- "Podcast for my son", "story about X for Quentin", "my son asked about..."
Usage examples:
My son just watched Apollo 13 and he's been asking why they called it a 'successful failure'.
Can you prepare a 20-minute audio story for him? Also a discussion guide and reading list.
Quentin has been asking 'what is the universe expanding into?' for three days.
Can you make a podcast episode for him? Don't dumb it down — he loves black holes.
After school Quentin asked what a black hole actually is. Can you create a story and discussion guide?
What you get:
- Pedagogical brief — the educational strategy and development goals embedded in the content. Review and approve before anything is generated.
- Audio story script — ~20 minutes read aloud, character-driven, Feynman-style. Engaging for both child and parent.
- Discussion guide — 8 question types covering recall, understanding, critical thinking, empathy, counterfactual reasoning, and systems thinking.
- Reading / watching list — curated next steps with difficulty ratings (⭐ to ⭐⭐⭐).
kids-school-exercises
Generates printable 30-minute exercise sheets for 4th grade schoolwork (Lehrplan 21, Kanton Zürich). Subjects: Mathematik, Deutsch, Englisch, Natur Mensch Gesellschaft. All content in Hochdeutsch. Sheets are completed on paper; photos of completed sheets are corrected by Claude.
Three modes:
Note: prompts are written in English — the generated exercise sheets are always in Hochdeutsch (except English subject exercises).
Mode A — Generate from topic:
Quentin has a Maths test next week on written multiplication (3-digit × 1-digit).
Can you create an exercise sheet?
Deutsch: practise articles and plural forms — he keeps making mistakes there.
Can you create an English exercise sheet on simple present and yes/no questions?
Mode B — Analyse a graded test (attach photo):
[photo of graded test attached]
Quentin got his Deutsch test back. Can you analyse the mistakes
and create a targeted exercise sheet?
Mode C — Correct a completed sheet (attach photo):
[photo of completed exercise sheet attached]
Can you correct this?
Each exercise is assessed on three dimensions: correctness, method (intermediate steps shown), and presentation (legibility, alignment). A correct answer without working shown is flagged.
dev-guidelines
Adapted from forrestchang/andrej-karpathy-skills (May 2026).
Enforces deliberate, surgical coding behaviour. Before any code is written, an explicit strategy and verifiable success criterion must be stated. Ambiguous requests are met with a targeted clarifying question, not a default interpretation.
When it triggers:
- Any request to write, review, refactor, or fix code
What changes:
Without the skill:
"Clean up the auth module" → Claude starts editing
With the skill:
"Clean up the auth module" → Claude asks: what specifically should change, what should stay the same, and how do we verify it's done?
