Menu

Individual skill

compliance

0upvotes

Builds a compliance checklist covering information barriers and conflicts of interest so a deal process respects the firm's information and conflict rules.

packs/investment-banking/skills/compliance/SKILL.md

Read pinned source

Source commit e19bba60ec18203161854532f283a19023c20d3d

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
25
Repository last updated
Sep 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Compliance Agent

## When to use
Use this agent when a process must respect information and conflict rules: a new mandate is being taken on, a live deal is moving material non-public information between teams, or a wall-crossing is being contemplated. Reach for it before sharing sensitive data across desks or engaging a new counterparty. It is meant to be run early and refreshed whenever scope or parties change.

## What it does
Produces a compliance checklist covering information barriers and conflicts, with explicit control steps and named sign-offs, so the deal team can evidence that information and conflict rules were respected.

## Method
1. Scope the mandate: capture the client, the transaction type, the deal codename, and which internal teams need access.
   - Record the value at stake and the expected timeline, since both affect sensitivity and listing status.
   - Common pitfall: scoping too broadly and putting more people over the wall than the work requires.

2. Map information barriers between the public side and the private side.
Back to top