python-package-management Skill
Guide for managing packages in the Agent Framework Python monorepo, including creating new connector packages, versioning, and the lazy-loading pattern. Use this when adding, modifying, or releasing packages. Published by microsoft in agent-framework.
Decision snapshot
Is this a fit?
Developers using agent-framework, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
13 days ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is python-package-management Skill?
Guide for managing packages in the Agent Framework Python monorepo, including creating new connector packages, versioning, and the lazy-loading pattern. Use this when adding, modifying, or releasing packages. Published by microsoft in agent-framework. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using agent-framework
Declared skill metadata
- Source file: python/.github/skills/python-package-management/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use python-package-management Skill
- Use it for developers using agent-framework.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/agent-framework
- Skill file: python/.github/skills/python-package-management/SKILL.md
What it does
Guide for managing packages in the Agent Framework Python monorepo, including creating new connector packages, versioning, and the lazy-loading pattern. Use this when adding, modifying, or releasing packages.
Skill instructions
Python Package Management Monorepo Structure python/ ├── pyproject.toml Root package (agent-framework) ├── packages/ │ ├── core/ agent-framework-core (main package) │ ├── foundry/ agent-framework-foundry │ ├── lab/ Standalone uv project, excluded from the root workspace │ ├── anthropic/ agent-framework-anthropic │ └── ... Other connector packages - agent-framework-core contains core abstractions and OpenAI/Azure OpenAI built-in - Provider packages extend core with specific integrations - Root agent-framework depends on agent-framework-core[all]. Despite the existing extra name, this is a curated standard install set, not every package at a particular lifecycle stage. - Entries in agent-framework-core[all] carry lower and upper bounds. Workspace integrations use the version released with the current Core cohort as their lower bound so pip does not backtrack across old cyclic core[all] - integration - core combinations. - packages/lab is intentionally excluded from the root uv workspace.
Verified compatibility and discovery
Frequently asked questions
What is python-package-management?
python-package-management is a open-source AI agent skill with Copy skill directory. Guide for managing packages in the Agent Framework Python monorepo, including creating new connector packages, versioning, and the lazy-loading pattern.
Who is python-package-management best for?
python-package-management is best for reusing agent instructions, scripts, and references.
How do I install python-package-management?
Install or run python-package-management using Copy skill directory. Check python-package-management for the latest setup command.
Is python-package-management actively maintained?
python-package-management may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
