Is proceed safe to install?

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

skills/proceed/SKILL.md · 1 file

skills/proceed/SKILL.md1.9 KB · Markdown

name: proceed

description: Execute an implementation plan with surgical precision. Use after a planning phase (plan-now or similar) has produced a step-by-step strategy and identified critical files. Focuses on precise code changes with verification at each step.

Proceed Command

Execute the provided implementation plan with surgical precision.

CRITICAL: This is an EXECUTION task. Implement changes exactly as specified in the plan.

Process

Review the Plan: Analyze the provided implementation plan and critical files. Understand the architectural decisions and sequence of operations before writing any code.

Execute Surgically:

Implement changes step-by-step as outlined in the plan.
Use ast-grep (preferred) or the Edit tool for code transformations.
Follow the Find -> Transform -> Verify workflow.
Complete each task in the plan sequentially. Batch independent operations where possible, but never batch dependent ones.

Verify After Each Step:

After each file modification, use difft to inspect changes and ensure no unintended modifications.
If the project has build/lint/test commands available, run them to catch regressions early.
If verification fails, debug and fix before proceeding to the next step.

Finalize:

Run available build/lint/test commands for final verification.
VCS operations (commits, branch management) only if the user explicitly requests them or the plan specifies them.

Required Output

End your response with:

Implementation Summary

[File path] - [Status: e.g., "Implemented & Verified"]
[File path] - [Status: e.g., "Updated & Tested"]

Verification Results

Build: [pass/fail/not available]
Lint: [pass/fail/not available]
Tests: [pass/fail/not available]

Remember: Execute the plan precisely. Follow existing patterns. Verify every change.

proceed— agent skill

Is proceed safe to install?

Proceed Command

Process

Required Output

Implementation Summary

Verification Results

Audit the pieces. Scan the whole. Decide.