Skip to content
Back to skills

Python Conventions

ASecurity

Conventions for python code. Load before writing or editing any Python in this repository.

  • 9 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 12, 2026
developmentpythonexpress

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add kpenev/AutoWISP --skill python-conventions --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Python Conventions?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Python Conventions
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/kpenev-python-conventions/badge)](https://www.skillsdirectory.com/skills/kpenev-python-conventions)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: python-conventions
description: Conventions for python code. Load before writing or editing any Python in this repository.
---
# Python Conventions

- Use snake_case for variable and function names

- Use CamelCase for class names

- Avoid single letter variables except when really obvious (e.g. x, y, ...)

- Avoid variable names that differ only by a single letter e.g. (positon and
  positions)

- Keep a value local to its only user; a module-level constant is for
  something shared.

- Before writing a helper, a checker or a test fixture, look for an existing
  one to reuse or generalize: a near-copy of something already there is two
  things to keep in step. E.g. a test needing cameras generalized the
  fixture's own `_add_camera` rather than adding its own, and the
  configuration page's rule warnings reuse the expression library's.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.