Skill Test
v1.0.0Test skills before using or publishing. Trial, compare, evaluate in isolation without affecting your environment.
⭐ 2· 1.9k·13 current·15 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the contents: the SKILL.md and auxiliary docs describe workflows for testing, comparing, and evaluating other skills. There are no unrelated env vars, binaries, or install steps requested.
Instruction Scope
Instructions focus on spawning isolated sub-agents and reviewing SKILL.md and auxiliary files. This stays in-scope, but the doc advises loading 'skill content' into sub-agents and optionally asking for test credentials — that is expected for a tester but could expose secrets if the tester or platform isn't careful.
Install Mechanism
No install spec or code files are provided, so nothing is written to disk by the skill itself. The docs mention using npx clawhub install as a testing convenience; that is an external CLI operation under the user's control, not part of the skill payload.
Credentials
The skill requests no environment variables or credentials. It does advise asking the user for test credentials if a skill requires them — this is reasonable for testing, but users should prefer ephemeral/test-only credentials and avoid pasting production secrets into a test run.
Persistence & Privilege
Flags are default (always: false, model invocation allowed). The skill does not request persistent presence or attempt to modify other skills or system-wide settings.
Assessment
This skill is a tester/checklist and appears coherent — it doesn't request credentials or install code itself. Before using: (1) verify your platform truly isolates sub-agents (so tests can't access your real files/env), (2) never paste production credentials into a test; use ephemeral/test accounts, (3) inspect auxiliary files (compare.md, evaluate.md, sandbox.md) yourself before running automated tests, and (4) if you run commands like 'npx clawhub install', ensure you trust the source of that tool. If you need higher assurance, run tests in a separate VM or container and remove the test folder after completion.Like a lobster shell, security has layers — review code before you run it.
latestvk979wvzmarja98dwkwz0j9yags80y867
License
MIT-0
Free to use, modify, and redistribute. No attribution required.