tech-python
Skill1 starsChanged 28 days agoMITView on GitHub
Technology skill loaded when writing Python applications or scripts.
In this repository29 other files it gives its agents.
- exec-accessibilitySkill
- exec-architectureSkill
- exec-code-reviewSkill
- exec-debuggingSkill
- exec-documentationSkill
- exec-performanceSkill
- exec-refactoringSkill
- exec-repo-patternsSkill
- exec-securitySkill
- exec-testingSkill
- exec-ui-uxSkill
- exec-verificationSkill
- tech-dockerSkill
- tech-flutterSkill
- tech-goSkill
- tech-graphqlSkill
- tech-kotlinSkill
- tech-nextjsSkill
- tech-nodeSkill
- tech-postgresSkill
- tech-reactSkill
- tech-rustSkill
- tech-swiftSkill
- tech-tailwindSkill
- tech-typescriptSkill
- tech-vueSkill
- linear-spanks-gitSkill
- linear-spanksSkill
- linear-workflowSkill
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
- Distinctive: line 11
When writing Python, adhere to modern tooling and typing standards:
- Very specific: line 13
Type Hinting: Always use type hints (def process(data: list[str]) -> int:).
- Very specific: line 14
Formatting & Linting: Write code that conforms to Ruff or Black formatting standards.
- Very specific: line 15
Environment Management: Prefer modern tools like uv or Poetry for dependency management.
- Very specific: line 16
Testing: Write tests using pytest. Use fixtures for setup/teardown instead of setup_method.
- Very specific: line 17
Comprehensions: Use list/dict/set comprehensions for simple transformations, but fall back to standard for loops if the comprehension …
≈ “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.
Files
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:
- Type Hinting: Always use type hints (
def process(data: list[str]) -> int:). Usetyping.Optionalor| Noneexplicitly. - Formatting & Linting: Write code that conforms to
RufforBlackformatting standards. Avoid overly clever one-liners. - Environment Management: Prefer modern tools like
uvorPoetryfor dependency management. Never global-install packages usingpip. - Testing: Write tests using
pytest. Use fixtures for setup/teardown instead ofsetup_method. - Comprehensions: Use list/dict/set comprehensions for simple transformations, but fall back to standard
forloops if the comprehension becomes difficult to read.
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
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.

