⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
document-review
Reviews financial documents (prospectuses, ADVs, marketing materials) for FINRA 2210 compliance, required disclosures, and balanced presentation. Use when reviewing financial statements, audit documents, regulatory filings, or when the user mentions compliance checks, financial audits, or document verification.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
OpenGAP | your repository becomes your agent
opengap— the OpenGAP CLI, published as@open-gitagent/opengap. Previously published as@open-gitagent/gapmanand originally@open-gitagent/gitagent; thegitagentcommand is still installed as an alias for backward compatibility.
OpenGAP (the Git Agent Protocol) is a framework-agnostic, git-native standard for defining AI agents. Clone a repo, get an agent. opengap is its reference CLI.
Why
Every AI framework has its own structure. There's no universal, portable way to define an agent that works across Claude Code, OpenAI, LangChain, CrewAI, and AutoGen. gitagent fixes that.
- Git-native — Version control, branching, diffing, and collaboration built in
- Framework-agnostic — Export to any framework with adapters
- Compliance-ready — First-class support for FINRA, Federal Reserve, SEC, and segregation of duties
- Composable — Agents can extend, depend on, and delegate to other agents
The Standard
Your repository becomes your agent. Drop these files into any git repo and it becomes a portable, framework-agnostic agent definition — everything else (CLI, adapters, patterns) builds on top of it.
my-agent/
│
│ # ── Core Identity (required) ──────────────────────────
├── agent.yaml # Manifest — name, version, model, skills, tools, compliance
├── SOUL.md # Identity, personality, communication style, values
│
│ # ── Behavior & Rules ──────────────────────────────────
├── RULES.md # Hard constraints, must-always/must-never, safety boundaries
├── DUTIES.md # Segregation of duties policy and role boundaries
├── AGENTS.md # Framework-agnostic fallback instructions
│
│ # ── Capabilities ──────────────────────────────────────
├── skills/ # Reusable capability modules (SKILL.md + scripts)
│ └── code-review/
│ ├── SKILL.md
│ └── review.sh
├── tools/ # MCP-compatible tool definitions (YAML schemas)
├── workflows/ # Multi-step procedures/playbooks
│
│ # ── Knowledge & Memory ────────────────────────────────
├── knowledge/ # Reference documents the agent can consult
├── memory/ # Persistent cross-session memory
│ └── runtime/ # Live agent state (dailylog.md, context.md)
│
│ # ── Lifecycle & Ops ───────────────────────────────────
├── hooks/ # Lifecycle event handlers (bootstrap.md, teardown.md)
├── config/ # Environment-specific overrides
├── compliance/ # Regulatory compliance artifacts
│
│ # ── Composition ───────────────────────────────────────
├── agents/ # Sub-agent definitions (recursive structure)
│ └── fact-checker/
│ ├── agent.yaml
│ ├── SOUL.md
│ └── DUTIES.md # This agent's role, permissions, boundaries
├── examples/ # Calibration interactions (few-shot)
│
│ # ── Runtime ───────────────────────────────────────────
└── .gitagent/ # Runtime state (gitignored)
Only two files are required: agent.yaml (the manifest) and SOUL.md (the identity). Everything else is optional — add what you need, ignore the rest.
Patterns
These are the architectural patterns that emerge when you define agents as git-native file systems.
Human-in-the-Loop for RL Agents
When an agent learns a new skill or writes to memory, it opens a branch + PR for human review before merging.
Segregation of Duties (SOD)
No single agent should control a critical process end-to-end. Define roles (maker, checker, executor, auditor), a conflict matrix (which roles can't be the same agent), and handoff workflows — all in agent.yaml + DUTIES.md. The validator catches violations before deployment.
compliance:
segregation_of_duties:
roles:
- id: maker
description: Creates proposals
permissions: [create, submit]
- id: checker
description: Reviews and approves
permissions: [review, approve, reject]
conflicts:
- [maker, checker] # maker cannot approve own work
assignments:
loan-originator: [maker]
credit-reviewer: [checker]
handoffs:
- action: credit_decision
required_roles: [maker, checker]
approval_required: true
enforcement: strict
Live Agent Memory
The memory/ folder holds a runtime/ subfolder where agents write live knowledge — dailylog.md, key-decisions.md, and context.md — persisting state across sessions.
Agent Versioning
Every change to your agent is a git commit. Roll back broken prompts, revert bad skills, and explore past versions — full undo history for your agent.
Shared Context & Skills via Monorepo
Root-level context.md, skills/, tools/ are automatically shared across every agent in the monorepo. No duplication, one source of truth.
Branch-based Deployment
Use git branches (dev → staging → main) to promote agent changes through environments, just like shipping software.
Knowledge Tree
The knowledge/ folder stores entity relationships as a hierarchical tree with embeddings, letting agents reason over structured data at runtime.
Agent Forking & Remixing
Fork any public agent repo, customize its SOUL.md, add your own skills, and PR improvements back upstream — open-source collaboration for AI agents.
CI/CD for Agents
Run opengap validate on every push via GitHub Actions. Test agent behavior in CI, block bad merges, and auto-deploy — treat agent quality like code quality.
Agent Diff & Audit Trail
git diff shows exactly what changed between agent versions. git blame traces every line to who wrote it and when — full traceability out of the box.
Tagged Releases
Tag stable agent versions like v1.1.0. Pin production to a tag, canary new versions on staging, and roll back instantly if something breaks.
Secret Management via .gitignore
Agent tools that need API keys read from a local .env file — kept out of version control via .gitignore. Agent config is shareable, secrets stay local.
Agent Lifecycle with Hooks
Define bootstrap.md and teardown.md in the hooks/ folder to control what an agent does on sta
// HOW IT'S BUILT
KEY FILES