agentleFS
GiammeGiamme/linear-spanks/skills/extras/tech-python/SKILL.md

tech-python

Skill1 starsChanged 28 days agoMITView on GitHub

Technology skill loaded when writing Python applications or scripts.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When writing Python, adhere to modern tooling and typing standards:

    line 11
  2. Very specific:

    Type Hinting: Always use type hints (def process(data: list[str]) -> int:).

    line 13
  3. Very specific:

    Formatting & Linting: Write code that conforms to Ruff or Black formatting standards.

    line 14
  4. Very specific:

    Environment Management: Prefer modern tools like uv or Poetry for dependency management.

    line 15
  5. Very specific:

    Testing: Write tests using pytest. Use fixtures for setup/teardown instead of setup_method.

    line 16
  6. Very specific:

    Comprehensions: Use list/dict/set comprehensions for simple transformations, but fall back to standard for loops if the comprehension …

    line 17

≈ “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 Best Practices

Apply this skill after inspecting repository conventions and supported versions. Treat its rules as defaults unless they protect a concrete safety property; preserve an established project pattern when it conflicts, and record the reason in the implementation plan.

When writing Python, adhere to modern tooling and typing standards:

  1. Type Hinting: Always use type hints (def process(data: list[str]) -> int:). Use typing.Optional or | None explicitly.
  2. Formatting & Linting: Write code that conforms to Ruff or Black formatting standards. Avoid overly clever one-liners.
  3. Environment Management: Prefer modern tools like uv or Poetry for dependency management. Never global-install packages using pip.
  4. Testing: Write tests using pytest. Use fixtures for setup/teardown instead of setup_method.
  5. Comprehensions: Use list/dict/set comprehensions for simple transformations, but fall back to standard for loops if the comprehension becomes difficult to read.

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.