agentleFS
usk6666usk6666/yorishiro-proxy/.claude/skills/license-check/SKILL.md

license-check

Skill19 starsChanged 23 days agoApache-2.0View on GitHub

Check licenses of all dependencies and detect prohibited licenses

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check the LICENSE file of each dependency's repository/package

    line 23

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

/license-check

A skill for checking the licenses of all project dependency libraries.

License Policy

Allowed

MIT, BSD-2-Clause, BSD-3-Clause, Apache-2.0, ISC, MPL-2.0

Prohibited

GPL-2.0, GPL-3.0, LGPL-2.1, LGPL-3.0, AGPL-3.0 and other GPL variants

Steps

  1. List all dependencies with go list -m -json all
  2. Check the LICENSE file of each dependency's repository/package
  3. Compare licenses against the policy
  4. Display results in a table:
    • Dependency | Version | License | Status (OK / PROHIBITED / UNKNOWN)
  5. Warn if any prohibited or unknown licenses are found

Notes

  • For UNKNOWN licenses, recommend manual verification
  • Include transitive dependencies (indirect) in the scope

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.