agentleFS
Sign inStart free
aprameyakaprameyak/coding-skills/python-quality/SKILL.md

python-quality

Skill1 starsChanged 41 days agoMITView on GitHub

Write clear, typed, idiomatic Python. Use when editing Python code, scripts, APIs, or tests.

4 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

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the repo’s formatter/linter (ruff, black, isort, mypy/pyright).

    line 10
  2. Distinctive:

    Prefer clear functions with explicit parameters over deep nesting.

    line 11
  3. Distinctive:

    Use type hints on public functions and complex internals.

    line 12
  4. Distinctive:

    Use context managers for resources.

    line 14
  5. Distinctive:

    Prefer pathlib and stdlib where enough.

    line 15
  6. Distinctive:

    Keep modules cohesive; avoid circular imports via structure, not hacks.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 Quality

Rules

  • Follow the repo’s formatter/linter (ruff, black, isort, mypy/pyright).
  • Prefer clear functions with explicit parameters over deep nesting.
  • Use type hints on public functions and complex internals.
  • Raise specific exceptions; include context in messages.
  • Use context managers for resources.
  • Prefer pathlib and stdlib where enough; add deps only when needed.
  • Keep modules cohesive; avoid circular imports via structure, not hacks.

Avoid

  • Bare except:
  • Mutable default arguments
  • Wildcard imports
  • Mixing tabs/spaces or fighting the project’s style

Checklist

  • Relevant tests pass
  • Types/lints clean for touched files
  • Scripts have clear entrypoints and exit codes

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