ork-assess
Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a…
Seed configs for Vercel emulate: stateful GitHub, Vercel, Google, Slack, Stripe, AWS and more, not mocks. Use when setting up test environments, CI or offline development.
Claude Code
$ npx -y skills add yonatangross/orchestkit --skill emulate-seed --agent claude-code
Codex
$ npx skills add yonatangross/orchestkit --skill emulate-seed -a codex -y
Cursor
$ npx skills add yonatangross/orchestkit --skill emulate-seed -a cursor -y
Gemini CLI
$ npx skills add yonatangross/orchestkit --skill emulate-seed -a gemini-cli -y
GitHub Copilot
$ npx skills add yonatangross/orchestkit --skill emulate-seed -a github-copilot -y
OpenCode
$ npx skills add yonatangross/orchestkit --skill emulate-seed -a opencode -y
Windsurf
$ npx skills add yonatangross/orchestkit --skill emulate-seed -a windsurf -y
name: emulate-seed compatibility: "Claude Code 2.1.277+" description: "Seed configs for Vercel emulate: stateful GitHub, Vercel, Google, Slack, Stripe, AWS and more, not mocks. Use when setting up test environments, CI or offline development." user-invocable: false disable-model-invocation: false context: inherit metadata: category: testing upstream-package: emulate upstream-version-tested: "0.12.0" version: "1.3.0" author: "OrchestKit" complexity: "medium" tags: "emulate, testing, api-emulation, github, vercel, google, stripe, resend, okta, clerk, mongodb, seed, ci, stateful-testing"
Upstream version reference: `emulate` 0.12.0 (2026-09-30).
Generate and manage seed configs for [emulate](https://github.com/vercel-labs/emulate) (Apache-2.0) — Vercel Labs' stateful API emulation tool. Each category has individual rule files in `rules/` loaded on-demand.
> **Paired agent:** This skill pairs with the [`emulate-engineer`](../../agents/emulate-engineer.md) subagent (`subagent_type: "ork:emulate-engineer"`). When a task involves generating a full emulate config from scratch, webhook HMAC setup, CI pipeline integration, or parallel-worker port isolation, spawn the agent rather than handling it inline — it has the full 13-emulator service-port matrix and seed-rules in context.
**Not mocks.** Emulate provides full state machines with cascading deletes, cursor pagination, webhook delivery, and HMAC signature verification. Create a PR via the API and it appears in `GET /repos/:owner/:repo/pulls`. Delete a repo and its issues, PRs, and webhooks cascade-delete.
`scripts/auto-discover.sh` scans the project's `package.json`, matches deps against `references/dep-to-emulator-map.json`, and either reports the matches or writes `emulate.config.yaml`. Three modes:
| Mode | Behavior | |---|---| | (default) | Report matched deps + emulator union on stderr; do not write | | `--json` | Emit machine-readable JSON instead of human report | | `--apply` | Write `emulate.config.yaml` (refuses to overwrite without `--force`) |
$ bash "${CLAUDE_SKILL_DIR}/scripts/auto-discover.sh"
emulate-seed --auto — scanning /path/to/package.json
Detected:
@octokit/rest → github · Any GitHub API client
next-auth → google-oauth, apple-auth, microsoft-entra · Default OAuth providers
stripe → stripe
@vercel/blob → aws · @vercel/blob is S3-compatible
Union: apple-auth, aws, github, google-oauth, microsoft-entra, stripe
$ bash "${CLAUDE_SKILL_DIR}/scripts/auto-discover.sh" --apply
…
✓ Wrote /path/to/emulate.config.yaml with 6 service(s)Multi-emulator deps default to all reasonable providers; the user prunes the YAML afterwards. Unmapped deps are silently skipped — extending coverage is a docs PR (edit `references/dep-to-emulator-map.json`), not a code change.
`dev` reads the resulting `emulate.config.yaml` at boot — see `src/skills/dev/scripts/boot.sh`.
| Category | Rules | Impact | When to Use | |----------|-------|--------|-------------| | [Seed Config](#seed-config) | 1 | HIGH | Setting up emulate.config.yaml for test environments | | [Service Selection](#service-selection) | 1 | MEDIUM | Choosing GitHub/Vercel/Google for your tests | | [Webhook Setup](#webhook-setup) | 1 | MEDIUM | Testing webhook delivery with HMAC verification | | [Parallel CI](#parallel-ci) | 1 | HIGH | Running tests in parallel without port collisions | | [Auth Tokens](#auth-tokens) | 1 | MEDIUM | Seeding tokens mapped to emulated users |
**Total: 5 rules across 5 categories**
# Install (packages published under @emulators/* scope) npm install --save-dev emulate # Start all services npx emulate # Start specific services with seed data npx emulate --service github,stripe --seed ./emulate.config.yaml # Generate a starter config npx emulate init --service github
> **New across releases:** > - **0.5.0** — added Clerk, MongoDB Atlas, Stripe, Resend, and Okta emulators; portless integration (embedded emulators without dedicated ports); Google OAuth `hd` claim support; Stripe Checkout + Resend magic link examples; AWS S3 emulator now matches the official SDK wire format. > - **0.6.0** — expanded Slack (OAuth v2 consent UI, conversations/reactions). > - **0.6.1** — Vercel Blob store. > - **0.7.0** — added Linear (13th provider): stateful orgs/teams/issues/cycles + webhooks. > - **0.8.0** — added Twilio (14th provider): accounts, phone numbers, messages, calls, conversations, messaging services, Verify flows, and simulator endpoints, with a Next.js SMS-verification example. > - **0.9.0** — added a Nuxt emulator adapter (alongside the Next.js adapter); provider count unchanged. > - **0.10.0** — stateful GitHub reposito
The Complete AI Development Toolkit for Claude Code. 115 skills, 36 agents, 163 hooks. Install `ork` for stable (v10.x).
Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a…
Compare plausible implementation, architecture, product, or operational approaches before committing to one. Use when a request…
Map an unfamiliar codebase, feature, architecture, data flow, or operational path with file-backed evidence. Use when a request…
Render an answer inline as compact ASCII or box-drawing art with semantic status icons. Use for status, inventories, budgets,…
Make an approved, scoped change and prove the affected behavior. Use when a request asks to implement, build, add, or land a…
Review a pull request or branch for correctness, regressions, security, operational risk, and missing evidence. Use when a…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.