uv-package-manager
This skill should be used when the user asks to "set up a Python project with uv", "manage Python dependencies", "configure uv", "create a virtual environment with uv", "migrate from pip to uv", "speed up CI with uv", or when working with uv for virtual environments, package management, lockfiles, Docker builds, or Python version management.
What this skill does
# uv Package Manager Fast Python package installer and resolver written in Rust. 10-100x faster than pip, with built-in virtual environment management, Python version management, and lockfile support. ## When to Activate - Setting up new Python projects - Managing Python dependencies - Creating and managing virtual environments - Installing or pinning Python interpreters - Resolving dependency conflicts - Migrating from pip, pip-tools, or poetry - Optimizing CI/CD pipelines or Docker builds - Working with lockfiles for reproducible builds - Managing monorepo Python projects ## Quick Start ```bash # Create a new project uv init my-project cd my-project # Add dependencies uv add requests pandas # Add dev dependencies uv add --dev pytest black ruff # Sync all dependencies (creates venv if needed) uv sync # Run commands in the virtual environment uv run pytest uv run python app.py ``` ## Essential Commands ```bash # Project management uv init [PATH] # Initialize project uv add PACKAGE # Add dependency uv remove PACKAGE # Remove dependency uv sync # Install dependencies uv lock # Create/update lockfile # Virtual environments uv venv [PATH] # Create venv uv run COMMAND # Run in venv (no activation needed) # Python management uv python install VERSION # Install Python uv python list # List installed Pythons uv python pin VERSION # Pin Python version # Package installation (pip-compatible) uv pip install PACKAGE # Install package uv pip uninstall PACKAGE # Uninstall package uv pip freeze # List installed uv pip list # List packages # Utility uv cache clean # Clear cache uv --version # Show version ``` ## Best Practices 1. **Always use lockfiles** — Commit `uv.lock` for reproducibility 2. **Pin Python version** — Use `.python-version` via `uv python pin` 3. **Separate dev dependencies** — Use `uv add --dev` for test/lint tools 4. **Prefer `uv run`** — Avoid manual venv activation 5. **Use `--frozen` in CI** — Exact reproduction from lockfile 6. **Leverage global cache** — uv shares a cache across all projects 7. **Use workspaces** — For monorepo projects with `[tool.uv.workspace]` 8. **Export for compatibility** — `uv export --format requirements-txt` when needed ## Reference Documentation Detailed guides for each workflow: - **Virtual Environments** — [references/virtual-environments.md](references/virtual-environments.md) — Creating, activating, `uv run` - **Package Management** — [references/package-management.md](references/package-management.md) — Adding, removing, upgrading, locking deps - **Python Versions** — [references/python-versions.md](references/python-versions.md) — Installing, pinning Python versions - **Project Configuration** — [references/project-configuration.md](references/project-configuration.md) — pyproject.toml, existing projects, monorepo - **CI/CD & Docker** — [references/ci-cd-docker.md](references/ci-cd-docker.md) — GitHub Actions, multi-stage Dockerfiles - **Lockfiles & Caching** — [references/lockfiles-caching.md](references/lockfiles-caching.md) — Lockfile workflows, cache, parallel, offline - **Migration Guide** — [references/migration-guide.md](references/migration-guide.md) — From pip, poetry, pip-tools - **Tooling Integration** — [references/tooling-integration.md](references/tooling-integration.md) — Pre-commit hooks, VS Code settings ## Resources - [Official documentation](https://docs.astral.sh/uv/) - [GitHub repository](https://github.com/astral-sh/uv) - [Migration guides](https://docs.astral.sh/uv/guides/)
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.