Skip to content

chore: remove dangling references to the deleted token-report skill#503

Merged
aaronjmars merged 1 commit into
mainfrom
chore/cleanup-token-report-refs
Jun 19, 2026
Merged

chore: remove dangling references to the deleted token-report skill#503
aaronjmars merged 1 commit into
mainfrom
chore/cleanup-token-report-refs

Conversation

@aaronjmars

Copy link
Copy Markdown
Owner

token-report was removed on 2026-06-15 (callable capability merged into token-movers), but ~9 references to it as a live skill were left behind. This repoints/de-lists them so nothing names a skill that no longer exists.

Changed (Class A — slug references)

File What it was Fix
skills/skill-health/tests/smoke.sh real bugtoken-report in CANARY_SKILLS, so the dry-run structural check targeted a deleted skill dir token-movers
.github/ISSUE_TEMPLATE/bug_report.yml example/placeholder skill name (×3) token-movers
README.md per-skill override YAML snippet token-movers
SHOWCASE.md crypto-cluster example list drop token-report
docs/smithery-manifest.json orphaned static manifest (its generator skill was also deleted) remove the dead aeon-token-report tool entry
docs/smithery-submission.md submission table row remove dead row
skills/syndicate-article/SKILL.md tag keyword-map drop dead slug
skills/update-gallery/SKILL.md crypto category list drop dead slug
docs/skill-graph.md dead node + broken click-link to deleted skills/token-report/SKILL.md remove (also self-heals on next skill-graph run)

JSON re-validated; smoke.sh passes bash -n.

Deliberately NOT in this PR

Closes nothing on its own; companion to #502.

token-report was removed on 2026-06-15 (its callable capability merged into
token-movers), but ~9 references to it as a live skill were left behind. This
repoints/de-lists them so nothing names a skill that no longer exists:

- skills/skill-health/tests/smoke.sh: token-report was a CANARY_SKILLS entry,
  so the dry-run structural check pointed at a deleted skill dir -> token-movers
- .github/ISSUE_TEMPLATE/bug_report.yml: example/placeholder skill name -> token-movers
- README.md: per-skill override YAML snippet -> token-movers
- SHOWCASE.md: crypto-cluster example list -> drop token-report
- docs/smithery-manifest.json: removed the orphaned aeon-token-report tool entry
- docs/smithery-submission.md: removed the dead submission row
- skills/syndicate-article, skills/update-gallery: dropped the dead slug from
  the tag/category maps
- docs/skill-graph.md: removed the dead node + its broken click-link to the
  deleted skills/token-report/SKILL.md (regenerates clean on the next
  skill-graph run regardless)

Deliberately NOT touched:
- The articles/token-report-*.md data-contract refs (heartbeat "Token Pulse",
  operator-scorecard, skill-freshness, price-alert, wallet-risk, docs/status.md):
  token-movers produces no article, so that feature is orphaned, not mis-slugged.
  Tracked separately rather than faked with a rename.
- examples/* (handled by the a2a-server README PR).
- Sibling skills deleted in the same 2026-06-15 commit (token-alert,
  defi-monitor, wallet-digest, feature) still appear in some of these lists;
  left in place to keep this PR scoped to token-report.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@aaronjmars aaronjmars merged commit 562f78b into main Jun 19, 2026
3 checks passed
@aaronjmars aaronjmars deleted the chore/cleanup-token-report-refs branch June 19, 2026 14:01
aaronjmars added a commit that referenced this pull request Jun 19, 2026
…-15 (#504)

Follow-up to #503 (which cleaned up token-report). Same class of bug: token-alert,
defi-monitor, wallet-digest, and feature were removed on 2026-06-15 but left
dangling references. Repointed to live successors or de-listed:

- token-alert  -> price-alert   (real-time price/volume alerts)
- defi-monitor -> defi-overview (DeFi activity overview)
- wallet-digest-> treasury-info (wallet balances/holdings)
- feature      -> pr-review     (example skill name in the issue template)

Files: smithery-manifest.json + smithery-submission.md (removed the orphaned
tool entries), export-skill + README.md (broken example commands), bug_report.yml
(example skill name), update-gallery/syndicate-article/SHOWCASE (catalog/tag
lists), auto-workflow/narrative-convergence/compute-pulse/spawn-instance
(cross-references + example skill lists), wallet-profile (balance-skill pointer),
and skill-evals/evals.json (removed the dead token-alert eval block — the skill
can't run, so the eval can't either). JSON re-validated.

Deliberately NOT touched:
- docs/index.md: a stale sample catalog referencing ~10 skills deleted on
  2026-06-15 (also polymarket, memory-flush, github-issues, trending-coins,
  write-tweet, monitor-runners). Needs a full catalog refresh, not a 4-skill
  surgical edit; flagged for follow-up.
- docs/skill-graph.md: AUTO-GENERATED by the `skill-graph` skill and currently
  carries 8+ dead nodes. Re-running that skill regenerates it clean against the
  live catalog — hand-editing 4 of N nodes is the wrong fix.
- False positives left intact: `feature` as an issue-LABEL (issue-triage,
  shiplog, github-releases, workflow-templates), the displayName("defi-monitor")
  string-formatting unit test, dated blog posts, the spawn-instance note that
  CORRECTLY lists these as non-existent, `liquidpad-token-alert` (a different
  live skill), and illustrative sample-output blocks.
- Sibling skills deleted in the same commit but out of this PR's scope
  (thread-formatter, polymarket, monitor-runners, etc.) still appear in some
  shared lists; left for a follow-up sweep.

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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant