Test Runner

v1.0.0

Write, run, and manage unit, integration, and E2E tests across TypeScript, Python, and Swift using recommended frameworks.

12· 11k·99 current·103 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
The SKILL.md content is a test-runner guide (commands for Vitest, Jest, pytest, XCTest, Playwright, coverage, and testing patterns). There are no unrelated credential or binary requirements declared, and the instructions match the stated purpose.
Instruction Scope
Instructions remain within the domain of writing and running tests (installing test deps, running test commands, viewing coverage). Minor issues: a typo appears ('uv pip install pytest...' instead of 'pip install ...' or 'python -m pip install ...') and a few example assertions/APIs may not exactly match specific framework APIs — these are correctness/usability issues, not scope creep. No instructions read or exfiltrate system files, environment variables, or external endpoints beyond standard package installers and test runners (Playwright will download browsers as expected).
Install Mechanism
No install spec is present (instruction-only). Commands in SKILL.md use package managers (npm/npx, pip, swift) — expected for a test-runner guide. Nothing instructs downloading arbitrary archives from unknown hosts.
Credentials
The skill declares no required environment variables, credentials, or config paths. The instructions do not request secrets or unrelated credentials.
Persistence & Privilege
always is false and the skill does not request persistent system privileges or attempt to modify other skills or global agent configuration.
Assessment
This skill is a plain testing guide and appears coherent and low-risk. Before running commands from the file: (1) fix the obvious typos (e.g., 'uv pip install...' likely should be a normal pip install invocation), (2) verify package install commands against your project's package manager and lockfiles, and (3) run commands in a controlled/dev environment (or CI) if you want to avoid unintentionally installing dependencies or downloading browsers (Playwright). If you need automated or networked behavior beyond local test runs, inspect or request code that performs that functionality before giving the skill broader privileges.

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

latestvk979r2ht2qsd76z20x941r301x802p52

License

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

Comments