response-compliance
OpenResponses API compliance testing. Use when testing the Response API endpoint, running compliance tests, or debugging Response API schema issues. Triggers on 'compliance', 'response api test', 'openresponses test'.
Best use case
response-compliance is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
OpenResponses API compliance testing. Use when testing the Response API endpoint, running compliance tests, or debugging Response API schema issues. Triggers on 'compliance', 'response api test', 'openresponses test'.
Teams using response-compliance should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/response-compliance/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How response-compliance Compares
| Feature / Agent | response-compliance | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
OpenResponses API compliance testing. Use when testing the Response API endpoint, running compliance tests, or debugging Response API schema issues. Triggers on 'compliance', 'response api test', 'openresponses test'.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
SKILL.md Source
# OpenResponses Compliance Test Run the official OpenResponses compliance test suite against the local (or remote) Response API endpoint. ## Quick Start ```bash # From the openapi package directory cd lobehub/packages/openapi # Run all tests (dev mode, localhost:3010) APP_URL=http://localhost:3010 bun run test:response-compliance -- \ --auth-header "lobe-auth-dev-backend-api" --no-bearer --api-key 1 # Run specific tests only APP_URL=http://localhost:3010 bun run test:response-compliance -- \ --auth-header "lobe-auth-dev-backend-api" --no-bearer --api-key 1 \ --filter basic-response,streaming-response # Verbose mode (shows request/response details) APP_URL=http://localhost:3010 bun run test:response-compliance -- \ --auth-header "lobe-auth-dev-backend-api" --no-bearer --api-key 1 -v # JSON output (for CI) APP_URL=http://localhost:3010 bun run test:response-compliance -- \ --auth-header "lobe-auth-dev-backend-api" --no-bearer --api-key 1 --json ``` ## Prerequisites - Dev server running with `ENABLE_MOCK_DEV_USER=true` in `.env` - The `api/v1/responses` route registered (via `src/app/(backend)/api/v1/[[...route]]/route.ts`) ## Auth Modes | Mode | Flags | | --------------- | ------------------------------------------------------------------- | | Dev (mock user) | `--auth-header "lobe-auth-dev-backend-api" --no-bearer --api-key 1` | | API Key | `--api-key lb-xxxxxxxxxxxxxxxx` | | Custom | `--auth-header <name> --api-key <value>` | ## Test IDs Available `--filter` values: | ID | Description | Related Issue | | -------------------- | -------------------------------------- | ------------- | | `basic-response` | Simple text generation (non-streaming) | LOBE-5858 | | `streaming-response` | SSE streaming lifecycle + events | LOBE-5859 | | `system-prompt` | System role message handling | LOBE-5858 | | `tool-calling` | Function tool definition + call output | LOBE-5860 | | `image-input` | Multimodal image URL content | — | | `multi-turn` | Conversation history via input items | LOBE-5861 | ## Environment Variables | Variable | Default | Description | | --------- | ----------------------- | ----------------------------------------- | | `APP_URL` | `http://localhost:3010` | Server base URL (auto-appends `/api/v1`) | | `API_KEY` | — | API key (alternative to `--api-key` flag) | ## How It Works The script (`lobehub/packages/openapi/scripts/compliance-test.sh`) clones the official [openresponses/openresponses](https://github.com/openresponses/openresponses) repo into `scripts/openresponses-compliance/` (gitignored) and runs its CLI test runner. First run clones; subsequent runs update from upstream. ## Debugging Failures 1. Run with `-v` to see full request/response payloads 2. Common failure patterns: - **"Failed to parse JSON"**: Auth failed, server returned HTML redirect - **"Response has no output items"**: LLM execution not yet implemented - **"Expected number, received null"**: Missing required field in response schema - **"Invalid input"**: Zod validation on response schema — check field format ## Key Files - **Types**: `lobehub/packages/openapi/src/types/responses.type.ts` - **Service**: `lobehub/packages/openapi/src/services/responses.service.ts` - **Controller**: `lobehub/packages/openapi/src/controllers/responses.controller.ts` - **Route**: `lobehub/packages/openapi/src/routes/responses.route.ts` - **Test script**: `lobehub/packages/openapi/scripts/compliance-test.sh` - **Cloud route**: `src/app/(backend)/api/v1/[[...route]]/route.ts`
Related Skills
\<task_skill_guides>
You are executing a task within the LobeHub task system. Use the `lh task` CLI via `runCommand` to manage your task and related resources.
zustand
Zustand state management guide. Use when working with store code (src/store/**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.
version-release
Version release workflow. Use when the user mentions 'release', 'hotfix', 'version upgrade', 'weekly release', or '发版'/'发布'/'小班车'. Provides guides for Minor Release and Patch Release workflows.
upstash-workflow
Upstash Workflow implementation guide. Use when creating async workflows with QStash, implementing fan-out patterns, or building 3-layer workflow architecture (process → paginate → execute).
typescript
TypeScript code style and optimization guidelines. MUST READ before writing or modifying any TypeScript code (.ts, .tsx, .mts files). Also use when reviewing code quality or implementing type-safe patterns. Triggers on any TypeScript file edit, code style discussions, or type safety questions.
trpc-router
TRPC router development guide. Use when creating or modifying TRPC routers (src/server/routers/**), adding procedures, or working with server-side API endpoints. Triggers on TRPC router creation, procedure implementation, or API endpoint tasks.
testing
Testing guide using Vitest. Use when writing tests (.test.ts, .test.tsx), fixing failing tests, improving test coverage, or debugging test issues. Triggers on test creation, test debugging, mock setup, or test-related questions.
store-data-structures
Zustand store data structure patterns for LobeHub. Covers List vs Detail data structures, Map + Reducer patterns, type definitions, and when to use each pattern. Use when designing store state, choosing data structures, or implementing list/detail pages.
spa-routes
MUST use when editing src/routes/ segments, src/spa/router/desktopRouter.config.tsx or desktopRouter.config.desktop.tsx (always change both together), mobileRouter.config.tsx, or when moving UI/logic between routes and src/features/.
recent-data
Guide for using Recent Data (topics, resources, pages). Use when working with recently accessed items, implementing recent lists, or accessing session store recent data. Triggers on recent data usage or implementation tasks.
react
React component development guide. Use when working with React components (.tsx files), creating UI, using @lobehub/ui components, implementing routing, or building frontend features. Triggers on React component creation, modification, layout implementation, or navigation tasks.
project-overview
Complete project architecture and structure guide. Use when exploring the codebase, understanding project organization, finding files, or needing comprehensive architectural context. Triggers on architecture questions, directory navigation, or project overview needs.