Use the factset CLI to discover, inspect, and run FactSet API operations instead of guessing API names, request bodies, or raw HTTP routes.
Treat this file as the thin agent-facing wrapper. The synced references are the source of truth for exact command syntax and request-shape guidance.
If you are reading the authored repo copy under skills/factset-cli, the generated references/docs/ tree may not exist yet. In that case, use the canonical repo files under docs/. In the public install surface, that same content lives under references/docs/.
Working Rules
- Start from the user’s business question, not from an API guess.
- Use
factset list, thenfactset <api>, thenfactset <api> <operation> --helpbefore falling back to raw schema inspection. - Prefer
--exampleover--template, and prefer--template=fullover reading raw OpenAPI when you still need more input detail. - Use the narrowest operation that directly answers the question.
- Report exact commands, identifiers, filters, and absolute dates for time-sensitive results.
- If a request needs input and none was provided, use the CLI’s missing-input guidance instead of inventing your own request shape.
- Treat
403 Forbiddenas an entitlement hint unless the response clearly says auth failed.
Local References
- Read references/docs/cli.md for the canonical CLI guide, input-shape conventions, examples, and common error handling. In the authored repo tree, the same content lives under
docs/. - Use evals/evals.json together with evals/README.md when improving the shipped FactSet-only CLI and skill surface. These eval materials are intentionally product-local. Cross-product Flow orchestration benchmarks live at the repo root under
tools/integration-evals/and are not part of this public skill tree. - Do not use the generated per-API helper skills under
generated/skills/factset-*as the primary interface. The public install surface is the single generalfactset-cliskill.