How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

asas-testing-verification - Skill

Name: asas-testing-verification
Author: asas-erp-saas-1

Imported from asas-erp-saas-1/As (docs/engineering-history/branches/056-platform-architecture-2026/docs/engineering-history/branches/054-platform-architecture-2026/docs/engineering-history/branches/051-platform-architecture-2026/engineering-history/branch-snapshots/048--chore--consolidation-promotion-2026-10-16/.agents/skills/asas-testing-verification/SKILL.md). Install upstream with npx skills add asas-erp-saas-1/As --skill asas-testing-verification. Copyright stays with the author.

Testing and Verification

Principle

The implementing agent is not the sole evidence for correctness. Verification must be fresh and adversarial for material changes.

Test layers

Use the smallest sufficient combination of:

static/type/lint checks;
unit tests;
domain invariant tests;
state-machine legal/illegal transition tests;
integration tests;
database constraint tests;
RLS/tenant tests;
authorization tests;
event/outbox/idempotency tests;
concurrency/race tests;
API contract/webhook tests;
E2E/browser tests;
accessibility tests;
visual regression;
migration replay/rollback evidence;
performance/recovery tests when applicable.

Critical commercial loop

Trace and test: Project → Building → Unit → Lead → Assignment → Activity → Visit → Offer → Reservation → Contract → Payment Plan → Payment/Receipt → Audit → Reporting.

Verification status

Use only: VERIFIED / FAILED / BLOCKED / NOT_EXECUTED.

A passing typecheck is not domain verification. A screenshot is not interaction verification. Documentation is not runtime evidence.

Evidence

Record exact commands, inputs, outputs, commit and artifact references for material closure. Never invent missing evidence.

Install asas-testing-verification and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "asas-erp-saas-1-as-asas-testing-verification", "kind": "skill", "name": "asas-testing-verification", "description": "Independently verify ASAS implementation through unit, integration, contract, state, concurrency, security, RLS, E2E and visual evidence.", "publisher": "asas-erp-saas-1", "version": "1.0.0", "capabilities": { "domains": [ "coding", "legal" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Independently verify ASAS implementation through unit, integration, contract, state, concurrency, security, RLS, E2E and visual evidence." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/asas-erp-saas-1/As", "path": "docs/engineering-history/branches/056-platform-architecture-2026/docs/engineering-history/branches/054-platform-architecture-2026/docs/engineering-history/branches/051-platform-architecture-2026/engineering-history/branch-snapshots/048--chore--consolidation-promotion-2026-10-16/.agents/skills/asas-testing-verification/SKILL.md", "ref": "2672247aab8ce830091db1df83d1b233aa88d17f", "url": "https://github.com/asas-erp-saas-1/As/blob/2672247aab8ce830091db1df83d1b233aa88d17f/docs/engineering-history/branches/056-platform-architecture-2026/docs/engineering-history/branches/054-platform-architecture-2026/docs/engineering-history/branches/051-platform-architecture-2026/engineering-history/branch-snapshots/048--chore--consolidation-promotion-2026-10-16/.agents/skills/asas-testing-verification/SKILL.md", "key": "asas-erp-saas-1/As/docs/engineering-history/branches/056-platform-architecture-2026/docs/engineering-history/branches/054-platform-architecture-2026/docs/engineering-history/branches/051-platform-architecture-2026/engineering-history/branch-snapshots/048--chore--consolidation-promotion-2026-10-16/.agents/skills/asas-testing-verification/SKILL.md" } }, "instructions": "# Testing and Verification\n\n## Principle\n\nThe implementing agent is not the sole evidence for correctness. Verification must be fresh and adversarial for material changes.\n\n## Test layers\n\nUse the smallest sufficient combination of:\n- static/type/lint checks;\n- unit tests;\n- domain invariant tests;\n- state-machine legal/illegal transition tests;\n- integration tests;\n- database constraint tests;\n- RLS/tenant tests;\n- authorization tests;\n- event/outbox/idempotency tests;\n- concurrency/race tests;\n- API contract/webhook tests;\n- E2E/browser tests;\n- accessibility tests;\n- visual regression;\n- mi", "cost": { "context_tokens": 308 } }

asas-testing-verification

About

Testing and Verification

Principle

Test layers

Critical commercial loop

Verification status

Evidence

Use it

Install asas-testing-verification and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews