메뉴
Use this skill to deterministically find license information for Python packages by checking PyPI metadata first, then falling back to Git repository LICENSE files using shallow cloning.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | python-packaging-license-finder |
| description | Use this skill to deterministically find license information for Python packages by checking PyPI metadata first, then falling back to Git repository LICENSE files using shallow cloning. |
| allowed-tools | Bash Skill |
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.
When a user asks to find the license for a Python package, follow this deterministic process:
If a source repository URL is provided by the caller, skip PyPI lookup entirely:
git:shallow-clone skillYou can also use the script with a source URL to trigger this flow:
./scripts/find_license.py <package_name> --source-url <url>
If no source URL is provided, proceed with Step 1.
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.
If no license is found in PyPI metadata, search the package's source repository:
Skill: git:shallow-clone
find . -iname "license*" -o -iname "copying*" -o -iname "copyright*" | head -10
head -20 <license_file>
./scripts/find_license.py requests
Expected: Find "Apache-2.0" from PyPI metadata
./scripts/find_license.py some-package
Expected: Fall back to repository search if PyPI metadata is incomplete
./scripts/find_license.py django 4.2.0
Expected: Find license for specific Django version
This skill complements:
The skill focuses on finding license information, while license-checker focuses on assessing license compatibility for redistribution.
Check an ODH module operator repository for contract violations against the platform onboarding guide. Validates PlatformObject status, CRD structure, Helm chart content, webhook ownership, metadata conventions, and reconciler chain ordering. Use during code review or after scaffolding a new module.
Read existing in-tree ODH operator component code and produce a step-by-step extraction checklist for migrating it to a standalone module. Analyzes controller logic, webhooks, RBAC, embedded manifests, and DSC field mappings. Use when extracting a component from the monolithic operator into its own module repo.
Given a component name, generate a complete standalone ODH module operator repository. Produces Go module, CRD types implementing PlatformObject, controller skeleton with reconciler builder pattern, Helm chart, Makefile, CI config, singleton webhook, and AGENTS.md. Use when starting a new module from scratch.
Generate AIPCC Commits style commit messages or summarize existing commits
Hello world plugin implementation
Generate comprehensive sprint summaries by analyzing JIRA sprint data, including issue breakdown, progress metrics, and team performance insights.