Agent skill

Emulate Seed

by yonatangross in yonatangross/orchestkit

Generate emulate seed configs for stateful API emulation. An agent skill from yonatangross/orchestkit.

MITAuto-check passedBackend & APIs

Install Emulate Seed

skills CLI
$ npx skills add yonatangross/orchestkit --skill emulate-seed -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install yonatangross/orchestkit emulate-seed --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/skills/emulate-seed .claude/skills/emulate-seed && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
emulate-seed
GitHub stars
290
Token cost
~4.5k tokens
SKILL.md length
1,378 words
Files
18 (incl. scripts, references)
Skills in repo
108
Repo updated
First seen
Licence
MIT

At a glance

Generate emulate seed configs for stateful API emulation. An agent skill from yonatangross/orchestkit.

  • Setting up test environments
  • SKILL.md covers New in 2026-04 (emulate 0.4.x), Auto-Discovery (M125 #4), Quick Reference and Quick Start, plus 9 more sections
  • Runs Shell scripts from its folder; calls npx, bash and stripe
  • Integration tests

What it does

Emulate Seed is an agent skill from yonatangross/orchestkit. Generate emulate seed configs for stateful API emulation. Wraps Vercel's emulate tool for GitHub, Vercel, Google OAuth, Slack, Apple Auth, Microsoft Entra, AWS, Okta, Clerk, Resend, Stripe, and MongoDB Atlas APIs — full state machines, not mocks. Use when setting up test environments, CI pipelines, integration tests, or offline development.

Its SKILL.md is about 4.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 20 other files, including scripts and reference files (for example `references/api-coverage.md`, `references/cli-reference.md` and `references/dep-to-emulator-map.json`). Compatibility notes: Claude Code 2.1.277+

It sits in Backend & APIs, covering OAuth and OpenID Connect, CI/CD and Integration testing. It works with Vercel, Stripe, Okta and Slack. The repository describes itself as: The Complete AI Development Toolkit for Claude Code. 106 skills, 36 agents, 171 hooks. Install ork for stable (v9.x), or ork-alpha for the v10 line, which ships daily. The licence is MIT.

When your agent uses it

  • Setting up test environments
  • Integration tests
  • Offline development

Example prompts

  • “/emulate-seed”

Requirements

  • Node.js
  • A Bash shell
  • Compatibility (from SKILL.md): Claude Code 2.1.277+

What it can do on your machine

Read from SKILL.md and the folder at commit 02bbf9a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • npx
    • bash
    • stripe
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Claude Code 2.1.277+

    From compatibility in the SKILL.md frontmatter.

Context cost

Emulate Seed loads about 4.5k tokens when it runs, and up to ~24k if it reads all its reference files. Until then it costs about 89 tokens; SKILL.md has 1,378 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~89
When it runs · the whole SKILL.md, loaded when a task matches
~4.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~24k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from yonatangross/orchestkit at commit 02bbf9a, republished under its MIT licence (© yonatangross). 1,378 words, ~4,491 tokens.

Download SKILL.mdSave it as .claude/skills/emulate-seed/SKILL.md (or your agent's skills folder). This skill also uses 17 other files; get the full folder from GitHub.
name
emulate-seed
description
Generate emulate seed configs for stateful API emulation. Wraps Vercel's emulate tool for GitHub, Vercel, Google OAuth, Slack, Apple Auth, Microsoft Entra, AWS, Okta, Clerk, Resend, Stripe, and MongoDB Atlas APIs — full state machines, not mocks. Use when setting up test environments, CI pipelines, integration tests, or offline development.
compatibility
Claude Code 2.1.277+
user-invocable
false
disable-model-invocation
false
context
inherit
metadata.category
testing
metadata.upstream-package
emulate
metadata.upstream-version-tested
0.12.0
metadata.version
1.3.0
metadata.author
OrchestKit
metadata.complexity
medium
metadata.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).

Emulate Seed Configs

Generate and manage seed configs for 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 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.

New in 2026-04 (emulate 0.4.x)

  • Modular @emulators/* packages — each service is its own package (@emulators/github, @emulators/stripe, etc.); top-level emulate re-exports createEmulator and the CLI.
  • 4 new services (12 total): mongoatlas:4007, okta:4008, resend:4009, stripe:4010 with drop-in seed YAML blocks.
  • Resend local inbox — GET http://localhost:4009/inbox returns captured emails for assertions without hitting a real provider.
  • Stripe hosted checkout — real session redirect flow + checkout.session.completed/expired webhook delivery, suitable for E2E payment tests.
  • MongoDB Atlas — Admin API v2 (projects/clusters/DB users) + Data API v1 with full CRUD + aggregate.
  • Okta OIDC — full discovery, JWKS, authorize/token/userinfo/revoke/introspect plus Users/Groups/Apps CRUD.
  • Entra / Apple / Slack expansions (v0.4.0) — PKCE + refresh rotation (Entra), RS256 JWKS (Apple), OAuth v2 consent UI (Slack).
  • @emulators/adapter-next — catch-all Next.js route handler runs emulators on the same origin as the app; fixes OAuth callback URL drift on Vercel preview deploys.

Auto-Discovery (M125 #4)

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:

ModeBehavior
(default)Report matched deps + emulator union on stderr; do not write
--jsonEmit machine-readable JSON instead of human report
--applyWrite emulate.config.yaml (refuses to overwrite without --force)
bash
$ 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.

Quick Reference

CategoryRulesImpactWhen to Use
Seed Config1HIGHSetting up emulate.config.yaml for test environments
Service Selection1MEDIUMChoosing GitHub/Vercel/Google for your tests
Webhook Setup1MEDIUMTesting webhook delivery with HMAC verification
Parallel CI1HIGHRunning tests in parallel without port collisions
Auth Tokens1MEDIUMSeeding tokens mapped to emulated users

Total: 5 rules across 5 categories

Quick Start

bash
# 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

Services (0.10.0 — 14 emulators)

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 repository contents and commit history (GET /repos/:owner/:repo/readme, GET/PUT/DELETE /repos/:owner/:repo/contents/:path where writes produce real commits, GET /repos/:owner/:repo/commits, and GET /repositories/:id by numeric ID); a readonly generatedSecrets array on the Emulator object with a new exported GeneratedSecret type; GitHub App JWT verification now accepts PKCS#8 as well as PKCS#1 keys. Provider count unchanged.

All backwards-compatible, with one behaviour change worth knowing: 0.10.0 switched Stripe webhook deliveries to Stripe's own Stripe-Signature header format. Upstream files it under bug fixes rather than breaking changes, but a test asserting the old GitHub-style sha256= header on a Stripe delivery will now fail. See Webhook Delivery below for both formats.

ServiceDefault PortCoverage
Vercel:4000Projects, deployments, domains, env vars, teams
GitHub:4001Repos, PRs, issues, comments, reviews, Actions, webhooks, orgs, teams
Google OAuth:4002OAuth 2.0 authorize, token exchange, userinfo
Slack:4003Chat, conversations, users, reactions, OAuth v2 with consent UI
Apple Auth:4004Sign in with Apple — OIDC discovery, JWKS (RS256), auth flow, token exchange
Microsoft Entra:4005OAuth 2.0/OIDC v2.0, authorization code + PKCE, refresh token rotation, v1 token endpoint, Graph /users/{id}
AWS:4006S3 buckets, SQS queues, IAM users/roles, STS identity
MongoDB Atlas (0.4+):4007Admin API v2 (projects, clusters, DB users) + Data API v1 (full CRUD + aggregate)
Okta (0.4+):4008OIDC discovery, JWKS, authorize/token/userinfo/revoke/introspect, Users/Groups/Apps CRUD
Resend (0.4+):4009Send + batch (100/req), list/retrieve/cancel, domains, API keys, audiences, contacts, local inbox (GET /inbox)
Stripe (0.4+):4010Customers, payment methods, customer sessions, payment intents, charges, products, prices, hosted checkout session w/ webhook delivery
Clerk (0.5+)(on-demand)Users, sessions, organizations
Linear (0.7+)(on-demand)Orgs, teams, issues, cycles, webhooks
Twilio (0.8+)(on-demand)Accounts, phone numbers, messages, calls, conversations, messaging services, Verify flows, simulator endpoints

See references/api-coverage.md for full endpoint lists.

Next.js Adapter (0.4+) — @emulators/adapter-next

Runs emulators on the same origin as your Next.js app via a catch-all route handler. Fixes the OAuth callback URL drift problem on Vercel preview deploys — no more http://localhost:4001 redirect mismatches.

typescript
// next.config.js
const { withEmulate } = require('@emulators/adapter-next')
module.exports = withEmulate({ /* your next config */ })

// app/api/[...emulate]/route.ts
import { createEmulateHandler } from '@emulators/adapter-next'
export const { GET, POST } = createEmulateHandler({
  services: ['github', 'stripe', 'resend'],
  persistence: { /* load(), save() or built-in filePersistence */ },
})
Show full SKILL.md (544 more words)Show less

Seed Config Structure

A seed config pre-populates the emulator with tokens, users, repos, and projects so tests start from a known state.

yaml
# emulate.config.yaml
tokens:
  dev_token:
    login: yonatangross
    scopes: [repo, workflow, admin:org]
  ci_token:
    login: ci-bot
    scopes: [repo]

github:
  users:
    - login: yonatangross
      name: Yonatan Gross
    - login: ci-bot
      name: CI Bot
  repos:
    - owner: yonatangross
      name: my-project
      private: false
      default_branch: main
      topics: [typescript, testing]

vercel:
  users:
    - username: yonatangross
      email: yonaigross@gmail.com
  projects:
    - name: my-docs
      framework: next

# NEW in 0.4.x — drop-in seed blocks
okta:
  users:
    - login: alice@example.com
      firstName: Alice
      lastName: Smith
  groups: [{ name: Everyone }, { name: Admins }]
  apps: [{ name: My Web App }]
  authorization_servers:
    - name: default
      audiences: ["api://default"]

resend:
  domains: [{ name: example.com }]
  api_keys: [{ name: default }]
  # In tests: GET http://localhost:4009/inbox to assert captured emails

stripe:
  customers:
    - name: Test Customer
      email: customer@example.com
  products: [{ name: Pro Plan }, { name: Starter Plan }]
  prices:
    - { product: Pro Plan, unit_amount: 4900, currency: usd, recurring: { interval: month } }
    - { product: Starter Plan, unit_amount: 1900, currency: usd, recurring: { interval: month } }
  # Webhook delivery fires on checkout.session.completed / expired

mongoatlas:
  projects: [{ name: my-project }]
  clusters: [{ project: my-project, name: my-cluster }]
  database_users: [{ project: my-project, username: app-user }]

See rules/seed-config.md for full schema and best practices.

Programmatic SDK

Service packages live under the @emulators/* scope (e.g., @emulators/github, @emulators/stripe). The programmatic API (createEmulator) is exported from the top-level emulate package.

typescript
import { createEmulator } from 'emulate'

const github = await createEmulator({ service: 'github', port: 4001 })
// github.url -> 'http://localhost:4001'

// State is real — create a PR and it appears in the list
const res = await fetch(`${github.url}/repos/org/repo/pulls`, {
  method: 'POST',
  headers: { Authorization: 'Bearer dev_token' },
  body: JSON.stringify({ title: 'Test PR', head: 'feature', base: 'main' })
})

const prs = await fetch(`${github.url}/repos/org/repo/pulls`)
// -> includes the PR we just created

// Auto-generated credentials (0.10.0+): readonly GeneratedSecret[], each
// { service, kind, id, label, value }. A GitHub App emulator, for example,
// generates its own RSA key rather than making you supply one.
github.generatedSecrets

// Cleanup
github.reset()       // Synchronous state wipe
await github.close() // Shut down server

seed here is a parsed object, not a path. Only the CLI --seed flag takes a filename. For multi-service setup, lifecycle hooks, and the Vitest/Jest wiring, see references/upstream.md. For the ork-side corrections to that API, see references/ork-delta.md.

Webhook Delivery

Emulate delivers real webhooks with HMAC-SHA256 signatures when state changes. The signature FORMAT is per-provider, so one generic verifier does not cover every service. GitHub-format headers remain the default; Stripe has used its own format since 0.10.0.

typescript
import crypto from 'crypto'

// GitHub format (the default for most services): sha256=<hmac over the raw body>
function verifyWebhook(payload: string, signature: string, secret: string): boolean {
  const expected = 'sha256=' + crypto
    .createHmac('sha256', secret)
    .update(payload)
    .digest('hex')
  return crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected))
}

// Stripe format, as of emulate 0.10.0: Stripe-Signature: t=<timestamp>,v1=<hmac>,
// where the HMAC covers `<timestamp>.<raw body>`, NOT the body alone. Verifying a
// Stripe delivery with the GitHub helper above fails on both counts.
function verifyStripeWebhook(rawBody: string, header: string, secret: string): boolean {
  const parts = Object.fromEntries(header.split(',').map((kv) => kv.split('=')))
  const expected = crypto
    .createHmac('sha256', secret)
    .update(`${parts.t}.${rawBody}`)
    .digest('hex')
  return crypto.timingSafeEqual(Buffer.from(parts.v1), Buffer.from(expected))
}

See rules/webhook-setup.md for webhook receiver patterns.

CI Integration

yaml
# .github/workflows/test.yml
jobs:
  test:
    steps:
      - uses: actions/checkout@v4
      - name: Start emulate
        run: npx emulate --service github --seed .emulate/ci.yaml &
      - name: Wait for emulate
        run: sleep 2
      - name: Run tests
        run: npm test
        env:
          GITHUB_API_BASE: http://localhost:4001
          VERCEL_API_BASE: http://localhost:4000
Parallel Test Execution

Each test worker gets its own port to avoid race conditions:

typescript
// vitest.config.ts
const workerPort = 4001 + parseInt(process.env.VITEST_WORKER_ID || '0')

See rules/parallel-ci.md for full parallel isolation patterns.

Decision Matrix

ToolWhen to UseStateful?Platforms
emulate (FIRST CHOICE)GitHub/Vercel/Google/Slack/Apple/Entra/AWS/Okta/Resend/Stripe/MongoDB/Clerk/Linear testingYESAll 13 services
PactContract verification between servicesNoAny
MSWIn-browser/Node HTTP mockingNoAny
NockNode.js HTTP interceptNoAny
WireMockHTTP stub serverPartialAny

Use emulate when:

  • Testing code that calls GitHub, Vercel, Google, Slack, Apple, Entra, AWS, Okta, Resend, Stripe, MongoDB Atlas, Clerk, or Linear
  • You need state persistence across multiple API calls in a test
  • You want webhook delivery with real HMAC signatures (GitHub, Stripe)
  • You need cascading side-effects (delete repo -> PRs cascade-delete)
  • You need to assert on sent emails without hitting a real provider (Resend local /inbox)
  • You need hosted Stripe checkout sessions with real redirect flow in tests

Use MSW/Nock when:

  • Mocking arbitrary HTTP APIs not covered by emulate
  • You need in-browser interception (MSW)
  • Tests only need single request/response pairs

Upstream coverage (do not restate)

This skill is a wrap plus our delta. emulate ships its own per-service reference docs; copying them here only produces something that goes stale on the next release. If a topic below comes up, read the first-party source, not a paraphrase.

TopicFirst-party source
Programmatic API (createEmulator, url, reset(), close()), Vitest/Jest wiring, config auto-detection order, token fallbackreferences/upstream.md (synced from vercel-labs/emulate, skills/emulate/SKILL.md)
GitHub endpoint recipes, GitHub App JWT seeding, Octokit and Auth.js base-URL wiring, GitHub OAuth flowhttps://github.com/vercel-labs/emulate/blob/main/skills/github/SKILL.md
Google OIDC discovery, JWKS, authorize/token/userinfo/revoke, PKCE, google-auth-library, Passport, openid-clienthttps://github.com/vercel-labs/emulate/blob/main/skills/google/SKILL.md
Vercel endpoint recipes, cursor pagination, team scoping, integration OAuth flowhttps://github.com/vercel-labs/emulate/blob/main/skills/vercel/SKILL.md
Every other emulator (Slack, Apple, Entra, AWS, Okta, Resend, Stripe, MongoDB Atlas, Clerk, Linear, Twilio)https://github.com/vercel-labs/emulate/tree/main/skills

What stays ours: references/ork-delta.md (the corrections and house conventions that are not in any vendor doc), references/cli-reference.md, references/api-coverage.md, references/dep-to-emulator-map.json, scripts/auto-discover.sh, and everything in rules/.

Read references/ork-delta.md before copying any snippet out of a vendor doc. It records the two API facts vendor prose does not spell out (the exported factory is createEmulator, and seed in the programmatic options is an object rather than a path) plus the *_API_BASE env-var convention this repo uses instead of the vendor's *_EMULATOR_URL.

  • testing-integration — Integration test patterns (emulate as first choice for API tests)
  • testing-e2e — End-to-end test patterns with emulated backends
  • testing-unit — Unit test patterns (use emulate for API-dependent units)
  • security-patterns — Auth token patterns (emulate token seeding)

CLI Reference

See references/cli-reference.md for all CLI flags and commands.

© yonatangross, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 17 other files (scripts, references) in src/skills/emulate-seed of yonatangross/orchestkit.

  • SKILL.md
  • references/api-coverage.md
  • references/cli-reference.md
  • references/dep-to-emulator-map.json
  • references/ork-delta.md
  • references/upstream-github.md
  • references/upstream-google.md
  • references/upstream-vercel.md
  • references/upstream.md
  • rules/_sections.md
  • rules/_template.md
  • rules/auth-tokens.md
  • rules/parallel-ci.md
  • rules/seed-config.md
  • rules/service-selection.md
  • rules/webhook-setup.md
  • scripts/auto-discover.sh
  • test-cases.json

Open the folder on GitHubat commit 02bbf9a

Compare with similar skills

Emulate Seed next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Emulate Seed compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Emulate Seed this skillyonatangross/orchestkit290—~4.5kAutomated safety check: PassMIT
Add OAuth Integrationrome-os/rome737—~3.6kAutomated safety check: PassMIT
Validate OAuth Integrationrome-os/rome737—~2kAutomated safety check: NotesMIT
Chat SDKvercel/vercel-plugin301—~2.9kAutomated safety check: PassCustom licence
Stripe Best Practiceskanchengw/cnllm1752 repos~925Automated safety check: PassApache-2.0
GitHub OAuth Nango IntegrationAgentWorkforce/relay8671 repos~3.4kAutomated safety check: PassApache-2.0

Similar skills

  • Add a new Rome-managed OAuth integration for a third-party service so a user can delegate access by clicking Connect, and Rome can act on the service with the delegated token (the GitHub/Slack model…

    737 GitHub stars~3.6k tokensUpdated today
    Backend & APIsAuto-check passed
  • Validate a Rome-managed OAuth integration end-to-end — prove a user can click Connect and Rome ends up holding a delegated token it can use to call the provider's API.

    737 GitHub stars~2k tokensUpdated today
    Backend & APIsAuto-check: notes
  • Chat SDK

    vercel/vercel-plugin

    Official

    Vercel Chat SDK expert guidance. An agent skill from vercel/vercel-plugin.

    301 GitHub stars~2.9k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Stripe Best Practices

    kanchengw/cnllm

    Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial…

    175 GitHub starsUsed in 2 repos~925 tokens
    Backend & APIsAuto-check passed
  • GitHub OAuth Nango Integration

    AgentWorkforce/relay

    A skill your agent uses when implementing GitHub OAuth + GitHub App authentication with Nango - provides two-connection pattern for user login and repo access with webhook handling

    867 GitHub starsUsed in 1 repo~3.4k tokens
    Backend & APIsAuto-check passed
  • Emulate

    UsefulSoftwareCo/executor

    Use the @executor-js/emulate service emulators (GitHub, Google, Stripe, Resend, WorkOS, …) to test integrations for real — full OpenAPI specs, working OAuth flows, mintable credentials, and a…

    4.1k GitHub stars~2.2k tokensUpdated today
    Backend & APIsAuto-check: notes

More from yonatangross/orchestkit

All 108 skills in this repo
  • API Design

    yonatangross/orchestkit

    API contract design for REST and GraphQL, covering resource shape, URL and header versioning with deprecation windows, RFC 9457 Problem Details error handling, and OpenAPI specs.

    290 GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Architecture Decision Record

    yonatangross/orchestkit

    ADR templates in the Nygard format with context, decision, consequences, and alternatives.

    290 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Audit Full

    yonatangross/orchestkit

    Single-pass codebase analysis leveraging a 1M-token context window for comprehensive security scanning, architecture review, and dependency auditing.

    290 GitHub stars~3.5k tokensUpdated today
    Auto-check: notes
  • Code Review Playbook

    yonatangross/orchestkit

    Structured review processes, conventional comments, language-specific checklists, and feedback templates.

    290 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Create PR

    yonatangross/orchestkit

    Creates GitHub pull requests with pre-flight validation, conventional title formatting, and structured summary generation.

    290 GitHub stars~4.5k tokensUpdated today
    Auto-check: notes
  • Explore

    yonatangross/orchestkit

    Multi-angle codebase exploration spawning 3-5 parallel agents for code structure, data flow, architecture patterns, and health assessment.

    290 GitHub stars~3.9k tokensUpdated today
    Auto-check: notes

Questions about Emulate Seed

What does Emulate Seed do?

Generate emulate seed configs for stateful API emulation. An agent skill from yonatangross/orchestkit. Emulate Seed is an agent skill from yonatangross/orchestkit. Generate emulate seed configs for stateful API emulation.

When should I use Emulate Seed?

Emulate Seed fits situations like: setting up test environments; integration tests; offline development.

How do I install Emulate Seed in Claude Code?

Run `npx skills add yonatangross/orchestkit --skill emulate-seed -a claude-code`. Or copy the skill folder (src/skills/emulate-seed in yonatangross/orchestkit) into .claude/skills/emulate-seed in your project. Claude Code loads it when a task matches its description.

How do I install Emulate Seed in Codex?

Run `npx skills add yonatangross/orchestkit --skill emulate-seed -a codex`. Or copy the skill folder (src/skills/emulate-seed in yonatangross/orchestkit) into .agents/skills/emulate-seed in your project. Codex loads it when a task matches its description.

Can I use Emulate Seed in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yonatangross/orchestkit --skill emulate-seed -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/emulate-seed, .gemini/skills/emulate-seed, .github/skills/emulate-seed and .opencode/skills/emulate-seed in your project.

What does Emulate Seed need to run?

Going by SKILL.md and its folder, Emulate Seed needs a shell for the scripts in its folder and the command-line tools its instructions call (npx, bash, stripe and npm). Our summary lists: Node.js; A Bash shell. Compatibility (from SKILL.md): Claude Code 2.1.277+.

Does Emulate Seed access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Emulate Seed safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Emulate Seed use?

Emulate Seed is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Emulate Seed use?

About 4.5k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 20k tokens, read only when the agent opens those files.

What are the alternatives to Emulate Seed?

Skills that share tags, products or a category with Emulate Seed: Add OAuth Integration (rome-os/rome, 737 stars), Validate OAuth Integration (rome-os/rome, 737 stars), Chat SDK (vercel/vercel-plugin, 301 stars) and Stripe Best Practices (kanchengw/cnllm, 175 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Emulate Seed?

yonatangross (a GitHub user) maintains it in yonatangross/orchestkit, which has 290 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on October 9, 2026.

Source: yonatangross/orchestkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.