agentsclimarketplace
Sign in

Skill learn

Skill rxdaozhang/skill-learn/skills/skill-learn

Consolidate actionable lessons after another skill is used and required multiple correction rounds. Use this skill at task closure to extract concrete failures from the current conversation, propose safe incremental updates to the original skill files, show a diff first, and only apply changes after explicit user confirmation. Works for Claude and Codex skill workflows.From its SKILL.md

Install
npx -y skills add rxdaozhang/skill-learn --skill skill-learn

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.3 KB, 619 tokens by cl100k_base, as published. Nobody here has run it

Skill Learn

Overview

Use this skill at the end of a task to improve the original skill that was just used. Extract concrete, evidence-based lessons from the current conversation and convert them into executable guidance for the target skill.

Workflow

  1. Resolve the target skill.
  2. Collect evidence from the current conversation only.
  3. Extract lessons in a strict schema.
  4. Propose incremental file updates.
  5. Show diff/patch before write.
  6. Apply changes only after explicit confirmation.

Resolve Target Skill

Follow this resolution order:

  1. Use explicit target path from user input if provided.
  2. Otherwise infer from the most recently used skill in the current context.
  3. If still ambiguous, ask one clarifying question and stop before proposing any write.

Never guess a target when two or more plausible skills exist.

Extract Lessons from Chat History

Use only the current conversation as evidence.

For each lesson, output this schema:

  • Rule: What to do next time.
  • Anti-pattern: What failed or caused rework.
  • Correction: Concrete action to prevent recurrence.
  • Trigger: When this rule should be applied.
  • Example (optional): A short concrete example.

Quality gate:

  • Reject vague lessons such as "be better" or "be careful."
  • Require concrete evidence from an observed iteration or correction.
  • Prefer procedural wording that another agent can execute directly.

If evidence is insufficient, report that and do not propose a file write.

For reusable patterns and examples, consult:

  • references/lesson-patterns.md

Update Rules (Incremental Only)

When proposing updates to the target skill:

  1. Never rewrite the entire file.
  2. Prefer updating an existing anchored section such as ## Lessons Learned.
  3. If no suitable anchor exists, append a bounded new section at the end.
  4. Keep unrelated sections unchanged.
  5. Keep SKILL.md concise; move long canonical detail to references/skill-learn-lessons.md in the target skill and add a pointer from SKILL.md.

Do not delete or reorder unrelated guidance unless explicitly requested.

Diff-First Confirmation

Before any write:

  1. Present a readable diff/patch for each target file.
  2. Summarize the expected behavioral improvement.
  3. Ask for explicit confirmation.

Write only after confirmation. If confirmation is not provided, stop after delivering the proposal.

Failure Handling

Handle these cases explicitly:

  1. Target skill not found: ask for path or exact skill name.
  2. Multiple candidate targets: request disambiguation.
  3. No clear lessons with evidence: return "no high-confidence lesson updates."
  4. Requested change violates incremental policy: explain and offer an incremental alternative.

Output Format

Use this response structure:

  1. Target Skill
  2. Evidence Extracted
  3. Proposed Lessons (Rule / Anti-pattern / Correction / Trigger / Example)
  4. Proposed File Changes
  5. Diff Preview
  6. Confirmation Request

What ships with it: 1 file

1.9 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most learn study skills give in 619 tokens

Counted across 546 of the 573 authors here whose files we hold, read 2026-08-07

  • Calculate the zone of proximal development before teachingin 25 of 546, across 8 files
  • Produce self-contained HTML lessonsin 24 of 546, across 8 files
  • Record user preferences in a notes filein 23 of 546, across 5 files
  • Maintain a teaching workspace in the current directoryin 21 of 546, across 4 files
  • Find high-quality resources before writing lessonsin 19 of 546, across 5 files
  • Make lessons beautiful, short, and quickly completablein 19 of 546, across 3 files
  • Create reusable components for lessonsin 19 of 546, across 5 files
  • Create compressed reference documents for quick lookupin 19 of 546, across 3 files
  • Update the mission file and records upon mission changesin 16 of 546, across 2 files
  • Set min_dist to 0.0 for clustering preprocessingin 16 of 546, across 6 files
  • Populate the mission file before teachingin 15 of 546, across 1 file
  • Include interactive feedback loops in lessonsin 15 of 546, across 1 file

Said here and by no other author read

  • resolve the target skill
  • collect evidence from the current conversation
  • extract lessons in the specified schema
  • propose incremental file updates
  • apply changes only after explicit confirmation
  • reject vague lessons

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,512. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.