Skip to main content
ZICQ

Skills ZICQ category:Agent Workflows python

Python

Python development guidelines and best practices. Use when working with Python code.

344 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

Python development guidelines and best practices

When to use it

working with Python code

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Python Guidelines; Design Principles; Code Style; Type Annotations; Architecture; Dependency Injection.

File analysis

File analysis: besides SKILL.md, the body references references/uv-scripts.md, references/uv-monorepo.md. Those resources load on demand.

Python GuidelinesDesign PrinciplesCode StyleType AnnotationsArchitectureDependency InjectionModule OrganizationEnvironment VariablesData ModelsTestingStructureQuality

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
name
python
description
Python development guidelines and best practices. Use when working with Python code.
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 2
  • references/uv-scripts.md
  • references/uv-monorepo.md

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "python" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-9525794e496d1ac9-Python.html
Save it as .cursor/skills/python/SKILL.md or .claude/skills/python/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/siviter-xyz/dot-agent instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/siviter-xyz/dot-agent' --list

npx skills add 'https://github.com/siviter-xyz/dot-agent' --skill 'python'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout
--- name: python description: Python development guidelines and best practices. Use when working with Python code. --- # Python Guidelines Standards and best practices for Python development. Follow these guidelines when writing or modifying Python code. ## Design Principles Apply DRY, KISS, and SOLID consistently. Prefer functional methods where relevant; use classes for stateful behavior. Use composition with Protocol classes for interfaces rather than inheritance. Each module should have a single responsibility. Use dependency injection for class dependencies. ## Code Style - **Naming**: Descriptive yet concise names for variables, methods, and classes - **Documentation**: Docstrings for all classes, functions, enums, enum values - **Type hints**: Use consistently; avoid `Any` unless necessary - **Imports**: Avoid barrel exports in `__init__.py`; prefer blank files ## Type Annotations - Use `dict`, `list` instead of `typing.Dict`, `typing.List` - Use `str | None` instead of `Optional[str]` - Include `from __future__ import annotations` at top of files with type hints - Prefer built-in types over typing module equivalents ## Architecture ### Dependency Injection - Always inject dependencies via constructors or methods when using classes - One service class per module (interface and class models allowed in addition) - Use Protocol classes to define interfaces for dependency injection and testing ### Module Organization - Each module focuses on one concern with clear boundaries - Extract reusable methods to avoid duplication - Design for reusability across contexts ### Environment Variables - Use an `environment.py` file with individual methods per variable (e.g., `api_key()` for `API_KEY`, `database_url()` for `DATABASE_URL`) - Co-locate all environment access in one place per package for easier mocking in tests ### Data Models - Use Pydantic v2 for schemas, validation, and data models - Leverage Pydantic's type validation, serialization, and configuration management - Use Pydantic models for API request/response schemas, configuration objects, and data transfer objects ## Testing ### Structure - Tests mirror `src/` directory structure - Test methods start with `test_` - Use test class suites: for `def foo()` create `class TestFoo` - Keep names concise, omit class suite name from method - Always check for appropriate unit tests when changing code ### Quality - Use AAA (Arrange, Act, Assert) pattern - Tests should be useful, readable, concise, maintainable - Avoid tests that create massive diffs or become burdensome ### Tools - Prefer `pytest` over `unittest` - Use `pytest-mock` for mocking - Use `conftest.py` for shared fixtures - Use `tests/__test___` for shared testing code ## Implementation When implementing Python code: - Ensure code passes type checking and tests before committing - Group related changes with tests in atomic commits - Check for existing workflow patterns (spec-first, TDD, etc.) and follow them ## References - For adhoc Python scripts in uv-managed projects, see `references/uv-scripts.md`. - For monorepo-specific patterns using uv and Hatch, see `references/uv-monorepo.md`.

Related skills

Agent Workflows

Skill Creator

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that exte…

Agent Workflows

Clawdhub

Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fl…

Agent Workflows

Agent Team Orchestration

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team …

Agent Workflows

Superpowers

Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan →…