agentleFS
hushh-labshushh-labs/hushh-research/.agents/skills/oss-license-governance/SKILL.md

oss-license-governance

Skill40 starsChanged 5 days agoApache-2.0View on GitHub

Use when changing Apache-2.0 licensing, SPDX/REUSE coverage, package license metadata, or third-party notice generation across consent-protocol and hushh-research.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 3 are distinctive, and 6 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.

  • 6

    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 Apache-2.0 as the first-party default across root and subtree unless an explicit exception is documented.

    line 64
  3. Very specific:

    Keep NOTICE, REUSE coverage, and third-party inventories aligned in the same change.

    line 65
  4. Distinctive:

    Treat package-manifest license drift as a release blocker for public packages.

    line 66
  5. Distinctive:

    Run a second verification pass after editing the license surface.

    line 68
  6. Very specific:

    If the task is broader repo governance, use repo-operations.

    line 73
  7. Very specific:

    If the task is documentation-home governance, use docs-governance.

    line 74
  8. Very specific:

    If the task is subtree routing or optional-mirror sync policy, use subtree-upstream-governance.

    line 75
  9. Very specific:

    If the task is package-runtime behavior beyond the license surface, use backend or frontend.

    line 76

≈ “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 OSS License Governance Skill

Purpose and Trigger

  • Primary scope: oss-license-governance-intake
  • Trigger on Apache-2.0 transition work, LICENSE or NOTICE updates, SPDX/REUSE coverage, package license metadata changes, or third-party notice inventory generation.
  • Avoid overlap with docs-governance, repo-operations, and backend.

Coverage and Ownership

  • Role: owner
  • Owner family: oss-license-governance

Owned repo surfaces:

  1. LICENSE
  2. LICENSES
  3. NOTICE
  4. REUSE.toml
  5. THIRD_PARTY_NOTICES.md
  6. consent-protocol/LICENSE
  7. consent-protocol/NOTICE
  8. consent-protocol/THIRD_PARTY_NOTICES.md
  9. scripts/licenses
  10. .agents/skills/oss-license-governance

Non-owned surfaces:

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

Do Use

  1. Apache-2.0 license-surface changes across root and subtree.
  2. SPDX/REUSE coverage and notice-generation policy.
  3. Package-manifest license cleanup for first-party published packages.
  4. Third-party notice inventory generation and verification.

Do Not Use

  1. Generic docs-home placement work.
  2. CI/deploy operations work unless the issue is license-gate specific.
  3. Broad backend or frontend implementation that only incidentally touches licensed files.

Read First

  1. LICENSE
  2. NOTICE
  3. REUSE.toml
  4. consent-protocol/pyproject.toml
  5. hushh-webapp/package.json
  6. packages/hushh-mcp/package.json

Workflow

  1. Keep Apache-2.0 as the first-party default across root and subtree unless an explicit exception is documented.
  2. Keep NOTICE, REUSE coverage, and third-party inventories aligned in the same change.
  3. Treat package-manifest license drift as a release blocker for public packages.
  4. Generate notice artifacts from real lockfiles and dependency metadata rather than hand-editing lists.
  5. Run a second verification pass after editing the license surface.
  6. For root plus subtree licensing changes, run a third check from the canonical repo entrypoint before closing the work.

Handoff Rules

  1. If the task is broader repo governance, use repo-operations.
  2. If the task is documentation-home governance, use docs-governance.
  3. If the task is subtree routing or optional-mirror sync policy, use subtree-upstream-governance.
  4. If the task is package-runtime behavior beyond the license surface, use backend or frontend.

Required Checks

python3 scripts/licenses/verify_apache_surface.py
python3 scripts/licenses/generate_third_party_notices.py
./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.