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/deploying-go/exercise/SHUTDOWN.md
View on GitHub# Shutdown — timesvc
Answer each question on the `A:` line below it, in your own words, in at
least a couple of sentences. `check.sh` checks that you answered and that the
answers name the mechanisms by their real names; your tutor reads what you
actually wrote.
## Q1. The sequence
Something deletes one of your pods — `kubectl delete pod`, a rolling update,
a node drain. Trace what happens from that moment until the container is
gone. Name every step in order, say which two things happen *in parallel*,
and say where SIGTERM, terminationGracePeriodSeconds, preStop and SIGKILL
each appear.
A: TODO
## Q2. The ordering requirement
Which has to happen first: this pod leaving the Service's endpoints, or your
server stopping accepting new connections? Say why that order and not the
other, what breaks when they happen the wrong way round, and which two things
in *your* files enforce the order.
A: TODO
## Q3. The budget
Write out your arithmetic: the preStop sleep, the server's own shutdown
timeout, and terminationGracePeriodSeconds — the three numbers you chose, and
why they add up the way they do. What happens if the sum exceeds the grace
period?
A: TODO
## Q4. The runtime
What did you set GOMAXPROCS and GOMEMLIMIT to, and why those values? Say what
the Go runtime would have decided on its own inside this container, and what
that costs you.
A: TODO
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 |