CtrlK
BlogDocsLog inGet started
Tessl Logo

sec-edgar

U.S. SEC EDGAR fetch interface — resolve a ticker to its CIK, list recent filings (10-K / 10-Q / 8-K and friends) with primary-document URLs, and pull XBRL companyfacts financial series. Free, no API key; rate-limited by IP so every request is throttled and carries a contact User-Agent. United States only.

64

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/sec-edgar/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

The body is lean, highly actionable, and well-structured with verified one-level-deep references; the only gap is an implicit rather than explicit validation checkpoint in the fetch workflow.

Suggestions

Add an explicit checkpoint after ticker resolution, e.g. "If cik_for returns None, the ticker is not a U.S. listing — stop and tell the user rather than proceeding."

DimensionReasoningScore

Conciseness

The body is dense yet lean: every section delivers specifics Claude would not infer (zero-padded 10-digit CIK, case-sensitive us-gaap metric names, ISO date strings, envelope vs. dict return shapes) without padding with concepts Claude already knows.

3 / 3

Actionability

Provides concrete executable guidance — copy-paste JSON tool invocations and a real Python import block with inline return-value comments — plus a pointer to a runnable end-to-end script, matching the fully-executable anchor.

3 / 3

Workflow Clarity

The ticker → CIK → filings → metric series sequence is shown clearly and the unlisted-ticker failure case ("None if not in the SEC table") is noted inline, but there is no explicit validate-then-proceed checkpoint or error-recovery feedback loop around the CIK-resolution step.

2 / 3

Progressive Disclosure

SKILL.md is an overview that signals one-level-deep references via a dedicated Reference Docs section (four files, each described) and a Scripts section, and every referenced path (sec_edgar_client.md, get_sec_filings_tool.md, endpoints_and_limits.md, forms_and_concepts.md, sec_filings_example.py) resolves to a real bundle file.

3 / 3

Total

11

/

12

Passed

Description

67%

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 specific and well-scoped to a distinct niche, but it lacks an explicit "Use when…" trigger clause and mixes in technical jargon that weakens natural trigger-term coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when fetching SEC EDGAR filings, 10-K/10-Q/8-K data, or XBRL company financials for a U.S. ticker."

Soften technical jargon by adding natural user-facing terms such as "financial data", "earnings reports", or "SEC filings" alongside "XBRL companyfacts" and "CIK".

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "resolve a ticker to its CIK", "list recent filings (10-K / 10-Q / 8-K and friends) with primary-document URLs", and "pull XBRL companyfacts financial series" — matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Clearly answers what the skill does, but provides no "Use when…" clause or equivalent explicit trigger guidance; the "when" is only implied by scope notes ("United States only", "Free, no API key"), which per the rubric caps completeness at 2.

2 / 3

Trigger Term Quality

Contains relevant natural terms (SEC EDGAR, filings, 10-K / 10-Q / 8-K, ticker) but leans technical with jargon like "CIK", "XBRL companyfacts", and "primary-document URLs", and omits common softer variations such as "financial data" or "earnings".

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — a U.S. SEC EDGAR fetch interface scoped to U.S. equities only — making it unlikely to trigger for other data-source skills (tushare / yfinance / akshare).

3 / 3

Total

10

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 5 missing, 5 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
HKUDS/Vibe-Trading
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.