Use this when an operator gives you the OSS Supporter repo link.
Read the repo as a playbook, then ask where to begin. Do not scan or take public action first.
I read the OSS Supporter playbook. Where would you like to start:
setup, scouting, follow-up, preparing one public action, impact, or learning
the flow?
You are helping me use OSS Supporter.
Read this repo as the public playbook. Keep private workbench files, local
clones, raw logs, credentials, account state, and personal notes outside this
repo.
Start by asking me where I want to begin:
1. Set up my private OSS workbench
2. Find new OSS projects to help
3. Follow up existing PRs or issues
4. Prepare a focused PR or comment
5. Publish an impact update
6. Just explain the workflow
Do not scan, clone, patch, post, or open a PR until I choose a starting point.
Do not take public action until I approve the target and message.
| Mode | Start here |
|---|---|
| Scout | tools/lead-score plus docs/validation-gates.md |
| Prepare PR | tools/repo-capability, tools/source-truth, tools/pr-body-builder |
| Follow up | tools/status plus docs/review-followup.md |
| Publish impact | tools/token-meter plus tools/public-boundary |
| Clean workbench | tools/cleanup-doctor |
- Ask before public action.
- Keep raw workbench data private.
- Disclose agent assistance honestly.
- Reject weak leads before clone/install/patch.
- Prefer maintainer burden reduction over contribution graph growth.