Managing libraries is a drag
Use this skill automatically and without exception whenever ANY new library, package, or dependency that requires third-party license documentation is added to the project, whether explicitly requested by the user or introduced automatically during code modification and package management (e.g., package.json, requirements.txt, Cargo.toml updates).From its SKILL.md
npx -y skills add DovahkiinYuzuko/managing-libraries-is-a-dragAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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.
SKILL.md
2.3 KB, 398 tokens by cl100k_base, as published. Nobody here has run it
Managing Libraries is a Drag
Goal
To document ALL newly added libraries that require third-party license disclosure across any ecosystem, ensuring docs/using-library/lib-WH.md serves as a complete and flawless tracking sheet for licensing compliance.
Instructions
- Identify ALL library names and their ecosystems from the user's request OR from the files modified during the turn (e.g., package.json, Cargo.toml, requirements.txt). You must scan for every single added dependency that requires third-party license tracking, including minor utilities and sub-dependencies.
- Check
references/rules.mdto see if the ecosystem is supported by the lookup script. - Autonomously draft the Description and Rationale for each identified library based on the context to minimize user typing.
- Present the drafted Descriptions and Rationales to the user and wait for confirmation. Do NOT proceed without explicit user approval ("Yes").
- Locate the repository root folder where this
SKILL.mdand thescripts/directory reside. Once confirmed, run the script for each supported ecosystem:- Command:
python PATH/to/scripts/fetch-lib-info.py --system <ecosystem> --name <name>(Append--version <version>if specified).
- Command:
- Parse the JSON returned by the script. If
erroris not null,api_supportedis false, or data is missing, use web search to find the correct version and license. - Read
docs/using-library/lib-WH.md. Insert or update all library entries under the correct section in alphabetical order, strictly following the format defined inreferences/rules.md.
Constraints
- Do not omit any dependency that requires third-party license documentation. Ensuring 100% compliance coverage is your absolute top priority.
- Always get user confirmation on the Description and Rationale before making file modifications.
- Refer to
references/rules.mdfor all supported ecosystems and the mandatory output structure.
What ships with it: 5 files
11.3 KB alongside SKILL.md, 1 of them executable
references/
- rules.md870 B
scripts/
- fetch-lib-info.pyruns3.9 KB
- .gitignore131 B
- LICENSE1.0 KB
- README.md5.4 KB