kelly-disclosure-tracker

Manage standardized disclosure checklists for financing vehicles across entities.

4|3|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/mr-kelly/skills --skill kelly-disclosure-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kelly-disclosure-tracker
Source: https://github.com/mr-kelly/skills/tree/main/skills/kelly-disclosure-tracker
Command: npx skills add https://github.com/mr-kelly/skills --skill kelly-disclosure-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires hono, @hono/node-server, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill solves the challenge of managing complex, multi-entity disclosure checklists for financing vehicles (funds/SPVs) by providing a structured, local-first review environment that prevents data leakage and ensures consistency across origination, management, and listing roles.

Core Features & Use Cases

  • Cross-Entity Reconciliation: Automatically flags discrepancies between origination, fund-manager, and listing-venue data.
  • Reviewer Workflow: Provides a dedicated UI for marking items as verified, flagging inconsistencies, or requesting source documents with persistent notes.
  • Use Case: A compliance officer uses this to reconcile AUM figures between an offshore fund manager's statement and an exchange's listing filing, ensuring all items are ready before a vehicle's target close date.

Quick Start

Invoke the disclosure tracker by typing /kelly-disclosure-tracker and follow the prompts to seed your local batch and open the review dashboard.

Frequently Asked Questions about kelly-disclosure-tracker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reconcile disclosure checklists across multiple financing vehicle entities?

Cross-entity reconciliation for financing vehicles is handled by automatically flagging discrepancies between onshore origination, offshore fund-manager, and listing-venue data within a local-only file-backed environment. It ensures consistency across origination, management, and listing roles to prevent data leakage.

What is the best way to track reviewer decisions for SPV compliance workflows?

Reviewer decision-tracking for SPV compliance workflows is managed through a dedicated interface for marking items as verified, flagging inconsistencies, or requesting source documents with persistent notes. This standardizes the review process for fund and special purpose vehicle disclosures.

Do I need Node.js to run batch generation scripts for disclosure reconciliation?

Yes, Node.js runtime is required to execute batch generation and decision-reporting scripts for disclosure reconciliation workflows. The local-first environment relies on it to process compliance checklists and generate reviewer reports securely.

Can I use this for local compliance review of offshore fund manager and listing venue data?

Yes, local compliance review for offshore fund-manager and listing-venue data is fully supported. The system manages standardized disclosure checklists across these entities, allowing compliance officers to reconcile figures like AUM safely before a vehicle's target close date.

How does cross-entity reconciliation work for financing vehicle discrepancies?

Cross-entity reconciliation works by comparing standardized disclosure data across onshore origination, offshore fund-manager, and listing-venue entities. It automatically flags inconsistencies, such as mismatched AUM figures between fund manager statements and exchange filings.

Are there limitations to using a local-only file-backed environment for disclosure tracking?

A local-only file-backed environment for disclosure tracking prevents external data leakage but limits real-time multi-user collaboration. It is designed for secure, individual compliance review workflows rather than distributed team synchronization across entities.