agentleFS
hushh-labshushh-labs/hushh-research/.agents/skills/contributor-onboarding/SKILL.md

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.

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
  1. Very specific:

    Avoid overlap with docs-governance, repo-operations, and backend.

    line 12
  2. Distinctive:

    Keep exactly one blessed monorepo contributor path and one aligned standalone upstream path.

    line 62
  3. Very specific:

    Keep uv as the canonical Python toolchain everywhere contributor docs mention backend setup.

    line 63
  4. Distinctive:

    Keep secrets hydrated into ignored local files only.

    line 64
  5. Very specific:

    Treat doctor output as the first-run truth surface for local readiness.

    line 65
  6. Distinctive:

    Verify onboarding changes twice: once through the direct scripts and once through the canonical repo entrypoint.

    line 66
  7. Very specific:

    If the task becomes docs-home governance, use docs-governance.

    line 72
  8. Very specific:

    If the task becomes CI/deploy/runtime operations, use repo-operations.

    line 73
  9. Very specific:

    If the task becomes subtree maintainer policy, use subtree-upstream-governance.

    line 74
  10. Very specific:

    If the task is backend runtime behavior instead of setup flow, use backend.

    line 75

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Hussh Contributor Onboarding Skill

Purpose and Trigger

  • Primary scope: contributor-onboarding-intake
  • Trigger on contributor setup, bootstrap flow, devcontainer/Codespaces setup, doctor readiness, or monorepo versus standalone onboarding alignment.
  • Avoid overlap with docs-governance, repo-operations, and backend.

Coverage and Ownership

  • Role: owner
  • Owner family: contributor-onboarding

Owned repo surfaces:

  1. README.md
  2. contributing.md
  3. .devcontainer
  4. docs/development/guides/getting-started.md
  5. scripts/env
  6. consent-protocol/README.md
  7. consent-protocol/CONTRIBUTING.md
  8. .agents/skills/contributor-onboarding

Non-owned surfaces:

  1. docs-governance
  2. repo-operations
  3. backend
  4. subtree-upstream-governance

Do Use

  1. One blessed contributor path for the monorepo.
  2. Standalone consent-protocol onboarding that stays aligned with the monorepo toolchain.
  3. Bootstrap, profile hydration, and doctor ownership.
  4. Devcontainer or Codespaces readiness for contributors.

Do Not Use

  1. Generic docs placement work outside onboarding.
  2. Runtime env or deploy secret parity work.
  3. Subtree maintainer policy that normal contributors should never see.

Read First

  1. README.md
  2. contributing.md
  3. docs/development/guides/getting-started.md
  4. scripts/env/bootstrap.sh
  5. scripts/env/bootstrap_profiles.sh
  6. scripts/env/doctor.sh
  7. consent-protocol/CONTRIBUTING.md

Workflow

  1. Keep exactly one blessed monorepo contributor path and one aligned standalone upstream path.
  2. Keep uv as the canonical Python toolchain everywhere contributor docs mention backend setup.
  3. Keep secrets hydrated into ignored local files only; onboarding docs must not encourage tracked secrets.
  4. Treat doctor output as the first-run truth surface for local readiness.
  5. Verify onboarding changes twice: once through the direct scripts and once through the canonical repo entrypoint.
  6. For bootstrap, devcontainer, or profile-shape contract changes, do a third check before calling the onboarding path stable.
  7. 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

  1. If the task becomes docs-home governance, use docs-governance.
  2. If the task becomes CI/deploy/runtime operations, use repo-operations.
  3. If the task becomes subtree maintainer policy, use subtree-upstream-governance.
  4. 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 verify

Download now (ZIP)

Does 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.