agentleFS
BenknightdarkBenknightdark/neo-skills/skills/neo-python/SKILL.md

neo-python

Skill7 starsChanged 6 months agoMITView on GitHub

Use this skill when writing, reviewing, debugging, or architecting Python 3.10+ code, including type hints, structural pattern matching, dataclasses, async/task groups, packaging-aware project structure, testability, and maintainability.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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. Very specific:

    Write Python code with complete Type Hints, prioritizing the X | Y syntax.

    line 31
  2. Very specific:

    Prefer modern language features: match statements (3.10+), TaskGroup (3.11+), and new generic syntax (3.12+).

    line 32
  3. Distinctive:

    Ensure code passes static analysis and unit tests.

    line 33
  4. Very specific:

    PEP 8 Compliance: Follow official style guidelines.

    line 37
  5. Very specific:

    Async Processing: Use 3.11+ asyncio.TaskGroup to manage concurrent tasks.

    line 38
  6. Very specific:

    Error Handling: Use specific exception types and leverage 3.11+ ExceptionGroup and except* syntax.

    line 39
  7. Distinctive:

    All public APIs should have complete type hints.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 3.10+ Expert Skill

Trigger On

  • The user asks to write, debug, review, or refactor Python code.
  • Working in a repository containing *.py, pyproject.toml, requirements.txt, Pipfile, or poetry.lock.
  • Requires asynchronous programming (asyncio), type hinting, or modern Python feature recommendations.
  • The project needs setup for testing frameworks (pytest) or static analysis tools (ruff, mypy).

Workflow

  1. Perceive:
    • Inspect the project root to identify package management tools: pyproject.toml (Poetry/PDM/Ruff), requirements.txt (pip), or environment.yml (Conda).
    • Probe for Python version requirements (ensure compatibility with 3.10+ minimum).
    • Identify the application type: Web API (FastAPI, Flask, Django), Data Science (Pandas, PyTorch), or CLI tools.
  2. Reason:
    • Evaluate if the current code follows modern Python (3.10+) idioms (e.g., match/case, | union types).
    • Decide if type checking (MyPy/Pyright) or auto-formatting (Ruff/Black) needs to be introduced.
    • Recommend appropriate architectural patterns based on project scale.
  3. Act:
    • Write Python code with complete Type Hints, prioritizing the X | Y syntax.
    • Prefer modern language features: match statements (3.10+), TaskGroup (3.11+), and new generic syntax (3.12+).
    • Ensure code passes static analysis and unit tests.

Coding Standards

  • Type Hinting: Strongly recommended for all function signatures. Use 3.10+ union syntax like list[int | str].
  • PEP 8 Compliance: Follow official style guidelines. Recommended to use ruff as a linter and formatter for consistency.
  • Async Processing: Use 3.11+ asyncio.TaskGroup to manage concurrent tasks.
  • Error Handling: Use specific exception types and leverage 3.11+ ExceptionGroup and except* syntax.

Tooling Recommendations

  • Linter / Formatter: ruff (high performance and highly integrated).
  • Type Checker: mypy or pyright.
  • Testing: pytest with pytest-asyncio or pytest-cov.
  • Package Management: Poetry or uv to ensure dependency locking and environment consistency.

Deliver

  • Code Quality Report: Identify parts that do not comply with 3.10+ modern syntax or PEP 8.
  • Best Practice Recommendations: Provide specific refactoring suggestions, such as converting complex logic into match/case structures.
  • Validated Code: Provide Python source code accompanied by test cases and passed type checks.

Validate

  • Code must run in a Python 3.10+ environment.
  • Functions should have Docstrings (following Google or NumPy styles).
  • Complex logic should include unit tests.
  • All public APIs should have complete type hints.

Documentation

Official References

Internal References

  • Modern Python syntax evolution (3.10-3.14) and PEP 8 naming conventions
  • Recommended modern Python 3.10 - 3.14 development patterns and best practices
  • Outdated Python practices to avoid, common pitfalls, and security traps
  • Intelligent detection and management of Python project virtual environments and dependency tools

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.