How do I install the Python Packaging License Finder skill?

Run npx skillmds add tools-only/python-packaging-license-finder in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Python Packaging License Finder safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Python Packaging License Finder?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Python Packaging License Finder free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Python Packaging License Finder?

tools-only (@tools-only) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Python Packaging License Finder by tools-only

Name: Python Packaging License Finder
Rating: 4.5 (4 reviews)
Author: tools-only

File contents

Python Package License Finder

This skill helps you deterministically find license information for Python packages using a two-step approach: first checking PyPI metadata, then searching the source repository if needed.

Instructions

When a user asks to find the license for a Python package, follow this deterministic process:

Step 1: Check PyPI Metadata

First, attempt to find the license from PyPI using the package inspection script:

./scripts/find_license.py <package_name> [version]

If the script finds a license in the PyPI metadata, stop here and return the license name.

Step 2: Search Git Repository (if PyPI fails)

If no license is found in PyPI metadata, search the package's source repository:

Get the source repository URL from the PyPI metadata (the script will provide it)
Use the shallow-clone skill to clone the repository:
```
Skill: git:shallow-clone
```

Search for LICENSE files in the cloned repository:

find . -iname "license*" -o -iname "copying*" -o -iname "copyright*" | head -10

Read the license file to identify the license type:
```
head -20 <license_file>
```

Step 3: Report Results

License Found: Return the license name (e.g., "MIT License", "Apache-2.0", "GPL-3.0")
License Not Found: Report that the license could not be determined

Usage Examples

Find License for Popular Package

./scripts/find_license.py requests

Expected: Find "Apache-2.0" from PyPI metadata

Find License for Package with Missing PyPI License

./scripts/find_license.py some-package

Expected: Fall back to repository search if PyPI metadata is incomplete

Specific Version Analysis

./scripts/find_license.py django 4.2.0

Expected: Find license for specific Django version

Error Handling

Package Not Found

Verify package name spelling
Check package availability on PyPI
Suggest alternative package names

Repository Access Issues

Report if source repository is unavailable
Note private/restricted repositories
Suggest manual license verification

License File Parsing

Handle non-standard license file formats
Report unclear or multiple licenses
Recommend manual review for complex cases

Integration Notes

This skill complements:

python-packaging-complexity - License info helps assess redistribution complexity
python-packaging-license-checker - Provides license names for compatibility assessment
python-packaging-source-finder - Uses similar PyPI metadata analysis

The skill focuses on finding license information, while license-checker focuses on assessing license compatibility for redistribution.

---name: python-packaging-license-finderdescription: Deterministically find license information for Python packages by checking PyPI metadata first, then falling back to Git repository LICENSE files using shallow cloning.--- # Python Package License Finder This skill helps you deterministically find license information for Python packages using a two-step approach: first checking PyPI metadata, then searching the source repository if needed. ## Instructions When a user asks to find the license for a Python package, follow this deterministic process: ### Step 1: Check PyPI Metadata First, attempt to find the license from PyPI using the package inspection script: ```bash ./scripts/find_license.py <package_name> [version] ``` If the script finds a license in the PyPI metadata, **stop here** and return the license name. ### Step 2: Search Git Repository (if PyPI fails) If no license is found in PyPI metadata, search the package's source repository: 1. **Get the source repository URL** from the PyPI metadata (the script will provide it) 2. **Use the shallow-clone skill** to clone the repository: ``` Skill: git:shallow-clone ``` 3. **Search for LICENSE files** in the cloned repository: ```bash find . -iname "license*" -o -iname "copying*" -o -iname "copyright*" | head -10 ``` 4. **Read the license file** to identify the license type: ```bash head -20 <license_file> ``` ### Step 3: Report Results - **License Found**: Return the license name (e.g., "MIT License", "Apache-2.0", "GPL-3.0") - **License Not Found**: Report that the license could not be determined ## Usage Examples ### Find License for Popular Package ```bash ./scripts/find_license.py requests ``` **Expected**: Find "Apache-2.0" from PyPI metadata ### Find License for Package with Missing PyPI License ```bash ./scripts/find_license.py some-package ``` **Expected**: Fall back to repository search if PyPI metadata is incomplete ### Specific Version Analysis ```bash ./scripts/find_license.py django 4.2.0 ``` **Expected**: Find license for specific Django version ## Error Handling ### Package Not Found - Verify package name spelling - Check package availability on PyPI - Suggest alternative package names ### Repository Access Issues - Report if source repository is unavailable - Note private/restricted repositories - Suggest manual license verification ### License File Parsing - Handle non-standard license file formats - Report unclear or multiple licenses - Recommend manual review for complex cases ## Integration Notes This skill complements: - **python-packaging-complexity** - License info helps assess redistribution complexity - **python-packaging-license-checker** - Provides license names for compatibility assessment - **python-packaging-source-finder** - Uses similar PyPI metadata analysis The skill focuses on **finding** license information, while license-checker focuses on **assessing** license compatibility for redistribution.

Frequently asked questions