Install
$ agentstack add skill-m-binimran-finance-pack-risk-assessment ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
risk-assessment
Name the real risks, size them, and say what changes the picture - not a generic disclaimer list.
Process
- Enumerate by category: market/competitive, financial (leverage, liquidity, FX, rates), operational,
regulatory/legal, key-person, customer/supplier concentration, technology, macro.
- Likelihood x impact for each (and time horizon) - prioritize the ones that are both probable and severe.
- Quantify where possible (e.g. "a 200bps rate rise adds $Xm interest"; "top-customer loss = Y% of revenue").
- Mitigants & monitors: what reduces each risk and the early-warning metric to watch.
- Tie to the thesis: which risks would actually break it (
scenario-analysisbear case).
Output
- A prioritized risk register: risk -> likelihood/impact -> quantified exposure -> mitigant -> monitor, plus the
2-3 thesis-breakers.
Guardrails
- Quantify, don't just list (
analysis-objectivity); exposure figures sourced where used. - Be honest about the downside; don't bury risks to support a conclusion.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: m-binimran
- Source: m-binimran/finance-pack
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.