fabric-e2e

Execute end-to-end tests validating API, CLI, data capture, triage, recall, storage, and error handling.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/adaw/skills --skill fabric-e2e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fabric-e2e
Source: https://github.com/adaw/skills/tree/main/fabric-e2e
Command: npx skills add https://github.com/adaw/skills --skill fabric-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures the entire LLM system functions correctly from end-to-end, catching integration issues that unit tests miss, and acting as a final quality gate before code is considered complete.

Core Features & Use Cases

  • Full Stack Validation: Tests API, CLI, capture pipeline, triage, recall with scoring, storage, and error handling.
  • Quality Gate: Confirms observations flow correctly from capture to recall, ensuring proper data handling and XML injection.
  • Use Case: Before merging new features, run this Skill to verify that new user inputs are captured, processed, stored, and can be recalled with accurate scoring, ensuring the system behaves as expected in a live environment.

Quick Start

Run the end-to-end tests for the fabric system to validate the full stack.

Frequently Asked Questions about fabric-e2e

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

FAQPage Schema
How do I run end-to-end integration tests for an LLM system before deployment?

End-to-end integration testing for an LLM system is executed against a live environment to validate the complete operational pipeline, including API, CLI, data capture, triage, recall with scoring, storage, and error handling. This serves as a final quality gate to ensure system integrity before deployment.

What is e2e testing for a data pipeline and recall mechanisms?

E2e testing for a data pipeline and recall mechanisms validates that observation data flows correctly from capture to recall. It ensures proper data handling, XML injection, and accurate scoring, confirming the system behaves as expected when processing new user inputs.

Does this integration testing skill work as a standalone quality gate or does it require dependencies?

This integration testing skill operates as a standalone quality gate with zero dependencies. It independently confirms the integrity of the observation data flow and recall accuracy by executing comprehensive tests against a live LLM system's API and CLI.

Why do I need full stack validation if I already have unit tests for my API and CLI?

Full stack validation is needed because it catches integration issues that unit tests miss. While unit tests isolate components, full stack validation verifies the interaction between API, CLI, capture, triage, recall, and storage, ensuring the entire system functions correctly end-to-end.

How do I validate that captured observations are stored and recalled with accurate scoring?

To validate that captured observations are stored and recalled with accurate scoring, run comprehensive end-to-end tests against the live system. This verifies the complete data flow from capture to storage, ensuring recall mechanisms return accurate scores and handle errors correctly.