← ClaudeAtlas

skill-harvestlisted

Load when the user wants to find, create, improve or publish agent skills from the work already done across ALL their Claude Code sessions, or wants a chat that "watches every chat" for skills. It reads every past session on the machine in minutes, finds the methods that repeat or keep failing, checks the public market (skills.sh / GitHub) before building anything, flags skills that were installed but never loaded in the sessions that needed them and hands them to those sessions, and only publishes a skill that passed a strict gate (evidence, market gap, with/without test, no private data). Triggers on "harvest skills", "mine my chats for skills", "what skills am I missing", "which skills do my chats forget", "create skills from my conversations", "publish this skill to GitHub", "creador de skills", "saca skills de mis chats", "qué skill me falta", "qué skills se les olvidan a los chats", "sube la skill a GitHub". Not for writing one skill from scratch with no history (use skill-creator) and not for live in-s
RabbitDesigns22/claude-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill RabbitDesigns22/claude-skills
# Skill Harvest Your sessions already contain your best skills. The repeated asks, the third attempt that finally worked, the correction the user had to make twice: that is a method nobody has written down. This skill finds it across every session, checks whether the world already has it, and builds only what is missing and proven. It also finds the cheaper win most setups miss: **the skill was already installed and the session never loaded it.** In real fleets this is the most common gap, more common than a missing skill. ## The loop (run in this order) ``` - [ ] 1. Inventory: installed skills + skills already published by the user - [ ] 2. Digest every session (script) — never read raw .jsonl by hand - [ ] 3. Read the digests in parallel batches (subagents, fixed brief) - [ ] 4. Merge: one candidate list, evidence counted across sessions - [ ] 5. Market check every candidate (skills.sh + read the top SKILL.md) - [ ] 6. Gate: build only what passes all 6 checks - [ ] 7. Build + with/without test - [ ] 8. Hand forgotten skills to the sessions that need them - [ ] 9. Publish only on the user's ok, sanitized - [ ] 10. Log to the catalog; offer to schedule the next (incremental) run ``` ### 1. Inventory - Installed: `ls ~/.claude/skills` plus plugin skills listed in the session. - Published: the user's public skill repos (`https://api.github.com/users/<user>/repos`). - Keep both lists in the catalog (step 10). A candidate that matches either one becomes an UPDATE or a HAND-