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.
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
- contributor-onboardingSkill
- 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
- 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
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
- Very specific: line 12
Avoid overlap with docs-governance, repo-operations, and backend.
- Distinctive: line 64
Keep Apache-2.0 as the first-party default across root and subtree unless an explicit exception is documented.
- Very specific: line 65
Keep NOTICE, REUSE coverage, and third-party inventories aligned in the same change.
- Distinctive: line 66
Treat package-manifest license drift as a release blocker for public packages.
- Distinctive: line 68
Run a second verification pass after editing the license surface.
- Very specific: line 73
If the task is broader repo governance, use repo-operations.
- Very specific: line 74
If the task is documentation-home governance, use docs-governance.
- Very specific: line 75
If the task is subtree routing or optional-mirror sync policy, use subtree-upstream-governance.
- Very specific: line 76
If the task is package-runtime behavior beyond the license surface, use backend or frontend.
≈ “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 OSS License Governance Skill
Purpose and Trigger
- Primary scope:
oss-license-governance-intake - Trigger on Apache-2.0 transition work,
LICENSEorNOTICEupdates, SPDX/REUSE coverage, package license metadata changes, or third-party notice inventory generation. - Avoid overlap with
docs-governance,repo-operations, andbackend.
Coverage and Ownership
- Role:
owner - Owner family:
oss-license-governance
Owned repo surfaces:
LICENSELICENSESNOTICEREUSE.tomlTHIRD_PARTY_NOTICES.mdconsent-protocol/LICENSEconsent-protocol/NOTICEconsent-protocol/THIRD_PARTY_NOTICES.mdscripts/licenses.agents/skills/oss-license-governance
Non-owned surfaces:
docs-governancerepo-operationsbackendfrontendsubtree-upstream-governance
Do Use
- Apache-2.0 license-surface changes across root and subtree.
- SPDX/REUSE coverage and notice-generation policy.
- Package-manifest license cleanup for first-party published packages.
- Third-party notice inventory generation and verification.
Do Not Use
- Generic docs-home placement work.
- CI/deploy operations work unless the issue is license-gate specific.
- Broad backend or frontend implementation that only incidentally touches licensed files.
Read First
LICENSENOTICEREUSE.tomlconsent-protocol/pyproject.tomlhushh-webapp/package.jsonpackages/hushh-mcp/package.json
Workflow
- Keep Apache-2.0 as the first-party default across root and subtree unless an explicit exception is documented.
- Keep
NOTICE, REUSE coverage, and third-party inventories aligned in the same change. - Treat package-manifest license drift as a release blocker for public packages.
- Generate notice artifacts from real lockfiles and dependency metadata rather than hand-editing lists.
- Run a second verification pass after editing the license surface.
- For root plus subtree licensing changes, run a third check from the canonical repo entrypoint before closing the work.
Handoff Rules
- If the task is broader repo governance, use
repo-operations. - If the task is documentation-home governance, use
docs-governance. - If the task is subtree routing or optional-mirror sync policy, use
subtree-upstream-governance. - If the task is package-runtime behavior beyond the license surface, use
backendorfrontend.
Required Checks
python3 scripts/licenses/verify_apache_surface.py
python3 scripts/licenses/generate_third_party_notices.py
./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.

