← ClaudeAtlas

open-source-octopus-investigationlisted

Discover relevant open-source projects and contributors by crawling GitHub social graphs (stars, follows, contributions) from an origin, organizing findings into thematic 'tentacles', logging every profile/repo to a dedup tracker, and optionally filing issues. TRIGGERS: 'open source octopus investigation', 'octopus investigation', 'octopus search', 'octopus this', 'crawl the social graph', 'map the open-source landscape from <user>', 'who's connected to <github-user>', 'find projects like <repo> via stars/follows', 'technology scouting for <domain>'. Use when the user wants graph-based discovery (following human curation) rather than keyword search.
thdelmas/open-source-octopus-investigation · ★ 0 · AI & Automation · score 67
Install: claude install-skill thdelmas/open-source-octopus-investigation
# Octopus Investigation A systematic method for discovering relevant open-source projects and contributors by crawling social graphs on GitHub. You start from a single **origin** (a person or topic), extend **tentacles** outward through their network, and follow human curation — stars, follows, contributions — instead of keyword search. This surfaces projects that are hard to find through search because you're leveraging the taste of people already in the space. Reference guide (the canonical description): `docs/guides/octopus-investigation.md` in the theophile.world repo. ## Prerequisites - `gh` CLI must be authenticated (`gh auth status`). If not, stop and ask the user to run `gh auth login`. - All crawling uses `gh api` (no scraping). Be mindful of rate limits — check with `gh api rate_limit -q '.rate.remaining'` if calls start failing. ## Before you start: scope it An octopus search expands indefinitely. **Always confirm scope with the user first** unless they already gave it: - **Origin(s):** one well-chosen GitHub profile or topic. One strong origin beats five mediocre ones. - **Depth:** how many levels to crawl (default: 2 levels deep). - **Budget:** time or call limit (default: ~60 API calls / breadth-first, don't tunnel into one tentacle). - **Output:** tracker only, or also file GitHub issues? Into which repo? State the scope back in one line, then proceed. ## The process ### 1. Pick an origin Profile a single origin deeply embedded in the target ecosyste