self-improving-agent/SKILL.md
Capture corrections, errors, feature requests, and recurring best practices in a local `.learnings/` workspace so future agent runs can avoid repeating mistakes. Use when a command fails, a user corrects the agent, a missing capability is requested, a better repeatable approach is discovered, or before major work to review prior lessons.
npx skillsauth add leprachuan/pot-o-skills self-improving-agentInstall 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.
Use this skill to keep a lightweight local learning loop for Wee Orchestrator work and related repos.
Initialize a learning workspace in the current project root:
./scripts/init_learnings.sh
That creates:
.learnings/
├── LEARNINGS.md
├── ERRORS.md
└── FEATURE_REQUESTS.md
Do not overwrite existing files. Keep entries short, specific, and sanitized.
This skill is adapted for Wee Orchestrator rather than OpenClaw.
.learnings/ in the repo or agent workspace you are actively changing./opt/n8n-copilot-shim-dev/.learnings/ on the dev host./opt/wee-dev, /opt/wee-qa, or /opt/skills/<skill-name>, keep .learnings/ inside that repo.| Situation | Destination |
|---|---|
| Unexpected command or tool failure | .learnings/ERRORS.md |
| User correction or outdated assumption | .learnings/LEARNINGS.md |
| Missing capability request | .learnings/FEATURE_REQUESTS.md |
| Better recurring implementation pattern | .learnings/LEARNINGS.md |
| Repeated bug pattern from multiple tasks | Update existing learning and increase recurrence metadata |
Before a substantial task, scan local learnings:
grep -n "^## \[" .learnings/*.md 2>/dev/null
If you are working in a familiar area, also search by topic:
grep -Rni "auth\|scheduler\|queue\|frontend" .learnings/ 2>/dev/null
When a learning is stable and broadly useful, promote it out of .learnings/:
CLAUDE.mdAGENTS.md.github/copilot-instructions.mdagent_lessonsFor Wee Orchestrator specifically, the most common promotion targets are /opt/AGENTS.md, /opt/CLAUDE.md, and the relevant repo-local AGENTS.md.
Use IDs like LRN-YYYYMMDD-001, ERR-YYYYMMDD-001, and FEAT-YYYYMMDD-001.
Always include:
Prefer updating an existing entry over duplicating it. Link related items with See Also.
Use these statuses consistently:
pendingin_progressresolvedwont_fixpromotedpromoted_to_skillThis skill includes small helper scripts:
scripts/activator.sh — reminder at prompt startscripts/error-detector.sh — reminder after shell/tool failuresFor Claude-style environments with hooks, see references/wee-orchestrator-integration.md.
For Copilot CLI, add a short reminder to AGENTS.md or copilot-instructions.md instead of relying on hooks.
references/examples.md — example entries for each log typereferences/wee-orchestrator-integration.md — setup guidance for local agent reposreferences/upstream.md — upstream source references and adaptation notesassets/ — starter templates for .learnings/ filesdata-ai
Interactive GitHub issues kanban board with agent assignments, due dates, and glassmorphism theming. Fully configurable for any GitHub repository.
data-ai
Interactive TODO board for Wee Canvas. Displays TODOs from both GitHub Issues (leprachuan/fosterbot-home) and flat files in two views: list and kanban. Features filtering, drag-and-drop status changes, quick-add, and auto-refresh every 30 seconds. Use when Foster asks to "show TODOs", "open TODO board", "view my tasks", or "TODO kanban".
tools
Web-based terminal tools for Wee Canvas: remote SSH terminal (WebSSH) and local bash terminal (ttyd). Embeds interactive terminal panels in Wee Canvas iframes. Use when the user asks for a 'web terminal', 'local terminal', 'browser SSH', 'webssh', or wants to interact with a host through the WebUI canvas. For browser windows, see the browser-window skill.
development
Use when you need to send WebEx notifications to flipkey-home-bot - supports markdown formatting, auto-retry with backoff, rate limiting, and message history tracking