dev-learner

Detect repeated conversation workflows and propose reusable skills.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/evolution-foundation/evo-nexus --skill dev-learner-evolution-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-learner
Source: https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-learner
Command: npx skills add https://github.com/evolution-foundation/evo-nexus --skill dev-learner-evolution-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dev-learner reduces repetitive effort by detecting recurring patterns in a conversation and proposing them as new reusable skills instead of leaving them as manual, repeated steps.

Core Features & Use Cases

  • Pattern detection: Identifies repeated workflows, prompts, outputs (artifact formats), and handoffs that occur 3+ times.
  • Skill extraction proposals: Names the candidate skill, documents triggers, steps, involved agents, and expected inputs/outputs.
  • Self-improving workspace loop: Optionally hands off creation to a skill-creator builtin to formalize the pattern as an actual skill.

Quick Start

Ask the AI to run the dev-learner meta-skill on your recent engineering session so it can propose which recurring workflow should become a new skill.

Frequently Asked Questions about dev-learner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify repeated conversation workflows to turn into reusable skills?

To identify repeated conversation workflows, you need pattern detection to analyze your session and flag sequences occurring 3 or more times. The dev-learner meta-skill automates this by extracting triggers, steps, and involved agents to propose reusable skills.

Can I extract reusable skills from engineering retrospectives automatically?

Yes, you can extract reusable skills from engineering retrospectives automatically. The dev-learner skill analyzes these sessions to detect recurring multi-agent handoffs and outputs, then generates a structured learner report proposing formalized skills.

What is the best way to reduce repeated manual prompting in multi-agent workflows?

The best way to reduce repeated manual prompting in multi-agent workflows is detecting recurring sequences and converting them into structured proposals. This approach extracts defined inputs, outputs, and steps, creating a documented handoff plan to formalize the pattern.

Does the dev-learner skill create the proposed skills or just detect the patterns?

The dev-learner skill detects patterns and proposes new skills, but does not formalize them directly. It produces a structured learner report and an optional handoff plan to a skill-creator, which handles the actual creation of the reusable skill.

How do I document multi-agent handoffs that repeat during development sessions?

To document repeating multi-agent handoffs, you apply pattern detection to extract the triggers, involved agents, and defined inputs/outputs. This generates a structured learner report detailing the recurring sequence for future skill creation.

What triggers the skill extraction process in a development session?

The skill extraction process is triggered when a specific workflow, prompt sequence, or multi-agent handoff repeats 3 or more times during a development session. Pattern detection then flags this recurrence for structured extraction and proposal generation.