How do I install the Python Style skill?

Run npx skillmds@latest add search-atlas-group/python-style 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.

Is Python Style 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 Style?

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 Style free to use?

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

Who published Python Style?

search-atlas-group (@search-atlas-group) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Python Style by search-atlas-group — Agent Skill

Name: Python Style
Author: search-atlas-group

Python Style

Python code style and tooling rules — Ruff linter on every modification, --break-system-packages flag for Homebrew Python on macOS, python-dotenv for env loading (never source .env). Use proactively when editing any .py file or installing Python packages.

File contents

python-style

Project-wide Python conventions. Auto-apply when touching any .py file.

Linting

Ruff is the linter. Run after every modification to any Python file in any project.

ruff check <path>
ruff check --fix <path>   # auto-fix safe issues
ruff format <path>        # formatter

Don't claim a Python edit complete until Ruff passes on the changed file.

Package installation (macOS Homebrew Python)

macOS Homebrew-managed Python rejects pip install without an explicit override. Use:

pip install --break-system-packages <package>

This is the team standard for macOS workstations. Do NOT recommend pipx or virtualenvs as a workaround unless the project explicitly uses them.

Environment / secrets loading

Load .env via python-dotenv. NEVER source .env.
Tokens live in per-project .env files, not a single global one. The historical "all in mb-mgmt/.env" pointer is stale — that file no longer exists at the documented path. Refer to the Credential Hygiene section in CLAUDE.md for current canonical token locations (ClickUp PAT in ~/daily-briefing/.env, Forge token embedded in ~/Sync/.git/config, etc.).
Never hardcode, never commit. See global Hard Rules in CLAUDE.md for the full secrets-handling policy.

from dotenv import load_dotenv
load_dotenv()  # loads from the project's local .env
import os
api_key = os.environ["SOME_API_KEY"]

Coding discipline (carries over from global CLAUDE.md)

Surface ambiguity before coding. Multiple interpretations → present them, don't pick silently.
Goal-driven execution. "fix the bug" → "write a test that reproduces it, then make it pass."
Clean up only YOUR orphans. Remove imports/vars/functions your changes made unused. Don't touch pre-existing dead code unless asked.

---name: python-styledescription: Python code style and tooling rules — Ruff linter on every modification, --break-system-packages flag for Homebrew Python on macOS, python-dotenv for env loading (never source .env). Use proactively when editing any .py file or installing Python packages.---# python-styleProject-wide Python conventions. Auto-apply when touching any `.py` file.## Linting**Ruff is the linter.** Run after every modification to any Python file in any project.```bashruff check <path>ruff check --fix <path> # auto-fix safe issuesruff format <path> # formatter```Don't claim a Python edit complete until Ruff passes on the changed file.## Package installation (macOS Homebrew Python)macOS Homebrew-managed Python rejects `pip install` without an explicit override. Use:```bashpip install --break-system-packages <package>```This is the team standard for macOS workstations. Do NOT recommend `pipx` or virtualenvs as a workaround unless the project explicitly uses them.## Environment / secrets loading- Load `.env` via `python-dotenv`. NEVER `source .env`.- Tokens live in **per-project `.env` files**, not a single global one. The historical "all in `mb-mgmt/.env`" pointer is **stale** — that file no longer exists at the documented path. Refer to the `Credential Hygiene` section in CLAUDE.md for current canonical token locations (ClickUp PAT in `~/daily-briefing/.env`, Forge token embedded in `~/Sync/.git/config`, etc.).- Never hardcode, never commit. See global Hard Rules in CLAUDE.md for the full secrets-handling policy.```pythonfrom dotenv import load_dotenvload_dotenv() # loads from the project's local .envimport osapi_key = os.environ["SOME_API_KEY"]```## Coding discipline (carries over from global CLAUDE.md)- **Surface ambiguity before coding.** Multiple interpretations → present them, don't pick silently.- **Goal-driven execution.** "fix the bug" → "write a test that reproduces it, then make it pass."- **Clean up only YOUR orphans.** Remove imports/vars/functions your changes made unused. Don't touch pre-existing dead code unless asked.

Frequently asked questions