insight-stand

Operate the Insight compose stand and run the deployed-stand test suite.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running the Insight deployed-stand test suite requires correctly bringing up a seeded compose environment, aiming pytest at the right stand, and distinguishing environment failures from real product defects — mistakes in any of these produce misleading failures that look like product bugs. ## Core Features & Use Cases - Stand lifecycle management: Bring the stand up with ./dev-compose.sh test-stand up, re-seed it, and tear it down with volume removal as the only reset mechanism. - Run targeting: Aim a test run at a local or remote stand via --base-url and --stand-manifest, including the localhost/TLS constraint that prevents silent session-cookie loss and login loops. - Failure triage: Diagnose stand-versus-product failures using the symptom table covering manifest errors, capability skips, scratch-row leaks, and gateway preflight aborts. - Use Case: When test-stand up fails or the suite aborts with UsageError: stand manifest unusable, use this Skill to identify whether the stand was seeded incorrectly and re-seed it before re-running. ## Quick Start Ask the assistant to bring the Insight test stand up, seed it, and run the stand test suite, then triage any failures.

Frequently Asked Questions about insight-stand

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

FAQPage Schema
How do I run the Insight stand test suite?

Run `./dev-compose.sh test-stand up` to bring up and seed the stand, then `./dev-compose.sh test-stand test` to execute the suite. Pass pytest arguments like `-k subchart` directly; a path argument does not narrow the run because pytest unions path arguments.

How do I point the stand tests at a remote stand?

Run pytest directly with `--base-url https://<stand>` and `--stand-manifest <path>`. The `test-stand test` verb cannot do this because it preflights localhost and aborts before reading your pytest arguments.

Why does the stand login loop and then return 503?

The base URL is not a trustworthy origin. Browsers only store `__Host-` cookies over TLS or on localhost, so a plain-http non-localhost URL drops the session cookie, causing login loops that the gateway rate limiter turns into a 503.

Why do stand tests fail with 'manifest is missing fixtures'?

The stand was seeded without the required fixture names or with an older roster. Re-seed the running stand with `./dev-compose.sh test-stand seed` to restore the expected fixtures declared in the manifest.

Can the stand test suite reset the database between runs?

No. The stand is read-only by contract and reset only by volume teardown via `./dev-compose.sh test-stand down`. Tests that create rows must delete them, or the `no_scratch_rows_survive` fixture fails the run.

Why do some stand tests skip with capability reasons?

Skipping means the stand legitimately lacks a capability, such as `ingestion: no` on the compose stand. This is expected behavior, not a failure — read the skip reason to confirm which capability the stand does not provide.