sec-edgar-pipeline — Claude Code skill: what it does, how to install
Configures the edgar-analyzer CLI to fetch SEC EDGAR filings by CIK, generate extraction code, and export compensation tables to CSV.
npx skills add bobmatnyc/claude-mpm-skills --skill sec-edgar-pipeline -a claude-codeWhat sec-edgar-pipeline does
The skill coordinates financial filing data retrieval using edgar-analyzer. It covers setting up projects with minimal templates, analyzing sample filings, generating custom parsing logic, and saving structured results to projects/<name>/output/.
SEC access fails immediately without a custom user agent containing an email address. The extraction generator also relies on OPENROUTER_API_KEY, while JINA_API_KEY remains optional. Built-in routines insert roughly 0.11-second delays between calls to avoid exceeding the SEC limit of 10 requests per second.
Prebuilt recipes focus on proxy statements like DEF 14A. The pipeline extracts executive compensation details through SCTAdapter, verifies them with sct_validator, and writes CSV reports covering company summaries and top executive pay figures.
What it helps with
- fetch corporate DEF 14A filings using 10-digit zero-padded CIK numbers
- generate extraction code for Summary Compensation Tables
- export parsed filing data into structured CSV and JSON summaries
- enforce the 10 requests per second SEC API rate limit
Example prompts for the agent
- Run edgar-analyzer setup with my SEC user agent and OpenRouter key
- Create an edgar-analyzer project to extract SCT tables from DEF 14A filings
- Generate extraction code and run the pipeline with CSV output
How to install sec-edgar-pipeline
1Skills CLI (Vercel)
npx skills add bobmatnyc/claude-mpm-skills --skill sec-edgar-pipeline -a claude-code2Manually: put the files in place
~/.claude/skills/sec-edgar-pipeline/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/sec-edgar-pipeline/
1Skills CLI (Vercel)
npx skills add bobmatnyc/claude-mpm-skills --skill sec-edgar-pipeline -a codex2Manually: put the files in place
.agents/skills/sec-edgar-pipeline/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add bobmatnyc/claude-mpm-skills --skill sec-edgar-pipeline -a cursor2Manually: put the files in place
.cursor/skills/sec-edgar-pipeline/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install bobmatnyc/claude-mpm-skills sec-edgar-pipeline2Manually: put the files in place
.github/skills/sec-edgar-pipeline/SKILL.md1Skills CLI (Vercel)
npx skills add bobmatnyc/claude-mpm-skills --skill sec-edgar-pipeline -a gemini-cli2Platform CLI
gemini skills install https://github.com/bobmatnyc/claude-mpm-skills --path universal/data/sec-edgar-pipelineManually: put the files in place
.devin/skills/sec-edgar-pipeline/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add bobmatnyc/claude-mpm-skills --skill sec-edgar-pipeline -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about sec-edgar-pipeline
How to install sec-edgar-pipeline in Claude Code?
Run npx skills add bobmatnyc/claude-mpm-skills --skill sec-edgar-pipeline -a claude-code in your terminal.
What does sec-edgar-pipeline do?
It guides the CLI workflow for downloading SEC EDGAR filings, synthesizing parsing code, and compiling executive pay reports.
What configuration is needed to run the pipeline?
You need an OPENROUTER_API_KEY and an SEC user-agent string formatted with your name and email.
Source text
SKILL.md · MIT
---
name: sec-edgar-pipeline
description: "SEC EDGAR extraction pipeline: setup, filing discovery by CIK, recipe-driven extraction, and report generation."
user-invocable: false
disable-model-invocation: true
version: 1.0.0
category: universal
author: Claude MPM Team
license: MIT
progressive_disclosure:
entry_point:
summary: "EDGAR pipeline: configure keys + user-agent, find filings by CIK, extract data via recipes/scripts, and export CSV/JSON reports."
when_to_use: "Building SEC EDGAR extraction flows, running edgar-analyzer CLI, or generating compensation/filing reports from DEF 14A and related filings."
quick_start: "1. edgar-analyzer setup 2. edgar-analyzer analyze-project projects/<name> 3. edgar-analyzer generate-code 4. edgar-analyzer run-extraction"
tags:
- sec
- edgar
- filings
- cik
- def14a
- extraction
---
# SEC EDGAR Pipeline
## Overview
This pipeline is centered on `edgar-analyzer` and the EDGAR data sources. The core loop is: configure credentials, create a project with examples, analyze patterns, generate code, run extraction, and export reports.
## Setup (Keys + User Agent)
Use the setup wizard to configure required keys:
```bash
python -m edgar_analyzer setup
# or
edgar-analyzer setup
```
Required entries:
- `OPENROUTER_API_KEY`
- (Optional) `JINA_API_KEY`
- `EDGAR` user agent string ("Name [email protected]")
## End-to-End CLI Workflow
```bash
# 1. Create project
edgar-analyzer project create my_project --template minimal
# 2. Add examples + project.yaml
# projects/my_project/examples/*.json
# 3. Analyze examples
edgar-analyzer analyze-project projects/my_project
# 4. Generate extraction code
edgar-analyzer generate-code projects/my_project
# 5. Run extraction
edgar-analyzer run-extraction projects/my_project --output-format csv
```
Outputs land in `projects/<name>/output/`.
## EDGAR-Specific Conventions
- **CIK** values are 10-digit, zero-padded (e.g., `0000320193`).
- **Rate limit**: SEC API allows 10 requests/sec. Scripts use ~0.11s delays.
- **User agent** is mandatory; include name + email.
## Scripted Example (Apple DEF 14A)
`edgar/scripts/fetch_apple_def14a.py` shows the direct flow:
1. Fetch latest DEF 14A metadata
2. Download HTML
3. Parse Summary Compensation Table (SCT)
4. Save raw HTML + extracted JSON + ground truth
## Recipe-Driven Extraction
`edgar/recipes/sct_extraction/config.yaml` defines a multi-step pipeline:
- Fetch DEF 14A filings by company list
- Extract SCT tables with `SCTAdapter`
- Validate with `sct_validator`
- Write results to `output/sct`
## Report Generation
`edgar/scripts/create_csv_reports.py` converts JSON results into:
- `executive_compensation_<timestamp>.csv`
- `top_25_executives_<timestamp>.csv`
- `company_summary_<timestamp>.csv`
## Troubleshooting
- **No filings found**: confirm CIK formatting and filing type (DEF 14A vs DEF 14A/A).
- **API errors**: slow down requests and confirm user-agent is set.
- **Extraction errors**: regenerate code or use manual ground truth in POC scripts.
## Related Skills
- `universal/data/reporting-pipelines`
- `toolchains/python/testing/pytest`
© Claude MPM Team · MIT · bobmatnyc/claude-mpm-skills