| name | finding-ai-builders |
| description | Use when the user asks to find true AI builders like a seed person, discover who to follow, monitor what builders are shipping, expand an AI builder watchlist, or separate builder signals from influencer noise. |
Finding AI Builders
Overview
Track builders, not influencers. This skill starts from a seed such as a Peter baseline, finds people with public shipping behavior, and turns them into Sondar watchlist entries and STRIKE/WATCH/IGNORE/KILL decisions.
Core rule:
Public shipping behavior beats public opinion.
Inputs
Use this skill with a GitHub profile, repo, org, project URL, builder name, or category such as Codex, Claude Code, OpenClaw, MCP, agent skills, observability, local inference, or model routing.
For a Peter baseline, look for agent workbench tools, usage/cost surfaces, local/MCP bridges, personal data tooling, and OpenClaw-adjacent infrastructure.
GitHub CLI Preflight
Use gh CLI for GitHub retrieval. Do not substitute web search for GitHub retrieval unless gh is unavailable and the user accepts degraded evidence.
Run this before research:
which gh
gh --version
gh auth status
If which gh or gh --version fails, stop and report that GitHub CLI is missing. If gh auth status fails, public unauthenticated calls may still work, but state the authentication gap before continuing.
Default retrieval commands:
gh api users/<login>
gh repo list <login> --source --limit 80 --json nameWithOwner,description,stargazerCount,primaryLanguage,updatedAt,url
gh api users/<login>/starred --method GET -H Accept:application/vnd.github.star+json -f per_page=100
gh search repos -- updated --order desc -- 30
gh repo view <owner>/<repo> --json nameWithOwner,description,stargazerCount,forkCount,issues,latestRelease,updatedAt,url