python
Skill2 starsChanged 6 days agoMITView on GitHub
Python service implementation or review, async FastAPI/SQLAlchemy APIs, pytest tests, and ruff/pyright/mypy setup or triage. Use for backend Python tasks. Not for frontend or non-Python work. Output: compatible typed code, offline tests, API guidance, or static-check configuration with evidence.
44 other projects use a version of this.
Adopted by
Most recently taken up by
- niksavis/handilytheir own version, first seen Nov 8, 2026
- testdino-hq/google-styleguides-skillstheir own version, first seen Nov 8, 2026
- niksavis/basiclytheir own version, first seen Nov 7, 2026
- its-ash/skillstheir own version, first seen Nov 1, 2026
- shubh3794/claude-code-portabletheir own version, first seen Nov 1, 2026
- rogue-dev-studio/ai-agents-roguetheir own version, first seen Nov 1, 2026
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.
alinaqiSkillandroid-kotlin
Android Kotlin development with Coroutines, Jetpack Compose, Hilt, and MockK testing
Also in 4 projects that use this
testdino-hqSkilljava
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-hqSkillcsharp
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
ffsshhttiikkSkillflutter
Flutter cross-platform framework
Also in 4 projects that use this
mcollinaSkillnode
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
dylantarreSkillangular
Builds token-driven Angular components with signals and standalone components. Use when creating Angular component libraries, integrating design tokens, or building design system components with new control flow syntax.
Also in 3 projects that use this
- +1 more from testdino-hq
Other versions44 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 44
- alinaqi/maggy★ 711same name
- alinaqi/claude-bootstrap★ 708same name
- Mindrally/skills★ 275same name
- kid-sid/claude-spellbook★ 190same name
- hass-energy/haeo★ 77same name
- nimadorostkar/Claude-Skills-collection★ 33same name
- maroffo/claude-forge★ 17same name
- G1Joshi/Agent-Skills★ 15same name
- kissgyorgy/coding-agents★ 15same name
- testdino-hq/google-styleguides-skills★ 15same name
34 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository39 other files it gives its agents.
- AGENTS.mdAGENTS.md
- change-verdictSkill
- code-simplifySkill
- code-traceSkill
- create-prSkill
- deploy-listSkill
- doc-maintainSkill
- feature-verifySkill
- flow-driveSkill
- flow-guideSkill
- git-smart-commitSkill
- git-worktreeSkill
- harness-setupSkill
- issue-analyzeSkill
- js-static-checksSkill
- laravelSkill
- legacy-characterization-testsSkill
- library-authorSkill
- merge-prepSkill
- module-designSkill
- nextjsSkill
- openspec-artifact-guardSkill
- opsx-apply-resumeSkill
- phpSkill
- phpunitSkill
- precommitSkill
- project-auditSkill
- project-briefSkill
- proposal-analyzeSkill
- pr-summarySkill
- reactSkill
- release-creatorSkill
- repo-intakeSkill
- repo-verifySkill
- swiftSkill
- tdd-workflowSkill
- ui-ux-verifySkill
- vue-2-notesSkill
- yii1Skill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 40 edited versions we read keep these.
0
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
- Very specific: line 12
Use $python <task> to implement, review, test, or configure the scoped Python service.
“Common” is measured: kept by at least 6 in 10 of the 40 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.
Files
Python
Use $python <task> to implement, review, test, or configure the scoped Python
service. Select the required internal procedure after resolving the target.
Resolve compatibility first
Identify the target package/subproject from the request and its own
pyproject.toml, lock, and checker configuration. An intentional explicit
version override wins; record it separately from observed constraints. Read
requires-python at its actual range precision: >=3.10 establishes a 3.10
floor, while >=3.9,<3.12 does not authorize 3.10-only syntax. Lock/configuration
conflicts, missing evidence, incompatible ranges, or several plausible package
scopes require asking and waiting before version-specific reference loads or
dependent edits. python --version describes the tool environment. Migration
requires an explicit destination; group resources and evidence for multi-target
work separately. Confirm framework/library major from target lock/manifest
before framework-specific API advice (especially Pydantic1 versus2).
Select local resources
| Task | Procedure |
| Typed language/service implementation or review | language |
| ruff/pyright/mypy configuration, suppression, lint triage | static |
| Async pytest fixtures, regression tests, offline API tests | testing |
| FastAPI routes, Depends, Pydantic, SQLAlchemy2 async, Alembic design | FastAPI |
Load only the selected procedure and any other specialty actually needed for the request. The language procedure assumes Python3.10+; TaskGroup needs3.11+. For an older target, preserve its syntax floor and give a bounded compatibility answer or request an explicit upgrade decision. FastAPI examples assume Pydantic2/SQLAlchemy2; adapt only after confirming target evidence.
These are local instructions; consumer source/configuration and tool binaries
are task inputs. Missing bundled resources are BLOCKED; missing tools or
external services are NOT_RUN/UNAVAILABLE. Do not recover local resources
from a predecessor skill or an ambient module.
Authority and completion
A request to implement or configure authorizes scoped source/test/configuration edits. Review/check tasks stay read-only; auto-fix/format writes require the corresponding edit intent. Use the project's test-first workflow for behavior. Preserve the configured coverage floor and offline/live test distinction. Migration design does not authorize executing DDL or mutating a shared database. Tooling hooks mentioned by the procedures describe consumer integration; this skill does not install or require dhpk hooks to perform its task.
Return the resolved target and compatibility floor, selected procedure, implementation/findings/test plan/configuration, actual lint/type/test evidence, and residual risk. API results retain transaction/auth/error boundaries; testing results retain isolated fixtures, dependency overrides, and live opt-in markers; static results retain command/configuration/suppression evidence. Keep local tests, provider/DB execution, commit, push, and publication separate.
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.

