Is diff-to-sop safe to install?

SaferSkills independently audited diff-to-sop (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.

diff-to-sop/SKILL.md · 1 file

diff-to-sop/SKILL.md1.4 KB · Markdown

name: diff-to-sop

description: Use when you want to convert a git diff into a step-by-step SOP including modified files, functions, and minimal code blocks for future integrations

Diff to SOP Skill

Overview

Transform a git diff into a short, actionable SOP. Captures files, functions, and code blocks. Enables future integrators to follow changes without reading all source code.

When to Use

After merging a new blockchain or service integration
Want a reusable SOP for future integrations
Do NOT use for generic diffs unrelated to operational steps

Core Pattern

Extract Modified Files

Identify all files with changes
List file paths in the SOP

Identify Changed Functions

Parse diff hunks to detect modified/added functions
Include function signatures in SOP

Include Minimal Code Blocks

For each modified function, include representative diff lines
Keep code blocks short but enough to understand change
Ignore *.pb.go files
Ignore Justfile files

Step-by-Step SOP Structure

Each step corresponds to a diff segment
Include:
Section title (what changed)
Files affected
Functions changed
Minimal code block

Quick Reference Template

### <Step Name>
- Files modified:
\`\`\`text
<file_path>
\`\`\`
- Functions changed:
\`\`\`<language>
<function_signature>
\`\`\`
- Diff example:
\`\`\`diff
<diff_lines>
\`\`\`

diff-to-sop— agent skill

Is diff-to-sop safe to install?

Diff to SOP Skill

Overview

When to Use

Core Pattern

Quick Reference Template

Audit the pieces. Scan the whole. Decide.