Clean Pytest

v0.1.0

Write clean, maintainable pytest tests using Fake-based testing, contract testing, and dependency injection patterns. Use when setting up test suites for Pyt...

0· 755·4 current·4 all-time
byMarco Borges@marcoracer
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
The name/description (clean pytest patterns, fakes, fixtures, contract tests) matches the content of SKILL.md. The examples and fixtures are appropriate for writing tests and reference typical application imports (e.g., myapp.services.user_service).
Instruction Scope
The runtime instructions are prose and code snippets for writing tests; they don't instruct the agent to read arbitrary system files, call external endpoints, or exfiltrate data. They only reference application-level imports and creating in-memory fakes/fixtures, which is expected for a test-patterns skill.
Install Mechanism
There is no install spec and no code files to be written or executed by the platform — instruction-only skills are low-risk. No downloads or package installs are specified.
Credentials
The skill declares no env vars or credentials. SKILL.md lists python3 under required bins in its front matter, which is proportionate for a pytest-oriented skill.
Persistence & Privilege
The skill is not marked always:true and requests no persistence or cross-skill config changes. Autonomous invocation is allowed (platform default) but presents no extra risk given the skill's limited scope.
Assessment
This skill is instruction-only and appears coherent for teaching and generating pytest patterns. Before using: ensure you have python3/pytest locally if you run examples; review any examples that import your app (e.g., myapp.services.user_service) so tests don't accidentally run against production resources; confirm the skill author/owner if provenance matters (registry metadata lacked a homepage while SKILL.md references a GitHub URL). There are no environment variables or install steps requested by the skill itself, so risks are limited to normal care when running test code against your codebase (avoid embedding secrets in tests or running tests that interact with live services).

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

latestvk97852j7yc517sxb5d0a1d0kc581jya7

License

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

Comments