continuous-self-improvement

Improves wiki infrastructure through a measured six-step fix-and-verify loop.

Updated May 29, 2026
One-click install
npx skills add https://github.com/Thedougler/shattered-sea-wiki --skill continuous-self-improvement-thedougler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: continuous-self-improvement
Source: https://github.com/Thedougler/shattered-sea-wiki/tree/main/.claude/skills/continuous-self-improvement
Command: npx skills add https://github.com/Thedougler/shattered-sea-wiki --skill continuous-self-improvement-thedougler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Autonomous wiki tooling drifts over time: lint warnings accumulate, scripts lack tests, skills bloat, and scheduled runs waste tokens producing nothing. This Skill provides a disciplined, measurement-driven process for improving the wiki's machinery — scripts, hooks, lint rules, skills, and settings — one verified fix at a time. ## Core Features & Use Cases - Six-Step Enforcement Loop: Runs MEASURE → IDENTIFY → FIX → ENFORCE → VERIFY → LOG on every invocation, requiring a sea health snapshot before and after each change. - Priority-Stack Issue Selection: Ranks candidate fixes from user frustration signals in transcripts (P0) down through lint errors, missing tests, workflow waste, and token bloat (P8), enforcing one problem per run. - Code-Level Enforcement: Pushes every fix down an enforcement stack — deny rules, hooks, lint rules, then skill edits — and requires a regression-prevention mechanism such as a test or registered hook. - Use Case: A scheduled daily routine fires, takes a health snapshot showing 143 deadend pages, adds a lint rule via TDD, verifies the count drops to 131, and commits feat: CSI — add wiki_lint rule (deadend_count: 143 → 131). ## Quick Start Ask the agent to run a continuous self-improvement pass on the wiki infrastructure and report the before-and-after health metrics.

Frequently Asked Questions about continuous-self-improvement

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

FAQPage Schema
How do I run a continuous self-improvement pass on my wiki?▼

Invoke the skill with a phrase like "improve the wiki" or via a scheduled routine. It takes a `sea health` baseline snapshot, picks the single highest-impact issue, fixes it with TDD, verifies improvement with a second snapshot, and commits the result.

What kinds of problems does this skill fix?▼

It targets infrastructure only: lint errors and warnings, missing script tests, workflow waste like zero-output autonomous runs, token bloat in skills and CLAUDE.md, and missing measurement metrics. Content creation, ingest, and session prep are explicitly out of scope.

Can this skill fix wiki content or lore problems?▼

No. Content issues such as lore, prose, or missing information are handled by dedicated content skills like daily-update or ttrpg-writing. This skill only improves the machinery — scripts, hooks, lint rules, and skill definitions.

What happens if the fix does not improve any metric?▼

The verification step rejects the change: all edits are reverted with git checkout, no second fix is attempted in the same run, and the failure is logged with the issue, attempt, result, and a suggested next step.

Why does each run only fix one problem?▼

The one-problem rule keeps changes surgical (three files or fewer excluding tests) and makes verification unambiguous. Additional issues discovered during a run are logged for future runs rather than fixed immediately.