Nm Parseltongue Python Testing

v1.0.0

Python testing patterns: pytest setup, fixtures, TDD, mocking, async tests, and integration tests

0· 34·1 current·1 all-time
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 (pytest, fixtures, async tests, TDD) match the SKILL.md and module contents. All suggested commands and files (pyproject.toml, pytest, pytest-asyncio, pytest-mock, CI workflows) are appropriate for a testing guidance skill.
Instruction Scope
Runtime instructions are limited to installing test/dev dependencies, configuring pytest/coverage, running pytest, and CI/workflow examples. There are no instructions to read unrelated system files, access secrets, or transmit data to external endpoints beyond standard CI/actions (e.g., actions/checkout, codecov).
Install Mechanism
This is an instruction-only skill (no install spec, no archives, no third-party download). It recommends pip-installing well-known pytest-related packages, which is proportionate and expected for this content.
Credentials
The skill declares no required environment variables, credentials, or config paths. The instructions reference only typical project files (pyproject.toml, tests/, conftest.py) and CI steps; no unexpected secrets or unrelated service credentials are requested.
Persistence & Privilege
always:false and no install actions means the skill will not persist or modify other skills. Model invocation is allowed by default (disable-model-invocation:false), which is normal; this alone is not a security concern given the skill's narrow scope.
Assessment
This skill is a documentation-style testing guide and appears coherent. Before using: (1) review any pip commands and add dependencies to your project in a controlled way (prefer a venv or CI), (2) inspect and approve the suggested CI workflow before adding it to your repository (to avoid unintended uploads of build artifacts or coverage reports), and (3) treat the skill like documentation — it gives commands to run locally that you should verify in your environment. There are no requested credentials or hidden network endpoints in the provided files.

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

latestvk97afwdfqnbnr76q7939caqrbn84vh2z

License

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

Runtime requirements

🧪 Clawdis

Comments