Menu
Screen the bundled transactions for AML red flags and draft a grounded SAR narrative. Usage /screen [--rule <name>]
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Value a public company's equity end-to-end (FCFE at CAPM cost of equity) with an IB deal team — multi-year EDGAR data, scenario forecasting, Monte-Carlo DCF, dual-source comps, a verification gate, and an investment-committee sign-off. Run `/valuation <cik|ticker>`.
Value a public company end-to-end from its CIK or ticker. Run `/valuation <cik|ticker>`. Orchestrates EDGAR fetch, three parallel valuation lanes (Monte-Carlo DCF, dual-source comparables, qualitative/risk), and reconciliation into a fair-value median + P10–P90, benchmarked against the real market price.
Generate a professional 2-page report on a publicly-traded company as a self-contained HTML website. Given a company name, orchestrates five subagents in order (Generalist, Data Retriever, Data Scientist, Financial Analyst, Report Writer) — pulling the latest 10-K from SEC EDGAR, cleaning the financials, analyzing them, and writing the report. Use when the user asks for a company report, equity write-up, or 10-K-based analysis. Triggers include "write a report on <company>", "company report for <X>", "/company-report".
One sentence on what this command does and when to invoke it. Usage /my-skill "<arg>"
Answer a question about the bundled NovaCorp filings, grounded and graded. Usage /ask "<question>"
Route a research question, gather grounded evidence, and write a cited brief. Usage /brief "<question>"
| name | screen |
| description | Screen the bundled transactions for AML red flags and draft a grounded SAR narrative. Usage /screen [--rule <name>] |
Run the full screen -> group -> draft -> review loop and save a report.
python -m tools.screen --json > reports/_flags.json
Add --rule <name> to limit to one pattern (structuring, round_number,
high_risk_jurisdiction, velocity).reports/_flags.json and group the flags by
account, listing each transaction's id, amount, date, and the rule reason.reports/_flags.json.reports/sar_<date>.md:
If no transaction fires, write "No suspicious activity detected by the configured rules." and stop — do not manufacture suspicion.
Try these to start:
/screen — screen everything; expect structuring, round-number, high-risk, and velocity flags./screen --rule structuring — isolate the smurfing pattern on ACC201./screen --rule high_risk_jurisdiction — see only the high-risk-country hits.