edgar-sec-filings

SEC EDGAR filing analysis — 10-K, 10-Q, 8-K, proxy statements, insider Form 4. Extract key financials, risk factors, management discussion, and generate investment signals from US public company filings.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/edgar-sec-filings/SKILL.md

Quality

Content

65%

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

A richly actionable, well-organized analytical framework whose main weaknesses are verbosity, an implicit rather than explicit workflow, and a monolithic structure with no progressive disclosure into reference files.

Suggestions

Split the per-filing-type frameworks (10-K/10-Q, 8-K, Form 4, 13F) into separate reference files linked from a leaner overview, improving both conciseness and progressive disclosure.

Add an explicit step-by-step workflow (retrieve filings → extract per dimension → compute composite score → emit output format) with a verification checkpoint on data completeness before scoring.

Trim explanatory parentheticals and the Notes section to facts Claude would not already know, tightening token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is information-dense with tables and code, but at ~298 lines it includes explanatory asides ('pricing power', 'cost pressure', 'may be pre-planned') and a Notes section restating widely-known EDGAR facts that could be tightened; not a level 1 wall of fluff, but not fully lean either.	2 / 3
Actionability	Provides executable yfinance code, concrete EDGAR URL templates, 8-K item-number signal rules, an insider-scoring function, and a complete copy-paste output format template — specific and actionable throughout.	3 / 3
Workflow Clarity	Analysis is organized into parallel dimensions with a composite scoring template and output format, but there is no explicit sequenced workflow with validation checkpoints; the operation is read-only so the destructive cap does not apply, yet a clear step sequence is still missing.	2 / 3
Progressive Disclosure	Sections are well organized, but the skill is a monolithic ~298-line SKILL.md (well over the 50-line simple-skill threshold) with content that could be split into reference files and no signaled one-level-deep references.	2 / 3
	Total	9 / 12 Passed

Description

82%

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

A specific, well-triggered description with concrete actions and a clear niche, weakened only by the absence of an explicit 'Use when...' trigger clause which caps completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when analyzing US public company SEC filings (10-K, 10-Q, 8-K, proxy statements, Form 4) or when the user mentions EDGAR filings or company financial disclosures.'

Consider adding common user phrasings like 'earnings reports', 'annual report', or 'quarterly report' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Extract key financials, risk factors, management discussion, and generate investment signals') alongside specific filing types, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	The 'what' is explicit, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2 rather than 3.	2 / 3
Trigger Term Quality	Natural user-facing terms are well covered — 'SEC EDGAR filing', '10-K', '10-Q', '8-K', 'proxy statements', 'Form 4' — the vocabulary a user requesting filing analysis would actually say.	3 / 3
Distinctiveness Conflict Risk	The 'SEC EDGAR filing analysis' niche with distinct filing-type triggers is clearly distinguishable and unlikely to fire for an unrelated skill.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: HKUDS/Vibe-Trading
Path: agent/src/skills/edgar-sec-filings/SKILL.md
Commit: 8643fcd

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.