Use when the user says /learn or asks to save this lesson.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add tigerless-labs/autoharness --skill learn --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Learn?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/tigerless-labs-learn)More formats (shields.io, HTML) on the badges page.
---
name: learn
description: Use when the user says /learn or asks to save this lesson.
category: general
---
# Learn: distill this session into the skill library
Review the conversation so far and distill what is worth keeping — through the
standard proposal chain, never by writing files.
1. Identify class-level, reusable lessons: corrected approaches, non-trivial
techniques, durable user preferences. Skip one-off narratives and
environment-specific failures.
2. Compare first: read the injected skill index; if an existing skill covers
the topic, prefer a `patch`/`update` over creating a near-duplicate.
3. Reconcile old with new: when a lesson supersedes an earlier rule, search
the managed skill trees for contradicting statements and stage updates so
the new version wins everywhere.
4. Stage every change exclusively via the `stage_skill` tool, one intent per
lesson, with `reason` and a verbatim `evidence` quote from this session.
The deterministic promoter validates and lands; rejects are reported at
the next session start.
If nothing meets the bar, say so and stage nothing.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...