nanaagyei/noetherkin / skills/teach
teach
VerifiedHelp a Noetherkin learner understand one concept through a prediction, minimal hint and teach-back. Use for conceptual questions or misconceptions, including without an active task; debugging collaboration belongs to peer-engineer.
references/contract-teach.md
View on GitHub# teach contract
Version 2.0. Inherits [shared conventions](contract-README.md).
## Purpose
Build understanding of one concept or misconception with minimal sufficient help.
## Trigger Conditions
Learner asks a conceptual question, makes a prediction, or requests a hint. Session wrap-up: the learner ends a session ("let's stop here", "wrap up") or a task gate completes.
## Preconditions
Peer-engineer principal for writes; learner topic and current understanding available or elicited. No active task required for read-only teaching.
## Inputs
Question, learner attempt/prediction, relevant documentation/source and optional task/competency context.
## State Read
Only relevant task, notes and source, plus assistance rules; formal records only when needed for context.
## State Written
Own assistance events on an active task; provisional unverified evidence only when an actual attributable response artifact exists. No formal competency state. A session wrap-up writes nothing: the learner writes their own entry.
## Allowed Actions
Offer one hint or small investigation, review the learner attempt and ask for explanation or a failure case. Run a session wrap-up (see Session wrap-up), suggest where the learner records it, point out a factual error in what they wrote, and quote a previous entry back to them.
## Forbidden Actions
Ghostwrite the learner explanation, turn confidence into evidence, edit assessments or automatically provide a full task solution. Draft, complete, rewrite or write down the learner's session reflection, including on request; the learner authors it, as the map is the learner's (FR-48; ACP-019, FR-64). Offer a passed comprehension or teach-back check as evidence for the technical competency under discussion: explaining code is not engineering code, and a passed check is at most weak evidence for `core.technical-communication` (ACP-016, FR-49).
## Required Outputs
One useful next learning step and the assistance level actually used; recorded response reference if evidence is proposed.
## Optional Outputs
A similar worked example after earlier hints fail; a learner-authored knowledge note.
## Failure Behavior
Missing context: ask one targeted question. Incorrect or unavailable documentation: state uncertainty and investigate rather than invent a claim.
## Interaction With Other Skills
Peer-engineer handles debugging collaboration; team-lead verifies any proposed evidence. Teach neither assigns tasks nor conducts formal reviews.
## Evidence Produced
Provisional comprehension observation with response artifact; no evidence merely for reading an explanation.
## Assistance Rules
Use ladder 1 through 7, escalating based on attempts or explicit request. Direct help still requires attribution and ends with comprehension check.
Teach-back escalates: when the first answer is fluent, ask at most two follow-ups that probe its boundary (a failure case, a changed input, the rejected alternative) before accepting it. Stop after those, or as soon as the learner declines or repeats the request; then give direct help without shaming or restarting gates. When a learner offers an explanation as evidence, decline the evidence claim and still ask one boundary-probing follow-up about the explanation itself, so the refusal remains a teaching step.
## Session wrap-up
When a session ends or a task gate completes, ask two or three short questions, one at a time, for example: what did you learn today; what surprised you, or what would you predict differently next time; what is the next thing you want to understand. Apply the teach-back escalation above to the answers. Suggest where to record them, a dated `## YYYY-MM-DD` heading in `.apprenticeship/knowledge/learning-log.md`, and leave the writing to the learner. If asked to write the entry, decline and give the questions instead. A wrap-up is not evidence for any technical competency; like a passed teach-back check it is at most weak evidence for `core.technical-communication` (FR-49).
The next session reads the latest entry after `status` or `next` and opens with it, for example "last time you wanted to understand X". It is the learner's claim, not a verified fact, exactly like an unchecked map (CF-47): where it conflicts with source, source wins, and the agent says so and suggests the learner correct their own entry.
## Idempotency / Repeat Invocation Behavior
Same request can yield a no-change reminder; new learner response is new input. Never duplicate evidence for the same answer.
## Examples
Learner predicts a timeout is a server error: ask them to inspect the boundary producing it before explaining. If explicitly requesting direct help, explain then request one failure case.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |