continuous-learning-v2

Convert Claude Code session observations into confidence-scored instincts per project.

1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/ROLLED740/vibe-clone-pro --skill continuous-learning-v2-rolled740
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: continuous-learning-v2
Source: https://github.com/ROLLED740/vibe-clone-pro/tree/main/.agent/skills/continuous-learning-v2
Command: npx skills add https://github.com/ROLLED740/vibe-clone-pro --skill continuous-learning-v2-rolled740

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination.

Core Features & Use Cases

  • Atomic instincts with confidence scoring that can be evolved into skills, commands, or agents.
  • Project-scoped instincts isolated per project with a global layer for universal patterns.
  • Hooks-based observation to deterministically capture tool usage and workflows.
  • Evolution pathway from instincts to skills, commands, and agents with promotion and sharing.

Quick Start

Activate the observer hooks to start transforming Claude Code sessions into instincts and evolving them into skills, commands, or agents.

Frequently Asked Questions about continuous-learning-v2

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

FAQPage Schema
How do I automatically capture Claude Code session observations and turn them into reusable skills?

You can automatically capture Claude Code session observations using hooks, which deterministically record workflows and tool usage, then convert them into atomic instincts with confidence scoring that evolve into skills, commands, or agents.

What are atomic instincts with confidence scoring in a learning system?

Atomic instincts with confidence scoring are granular behavioral patterns extracted from session observations, quantified by reliability to determine if they should remain project-scoped or be promoted globally to evolved capabilities like skills and agents.

How do I isolate learning instincts per project to prevent cross-project contamination?

To isolate learning instincts per project and prevent cross-project contamination, apply project-scoped instincts by default, keeping patterns separated per project while allowing universal patterns to be promoted to a global layer.

Does this instinct-based learning system require external dependencies to process session hooks?

No external dependencies are required to process session hooks, as the system relies entirely on internal scripts to capture tool usage and manage the evolution pathway from instincts to skills, commands, and agents.

What is the best way to evolve observed workflows into agents and commands?

The best way to evolve observed workflows into agents and commands is through a deterministic observation pipeline that clusters atomic instincts by confidence scoring, promoting universal patterns from a project scope to a global layer.