Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Lev Self

ASecurity

[WHAT] Self-improvement system transforming event streams into actionable system improvements [HOW] Analyze events.jsonl for patterns, generate proposals with confidence scores, human-approve, apply to skills/config/daemons [WHEN] Use when asking what lev can learn, proposing improvements, or conducting fail-forward root cause analysis [WHY] Enables proactive system evolution based on observed failures and patterns instead of reactive fixes Triggers: "what can lev learn", "propose improvemen...

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
code-qualitybashreact

Works with

cli

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill lev-self --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Lev Self?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Lev Self
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-lev-self/badge)](https://www.skillsdirectory.com/skills/lev-os-lev-self)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: lev-self
description: |
  [WHAT] Self-improvement system transforming event streams into actionable system improvements
  [HOW] Analyze events.jsonl for patterns, generate proposals with confidence scores, human-approve, apply to skills/config/daemons
  [WHEN] Use when asking what lev can learn, proposing improvements, or conducting fail-forward root cause analysis
  [WHY] Enables proactive system evolution based on observed failures and patterns instead of reactive fixes

  Triggers: "what can lev learn", "propose improvements", "self-learn", "why did X fail", "improve lev", "fail-forward"
version: 1.0.0
storage:
  events: ~/lev/.lev/events.jsonl
  proposals: ~/.config/lev/proposals/
  patterns: ~/.config/lev/patterns.jsonl

lifecycle_integration:
  stage: all stages (meta-improvement)
  input_artifact: events.jsonl + patterns
  output_artifact: improvement-proposals.md
---

# Lev Self-Improvement

Transform event streams into actionable system improvements. Proactive learning (not just reactive fixes).

## Quick Reference

| Trigger | Action |
|---------|--------|
| "what can lev learn?" | Full analysis cycle |
| "propose improvements" | Generate proposals from patterns |
| "why did X fail?" | Root cause analysis (fail-forward) |
| "self-learn" | Automated improvement cycle |

## Architecture

```
events.jsonl → Analyze → Patterns → Proposals → Human Review → Apply
                 ↑                                              │
                 └──────────── feedback loop ──────────────────┘
```

## Core Workflows

### 1. Event Analysis
```bash
lev learn analyze              # Detect patterns in events.jsonl
lev learn analyze --since 24h  # Last 24 hours only
```

See: `references/event-analysis.md`

### 2. Fail-Forward Protocol
When something fails, extract learning:
1. Capture: What happened? (exact error, context)
2. Root Cause: Why? (5 whys, dependencies)
3. Proposal: How to prevent? (skill patch, config change)
4. Confidence: How sure? (low/medium/high)

See: `references/fail-forward.md`

### 3. Proposal Workflow
```yaml
# ~/.config/lev/proposals/{id}.yaml
id: prop-abc123
type: skill-patch | config-change | new-workflow
target: ~/.claude/skills/lev/SKILL.md
confidence: 0.85
description: "Add timeout handling"
diff: |
  + timeout: 30s
status: pending | approved | rejected | applied
```

See: `references/proposals.md`

## Evolution Targets

| Target | Location | When |
|--------|----------|------|
| Skills | ~/.claude/skills/*/SKILL.md | Behavior improvements |
| Config | ~/lev/.lev/config.yaml | Settings optimization |
| Daemons | ~/.config/lev/daemons.yaml | Process tuning |
| Workflows | ~/lev/workflows/*.yaml | Pattern codification |

## Relationship to Other Skills

- **skill-evolver** (absorbed): Reactive skill fixes
- **lev** (sibling): Behavior definition (lev-self improves it)
- **bd** (integration): Track proposals as issues

## Storage Schema

```
~/.config/lev/
├── proposals/           # Pending proposals
│   └── {id}.yaml
├── memory/
│   ├── patterns.jsonl   # Detected patterns
│   ├── proposals.jsonl  # Proposal history
│   └── applied.jsonl    # Applied changes + outcomes
└── patterns.jsonl       # Active patterns for matching
```

## Confidence Thresholds

| Confidence | Action |
|------------|--------|
| ≥90% | Auto-apply (after notification) |
| 70-89% | Propose with recommendation |
| 50-69% | Propose, request review |
| <50% | Log only, don't propose |

See: `references/tracking-schema.md`

## CLI Quick Reference

```bash
# Analysis
lev learn analyze             # Full event analysis
lev learn patterns            # Show detected patterns

# Proposals
lev learn propose             # Generate proposals from patterns
lev learn review              # Interactive proposal review
lev learn apply <id>          # Apply approved proposal

# Tracking
lev learn status              # Show pending proposals
lev learn history             # Show applied changes
```

## Human-in-the-Loop

**All changes require confirmation:**
1. Proposal generated → notification
2. Human reviews diff
3. Approve/reject/modify
4. Applied changes logged with outcome

**Rollback:**
```bash
lev learn rollback <id>       # Revert applied proposal
```

---

*For detailed schemas and protocols, see references/*

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman Review

Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.

1023331 votes

Caveman Commit

Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.

1023331 votes

Verification Loop

一个全面的 Claude Code 会话验证系统。

2456590 votes

Springboot Verification

Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.

2456590 votes

Django Verification

Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.

2456590 votes
View all in code-quality →