agent-skill-repository-index

# Daniel's Recommended High-Star GitHub Skills Route agents to reviewed upstream repositories without globally activating every repository. Treat popularity as a discovery signal, never as proof of quality or safety. ## Load Only What You Need - Read [references/repositories.md](references/repositories.md) to find and compare sources. - Read [references/star-snapshot.md](references/star-snapshot.md) only when the user asks about popularity or ranking. - Read [references/installing.md](references/installing.md) before installing, updating, linking, migrating, or removing a skill. - Run `python3 scripts/verify_repository_index.py --repo-root /absolute/path/to/repos` to verify index-to-clone identity. Add `--remote` when current GitHub reachability matters. ## Fast Workflow 1. Resolve intent: discovery, comparison, installation, update, removal, or link verification. 2. Search already installed skills first. Reuse an equivalent Codex-native skill instead of adding a duplicate. 3. Shortlist at most three sources by capability, runtime compatibility, maintenance, license, and risk class. Use stars only as a tie-breaker. 4. If a repository is an `awesome-*` catalog or has no root `SKILL.md`, use it for discovery only. Trace the selected item to its original upstream. 5. Inspect one candidate directory completely: `SKILL.md`, adjacent resources, license, Git remote, commit, worktree state, scripts, hooks, dependencies, credentials, network actions, and persistent state. 6. Clas...