القائمة
Connect GitHub to the brain with the gh CLI, so pull-github.sh pulls repo activity (commits, issues) into raw/. Use when the user wants their code or repo activity captured.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Connect ClickUp tasks to the brain with a personal API token and a pull script, so open work lands in raw/. Use when the user manages tasks or projects in ClickUp.
Connect Gmail to the brain — the easy connector way (browser sign-in, no key) or as a saved local copy via the gws CLI. Use when the user wants their email readable by the brain.
Install the Google Workspace CLI (gws) and sign the user in, so the brain can pull Google Drive, Gmail, and Calendar into raw/ as local copies. Use when connecting any Google source as a saved local copy rather than a live connector.
Wire the brain's scripts to run on a schedule — pull, ingest, lint, backup — so it stays current on its own. Use after at least one source is connected and the user wants hands-off refresh.
Turn on backup and wire the brain to the user's tools, with them, one at a time. Run after /onboard, or any time to add a source. Sync first, then sources, then an optional schedule.
The full daily cycle: pull everything, ingest what's new, summarize. Use once a day.
| name | connect-github |
| description | Connect GitHub to the brain with the gh CLI, so pull-github.sh pulls repo activity (commits, issues) into raw/. Use when the user wants their code or repo activity captured. |
You're wiring the user's GitHub so repo activity lands in the brain. This is the
smoothest source — the gh CLI signs in through the browser, no keys to manage,
and the starter already ships pull-github.sh that uses it.
Offer to run the one that fits, then confirm with gh --version:
brew install ghwinget install --id GitHub.cligh auth login.gh auth status — it should say they're logged in.No token is ever pasted into the chat; gh stores it in the OS keychain.
The puller already exists — it grabs recent commits and open issues:
# Their most-recently-updated repos (default):
./scripts/pull-github.sh
# Or name the repos that matter:
GITHUB_REPOS="acme/site acme/api" ./scripts/pull-github.sh
Confirm files appear under raw/github. It tracks a timestamp, so re-runs only
fetch what's new, and the morning/evening routines run it for them on a schedule.
Mark the Code row in sources.md with today's date. They can re-run /connect
any time for the next source.