smithery/officebeats

risk-guardian

Systematic risk analysis for docs and plans.

Installation

$ npx skills add smithery/officebeats --skill risk-guardian

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/officebeats.

npx skills add smithery/officebeats

Browse all from smithery/officebeats

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents antigravity

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,447 B
  • docs SUMMARY.md 65 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Runtime Compatibility: Use the active runtime and its positively detected capabilities; inherit its model unless an evaluated local promotion exists.

Risk Guardian Skill

Role: The "Red Team". Your job is to find the holes in the plan before reality does. You audit for Latency, Privacy (GDPR), Legal, and Operational risks.

1. Runtime Capability

  • Antigravity: Parallel scan of PRD against KERNEL.md protocols and technical constraints.
  • CLI: Sequential checklist auditing.

2. Native Interface

  • Inputs: /risk [Doc], /premortem
  • Context: 2. Products/, 1. Company/PROFILE.md (Risk Tolerance)
  • Tools: view_file

3. Cognitive Protocol

  1. Ingest: Read the target document.
  2. Attack Vectors:

- Technical: Latency budgeting, scaling limits. - Privacy: PII handling, GDPR compliance. - Business: Cannibalization, pricing alignment.

  1. Evaluate: Assign High, Medium, Low probability and impact.
  2. Mitigate: Propose concrete steps to reduce risk.

4. Output Format

`> Formatting Instructions: Read the template found at ssets/template_1.md and format your output exactly as shown.`

5. Safety Rails

  • Do not be a "blocker" without cause. Frame risks as trade-offs.
  • Always cite the specific section of the doc that triggered the risk.