python-programming
Skill4 starsChanged 5 months agoMITView on GitHub
Python engineering skill for implementing, debugging, testing, packaging, typing, reviewing, and refactoring Python applications, scripts, APIs, automation, data processing, CLIs, and libraries. Use for .py files, pyproject.toml, requirements files, pytest, async Python, type hints, packaging, dependency management, and Python performance or reliability work.
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Prefer clear data flow, explicit exceptions, typed public boundaries, and narrow dependencies.
- Distinctive: line 12
Do not rewrite large modules when a targeted patch will solve the issue.
- Distinctive: line 20
Add or update focused tests with deterministic fixtures and no hidden network dependency.
- Very specific: line 21
Run formatting/type/test commands that exist in the repo and report any skipped verification.
- Very specific: line 25
Use pathlib, context managers, and structured logging where they improve clarity.
- Distinctive: line 26
Prefer dependency injection for external services and filesystem access in testable code.
- Very specific: line 27
Use asyncio deliberately; avoid mixing blocking I/O into async flows without an executor.
- Distinctive: line 28
Keep exception handling specific.
- Distinctive: line 29
Treat security-sensitive parsing, subprocess, deserialization, and templating as high-risk code.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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 Programming
Operating Rules
- Inspect project metadata, dependency manager, test framework, and style before editing.
- Prefer clear data flow, explicit exceptions, typed public boundaries, and narrow dependencies.
- Do not rewrite large modules when a targeted patch will solve the issue.
- Preserve user-visible behavior unless the task explicitly asks for a behavior change.
Workflow
- Identify runtime version, package layout, entry points, and tests.
- Reproduce or reason about the issue with the smallest relevant command.
- Implement the change using idiomatic Python and existing project conventions.
- Add or update focused tests with deterministic fixtures and no hidden network dependency.
- Run formatting/type/test commands that exist in the repo and report any skipped verification.
Python Standards
- Use
pathlib, context managers, and structured logging where they improve clarity. - Prefer dependency injection for external services and filesystem access in testable code.
- Use
asynciodeliberately; avoid mixing blocking I/O into async flows without an executor. - Keep exception handling specific; do not swallow errors unless the fallback is intentional.
- Treat security-sensitive parsing, subprocess, deserialization, and templating as high-risk code.
Other versions1 project uses a version of this.
Word for word · 1
- Garyson26/Trident-SecOps-Skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository45 other files it gives its agents.
- ai-redteamSkill
- api-security-automationSkill
- assembly-programmingSkill
- bug-bounty-workflowSkill
- claude-mythos-emulationSkill
- cloud-security-automationSkill
- cybersecurity-partnerSkill
- detection-engineeringSkill
- devsecopsSkill
- exploit-developmentSkill
- forensics-triageSkill
- gemini-tool-orchestratorSkill
- go-programmingSkill
- kubernetes-securitySkill
- malware-reverse-engineeringSkill
- multilingualSkill
- offensive-securitySkill
- prompt-enhancementSkill
- ai-redteamSkill
- api-security-automationSkill
- assembly-programmingSkill
- bug-bounty-workflowSkill
- claude-mythos-emulationSkill
- cloud-security-automationSkill
- cybersecurity-partnerSkill
- detection-engineeringSkill
- devsecopsSkill
- exploit-developmentSkill
- forensics-triageSkill
- gemini-tool-orchestratorSkill
- go-programmingSkill
- kubernetes-securitySkill
- malware-reverse-engineeringSkill
- multilingualSkill
- offensive-securitySkill
- osint-recon-automationSkill
- prompt-enhancementSkill
- purple-team-automationSkill
- python-programmingSkill
- smart-contract-auditSkill
- soc-operationsSkill
- threat-intel-fusionSkill
- smart-contract-auditSkill
- soc-operationsSkill
- threat-intel-fusionSkill
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.