contributor-onboarding
Skill40 starsChanged 4 days agoApache-2.0View on GitHub
Use when changing bootstrap, devcontainer, doctor, or contributor-first-run setup across the monorepo and the standalone consent-protocol path.
In this repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hushh-webapp/AGENTS.mdAGENTS.md
- impeccableSkill
- agent-orchestration-governanceSkill
- analytics-observability-governanceSkill
- animateSkill
- animation-vocabularySkill
- apple-designSkill
- autonomous-rca-governanceSkill
- backend-agents-operonsSkill
- backend-api-contractsSkill
- backend-runtime-governanceSkill
- backendSkill
- brandkitSkill
- client-env-paritySkill
- codex-skill-authoringSkill
- comms-communitySkill
- context-refreshSkill
- docs-governanceSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- founder-brief-curationSkill
- frontend-architectureSkill
- frontend-cache-coherenceSkill
- frontend-design-systemSkill
- frontend-native-surface-mapperSkill
- frontendSkill
- frontend-surface-placementSkill
- future-plannerSkill
- github-contribution-governanceSkill
- hushh-consent-mcpSkill
- hushh-icon-themeSkill
- iam-consent-governanceSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- improve-animationsSkill
- industrial-brutalist-uiSkill
- kai-test-account-resetSkill
- less-text-karma-jiSkill
- mcp-developer-surfaceSkill
- mobile-nativeSkill
- mobile-parity-auditSkill
- mobile-plugin-contractsSkill
- morphy-axSkill
- one-voice-governanceSkill
- oss-license-governanceSkill
- pdf-artifact-generationSkill
- pick-ui-librarySkill
- pkm-upgrade-rehearsalSkill
- planning-boardSkill
- pr-governance-reviewSkill
- profile-uiSkill
- prototypeSkill
- puppy-one-harnessSkill
- quality-contractsSkill
- release-ios-appstoreSkill
- repo-contextSkill
- repo-operationsSkill
- review-animationsSkill
- reviewer-app-testingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 3 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Avoid overlap with docs-governance, repo-operations, and backend.
- Distinctive: line 62
Keep exactly one blessed monorepo contributor path and one aligned standalone upstream path.
- Very specific: line 63
Keep uv as the canonical Python toolchain everywhere contributor docs mention backend setup.
- Distinctive: line 64
Keep secrets hydrated into ignored local files only.
- Very specific: line 65
Treat doctor output as the first-run truth surface for local readiness.
- Distinctive: line 66
Verify onboarding changes twice: once through the direct scripts and once through the canonical repo entrypoint.
- Very specific: line 72
If the task becomes docs-home governance, use docs-governance.
- Very specific: line 73
If the task becomes CI/deploy/runtime operations, use repo-operations.
- Very specific: line 74
If the task becomes subtree maintainer policy, use subtree-upstream-governance.
- Very specific: line 75
If the task is backend runtime behavior instead of setup flow, use backend.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hussh Contributor Onboarding Skill
Purpose and Trigger
- Primary scope:
contributor-onboarding-intake - Trigger on contributor setup, bootstrap flow, devcontainer/Codespaces setup,
doctorreadiness, or monorepo versus standalone onboarding alignment. - Avoid overlap with
docs-governance,repo-operations, andbackend.
Coverage and Ownership
- Role:
owner - Owner family:
contributor-onboarding
Owned repo surfaces:
README.mdcontributing.md.devcontainerdocs/development/guides/getting-started.mdscripts/envconsent-protocol/README.mdconsent-protocol/CONTRIBUTING.md.agents/skills/contributor-onboarding
Non-owned surfaces:
docs-governancerepo-operationsbackendsubtree-upstream-governance
Do Use
- One blessed contributor path for the monorepo.
- Standalone
consent-protocolonboarding that stays aligned with the monorepo toolchain. - Bootstrap, profile hydration, and
doctorownership. - Devcontainer or Codespaces readiness for contributors.
Do Not Use
- Generic docs placement work outside onboarding.
- Runtime env or deploy secret parity work.
- Subtree maintainer policy that normal contributors should never see.
Read First
README.mdcontributing.mddocs/development/guides/getting-started.mdscripts/env/bootstrap.shscripts/env/bootstrap_profiles.shscripts/env/doctor.shconsent-protocol/CONTRIBUTING.md
Workflow
- Keep exactly one blessed monorepo contributor path and one aligned standalone upstream path.
- Keep
uvas the canonical Python toolchain everywhere contributor docs mention backend setup. - Keep secrets hydrated into ignored local files only; onboarding docs must not encourage tracked secrets.
- Treat
doctoroutput as the first-run truth surface for local readiness. - Verify onboarding changes twice: once through the direct scripts and once through the canonical repo entrypoint.
- For bootstrap, devcontainer, or profile-shape contract changes, do a third check before calling the onboarding path stable.
- Maintainer-only smoke/reviewer overlays must stay outside the canonical contributor runtime contract. RCA or deploy workflows may load them from Secret Manager, but bootstrap must not seed them by default.
Handoff Rules
- If the task becomes docs-home governance, use
docs-governance. - If the task becomes CI/deploy/runtime operations, use
repo-operations. - If the task becomes subtree maintainer policy, use
subtree-upstream-governance. - If the task is backend runtime behavior instead of setup flow, use
backend.
Required Checks
./bin/hushh bootstrap --help
./bin/hushh env bootstrap
./bin/hushh doctor --mode local --json
./bin/hushh docs verifyDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

