CtrlK
BlogDocsLog inGet started
Tessl Logo

edgartools-sec-data

How to pull SEC EDGAR data with the edgartools Python package — company lookup, filings, XBRL financial statements, and filing sections like Item 1A risk factors. Use whenever a task involves SEC filings, 10-K/10-Q data, or company financials.

75

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an efficient, executable reference: ready-to-run code for each capability plus judicious domain guidance on segments, defensiveness, and reporting hygiene. It is read-only data access so the lack of a formal validate-checklist only lightly caps workflow clarity.

DimensionReasoningScore

Conciseness

Lean body of tight code examples plus brief, domain-specific guidance ('Consolidated revenue hides the story; the segment note is where concentration ... show up'); assumes Claude's competence and explains no basic concepts, so every token earns its place.

5 / 5

Actionability

Fully executable, copy-paste-ready code throughout — Company lookup, get_filings, tenk['Item 1A'], financials.income_statement(), segment-note text search — covering the common cases including YoY risk-factor diff and Form 4 insider filings.

5 / 5

Workflow Clarity

Clear sequence from 'Always set your identity first' through companies, filings, sections, financials, segments, and hygiene, with defensive fallbacks ('inspect it ... fall back to filing.text() ... note the fallback'); not 5 because there is no explicit validate/verify checklist, though the skill is read-only so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

Self-contained skill with no bundle files, organized into well-signaled sections (identity, companies/filings, reading the filing, financials, segments, patterns, hygiene); per the simple-skill guideline, well-organized sections without nested references merit a top score.

5 / 5

Total

19

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: concrete capabilities, an explicit 'Use whenever ...' trigger clause, and a distinctive SEC/EDGAR niche. Third-person voice is used correctly. The only gap is slightly limited synonym coverage in the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'company lookup, filings, XBRL financial statements, and filing sections like Item 1A risk factors' — giving comprehensive coverage of the skill's data-access surface; not score 4 because coverage is broad rather than having minor gaps.

5 / 5

Completeness

Explicitly states what ('pull SEC EDGAR data ... company lookup, filings, XBRL financial statements, and filing sections') and when ('Use whenever a task involves SEC filings, 10-K/10-Q data, or company financials') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural terms — 'SEC filings', '10-K/10-Q data', 'company financials' — that users would actually say; not 5 because common synonyms like 'annual/quarterly report', 'earnings', or 'financial statements' are absent.

4 / 5

Distinctiveness Conflict Risk

Niche terms — 'SEC EDGAR data', 'edgartools', '10-K/10-Q', 'Item 1A risk factors' — carve a clear niche with minimal overlap risk against other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
anthropics/cwc-workshops
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.