Validation test runner for MOOLLM skills. **Status: DESIGN** — harness and per-skill config to be implemented. - **Runner:** Discovers skills with `test.yml` or `.skill-test.yml`; runs entrypoint (pytest or script); passes env; reports pass/fail and drift. - **Per-skill:** Each skill declares entrypoint, runner type, env, marks. Tests can live inside the skill (e.g. `cursor-mirror/tests/`). - **Relation:** skill-snitch = audit/security; skill-test = validation/regression. Both use cursor-mirr...
Pro scans all 7 files and shows the line behind each finding
Scanned 10/6/2026
Skills Directorynpx -y skills add SimHacker/moollm --skill skill-test --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Skill Test?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/simhacker-skill-test)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
# skill-test
Validation test runner for MOOLLM skills. **Status: DESIGN** — harness and per-skill config to be implemented.
- **Runner:** Discovers skills with `test.yml` or `.skill-test.yml`; runs entrypoint (pytest or script); passes env; reports pass/fail and drift.
- **Per-skill:** Each skill declares entrypoint, runner type, env, marks. Tests can live inside the skill (e.g. `cursor-mirror/tests/`).
- **Relation:** skill-snitch = audit/security; skill-test = validation/regression. Both use cursor-mirror for observability.
Design docs (k-lines, source-grouped) live in **designs/**:
| K-line | Path | Content / source |
|--------|------|-------------------|
| RUNNER-DESIGN | designs/runner/RUNNER-DESIGN.md | Harness, config schema, placement, relation to snitch/mirror |
| CURSOR-MIRROR-VALIDATION-SUITE | designs/cursor-mirror/VALIDATION-SUITE.md | What to validate for cursor-mirror; layers; example config; pipeline hook |
See **designs/README.md** for full index.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
