skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
sprngr/rubber-duck58 installs

duck-risk

Adversarial risk review: failure modes, rollback safety, compatibility, trust-boundary misuse. Use when: "stress test this", "what could break", "rollback risk", "compatibility risk".

How do I install this agent skill?

npx skills add https://github.com/sprngr/rubber-duck --skill duck-risk
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill is a diagnostic tool designed to perform risk and security reviews of proposed code changes or system architectures. It operates purely through text analysis and does not contain any executable scripts, network operations, or file system modifications. It includes robust safety guardrails that emphasize user decision ownership and prevent unauthorized actions.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Risk review 🦆. Break it before users do.

Purpose

Identify highest-impact correctness/reliability/security-adjacent risks and smallest safe mitigations.

Philosophy Guardrails (skill-local)

Inherit shared guardrails from references/GUARDRAILS.md.

Skill-specific delta:

  • Risk findings and mitigations only; merge/approval decisions remain with user.

Activation

Use for adversarial review of proposal/change scope.

Method

1. Clarify scope (if missing)

  • ask 1-3 targeted clarifying questions when context is incomplete
  • state assumptions explicitly when evidence is missing

Required:

  • proposal/change scope or runtime path

Optional:

  • threat model
  • rollback constraints
  • compatibility constraints

If threat model/scope is missing, ask one targeted clarifying question.

2. Review for risk

  1. Inspect trust boundaries and failure classes first.
  2. Prioritize: security/correctness -> data integrity -> rollback/compat.
  3. Emit max 3 highest-impact findings.
  4. Include explicit Impact + Rollback in every finding.
  5. Prefer smallest safe mitigation.
  6. If uncertain assumptions, state assumption in one line and downgrade confidence.

3. Output findings

One line per finding:

<prefix> <path[:line|scope]> — <failure mode>. Impact: <user/data/scope>. Rollback: <blast radius + revert path>. Fix: <smallest safe mitigation>.

Prefixes:

  • 🔴 bug: correctness/security/data-loss
  • 🟡 risk: reliability/compat/rollback gap
  • ❓ question: missing context blocks judgment

Final line:

totals: <n> findings, <n> questions. coverage: trust-boundary=<checked|partial|missing>; rollback=<checked|partial|missing>.

Boundaries

  • No style/naming nits.
  • No simplification/duplication ownership (duck-simplify).
  • No final PR-thread formatting ownership (duck-review).

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/sprngr/rubber-duck/duck-risk">View duck-risk on skillZs</a>