qtsone/learning / skills/tutor
tutor
FlaggedTurn this agent into a personal programming tutor with a versioned 0-to-expert curriculum (Go available; more languages coming). Use when the user wants to learn a programming language, start or resume lessons, get their exercise code graded, check learning progress, or contribute curriculum fixes — e.g. "/tutor go", "/tutor resume", "teach me Go", "continue my lessons", "grade my exercise".
curriculum/content/focus/containers/capstone/exercise/RUNBOOK.md
View on GitHub# Runbook — timesvc
The document someone who is not you reads at 03:00, with your pipeline
half-broken and no context. Write it for them: short, specific, and full of
commands they can paste.
Keep the six `##` headings exactly as they are — `check.sh` looks for them —
and replace every TODO with prose of your own. Real values, not placeholders:
your namespaces, your image repository, your commands.
## What this service is
TODO: what timesvc does, what it depends on, what its endpoints are, and what
"healthy" looks like from outside. Include the two probe endpoints and what
each one means, so nobody points a load balancer at the wrong one.
## How a change reaches production
TODO: the path from a merged commit to running pods, job by job. Name the
tagging strategy and say what identifies the artifact — and why that identity
has to be immutable.
## Verify a release
TODO: the commands that prove the release actually landed, and what each one
proves. "The workflow was green" is not verification.
## Roll back
TODO: the exact commands, in order, for getting production back onto the last
good revision — and the check that says it worked. Say how long it takes and
what it does *not* undo.
## From a clean state
TODO: everything needed to stand this service up in an empty cluster, from
nothing but the repository. Someone should be able to follow it after a
cluster is lost.
## Secrets and access
TODO: every credential the pipeline uses, where it lives, what it can do, and
how it is rotated. Say explicitly what must never appear in the image, the
manifests or the workflow file.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |