跳到正文
FunCoding

搜索

搜索文档、Skill 和 MCP

fintel-data

Query Fintel (fintel.io) institutional market data through its REST API or official MCP server. Use this skill whenever the user mentions Fintel or asks about short interest, short interest ratio or days to cover, short squeeze data, borrow rate or cost to borrow, shares available to borrow, daily short volume, fails-to-deliver (FTD), 13F institutional owners ("who owns X"), insider buying or selling from SEC Form 3/4/5, analyst price targets, ratings and forecasts, dividend or earnings history and calendars, EOD or last prices, security lookup by ticker, CUSIP, ISIN, or FIGI, Fintel leaderboards, or their Fintel watchlists and alerts. Read-only: GET endpoints only.

安全3.4kplugins/data-providers/skills/fintel-data/SKILL.md

安装

把这段话发给 Claude Code、Codex 或 Cursor。智能体会先检查安全性,你确认后才安装。

读取 https://funcoding.ai/skills/himself65/finance-skills/fintel-data/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

Fintel Data Skill

Fintel (fintel.io) is an institutional-grade market intelligence platform. Its strongest datasets are the ones most other providers lack: short interest, borrow rates, short volume, fails-to-deliver, 13F institutional ownership, and insider transactions.

Fintel exposes two surfaces backed by the same data contract:

SurfaceEndpointAuthBest for
RESThttps://api.fintel.io/v1/*X-API-KEY headerDefault — curl from any CLI agent
MCPhttps://mcp.fintel.io/mcpX-API-KEY headerMCP-native clients, tool auto-discovery

Both require a Fintel API key. This skill is read-only — only call GET endpoints. The API also exposes write endpoints (create/delete stock lists, alert subscriptions, teams); do not call them.


Step 1: Resolve FINTEL_API_KEY

The skill resolves FINTEL_API_KEY in this order:

  1. FINTEL_API_KEY environment variable
  2. FINTEL_API_KEY in .env in the current directory
  3. FINTEL_API_KEY in .env at the git repo root (so a worktree inherits the key from the main checkout)
!`if [ -n "$FINTEL_API_KEY" ]; then echo "KEY_FROM_ENV_VAR"; elif [ -f .env ] && grep -qE "^FINTEL_API_KEY=" .env; then echo "KEY_FROM_LOCAL_DOTENV:$(pwd)/.env"; else GIT_COMMON=$(git rev-parse --path-format=absolute --git-common-dir 2>/dev/null); if [ -n "$GIT_COMMON" ]; then ROOT=$(dirname "$GIT_COMMON"); if [ -f "$ROOT/.env" ] && grep -qE "^FINTEL_API_KEY=" "$ROOT/.env"; then echo "KEY_FROM_ROOT_DOTENV:$ROOT/.env"; else echo "KEY_NOT_SET"; fi; else echo "KEY_NOT_SET"; fi; fi`

Then act on the result:

  • KEY_FROM_ENV_VAR — use $FINTEL_API_KEY directly in curl calls.
  • KEY_FROM_LOCAL_DOTENV:<path> / KEY_FROM_ROOT_DOTENV:<path> — load once before calling:
    export FINTEL_API_KEY=$(grep -E "^FINTEL_API_KEY=" <path> | head -1 | cut -d= -f2- | sed 's/^["'\'']//;s/["'\'']$//')
    
  • KEY_NOT_SET — ask the user for their key. Keys come with a Fintel API plan (fintel.io, docs at api.fintel.io/docs). They can either export FINTEL_API_KEY="..." or add FINTEL_API_KEY=... to .env at the repo root (preferred for worktrees).

Step 2: Resolve the Security

Most endpoints are addressed by {country}/{symbol} — an ISO country code plus ticker, e.g. us/AAPL. Default to us when the user gives only a ticker.

If the ticker is ambiguous or the user gives a company name, CUSIP, ISIN, or FIGI, resolve it first:

# name / ticker / CUSIP / ISIN / FIGI search
curl -s -H "X-API-KEY: $FINTEL_API_KEY" "https://api.fintel.io/v1/securities?query=apple&country=us"
# exact identifier lookup (type: cusip, isin, ticker, id)
curl -s -H "X-API-KEY: $FINTEL_API_KEY" "https://api.fintel.io/v1/identifiers/isin/US0378331005"

Step 3: Match the Request to an Endpoint

User wantsEndpointNotes
Short interest, days to cover/v1/securities/{country}/{symbol}/short-interestTrailing year, NYSE/NASDAQ-reported. Limited availability — must be enabled per account; 403 means not entitled
Borrow rate, cost to borrow, shares available/v1/securities/{country}/{symbol}/borrow-rateLatest securities-lending fee rate, rebate rate, shares available
Daily short volume/v1/securities/{country}/{symbol}/short-volumeTrailing year: short, short-exempt, total volume
Fails-to-deliver / FTD/v1/securities/{country}/{symbol}/fails-to-deliverTrailing-year SEC FTD records (US only)
Institutional owners / 13F holders/v1/securities/{country}/{symbol}/ownersCurrent SEC 13F-derived holders
Insider transactions / Form 4/v1/securities/{country}/{symbol}/insidersSEC Form 3/4/5-derived; count param
Analyst price targets/v1/securities/{country}/{symbol}/price-targetsHigh, low, mean, median
Analyst buy/hold/sell ratings/v1/securities/{country}/{symbol}/analyst-ratingsAggregated recommendations
Revenue / EPS forecasts/v1/securities/{country}/{symbol}/forecastAggregated analyst estimates
EOD price history/v1/securities/{country}/{symbol}/eodperiod: 1m, 3m, 6m, 1y (default), 2y, 3y, 5y, all
Latest price + derived stats/v1/securities/{country}/{symbol}/last-price52w high/low, WTD/MTD/YTD change; falls back to EOD close with meta.warnings=["quote_stale"]
Dividend history/v1/securities/{country}/{symbol}/dividends
Earnings history and surprises/v1/securities/{country}/{symbol}/earnings
Upcoming earnings (one stock / market-wide)/v1/securities/{country}/{symbol}/calendar/earnings or /v1/calendar/earningsfrom/to ISO dates, default today +7d, max 90d window
Upcoming dividends (one stock / market-wide)/v1/securities/{country}/{symbol}/calendar/dividends or /v1/calendar/dividendsSame window rules
A specific fundamental metric/v1/securities/{country}/{symbol}/data-points/{key}Discover keys via /v1/data-definitions?query=...
Top/bottom ranked stocks/v1/leaderboards then /v1/leaderboards/{key}/entries503 not_available means retry later; meta.status="beta" means stub data
Security profile, listings, identifier history/v1/securities/{country}/{symbol}
User's watchlists/v1/stock-lists, /v1/stock-lists/{id}/itemsAlso /insiders, /owners, /filings per list
User's alerts/v1/alerts, /v1/alert-messages
Account / entitlements/v1/account

Full parameter details, country/exchange discovery endpoints, and more curl examples: read references/api-reference.md.


Step 4: Call the API

curl -s -H "X-API-KEY: $FINTEL_API_KEY" \
  "https://api.fintel.io/v1/securities/us/AAPL/short-volume" | python3 -m json.tool
  • Success responses are JSON; some carry a meta object (warnings, freshness, status). Surface meta.warnings to the user when present.
  • Errors return {"error": {"code": "...", "message": "..."}} — e.g. unauthorized (bad/missing key), 403 (dataset not enabled for the account, common for short-interest), 503 not_available (ranking service down — retry later, don't treat as empty data).
  • Usage is metered per account — batch thoughtfully; don't poll.

Step 5: MCP Alternative (Optional)

For MCP-native setups, the same tools are discoverable from the official server (tool names like fintel.get_short_interest, fintel.get_security_owners — REST parity, same entitlements):

claude mcp add --transport http fintel https://mcp.fintel.io/mcp --header "X-API-KEY: your_key_here"

Prefer REST via curl when shell access is available — it needs no setup beyond the key. Use MCP when the user explicitly asks for it or shell access is restricted (note: neither works on Claude.ai's sandbox).


Step 6: Respond to the User

  • Format numbers cleanly: prices to 2 decimals, percentages to 1-2 decimals, share counts with commas or abbreviations (2.3M, 1.1B).
  • For short data: contextualize — short interest as % of float, days to cover, borrow fee trend direction. High borrow fee + falling shares available is the classic squeeze setup; present the data, not a prediction.
  • For ownership/insiders: use tables (holder, shares, change, date). Distinguish buys from sells and option exercises in Form 4 data.
  • Note the data source: "Fintel" with dataset provenance (SEC 13F, Form 3/4/5, NYSE/NASDAQ short reports) when relevant.
  • Never turn the data into a trading recommendation, price target, or squeeze call — present facts and let the user draw conclusions.

Reference Files

  • references/api-reference.md — full REST endpoint reference: all GET endpoints with parameters, defaults, limits, error semantics, MCP tool name mapping, and curl examples.

相似的 Skill

security-and-hardening
addyosmani/agent-skills103k

security-and-hardening

Hardens code against vulnerabilities. Use when auditing an input handler for vulnerabilities, when handling user input, authentication, data storage, or external integrations, or when checking a login flow is safe against the OWASP Top Ten. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services. Use when auditing dependencies for known vulnerabilities, triaging package-manager audit findings, or assessing supply-chain risk in a new package. Use when personal data or privacy compliance (GDPR, CCPA) is involved.

安全

archify
tt-a1i/archify80k

archify

Create polished, validated architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as explorable standalone HTML with inline SVG, dark/light themes, optional trace motion, and PNG/JPEG/WebP/SVG/WebM export. Accept plain-language requirements or pasted Mermaid flowchart, sequenceDiagram, and stateDiagram input; inspect repository evidence when the diagram must reflect real code. Use when the user asks to visualize system architecture, infrastructure, cloud/security/network topology, technical workflows, API call sequences, request lifecycles, data pipelines, ETL/ELT, data lineage, state machines, or to convert/beautify Mermaid. Also use for everyday subjects with steps, parts, relationships, or states: a leave or travel plan, an application or approval process, a back-and-forth such as renting, where money or documents go, or where an application or order stands. Not for numeric charts or dashboards.

安全

security-research
code-yeongyu/oh-my-openagent70k

security-research

Team Mode security research skill. Orchestrates 3 vulnerability hunters and 2 PoC engineers to audit a codebase in parallel, prove exploitability, classify root causes, and calibrate severity by actual exploitability. Use for security review, vulnerability research, exploitability audit, pre-release security check, threat model validation, and `/security-research`. Triggers: 'security-research', 'security research', 'security review', 'vulnerability audit', 'exploitability audit', '보안 리뷰', '취약점 감사'.

安全

007
sickn33/agentic-awesome-skills47k

007

Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.

安全

open-code-review
alibaba/open-code-review45k

open-code-review

Performs AI-powered code review on Git changes using the `ocr` CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply fixes when requested. With appropriate review rules, can detect various types of issues including bugs, security vulnerabilities, performance problems, and code quality concerns.

安全

open-code-review
alibaba/open-code-review45k

open-code-review

Performs AI-powered code review on Git changes using the `ocr` CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply fixes when requested. With appropriate review rules, can detect various types of issues including bugs, security vulnerabilities, performance problems, and code quality concerns.

安全