Is work-quick safe to install?

SaferSkills independently audited work-quick (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.

.claude/skills/work-quick/SKILL.md · 1 file

.claude/skills/work-quick/SKILL.md2.0 KB · Markdown

name: work-quick

description: Quick workflow for trivial changes (single-file fix, rename, typo). Skip the full Explore-Plan-TDD-Audit cycle. Trigger when the user wants a quick fix, a simple change, or mentions "quick", "fast", "rapid".

allowed-tools:

- Read

- Write

- Edit

- Bash

- Glob

- Grep

context: fork

model: sonnet

argument-hint: "[change description]"

Quick Fix Workflow

Quick mode for trivial changes that do not require the full cycle.

Eligibility criteria

This workflow is reserved for changes that meet ALL these criteria:

Criterion	Threshold
Files modified	1-3 maximum
Lines changed	< 50 lines
Impact	No public API change
Risk	No regression risk
Existing tests	Already pass (or no tests concerned)

Eligible examples: typo, variable rename, import fix, comment addition, CSS correction, version update.

NON eligible examples: new feature, refactoring, logic bug fix, interface change.

Workflow (3 steps)

1. SCAN - Quick check (30 seconds)

Read the target file
Identify the exact change
Verify that no existing test is impacted

2. FIX - Apply the change

Modify the file(s)
Verify the syntax (lint/typecheck if available)

3. VERIFY - Minimal validation

Run the existing tests: npm test / pytest / go test
If the tests pass: OK
If the tests fail: STOP, switch to /dev:dev-tdd

Expected output

## Quick Fix Applied

**Change**: [description]
**File(s)**: [list]
**Lines**: [+X / -Y]
**Tests**: PASS ✓

Ready for commit: `git add [files] && git commit -m "fix(scope): description"`

Guardrails

If the change exceeds the criteria → recommend /dev:dev-tdd
If the tests fail → STOP and switch to the full TDD workflow
NEVER make a public API change in quick mode
NEVER create a new file in quick mode (except a test)

IMPORTANT: This mode is a shortcut, not a workaround. When in doubt, use the full workflow.

NEVER use this mode for changes that impact business logic.

work-quick— agent skill

Is work-quick safe to install?

Quick Fix Workflow

Eligibility criteria

Workflow (3 steps)

1. SCAN - Quick check (30 seconds)

2. FIX - Apply the change

3. VERIFY - Minimal validation

Expected output

Guardrails

Audit the pieces. Scan the whole. Decide.