api-test

Redirects legacy analytics HTTP contract test references to the current stand-api-test and metric-test suites.

10|9|Updated May 22, 2026
One-click install
npx skills add https://github.com/constructorfabric/insight --skill api-test-constructorfabric
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-test
Source: https://github.com/constructorfabric/insight/tree/main/.claude/skills/api-test
Command: npx skills add https://github.com/constructorfabric/insight --skill api-test-constructorfabric

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill prevents confusion caused by outdated references to a retired in-process analytics endpoint contract testing rig by pointing developers to the current test suites. ## Core Features & Use Cases - Deprecation Redirect: Explains that the in-process analytics HTTP contract rig was retired and must not be used to write new tests. - Suite Routing: Directs HTTP contract test work to tests/stand/api/ per the stand-api-test skill, and seeded-bronze to served-metric data-path specs to tests/datapath/metrics/<class>/ per the metric-test skill. - Use Case: A developer following an old document that references api-test learns the rig is gone, finds the replacement suites, and can inspect the retired rig's code via git history at src/ingestion/tests/e2e/api. ## Quick Start Ask where analytics HTTP contract tests should be written now that the api-test rig is retired.

Frequently Asked Questions about api-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Where do I write analytics HTTP contract tests now?

Analytics HTTP contract tests now live in tests/stand/api/ and are written according to the stand-api-test skill. The old in-process contract rig documented by api-test was retired and must not be used for new tests.

How do I write seeded-bronze to served-metric data-path tests?

Data-path specs that seed bronze data and verify served metrics live in tests/datapath/metrics/<class>/ and run against a compose test-stand instance. Write them following the metric-test skill's guidance.

Can I still use the api-test skill to write tests?

No. The api-test skill is a historical redirect stub only; its description explicitly says not to use it for writing tests. Use stand-api-test for HTTP contract coverage or metric-test for data-path specs instead.

Where can I find the retired analytics contract rig code?

The retired rig's documentation and code remain in git history. Run git log --all -- src/ingestion/tests/e2e/api to inspect the old implementation and its evolution.

Why does the api-test skill still exist if the rig is retired?

It exists solely so old references to api-test resolve to something meaningful rather than breaking. It carries disable-model-invocation and read-only tools, acting purely as a signpost to the replacement suites.