src/orchestrator/skills/self-improvement/SKILL.md
Appends new entries to LESSONS-LEARNED.md via opencastle lesson CLI; searches past lessons for matching errors; proposes skill updates when retry patterns exceed thresholds. Use when consulting or updating LESSONS-LEARNED.md, after task failures, when capturing retrospective insights, or when a retry succeeds.
npx skillsauth add monkilabs/opencastle self-improvementInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Retry with different approach and it works → document lesson immediately. File: .opencastle/LESSONS-LEARNED.md
⛔ HARD GATE — Use the CLI. Do NOT edit LESSONS-LEARNED.md directly.
opencastle lesson --title "Short descriptive title" --category general --severity high \
--problem "What was observed" --wrong "Failing approach" --correct "Working solution" \
--why "Root cause"
Required: --title, --category, --severity, --problem · Optional: --wrong, --correct, --why
After writing: if lesson reveals gap in skill/instruction file, update that file too (prevents pitfall at source).
opencastle lesson to record working approach.tail -1 .opencastle/LESSONS-LEARNED.md — confirm entry has title, category, severity. If malformed → re-run with corrected flags.Quick search example:
rg "missing CRON_SECRET" .opencastle/LESSONS-LEARNED.md || true
Category, severity tables moved to LESSON-CATEGORIES.md. Use that file when tagging lessons.
Never skip reading lessons · Never fix without documenting · Never write vague entries · Never duplicate · Never defer to end of session
For expertise tracking, cross-session knowledge graphs, load agent-memory skill.
development
Defines 10 sequential validation gates: secret scanning, lint/test/build checks, blast radius analysis, dependency auditing, browser testing, cache management, regression checks, smoke tests. Use when running pre-deploy validation or CI checks, CI/CD pipelines, deployment pipeline validation, pre-merge checks, continuous integration, or pull request validation.
development
Generates test plans, writes unit/integration/E2E test files, identifies coverage gaps, flags common testing anti-patterns. Use when writing tests, creating test suites, planning test strategies, mocking dependencies, measuring code coverage, or test planning.
development
Provides model routing rules, validates delegation prerequisites, supplies cost tracking templates, defines dead-letter queue formats for Team Lead orchestration. Load when assigning tasks to agents, choosing model tiers, starting delegation session, running multi-agent workflow, delegating work, choosing which model to use, or assigning tasks.
testing
Saves, restores session state including task progress, file changes, delegation history. Use when saving progress, resuming interrupted work, picking up where you left off, or checkpointing current work.