Source repositories
Repository metadata, declared files, READMEs, licenses, activity, and release signals.
How SkillIndex turns public source material into comparable profiles for agent skills and MCP servers.
Repository metadata, declared files, READMEs, licenses, activity, and release signals.
Published setup instructions, package references, configuration examples, and linked docs.
Authentication, permissions, clients, runtimes, transports, and destructive-action indicators when evidence exists.
Consistent categories and project-health fields that make otherwise different projects easier to compare.
SkillIndex discovers public agent skills and MCP servers, identifies the canonical repository or skill file, and retains a link to the source. A profile is an evaluation layer, not a replacement for that source.
Public metadata and declared documentation are used to identify installation methods, compatible clients, runtimes, transports, requirements, licensing, authentication, permissions, and project activity. Undetected information remains unknown rather than being presented as fact.
Projects describe similar capabilities in very different ways. SkillIndex maps those details into consistent fields so developers can search and compare without manually translating every README.
Repository signals can change. Profiles surface source recency where available, and every profile provides a way to report outdated or incorrect information. Claimed profiles identify an owner, but verification is not an endorsement.
Reading the signals
Source clarity, licensing, documentation, and setup evidence available to evaluate.
Public recency and repository-health signals that suggest whether a project is active.
Public usage proxies such as stars and forks, used as context rather than proof of quality.
Automated signals are not a security audit, warranty, or endorsement. Review the source, requested permissions, and project documentation before installing software or connecting it to sensitive data.
Use SkillIndex to discover, evaluate, and compare. Use the linked repository to inspect the implementation and make the final call.
Find your fit