agentleFS
ChristopherAlphonseChristopherAlphonse/calphonse-skills/python/SKILL.md

python

Skill1 starsChanged yesterdayMITView on GitHub

Index and router for Python work. Use for any Python task: asyncio and concurrency, background jobs and task queues, code style and linting, configuration and settings, design patterns, error handling, observability (logging, metrics, tracing), packaging and publishing, profiling and performance, project structure, retries and timeouts, resource management, pytest, type hints and mypy/pyright, the uv package manager, and an anti-pattern review checklist. Picks the one sub-skill that fits and loads it on demand; nothing under this directory is read until a task needs it.

47 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 10 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

  • +1 more from testdino-hq

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 43 edited versions we read keep these.

  • 1

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

    Read one guide.md at a time.

    line 26
  2. Distinctive:

    Don't re-read a sub-skill already loaded in this session.

    line 29

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

This file is an index. The sub-skills live under references/, each at references/<name>/guide.md. Pick the row that matches the task, then read only that one guide.md.

Adapted from the MIT-licensed python-development plugin in wshobson/agents. Example URLs are replaced with placeholders such as API_ORIGIN.

Context rules (read these first)

  • The table below is enough to choose. Do not open a sub-skill to find out what it covers.
  • Open a sub-skill only when the task needs its guidance. Simple, well-known questions (a basic syntax question, a one-line explanation) don't need one.
  • Read one guide.md at a time. Read a second only if the task clearly crosses into its area.
  • A sub-skill's references/ files are off limits until that sub-skill's guide.md points you to one for the step you are on. Never list or bulk-read them.
  • Don't re-read a sub-skill already loaded in this session.

Sub-skills

Sub-skillRead when
references/async-python-patterns/guide.mdWriting asyncio code: async/await, tasks, gather, semaphores, async context managers and iterators, async APIs (FastAPI, aiohttp), mixing sync and async.
references/python-anti-patterns/guide.mdReviewing Python code against a checklist of common mistakes, or checking an implementation before finalizing it.
references/python-background-jobs/guide.mdMoving long-running or unreliable work off the request path: task queues (Celery and similar), workers, job status, idempotency, event-driven processing.
references/python-code-style/guide.mdLinting and formatting setup (ruff), naming conventions, import order, docstrings, project style standards.
references/python-configuration/guide.mdEnvironment variables, typed settings with pydantic-settings, secrets handling, per-environment behavior.
references/python-design-patterns/guide.mdDesigning or refactoring structure: KISS, separation of concerns, single responsibility, composition over inheritance, breaking up a God class, layering I/O away from business logic.
references/python-error-handling/guide.mdInput validation, exception hierarchies, fail-fast behavior, partial failure in batch work, translating errors at API boundaries.
references/python-observability/guide.mdStructured logging, metrics, distributed tracing, correlation IDs, debugging production behavior.
references/python-packaging/guide.mdBuilding a distributable library or CLI: pyproject.toml, entry points, versioning, building wheels, publishing.
references/python-performance-optimization/guide.mdSlow Python code: cProfile, line and memory profiling, finding bottlenecks, optimizing hot paths.
references/python-project-structure/guide.mdStarting a project or reorganizing one: directory layout, module boundaries, public API via __all__, import structure.
references/python-resilience/guide.mdRetries with exponential backoff, timeouts, fault-tolerant decorators, handling transient failures from external services.
references/python-resource-management/guide.mdContext managers, cleanup on error, connection and file handle lifetimes, streaming responses with accumulated state.
references/python-testing-patterns/guide.mdWriting or structuring tests with pytest: fixtures, mocking, parametrization, async tests, TDD.
references/python-type-safety/guide.mdType hints, generics, protocols, TypedDict, strict mypy or pyright configuration.
references/uv-package-manager/guide.mdUsing uv for virtual environments, dependencies, lockfiles, Python versions, scripts, and workspaces.

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.