Use live factor dashboard

Skill secapi-ai/secapi-skills/use-live-factor-dashboard

SEC API agent skills for source-cited filing research with hosted API and MCP workflows

Install

npx -y skills add secapi-ai/secapi-skills --skill use-live-factor-dashboard

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Monitors intraday factor returns, position loadings, and correlations. Use when you need a dated view of unusual factor movement and reported sensitivity.

SKILL.md

1.5 KB, as published. Nobody here has run it

Use Live Factor Dashboard

Use this as a monitoring skill: what is moving, when it was observed, and how a position's published loadings may be exposed. Do not imply a live trade signal.

First Read

curl --fail --silent --show-error \
  "https://api.secapi.ai/v1/factors/returns/intraday" \
  -H "x-api-key: $SECAPI_API_KEY"

What to provide

Give the agent a ticker when position sensitivity matters and say what makes a move worth investigating. The intraday endpoint is an observation at a response time, not a market-data guarantee.

Research path

Start with GET /v1/factors/returns/intraday and retain the response timestamp and freshness state when supplied.
Inspect a position with GET /v1/stocks/{ticker}/loadings.
Use GET /v1/factors/correlations for concentration context, not a directional forecast.
Use the response timestamp and any returned freshness state to decide whether the observation is suitable for the question.

Expected result

Show the unusual moves, the time observed, the position loadings that bear on sensitivity, and any stale, proxy, or degraded state returned by the API. Keep correlation and loading evidence separate from a claim about why a price moved. Intraday observations are not closing prices, execution instructions, or a guarantee of persistence.