ecosystem-links

Solid

Weekly link-health audit of ECOSYSTEM.md — checks every GitHub repo for archived/disabled state and every project URL for HTTP 4xx/5xx or redirect chains, surfacing dead/archived/moved entries before a casual reader stumbles into one. Closes the three-skill ecosystem loop with ecosystem-entrants (arrivals) and ecosystem-pulse (liveness).

AI & Automation 508 stars 166 forks Updated today MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
90
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

> **${var}** — Optional. `dry-run` skips notify (state still updates and article still writes). Empty = normal run. Today is ${today}. `ECOSYSTEM.md` is the curated catalog of projects, agents, and products building on top of Aeon — 30+ entries today, growing in irregular bursts. `ecosystem-pulse` measures activity for projects that already resolve to a GitHub repo. `ecosystem-entrants` reports week-over-week arrivals and departures. Neither catches entries whose URLs have gone 404, whose GitHub repo got archived, or whose custom domain lapsed. The first time a casual visitor clicks an ecosystem row and hits a dead page, the catalog stops being trustworthy. This skill closes that gap. It is a weekly Monday URL-health audit of every link in `ECOSYSTEM.md` — GitHub repos, X handles, custom project domains, anything in the links column. Read-only against `ECOSYSTEM.md`; curation stays a human PR decision per the file's own "Add your project" rules. Read `memory/MEMORY.md` for context. Read the last 8 days of `memory/logs/` for prior-run context. Read `soul/SOUL.md` + `soul/STYLE.md` if populated to match voice in the notification and article. ## Why a separate skill from ecosystem-pulse and ecosystem-entrants | Skill | Question answered | Cadence | Slot | |-------|-------------------|---------|------| | `ecosystem-pulse` | "Are listed projects shipping this week?" | Weekly (Mon 11:00 UTC) | Liveness of *known-good* GitHub repos | | `ecosystem-entrants` | "What was added to ...

Details

Author
aaronjmars
Repository
aaronjmars/aeon
Created
3 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

ecosystem-entrants

Weekly diff of ECOSYSTEM.md against last run — surfaces newly-added projects (and projects removed) as a discrete signal so new entrants aren't lost in the static list. Pairs with ecosystem-pulse (liveness) on Monday morning.

508 Updated today
aaronjmars
AI & Automation Solid

ecosystem-pulse

Weekly liveness check of the projects listed in ECOSYSTEM.md — stars/forks/last-commit recency + new releases for any project that can be matched to a GitHub repo

508 Updated today
aaronjmars
Data & Documents Listed

ecosystem-audit

ALWAYS use this skill when the user asks any question about their Claude Code setup, installed skills, memory system, handoffs, worktrees, or ~/.claude directory health. This is the go-to skill for introspection of the Claude Code environment itself. Specifically trigger on: (1) Skill inventory questions — "how many skills do I have", "which skills am I using", "what's dormant", "which skills can I uninstall", "are there overlapping skills"; (2) Cleanup and hygiene requests — "clean up my ecosystem", "audit my setup", "~/.claude feels bloated", "monthly hygiene check", "what needs cleanup", "stale worktrees", "orphaned handoff prompts"; (3) Diagnostic symptoms — "my memory system isn't working", "lessons aren't being picked up", "skill is not triggering", "claude keeps forgetting", "why is the wrong skill firing", "duplicate skill confusion"; (4) Health dashboards — "show me a health dashboard", "utilization across skills/memory/handoffs", "ecosystem health report"; (5) Any mention of auditing persistent arti

0 Updated 6 days ago
wan-huiyan