CtrlK
BlogDocsLog inGet started
Tessl Logo

fintel-data

Query Fintel (fintel.io) institutional market intelligence via the REST API at https://api.fintel.io/v1 with FINTEL_API_KEY (X-API-KEY header), or the official MCP server at https://mcp.fintel.io/mcp. Read-only data: short interest, borrow rate/fee and shares available to borrow, daily short volume, fails-to-deliver (FTD), institutional ownership from SEC 13F filings, insider transactions from SEC Form 3/4/5, analyst price targets, ratings and forecasts, dividends and earnings history, earnings and dividend calendars, EOD price bars, last trade price, security master lookup by ticker/CUSIP/ISIN/FIGI, leaderboards, watchlists and alerts. Triggers: "fintel", "fintel.io", short interest, short squeeze data, borrow rate, cost to borrow, shares available to borrow, FTD, fails to deliver, short volume, 13F holders, institutional owners, who owns X, insider buying, insider selling, Form 4 transactions, analyst price target, days to cover, short interest ratio.

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

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 content is a well-structured, mostly lean, read-only API skill with executable curl examples, an explicit error-handling/validation layer, and clean progressive disclosure to a real reference file. Its main room for improvement is tightening a few dense sections and making a couple of validation checkpoints more explicit.

Suggestions

Tighten the Step 1 inline key-resolution shell snippet or move it into references/api-reference.md to keep the overview lean.

Reframe the Step 4 error handling as an explicit validate-then-act checklist (e.g. 'on 403, stop and tell the user the dataset isn't entitled; on 503, retry once then stop') to reach a higher workflow-clarity anchor.

Consider consolidating the Step 3 endpoint table into references/api-reference.md and keeping only a representative subset inline, reducing repetition with the reference file.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, with mostly purposeful content; the dense inline key-resolution shell snippet is justified but slightly more than minimal. It sits clearly above the midpoint but a few lines could still be trimmed.

4 / 5

Actionability

It provides copy-paste-ready, fully executable curl commands with real headers, base URLs, and path params (e.g. the short-volume and securities-search examples), and covers the common call patterns plus a concrete MCP add command.

5 / 5

Workflow Clarity

A clear 6-step sequence (resolve key → resolve security → match endpoint → call → optional MCP → respond) with explicit error/validation checkpoints (403 not entitled, 503 retry, KEY_NOT_SET branch, surfacing meta.warnings). It falls just short of 5 because some checkpoints are described rather than framed as explicit validate-then-act gates.

4 / 5

Progressive Disclosure

The body is a focused overview with a single well-signaled, one-level-deep reference to the real references/api-reference.md file for full endpoint details, with content appropriately split between SKILL.md and the bundle.

5 / 5

Total

18

/

20

Passed

Description

100%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 a strong, third-person statement that comprehensively lists concrete capabilities and pairs them with an explicit, well-chosen set of natural-language triggers. It cleanly answers both what the skill does and when to invoke it, with a distinct niche that minimizes conflict risk.

DimensionReasoningScore

Specificity

The description enumerates many concrete data actions ("short interest, borrow rate/fee and shares available to borrow, daily short volume, fails-to-deliver (FTD), institutional ownership from SEC 13F filings, insider transactions") with comprehensive coverage across Fintel's datasets.

5 / 5

Completeness

It explicitly answers both "what" (a detailed capability list across multiple datasets) and "when" via the dedicated "Triggers:" clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

The explicit "Triggers:" clause covers natural user phrases and synonyms including "short interest", "short squeeze data", "borrow rate", "cost to borrow", "who owns X", "insider buying/selling", "Form 4 transactions", and "days to cover".

5 / 5

Distinctiveness Conflict Risk

The Fintel institutional-intelligence niche is clearly scoped with distinct triggers (FTD, 13F holders, borrow rate), giving it minimal overlap with other skills.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
himself65/finance-skills
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.