add-product-e2e-eval

Featured

Add or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.

AI & Automation 114,742 stars 19046 forks Updated today MIT

Install

View on GitHub

Quality Score: 92/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Add a Product E2E Eval Use this skill for **Product E2E Evals**: real Chromium, Paperclip server, database, runner, provider, and optionally Daytona. Everyday Workflows are in this family even when their packaged results are imported into Evalbook. Runner protocol cases against the mock control plane belong in [add-runner-eval](../add-runner-eval/SKILL.md). Locate the repository using `PAPERCLIP_ROOT` when supplied, or `git rev-parse --show-toplevel` from a checkout. From outside Git, inspect workspace roots such as `~/paperclipai/paperclip`; verify the selected root contains `tests/runner-e2e` and `packages/paperclip-runner`. Run commands from that repository root. The copied skill may live outside the checkout. Read `doc/evals.md`, then the authoritative `tests/runner-e2e/README.md`, the suite's section in `SUITES.md`, `FIXTURES.md`, `SECURITY.md`, and `EVERYDAY-WORKFLOWS.md` for the selected area. Inspect the nearest existing catalog entry, case, harness flow, matcher, evidence writer, and report test before changing anything. Keep the user journey on production browser/API surfaces; do not add private runner hooks or direct fixture database writes. Define one bounded workflow with a clear user outcome, durable state assertions, and independent evidence. Declare profile, environment, expected provider turns, timeout, cleanup, screenshots, artifact checks, and billing scope. Keep credentials and secrets out of catalog data, screenshots, fixture metadata, logs, and trac...

Details

Author
paperclipai
Repository
paperclipai/paperclip
Created
8 months ago
Last Updated
today
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category