CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sec-edgar

Retrieve and analyze public SEC filings, company facts, XBRL data, and filing metadata.

60

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./resources/bundled-skills/sec-edgar/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A compact, well-structured, non-padded skill body with clear sequencing and validation gates. Its main weakness is actionability: it tells Claude what to do but not how, lacking concrete EDGAR endpoints or example requests, and the Purpose section duplicates the frontmatter description.

Suggestions

Add concrete endpoint examples, e.g. fetching https://data.sec.gov/submissions/CIK##########.json for filing indexes and https://data.sec.gov/api/xbrl/companyfacts/CIK##########.json for XBRL facts.

Drop the 'Purpose' section or differentiate it from the frontmatter description to remove verbatim duplication.

Add a short feedback loop under Completion gates (e.g., 'If values do not reconcile, re-fetch the filing index and check amendment status before proceeding').

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence ('Normalize units and taxonomy concepts carefully', 'Reconcile extracted values to the filing tables and scale'), but the 'Purpose' section repeats the frontmatter description verbatim, a minor redundancy that keeps it below anchor 5.

4 / 5

Actionability

The tool-routing table and citation requirements ('Cite form, filing date, period, accession number, and SEC URL') provide some concrete guidance, but no executable specifics are given — e.g., the actual EDGAR endpoints like data.sec.gov/submissions/CIK##########.json or companyfacts URLs. This lands between the high-level-hints anchor (2) and the mostly-executable anchor (4).

3 / 5

Workflow Clarity

The 5-step workflow is clearly sequenced and the 'Completion gates' section supplies validation checkpoints (amended filings/restatements, reconciling values to tables and scale), matching the 'clear sequence with most checkpoints' anchor. It falls short of anchor 5 because there is no feedback loop describing what to do when a gate check fails.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no external reference files (no references/, scripts/, or assets/ directories exist, and the body makes no reference to any), and is organized into well-labeled sections, which per the simple-skill guideline merits a 5.

5 / 5

Total

16

/

20

Passed

Description

70%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.

A concise, specific, third-person description that clearly defines a distinct niche, but it lacks any 'Use when...' trigger clause and omits common user terms like EDGAR and 10-K/10-Q. Adding explicit trigger guidance would substantially raise completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about SEC filings, EDGAR data, or company financial disclosures such as 10-K or 10-Q reports.'

Include commonly-said synonyms like 'EDGAR', 'annual report', 'quarterly report', or '10-K/10-Q' in the description to improve trigger-term coverage.

Briefly enumerate the kinds of analysis offered (e.g., extracting financial facts, comparing periods) to move specificity from several-actions to comprehensive.

DimensionReasoningScore

Specificity

The description lists several specific actions ('Retrieve and analyze') across four concrete object types ('public SEC filings, company facts, XBRL data, and filing metadata'), matching the 'several specific actions; minor gaps' anchor. It falls short of anchor 5 because the scope of analysis (e.g., comparisons, trend analysis) is not enumerated.

4 / 5

Completeness

The 'what' is clear ('Retrieve and analyze public SEC filings, company facts, XBRL data, and filing metadata') but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural phrases like 'SEC filings', 'company facts', and 'XBRL data' are terms users would actually say, giving good keyword coverage. It misses a few common variations such as 'EDGAR', '10-K'/'10-Q', or 'annual/quarterly report', keeping it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

SEC filings and XBRL data form a clear niche with distinct triggers and minimal conflict risk against generic research or document skills, matching anchor 5.

5 / 5

Total

16

/

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

KunAgent/Kun

Path

resources/bundled-skills/sec-edgar/SKILL.md

Revision

8e16760

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill