What problem does it solve?
It prevents teams from judging trending GitHub projects by README and marketing alone, replacing hype-driven evaluation with a source-code-first audit that verifies architecture, star features, algorithm substance, and feedback loops.
Core Features & Use Cases
- Claim-to-Code Verification: Builds a claims ledger and traces every advertised feature from public API through entrypoint, state mutation, and future behavior.
- Algorithm Peel & Feedback Loop Tests: Classifies mechanisms as true algorithms, LLM judges, heuristics, rules, or external services, and validates self-improvement claims against a signal-decision-mutation-behavior chain.
- Structured Teardown Reports: Produces architecture maps, reproduction matrices, raw output audits, and Learn/Gap/Do-Not-Follow comparisons using templates in the references directory.
- Use Case: When evaluating a competitor agent runtime or a viral memory/RAG framework, run this Skill to produce an evidence-backed report separating real engineering from marketing before deciding what to adopt.
Quick Start
Ask the agent to teardown a specific open-source project, for example by saying: teardown the hermes agent runtime and tell me what is real versus marketing.