Analyze company in context

Skill secapi-ai/secapi-skills/analyze-company-in-context

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 analyze-company-in-context

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

Builds a concise issuer brief before deeper research. Use when a business, financial, factor, or macro fact could change the next question.

SKILL.md

2.0 KB, as published. Nobody here has run it

Analyze Company in Context

Build a short issuer brief before committing to a full diligence process. Start with a ticker or CIK and a reporting period. Add segment, factor, or macro context only when it changes the research question.

First Read

curl --fail --silent --show-error \
  "https://api.secapi.ai/v1/companies/overview?ticker=MSFT&include=segments,dilution" \
  -H "x-api-key: $SECAPI_API_KEY"

If the request starts with a name rather than a ticker or CIK, resolve it with GET /v1/entities/resolve before calling the issuer routes.

What to provide

Give the agent a ticker or CIK, the question it should help answer, and a reporting period or lookback where it matters. A company name alone must be resolved before issuer routes can be used.

Research path

Read GET /v1/companies/overview using ticker or cik. Its optional include values are segments, footnotes, dilution, and factors.
Use GET /v1/companies/segments when product, geographic, or operating mix matters. It accepts ticker or cik, plus optional period and segment_type.
Add GET /v1/factors/exposures only when factor sensitivity belongs in the decision.
Use GET /v1/macro/regimes only when country regime context changes the interpretation.
Use the security and earnings context endpoints as supporting material. Keep their returned context distinct from filing evidence.

Expected result

Lead with the issuer, the decision-relevant facts, and the open question. Follow with business mix, financial or filing context, and only the factor or macro overlays that matter. Name the report date and lookback. For every filing claim, retain the accession number, filing URL, and item, note, section, or page; label your conclusion as interpretation.

The result is a scoping brief, not a price target, hedge instruction, or substitute for full diligence.