Agent Skills › evolution-foundation/evo-nexus › dev-learner

dev-learner

GitHub

元技能，用于从对话中识别重复3次以上的模式，并提议将其提取为可复用的新技能，实现工作区自我改进。

.claude/skills/dev-learner/SKILL.md evolution-foundation/evo-nexus

Trigger Scenarios

长会话中出现未形式化的重复工作流程希望将手动调用的固定模式标准化项目回顾时寻找应被提取为技能的遗漏点

Install

npx skills add evolution-foundation/evo-nexus --skill dev-learner -g -y

More Options

Non-standard path

npx skills add https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-learner -g -y

Use without installing

npx skills use evolution-foundation/evo-nexus@dev-learner

指定 Agent (Claude Code)

npx skills add evolution-foundation/evo-nexus --skill dev-learner -a claude-code -g -y

安装 repo 全部 skill

npx skills add evolution-foundation/evo-nexus --all -g -y

预览 repo 内 skill

npx skills add evolution-foundation/evo-nexus --list

SKILL.md

Frontmatter

{
    "name": "dev-learner",
    "description": "Meta-skill — extract reusable skills from the current conversation. Identifies patterns that appeared 3+ times and proposes them as new skills. Pairs with skill-creator builtin."
}

Dev Learner

Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.

Meta-skill: scan the current conversation for patterns that appeared 3+ times and propose extracting them as reusable skills. The "self-improving workspace" feedback loop.

Use When

A long session involved repeated workflows that aren't yet skills
You want to formalize a pattern you keep manually invoking
Post-EPIC retrospective: what should have been a skill but wasn't?

Do Not Use When

Single-pattern conversation → no extraction value
The pattern is too specific to one project → keep as agent memory
The pattern is already a skill → just document it better

Workflow

Phase 1 — Pattern Detection

Scan the conversation for:

Repeated workflows — same sequence of agents called 3+ times
Repeated prompts — similar instructions issued repeatedly
Repeated outputs — same artifact format produced multiple times
Repeated handoffs — same agent pair invoked together repeatedly

Phase 2 — Extraction

For each detected pattern:

Name it (e.g., "PR review pipeline", "Debug investigation flow")
Describe the trigger
Document the steps
Identify the agents involved
Identify the inputs and outputs

Phase 3 — Proposal

Propose the new skill:

Name: suggested skill name (dev-{action} if engineering, {prefix}-{action} otherwise)
Trigger: when to invoke
Workflow: the steps
Pairs with: which agents/skills

Phase 4 — Creation (optional)

If user accepts, hand off to skill-creator (builtin) to actually generate the skill file.

Output

## Learner Report — {session topic}

### Patterns Detected
1. **{Pattern name}**
   - Occurrences: 4 times
   - Steps: ...
   - Suggested skill: `dev-{action}`

2. **{Pattern name}**
   - ...

### Skill Proposals
[Detailed proposal for each detected pattern]

### Recommendation
[Which to extract first, which to skip]