tobihagemann/turbo / claude/skills/route-lessons
route-lessons
VerifiedRoute lessons to instructions, auto memory, skills, the backlog, or a Turbo handoff after approval. Use when asked to "route lessons" or "where should this lesson go".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 18.7 KB |
| references/package-managed-skills.md | markdown | 1.3 KB |
| references/turbo-skill-lessons.md | markdown | 1.1 KB |
references/package-managed-skills.md
View on GitHub# Package-Managed Skills
## Classify the Skill
Read `~/.agents/.skill-lock.json`. Its top-level `skills` object is keyed by skill name, and a skill listed there was installed from a source that replaces it wholesale on its next update. Match on the resolved path rather than the name alone, against the entry's `skillPath`, so a local fork that replaced the installed copy is not mistaken for it.
- **Package-managed** — the skill matches an entry.
- **Ownership-unresolved** — the skill matches no entry, or the file does not exist. Absence settles nothing: such a skill may still be one a package manager replaces.
## Route Its Lessons
**Package-managed:** route the lesson straight to **Auto memory**, recording the skill it applies to, with no question put to the user.
**Ownership-unresolved:** before routing a lesson to the skill, say plainly that an edit to it survives only while the user maintains the skill themselves. Then use `AskUserQuestion` to ask which is the case, with the options phrased as that effect: edits to this skill stick, or the next update overwrites them.
- **Edits stick** — route the lesson by the remaining routing rules.
- **The next update overwrites them** — route the lesson to **Auto memory**, recording the skill it applies to.
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: 472k | 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: 323k | 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: 323k | 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: 323k | Updated | Claude CodeCodex | Verified | Install |