agentleFS
cnoe-iocnoe-io/ai-platform-engineering/.claude/skills/run-caipe-integration-tests/SKILL.md

run-caipe-integration-tests

Skill438 starsChanged 55 days agoApache-2.0View on GitHub

Run CAIPE integration tests — streaming comparison, metadata validation, and optionally full agent routing tests.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run integration tests against the local Docker Compose dev environment.

    line 13
  2. Distinctive:

    Verify the environment is ready:

    line 29
  3. Distinctive:

    If a supervisor is not running, tell the user and suggest:

    line 40
  4. Distinctive:

    Use the streaming testing skill:

    line 47
  5. Very specific:

    All output files are saved to /tmp/ with timestamps

    line 89

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

User Input

$ARGUMENTS

Goal

Run integration tests against the local Docker Compose dev environment. This command orchestrates the streaming testing skill and optionally the full agent integration tests.

Execution Steps

1. Parse arguments

Interpret the user's input to determine which test suites to run:

  • No arguments or "all": Run streaming comparison + agent validation
  • "streaming" or "stream": Run only the streaming comparison
  • "agents" or "agent": Run only agent checkpoint validation
  • "metadata" or "analyze": Run metadata analysis on an existing capture
  • A quoted query string (e.g. "what is caipe?"): Run streaming comparison with that query

2. Pre-flight checks

Verify the environment is ready:

# Check Docker is running
docker info > /dev/null 2>&1

# Check supervisors
curl -sf http://localhost:8000/.well-known/agent.json > /dev/null 2>&1 && echo "0.3.0 OK" || echo "0.3.0 NOT RUNNING"
curl -sf http://localhost:8041/.well-known/agent.json > /dev/null 2>&1 && echo "0.2.41 OK" || echo "0.2.41 NOT RUNNING"

If a supervisor is not running, tell the user and suggest:

docker restart caipe-supervisor caipe-supervisor-041

3. Run streaming comparison (if applicable)

Use the streaming testing skill:

./skills/streaming-testing/run_comparison.sh "${QUERY:-what can you do?}"

This runs: health check -> capture from both supervisors -> metadata analysis -> side-by-side comparison.

Report the key findings:

  • Time to first content (both versions)
  • Any safety check failures (marker leaks, metadata leaks)
  • Artifact breakdown differences

4. Run agent validation (if applicable)

./skills/persistence/validate_agent_checkpoints.sh

Report pass/fail summary.

5. Run Python unit tests (always)

PYTHONPATH=. uv run pytest tests/test_slack_narration_typing_status.py tests/test_streaming_e2e.py -v -m "not integration" --tb=short

Report pass/fail count.

6. Summary

Present a consolidated summary:

  • Streaming comparison: pass/fail with key metrics
  • Agent validation: pass/fail
  • Unit tests: X passed, Y failed
  • Any action items or issues found

Notes

  • The streaming comparison requires both supervisors (ports 8000 and 8041) to be running
  • Agent validation requires MongoDB and agent containers
  • Unit tests run without external dependencies
  • All output files are saved to /tmp/ with timestamps
  • For detailed docs, see skills/streaming-testing/SKILL.md and skills/integration-testing/SKILL.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.