Builderdna

ALWAYS use this skill when the user wants to analyze a GitHub developer or org, discover product/tool opportunities from developer activity, track tech trends in a domain (agent, LLM, MCP, etc.), or run BuilderDNA's analysis toolkit. Use when the user says "analyze X's GitHub", "what are people building in Y", "find opportunities in Z", "tech DNA", "builder insights", "trend radar", "what should I build", "developer landscape", "tech stack analysis", "competitive intelligence for X", or references BuilderDNA/builderdna directly. The skill wraps the core sandbox CLI commands (collect → trend → pain → opportunity → report) so the user never needs to remember flags — you translate intent into the right command chain. It does NOT replace the specialist skills (repo-trend, repo-awesome, twitter-learning, reddit-opportunity) or concept-radar (cross-source lifecycle). Reads state/hypotheses.json to track exploration across conversations. Uses goal-driven short-circuit pipeline to select the optimal execution path. A

flingjie Updated 0 repo stars

File contents

flingjie/builderdna commit ba864854d3 Runs: flingjie/value-discoveryflingjie/observability

Frequently asked questions

npx get-skill add flingjie/builderdna