SkillMM · Agent Skills Radar
Turning scattered GitHub Skills into a continuously maintained, assessable, reusable workflow asset library
AI Asset Curation & Research Product Case / 03
SkillMM turns scattered Agent Skills on GitHub into a daily maintained, searchable, assessable, and traceable AI workflow asset library.
This is neither a complete GitHub search engine nor an automated leaderboard. It solves what comes after discovery: verify that a real SKILL.md exists, assess completeness, usability, utility, and maintenance, then preserve reusable projects as durable assets.
Core users include AI product managers, AI creators, Agent workflow researchers, and users of Codex, Claude Code, Gemini CLI, and related tools.
The supplied snapshot dated 2026-08-11 contains 820 Skill projects across nine categories, including 394 rated excellent and 420 rated good.
The live product offers Daily Picks, Quality Archive, and All Skills views, with categories, search, sorting, detail views, and source actions.
A local Obsidian vault is the source of truth; Codex assists daily discovery and assessment, then a static build is published through Cloudflare Worker.
The Judgment Problem Stars Cannot Solve
Agent Skills, Claude Code Skills, and Codex workflows are growing across many repositories, but their documentation and runnability vary widely. Stars provide popularity context; they do not explain triggers, dependencies, boundaries, or reusable scenarios.
SkillMM therefore defines success as reducing discovery and judgment cost, not maximizing collection size. Within minutes, users should understand what a Skill does, why it is worth attention, and what to inspect before using it.
The Evaluation Funnel from Discovery to Curation
Each candidate is deduplicated, verified to contain a real SKILL.md, and reviewed through repository structure, documentation, and key files. Assessment looks beyond popularity to completeness, usability, utility, and maintenance.
Rating, curation score, recommendation rationale, tags, use cases, and pre-install checks form the judgment interface. Scores organize attention without pretending that editorial assessment is a universal objective truth.
Daily Operations Are the Product
Behind the website is a content supply chain: Codex discovers candidates daily, assists deduplication and assessment, writes local Obsidian records, updates daily and overview indexes, rebuilds the data, and publishes the public view.
The three views serve different jobs: Daily Picks answers what matters today, Quality Archive preserves durable value, and All Skills supports systematic retrieval. Freshness, synchronization, and operating reliability matter more than one-off interface novelty.
Local Asset Library, Public Display Layer
Local Markdown records preserve assessment detail, sources, and long-term indexes as the single source of truth. The public site receives only rebuilt static JSON and pages, hides local Obsidian paths, and exposes no writes, CMS, or cloud crawler.
This boundary keeps changeable, judgment-heavy research local while Cloudflare Worker serves stable, sanitized, fast public results. Visitors need no account and cannot reach local notes or temporary files.
PROCESS
Key Decisions
Curated, not comprehensive
Only projects that pass real SKILL.md verification and basic assessment enter the archive, preventing scale from turning the directory into another source of noise.
Stars are a signal, not a quality verdict
Stars and forks remain useful context but never replace checks of documentation, runnability, dependencies, practical scenarios, and maintenance.
Local source of truth, static publishing
Assessment and durable records stay local while the online layer is read-only display, reducing operating complexity and protecting local paths and unsanitized notes.
Stabilize supply before expanding the platform
Accounts, favorites, CMS, community, and cloud crawling stay out of scope until the daily discovery, assessment, archive, and publishing loop is reliably maintained.
Role & Collaboration
I led product positioning and knowledge operations: defining curation boundaries, assessment dimensions, taxonomy, information architecture, search and sorting logic, and the daily workflow from local records to public publishing.
Codex assists project discovery, repository reading, deduplication, field structuring, assessment, and site builds. I remain responsible for selection criteria, final ratings, public boundaries, and online acceptance.
Validation, Outcome & Reflection
The confirmed result is a live website whose supplied 2026-08-11 snapshot contains 820 Skill projects, nine categories, and three content views. This case does not invent traffic, adoption, or user-feedback outcomes.
Next-stage acceptance focuses on daily update reliability, local-to-live synchronization, and whether categories, search, and sorting cover core findability tasks. These are ongoing targets, not completed user outcomes.
The moat of a curation product is not the number of cards on screen, but an executable, traceable selection standard and content supply system that improves through practice.
Next, fixed share links, installation-risk labels, weekly rankings, and feeds should precede accounts, databases, or APIs. Platform complexity should serve validated reuse needs rather than become premature operating burden.
DEMO / 03
Product demo video
A 33-second walkthrough of the public snapshot, quality archive, category filters, project details, and assessment method. The video contains no local archive paths or internal configuration.


