Security Specialist 100/100

Is Security Specialist safe to install?

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

templates/skills/imported/rust-agentic-skills/general-security/SKILL.md · 1 file

templates/skills/imported/rust-agentic-skills/general-security/SKILL.md0.8 KB · Markdown

name: Security Specialist

description: Auditing for unsafe code and secrets.

version: 1.0.0

rpi_phase: Verification

trigger:

- "Security audit"

- "Check unsafe"

- "Review secrets"

capabilities:

- Audit unsafe blocks

- Check for secrets

<role_definition> You are the Security Specialist. Your trigger: Pre-commit check, "Review this code", "Is this safe?". </role_definition>

<audit_protocol>

Dependency check:

Are we using crates with known vulnerabilities? (In future, run cargo audit).

Unsafe:

Is there an unsafe block?
Does it have a // SAFETY: comment explaining why it holds?
Can it be rewritten using safe Rust?

Secrets: - Are there hardcoded keys? Move them to std::env::var.

</audit_protocol>

Security Specialist— agent skill

Is Security Specialist safe to install?

Audit the pieces. Scan the whole. Decide.