docs: refresh skill gallery + prune skill-graph of deleted skills#505
Merged
Conversation
Rebuild docs/index.md (the public Skill Gallery) and prune docs/skill-graph.md so neither references any skill deleted on 2026-06-15. docs/index.md: - Replaced every dead skill in the category tables and "Skills by Category" lists with a live equivalent (token-alert->token-movers, polymarket-> monitor-polymarket, defi-monitor->defi-overview, wallet-digest->treasury-info, feature->issue-triage, github-issues->issue-triage, build-skill->create-skill, search-papers->paper-digest, write-tweet->thread-writer, memory-flush->reflect, trending-coins/monitor-runners/polymarket-comments dropped). - Bumped the stale "50 skills" count to "180+". - Every remaining slug verified against skills/ dirs — no new dangling refs. docs/skill-graph.md (auto-generated; full regen needs the skill-graph skill): - Mechanically pruned the 17 dead nodes + their click links + 2 dead edges (routine -.-> github-issues), and the stale routine example chain (github-issues -> issue-triage, matching aeon.yml). - Recomputed every count: per-category headers and the summary table now sum to 176; updated the 196 references and verdict accordingly. - Banner now states it was mechanically pruned on 2026-06-19 and that re-running the skill-graph skill is still needed to re-add the ~7 newer live skills (176 mapped vs 183 live) and refresh dependency edges. - Mermaid integrity verified: no orphan clicks or edge endpoints. NOTE: dangling refs to 2026-06-15 deletions remain scattered across ~25 other files (skills.json/packs.json/aeon.yml, the CI workflow, apps/dashboard route.ts, smithery manifest/submission, evals.json, docs/skills.md, and several SKILL.md cross-references) — many are false-positive substring mentions in descriptions. That needs a separate, CI-aware pass and is intentionally not in this docs PR. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
aaronjmars
added a commit
that referenced
this pull request
Jun 19, 2026
Final consistency pass after #503/#504/#505. Cleans the *unambiguous* remaining references to skills deleted on 2026-06-15, and deliberately leaves the false-positive / editorial ones (documented below). Cleaned: - docs/smithery-manifest.json + docs/smithery-submission.md: removed the 6 dead tool entries (github-issues, monitor-runners, polymarket-comments, smithery-manifest, thread-formatter, write-tweet). These files are generated by the `smithery-manifest` skill, which was itself deleted — so they're static orphans, safe to hand-edit. JSON re-validated. - docs/skills.md: removed the 3 dead catalog rows (search-papers, build-skill, trending-coins). - skills/skill-evals/evals.json: removed the dead `polymarket` eval block. - Cross-references repointed to live successors: - pm-pulse: dropped `polymarket-comments` from the pairing (monitor-polymarket already covers comments) - contributor-spotlight: `thread-formatter` -> `thread-writer` (x2) - pm-manipulation: dropped the `pm-intel` reference - self-improve: `build-skill` -> `create-skill` - update-gallery: `polymarket`/`kalshi` -> `monitor-polymarket`/`monitor-kalshi` - CLAUDE.md: dropped `memory-flush` (reflect covers memory consolidation now) Deliberately LEFT (verified false-positive or editorial, not mechanical): - packs.json / skills.json: `memory-flush` / `ecosystem-entrants` appear only inside GENERATED skill *descriptions* (memory-dedupe, ecosystem-links), not as entries — confirmed they are not slugs. Fixing means editing those SKILL.md `description:` frontmatter and regenerating skills.json/packs.json (CI-coupled); out of scope for a dangling-ref sweep. - `competitor-radar` in 6 skills (skill-triage, fork-health, capabilities-map, ecosystem-pulse, sparkleware-catalog, atrium-watch): interwoven "Monday intelligence stack" scheduling-rationale prose referencing its old cron slot. Editorial (needs the current Monday schedule), harmless, not a dependency. - `v4-readiness` in capabilities-map / skill-adoption: a historical postmortem reference ("v4-readiness H1") and a one-shot-tool example — accurate as history. - apps/dashboard/.../route.ts: `note-taking` names the skill in a SUPERNOTES_API_KEY secret description; runtime code, left untouched. - .github/workflows/aeon.yml: `memory-flush` in a meta-skill analysis-skip list — a harmless no-op case branch; left to avoid touching CI for zero behavior change. - memory/topics/skill-spotlight.md: agent-maintained memory, not source. Did NOT touch skills.json / packs.json / aeon.yml / .github — the CI-gated config. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #503/#504. Rebuilds the two catalog docs so neither references any skill deleted on 2026-06-15.
docs/index.md(public Skill Gallery)Every dead skill in the category tables + "Skills by Category" lists replaced with a live equivalent (verified against
skills/dirs — no new dangling refs):token-alerttoken-moverspolymarketmonitor-polymarketdefi-monitordefi-overviewwallet-digesttreasury-infofeature/github-issuesissue-triagebuild-skillcreate-skillsearch-paperspaper-digestwrite-tweetthread-writermemory-flushreflecttrending-coins,monitor-runners,polymarket-commentsStale "50 skills" count → "180+".
docs/skill-graph.md(auto-generated)A full regen is the
skill-graphskill's job (I can't run the LLM skill here, and it'd also need to add newer skills). So this is a deterministic prune + recount:routine -.-> github-issues), and fixed the staleroutineexample chain (github-issues→issue-triage, matchingaeon.yml).196/verdict references.skill-graphskill is still needed to re-add the ~7 newer live skills (176 mapped vs 183 live) and refresh dependency edges.An authoritative repo-wide scan found dangling refs to 2026-06-15 deletions still scattered across ~25 other files, including:
skills.json,packs.json,aeon.yml— but the matches I spot-checked (memory-flush,ecosystem-entrants) are false-positive substring mentions in descriptions, not real entries (confirmed: not slugs inskills.json)..github/workflows/aeon.yml, runtimeapps/dashboard/.../route.ts(note-taking— likely a secret category, not a skill),memory/topics/,docs/smithery-{manifest.json,submission.md,yaml},skills/skill-evals/evals.json,docs/skills.md, and severalSKILL.mdcross-references.This needs a separate, CI-aware pass with per-file entry-vs-mention triage (touching
skills.json/packs.json/aeon.ymlblindly could tripci-skills-json/ci-packs-json/ci-capabilities-parity). Intentionally not folded into this docs PR. Happy to take it on next.