Python Code Review

v1.1.0

Reviews Python code for type safety, async patterns, error handling, and common mistakes. Use when reviewing .py files, checking type hints, async/await usag...

0· 128·1 current·1 all-time
byKevin Anderson@anderskev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name, description, and included reference documents all align with a Python review tool. The skill requests no binaries, env vars, or credentials, which is appropriate for an instruction-only linter/review guide.
!
Instruction Scope
SKILL.md and the included reference files stay within the scope of code review. One instruction asks the agent to load '../review-verification-protocol/SKILL.md' before reporting findings; that file is not present in the bundle and the relative path points outside the skill directory, which could cause the agent to attempt to read parent-level files or repository content. This is likely an oversight but worth confirming.
Install Mechanism
No install spec or code files are included; instruction-only skills are low-risk because they do not write code to disk or download external artifacts.
Credentials
The skill requires no environment variables, credentials, or config paths. All referenced content are static text files relevant to Python review, so requested access is proportionate.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request elevated or persistent privileges. Autonomous invocation is enabled (platform default) but this is expected for skills and not, by itself, a concern.
Assessment
This appears to be a straightforward, instruction-only Python code-review skill. Before installing, verify the referenced '../review-verification-protocol/SKILL.md' exists (or ask the author why the skill points outside its bundle). Confirm your agent is restricted from reading arbitrary files in parent directories or repos if you don't want it accessing other project files. If you proceed, test the skill on non-sensitive example code first to ensure it behaves as expected.

Like a lobster shell, security has layers — review code before you run it.

latestvk976kcqbaw13qwt4f3e7pbdn3583c2a4

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments