License compliance
Check the license before copying or vendoring third-party code, preserve required notices and attribution, and flag copyleft or unknown licenses before they enter the codebase. Use when copying code from other projects, adding dependencies, vendoring files, or maintaining attribution documents; do not use as legal advice beyond flagging conflicts for review.From its SKILL.md
npx -y skills add 26zl/universal-agent-skills --skill license-complianceAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.4 KB, 193 tokens by cl100k_base, as published. Nobody here has run it
License Compliance
Code without a compatible license is code you cannot ship.
Rules
- Identify the license before copying, vendoring, or adapting third-party code; no license means no permission, and such code stays out.
- Preserve copyright headers, license files, and notice content the license requires; vendored code keeps its license text beside it.
- Flag copyleft licenses such as GPL, AGPL, and SSPL before they enter a proprietary or differently licensed codebase, and leave the adoption decision to the owner.
- Confirm a new dependency's license is compatible with the project's declared license before adding it.
- Keep attribution documents accurate when dependencies change.
- Snippets taken from documentation, answers, or examples follow the same rules as any other third-party code.
Boundaries
- Flag and describe conflicts; final licensing judgments belong to the project owner or counsel.
- Never strip license headers, even during cleanups that remove other comments.
What ships with it: 1 file
216 B alongside SKILL.md
agents/
- openai.yaml216 B
Gives 0 of the 12 instructions most license compliance skills give in 193 tokens
Counted across 99 of the 137 authors here whose files we hold, read 2026-09-06
- Generate a structured attribution reportin 7 of 99, across 4 files
- Include alternative hypotheses and false flag considerationsin 7 of 99, across 4 files
- Collect evidence across all six attribution categoriesin 7 of 99, across 4 files
- Use ATT&CK technique IDs for TTP comparisonin 7 of 99, across 4 files
- Justify attribution confidence levelsin 6 of 99, across 3 files
- Favor the hypothesis with the least inconsistent evidencein 6 of 99, across 3 files
- Analyze infrastructure overlap between campaignsin 6 of 99, across 3 files
- Score each evidence item as consistent, inconsistent, or neutral per hypothesisin 6 of 99, across 3 files
- Override transitive versions when no direct fix existsin 5 of 99, across 2 files
- Install the Snyk CLI and authenticate with SNYK_TOKENin 5 of 99, across 2 files
- Scan package manifests and lockfiles in the CI/CD pipelinein 5 of 99, across 2 files
- Preview fixes with snyk fix --dry-run before applyingin 5 of 99, across 2 files
Said here and by no other author read
- Identify the license before copying third-party code
- Preserve copyright headers, license files, and notices
- Flag copyleft licenses before they enter the codebase
- Keep attribution documents accurate when dependencies change
- Apply the same rules to snippets and examples
- Leave adoption decisions to the project owner
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.