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.
Scanned 5/27/2026
Install via CLI
openskills install open-gitagent/opengap---
name: document-review
description: "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."
license: proprietary
allowed-tools: search-regulations generate-report
metadata:
author: gitagent-examples
version: "1.0.0"
category: compliance
risk_tier: high
---
# Document Review
## Instructions
When reviewing a financial document:
1. **Classify the document** — Determine document type (prospectus, ADV, customer agreement, marketing material, etc.)
2. **Identify applicable rules** — Map to FINRA 2210 (communications), SEC disclosure requirements, etc.
3. **Check required elements** — Verify all required disclosures, disclaimers, and content are present
4. **Assess accuracy** — Flag potentially misleading, exaggerated, or promissory statements
5. **Check balance** — Per FINRA 2210, ensure risks and benefits are presented in a balanced manner
6. **Review formatting** — Verify required prominence of disclosures
## Key Checks
- [ ] All required disclosures present
- [ ] No misleading or exaggerated claims
- [ ] Balanced presentation of risks and benefits
- [ ] Proper disclaimers included
- [ ] Correct classification (correspondence/retail/institutional)
- [ ] Principal pre-approval status verified (if retail communication)
## Output Format
For each finding, produce:
```
### [SEVERITY] — [Rule Reference]
- **Issue**: [What was found]
- **Location**: [Section/page reference]
- **Recommended action**: [Specific fix]
```
### Example Finding
```
### WARNING — FINRA 2210(d)(1)(A)
- **Issue**: Performance claim "consistently outperforms the market" lacks supporting data and time period
- **Location**: Page 2, paragraph 3
- **Recommended action**: Add specific time period, benchmark comparison, and standardized performance data per SEC Rule 482
```
No comments yet. Be the first to comment!
Set up the Globalize CLI, create a translation project, and connect a GitHub or GitLab repository. Use this skill when the user asks to set up Globalize, install the Globalize CLI, authenticate with Globalize, or connect their project to the Globalize translation platform. Also use when the user mentions @globalize-now/cli-client or globalise-now-cli. This skill handles installation, authentication, project creation, and repository connection. For managing existing projects (glossaries, style...
Team Mode security research skill. Orchestrates 3 vulnerability hunters and 2 PoC engineers to audit a codebase in parallel, prove exploitability, classify root causes, and calibrate severity by actual exploitability. Use for security review, vulnerability research, exploitability audit, pre-release security check, threat model validation, and `/security-research`. Triggers: 'security-research', 'security research', 'security review', 'vulnerability audit', 'exploitability audit', '보안 리뷰', '취...
Java Spring Boot 服务中关于身份验证/授权、验证、CSRF、密钥、标头、速率限制和依赖安全的 Spring Security 最佳实践。
Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection.