evidence-binder

Index evidence artifacts, reconcile request lists, and track provenance for regulatory exams.

Updated May 9, 2026
One-click install
npx skills add https://github.com/anotb/second-line-financial-services --skill evidence-binder-anotb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evidence-binder
Source: https://github.com/anotb/second-line-financial-services/tree/main/plugins/capability-plugins/risk-compliance-core/skills/evidence-binder
Command: npx skills add https://github.com/anotb/second-line-financial-services --skill evidence-binder-anotb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of evidence binders for regulatory exams and audits, significantly reducing the manual effort required to compile and organize evidence.

Core Features & Use Cases

  • Evidence Indexing: Indexes evidence artifacts with detailed metadata for traceability and verification.
  • Request List Reconciliation: Ensures that all items on the request list are reconciled with available evidence.
  • Provenance Tracking: Tracks the provenance of each evidence item to ensure authenticity and reproducibility.
  • Use Case: Imagine you are preparing for a regulatory exam and need to compile a binder for the examiner's request list. This Skill can help you organize the evidence, document its provenance, and reconcile the request list.

Quick Start

Use the evidence-binder skill to create a binder for a regulatory exam with the following inputs:

  • Binder Purpose: regulator-exam
  • Engagement Scope: institution, process, period, reviewer role
  • Engagement Scope Supplied: institution, persona, source posture, sector overlay, cross-cutting overlay

Frequently Asked Questions about evidence-binder

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

FAQPage Schema
How do I automate evidence binder creation for regulatory exams and audits?

You can automate evidence binder creation by indexing artifacts, reconciling request lists, and tracking provenance. This approach reduces manual effort by organizing evidence with detailed metadata for traceability and verification during regulatory exams.

What is request list reconciliation in compliance reporting?

Request list reconciliation ensures all items on an examiner's request list are matched with available evidence. This process guarantees complete coverage of regulatory requirements and prevents missing documentation during audit reviews.

How do I track provenance for audit evidence artifacts?

Tracking provenance for audit evidence involves documenting the origin and history of each artifact. This ensures authenticity and reproducibility by maintaining detailed metadata throughout the evidence indexing process.

Can I use this for risk management and compliance reporting preparation?

Yes, this is suitable for compliance, risk management, and audit departments. It requires defining the binder purpose as regulator-exam and supplying engagement scope details like institution, process, period, and reviewer role.

What inputs do I need to start compiling an evidence binder?

To start compiling an evidence binder, you need to define the binder purpose, engagement scope, and engagement scope supplied parameters. These inputs cover institution, persona, source posture, sector overlay, and cross-cutting overlay.

Does the evidence binder process require specific configuration formats?

Yes, the evidence binder process requires SKILL.md format for skill configuration and schema.json for structured output. These formats ensure proper indexing and reconciliation of regulatory compliance artifacts.