claude-skills-phoenix1479
Python package for applying a compact, production-ready Copilot policy set to any repository.
Install
pip install claude-skills-phoenix1479
Quick Start
claude-skills init . --profile production-core
claude-skills verify . --profile production-core
This init command also scaffolds a PR workflow file at .github/workflows/claude-skills-verify.yml.
Import API
import claude_skills
report = claude_skills.install(".")
print(report.created_count)
What gets installed (production-core)
- 8 agent modes
- 5 instruction weights
- 11 high-value workflow skills
- 3 templates
- 1 PR CI workflow (
.github/workflows/claude-skills-verify.yml) .github/copilot-instructions.mdbootstrap with auto-dispatch rules
Why this model
- Small package footprint compared with full libraries
- Enforces behavior at repository level where Copilot actually reads policy files
- Keeps token/credit usage lower by bundling only core skills
Corporate and Restricted Networks
Use one of these patterns depending on your environment:
1) Private Index (recommended for enterprises)
Mirror claude-skills-phoenix1479 to Artifactory/Nexus/Azure DevOps feed, then keep the same install command:
pip install claude-skills-phoenix1479
Set index config once on runners/developer machines:
pip config set global.index-url https://<private-index>/simple
pip config set global.trusted-host <private-index-host>
2) Proxy-Based Install
pip install claude-skills-phoenix1479 --proxy http://<proxy-host>:<port>
3) Offline Wheel Install (air-gapped)
On a connected machine:
python -m pip wheel claude-skills-phoenix1479 -w dist
On restricted machines:
pip install --no-index --find-links dist claude-skills-phoenix1479
CI for Every PR
The scaffolded workflow already runs:
claude-skills verify . --profile production-core
For non-GitHub CI, run the same command in your PR pipeline stage.
Detailed enterprise rollout options are documented in CORPORATE_INSTALL.md.
Package release/mirroring steps are documented in PYPI_RELEASE.md.
Metadata
Release files for claude-skills-phoenix1479 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| claude_skills_phoenix1479-0.1.1.tar.gz | 35.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| claude_skills_phoenix1479-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 78.5 kB
Release files / claude_skills_phoenix1479-0.1.1.tar.gz
| Download URL | claude_skills_phoenix1479-0.1.1.tar.gz |
|---|---|
| Size | 35.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c9317a95781e13274c7a862833b2fdb7a938499fab28f01c2ecfedfe9afe3ccb
|
|
BLAKE2b-256 checksum How to use checksums |
6412e4a504d756aa5b89a0581f520cab8bf031c2d31ef388d3926d2ef3cb4640
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / claude_skills_phoenix1479-0.1.1-py3-none-any.whl
| Download URL | claude_skills_phoenix1479-0.1.1-py3-none-any.whl |
|---|---|
| Size | 43.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
22272e33020f46c1d96cee72a7712aa15be9aff7c61933c589bf5ac7509b68da
|
|
BLAKE2b-256 checksum How to use checksums |
346974164308b3e9f9bf7c3cbf214ca536eb241826e7939339b2ff6ccc973f84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for claude-skills-phoenix1479 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.