How do I install the Python skill?

Run npx skillmds@latest add kissgyorgy/python in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Python skill do?

Write clean, readable Pythonic code. Use this skill any time you write or change a Python file. It is listed under Coding & Dev Tools on SkillMD.

Is Python safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Python?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Python free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Python?

kissgyorgy (@kissgyorgy) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Python by kissgyorgy — Agent Skill

Name: Python
Author: kissgyorgy

File contents

General guidelines

Coding Style

Always write clean, readable, well separated, well organized, Pythonic code.
Don't run linters or formatters, they will run automatically after every edit by the harness.
When using datetime, import it like this: import datetime as dt
CRITICAL: ALWAYS put ALL imports at the top of the file, NEVER inside functions, methods, or any other block. No exceptions. Use TYPE_CHECKING guard for type-only imports to avoid circular dependencies.

Type hints

ALWAYS type hint every function and method signature precisely even in tests.
NEVER write "-> None" type hint for return values, they are not necessary.
No need to type hint variables from functions call return values inside function bodies, they are inferred from the method return type, except extreme cases when the type is a huge help or a generic and it's concrete type cannot be determined.
Only use APIs, class names, variables or objects which you already read or know exist for sure.
Use the new pipe operator for Optional variables like this: value | None
Use Any for "all types" instead of object.

Testing

ALWAYS use pytest for all tests
ALWAYS assert on whole ouptut or full results in tests, not just tiny parts
For mocking, use pytest monkeypatch fixture, NEVER unittest.mock and NEVER any of the Mock classes or patch function
IMPORTANT: NEVER import from conftest.py
ALWAYS type hint test function parameters correctly.
Don't make a test class with only one function, a module-level test function is enough
NEVER use unittest.mock or any of the Mock classes or patch function, never assert on method calls, use real objects and assert on full results. When absolutely necessary and can't be avoided, use pytest.monkeypatch, when the test setup would be too difficult or the code have side effects, but consider writing a fake.
ALWAYS assert on the full result of the function call, never just list lengths or containment, except where that's the point.

Managing dependencies

Use uv add for adding dependencies, never directly edit pyproject.toml files.
For CLI scripts and apps, ALWAYS use click library instead of argparse, add it to dependencies if necessary.

---name: pythondescription: Write clean, readable Pythonic code. Use this skill any time you write or change a Python file.---# General guidelines# Coding Style- Always write clean, readable, well separated, well organized, Pythonic code.- Don't run linters or formatters, they will run automatically after every edit by the harness.- When using `datetime`, import it like this: `import datetime as dt`- CRITICAL: ALWAYS put ALL imports at the top of the file, NEVER inside functions, methods, or any other block. No exceptions. Use `TYPE_CHECKING` guard for type-only imports to avoid circular dependencies.# Type hints- ALWAYS type hint every function and method signature precisely even in tests.- NEVER write "-> None" type hint for return values, they are not necessary.- No need to type hint variables from functions call return values inside function bodies, they are inferred from the method return type, except extreme cases when the type is a huge help or a generic and it's concrete type cannot be determined.- Only use APIs, class names, variables or objects which you already read or know exist for sure.- Use the new pipe operator for `Optional` variables like this: `value | None`- Use `Any` for "all types" instead of `object`.# Testing- ALWAYS use `pytest` for all tests- ALWAYS assert on whole ouptut or full results in tests, not just tiny parts- For mocking, use pytest `monkeypatch` fixture, NEVER `unittest.mock` and NEVER any of the `Mock` classes or `patch` function- IMPORTANT: NEVER import from `conftest.py`- ALWAYS type hint test function parameters correctly.- Don't make a test class with only one function, a module-level test function is enough- NEVER use `unittest.mock` or any of the `Mock` classes or `patch` function, never assert on method calls, use real objects and assert on full results. When absolutely necessary and can't be avoided, use `pytest.monkeypatch`, when the test setup would be too difficult or the code have side effects, but consider writing a fake.- ALWAYS assert on the full result of the function call, never just list lengths or containment, except where that's the point.# Managing dependencies- Use `uv add` for adding dependencies, never directly edit `pyproject.toml` files.- For CLI scripts and apps, ALWAYS use `click` library instead of `argparse`, add it to dependencies if necessary.

Frequently asked questions

Python