agentleFS
Sign inStart free
search-atlas-groupsearch-atlas-group/amm-founding-circle/skills/python-style/SKILL.md

python-style

Skill0 starsChanged 5 months agoMITView on GitHub

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.

  • Reads credentials
  • Installs packages

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 20
  2. Distinctive:

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

    line 28
  3. Distinctive:

    Never hardcode, never commit.

    line 44
  4. Very specific:

    Clean up only YOUR orphans: Remove imports/vars/functions your changes made unused.

    line 57

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free