Is test-enforcement safe to install?

SaferSkills independently audited test-enforcement (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

library/methodologies/maestro/skills/test-enforcement/SKILL.md · 1 file

library/methodologies/maestro/skills/test-enforcement/SKILL.md1.1 KB · Markdown

name: test-enforcement

description: Automated test validation, coverage checking, and quality metrics with aggressive defaults

allowed-tools: [Read, Write, Edit, Bash, Grep, Glob]

Test Enforcement

Capabilities

Validates automated tests, checks coverage against thresholds, and reports quality metrics. Implements Maestro's "turn checks up to 11" philosophy with aggressive lint and test defaults.

Tool Use Instructions

Use Bash to run test suites, lint, and coverage commands
Use Read to examine test files and coverage reports
Use Grep to find untested code paths and missing test files
Use Glob to verify test file naming conventions
Use Write to generate coverage reports and test suggestions

Process Integration

Used across all Maestro processes for test verification
Used in maestro-maintenance.js (Coverage gap analysis)
Agents: Test Engineer, Coder (test writing)
Enforces: unit tests, integration tests, lint, format
Coverage thresholds configurable per project
"Turn checks up to 11" default behavior

test-enforcement— agent skill

Is test-enforcement safe to install?

Test Enforcement

Capabilities

Tool Use Instructions

Process Integration

Audit the pieces. Scan the whole. Decide.