← ClaudeAtlas

kelly-disclosure-trackerlisted

Cross-Entity Disclosure Tracker App-in-Skill — a local review workspace that helps a compliance/IR team assemble and track a standardized disclosure package per financing vehicle (fund/SPV), across a generic onshore origination entity, an offshore fund-manager entity, and a listing/exchange venue. Use when the user invokes $kelly-disclosure-tracker or /kelly-disclosure-tracker, wants to review disclosure checklists, vehicle readiness, cross-entity reconciliation flags, or reviewer notes across multiple financing vehicles. Local review workspace only — it never files anything or calls any external system.
mr-kelly/skills · ★ 3 · AI & Automation · score 74
Install: claude install-skill mr-kelly/skills
# Cross-Entity Disclosure Tracker ## Overview Use this skill as a local, file-backed App-in-Skill workspace for a compliance/IR team assembling a standardized disclosure package per financing vehicle (fund or SPV). Each vehicle's package spans three generic entity roles: - **Origination entity** — the onshore entity that originates/services the underlying assets. - **Fund-manager entity** — the offshore entity that manages the vehicle. - **Listing venue** — the exchange/listing venue where the vehicle's notes or units are listed. This is a **generic, brand-free** tool: no real company, regulator, or exchange is referenced anywhere in the skill, its data, or its UI. All vehicle and entity names in seed data are synthetic placeholders ("SPV Alpha 12", "Onshore Originator A", "Exchange One", and so on). Default interaction mode: App UI. Unless the user explicitly asks for chat-only handling, check onboarding/config, generate or refresh the local batch with `scripts/generate_batch.ts`, start/reuse the local app with `app/start.sh`, and give the actual local URL. Use chat-only mode only when the user says "纯聊天", "chat only", "不要打开 UI", or similar. This is a **workspace/review-queue hybrid**: the human works through a checklist per vehicle rather than approving a linear queue, but the underlying mechanics (statuses, decisions, a local file handoff) follow the same App-in-Skill review model. ## App UI Screenshots <table> <tr> <td width="50%"><img src="assets/screen