agentleFS
TsukiNi22TsukiNi22/ai-utils/skills/routers/python/SKILL.md

python

Skill1 starsChanged 3 days agoMITView on GitHub

Router for every Python task of the user - looks at the request and the project, then loads the right Python skills (python-project, python-class, python-style, python-comments, tests, ci-cd, benchmark). Invoke manually with /python.

45 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use android-kotlin, java and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • alinaqiSkill

    android-kotlin

    Android Kotlin development with Coroutines, Jetpack Compose, Hilt, and MockK testing

    Also in 4 projects that use this

  • testdino-hqSkill

    java

    Google's official Java style guide. Covers 2-space indentation, 100-char line limit, naming conventions, braces, imports, Javadoc, exception handling, lambdas, and streams. Enforces @Override annotations and specific imports.

    Also in 6 projects that use this

  • testdino-hqSkill

    csharp

    Google's official C# style guide. Covers naming conventions, formatting, LINQ, async/await, XML documentation, and .NET best practices.

    Also in 4 projects that use this

  • ffsshhttiikkSkill

    flutter

    Flutter cross-platform framework

    Also in 4 projects that use this

  • mcollinaSkill

    node

    Provides domain-specific best practices for Node.js development with TypeScript, covering type stripping, async patterns, error handling, streams, modules, testing, performance, caching, logging, and more. Use when setting up Node.js projects with native TypeScript support, configuring type stripping (--experimental-strip-types), writing Node 22+ TypeScript without a build step, or when the user mentions 'native TypeScript in Node', 'strip types', 'Node 22 TypeScript', '.ts files without compilation', 'ts-node alternative', or needs guidance on error handling, graceful shutdown, flaky tests, profiling, or environment configuration in Node.js. Helps configure tsconfig.json for type stripping, set up package.json scripts, handle module resolution and import extensions, and apply robust patterns across the full Node.js stack.

    Also in 4 projects that use this

  • VercelSkill

    react

    React renderer for json-render that turns JSON specs into React components. Use when working with @json-render/react, building React UIs from JSON, creating component catalogs, or rendering AI-generated specs.

    Also in 7 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 41 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Do not answer from this file: decide which skills apply, load them with the Skill tool (never the other routers: they are manual-only), …

    line 15
  2. Distinctive:

    Start the answer with one line: which skills were loaded and why (ex: "Skills : python-class, python-style, python-comments (nouvelle …

    line 41

“Common” is measured: kept by at least 6 in 10 of the 41 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 router

<name> (a skill) = the folder of that skill: ~/.claude/skills/<name> (setup.sh) or ${CLAUDE_SKILL_DIR}/../../*/<name> (plugin of the marketplace).

Request given with /python: $ARGUMENTS

Do not answer from this file: decide which skills apply, load them with the Skill tool (never the other routers: they are manual-only), then do the task following them. The request is the text given with /python (or, if empty, the latest request of the user; if there is none, inspect the project and propose what can be done).

1. Look at the context (quickly, in parallel)

  • pyproject.toml (package), src/main.py + src/app.py (MAGIC application), a lone script, requirements.txt, tests/, .venv/. Empty folder = new project.
  • GitHub repository? git remote -v (github.com -> CI/CD through ci-cd).
  • Files the request is about (open them before deciding).

2. Pick the skills (several can apply, load all of them before writing)

SituationSkills
new project / package / tool / application / "setup"python-project (it loads the others it needs, ci-cd on GitHub)
new class, abstract class, tool function, module, exception, constants, test filepython-class (+ python-style, python-comments)
write / edit / refactor / fix Python codepython-style + python-comments
comments / docstrings onlypython-comments
review Python code against the user's stylepython-style + python-comments (xstyle --rtk -c PY,G first)
unit tests (pytest): setup, write, runtests
slow code, profiling, benchmarkbenchmark (py-spy / cProfile part)
CI / CD (tests, style, PyPI, release)ci-cd
commit / docs asked at the endgit-conventions / readme-style

Rules: python-class never writes function logic; the local style of an existing file wins.

3. Say it

Start the answer with one line: which skills were loaded and why (ex: "Skills : python-class, python-style, python-comments (nouvelle classe dans une application MAGIC)").

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.