Is pr-body-formatter safe to install?

SaferSkills independently audited pr-body-formatter (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/pr-body-formatter/SKILL.md · 1 file

skills/pr-body-formatter/SKILL.md2.0 KB · Markdown

name: pr-body-formatter

description: "Generate a complete GitHub PR body with Summary, Changes, How tested, Test plan, and issue link from a branch diff plus issue reference, and never ship a placeholder body. Use for pr body template, format pr description, write a PR description, or API/CLI PR creation."

PR Body Formatter

Use this skill when opening a GitHub PR from a diff summary and issue reference. It produces a filled PR body and rejects leftover TODO-style placeholders before the PR is marked ready.

When to invoke

User says: "pr body template" / "format pr description" / "write a PR description"
Code in the conversation uses: GitHub CLI/API PR creation or a branch diff summary.

When NOT to invoke

The target repository has its own PR template; use the maintainer's template instead.
The user only wants a commit message.

Concrete example

User input:

Write the PR body for a branch that adds OIDC auth and closes acme/webapp#812.

Output:

## Summary
Adds an OIDC provider option to the auth module, closing acme/webapp#812.

## Changes
- `auth/oidc.py`: new `OIDCProvider` implementing the existing `AuthProvider` protocol
- `auth/factory.py`: register `oidc` in `PROVIDERS`
- `tests/test_oidc.py`: token exchange and error-path coverage

## How tested
- `pytest tests/test_oidc.py` - 7 passing
- Manual: ran the local auth flow against a Keycloak dev realm and verified token round-trip

## Test plan
- [ ] CI green
- [ ] Maintainer confirms OIDC config keys match docs

Closes acme/webapp#812

Pattern to apply

Inspect the diff summary and the linked issue.
Fill every section with specific file names, behavior, and test evidence.
Include the closing issue reference exactly once.
Search the body for TODO, TBD, and copied instruction text before returning it.
Refuse to emit a ready PR body if any placeholder remains.

Reference: assets/template.md.

Source

Distilled from production use across the author's automation projects. v0.1.0. See also: [[algora-bounty-scout]].

pr-body-formatter— agent skill

Is pr-body-formatter safe to install?

PR Body Formatter

When to invoke

When NOT to invoke

Concrete example

Pattern to apply

Source

Audit the pieces. Scan the whole. Decide.