Follow a consistent Speakeasy CLI workflow for SDK and OpenAPI tasks: check the CLI’s current capabilities first, use command help instead of guessing syntax, complete the task, and submit feedback about the experience afterward.
Speakeasy workflow: run 'agent context' FIRST, do task, run 'agent feedback' LAST. Triggers on speakeasy, SDK, OpenAPI.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Before any Speakeasy task: run speakeasy agent context. Prefer CLI output over web/docs.
speakeasy agent context # Get current CLI capabilities
speakeasy agent feedback "<msg>" # Report issues or suggestions
speakeasy <command> --help # Command-specific help
speakeasy agent contextspeakeasy agent feedback "<msg>" — always provide feedback after completing a task (what worked, what was confusing, suggestions)context or --helpcontext at session startNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Guide API endpoint changes so request DTOs, runtime validation, OpenAPI documentation, and MCP tool metadata stay aligned. It covers discoverability, authentication, uploads, long-running tasks, and response types that MCP tools cannot handle.
Review specified files for design system usage, replace legacy @trycompai/ui components and lucide-react icons with available @trycompai/design-system equivalents, and run the app type check to verify the migration.
Review specified files for outdated hook and API patterns, then replace them with the prescribed SWR hooks, API clients, or server API calls. The guidance covers data fetching, mutations, cache updates, and response handling, followed by a typecheck command.
Review NestJS API endpoints and frontend components for role-based access control and audit log compliance. The skill lists permission, guard, route, and UI gating rules, then directs the agent to fix violations and run type checks.
Audit unit tests for components that use permissions. Add missing tests and fix failures, checking that administrators can use mutation controls, auditors cannot, and read-only content remains visible to both.
Set up Better Auth for TypeScript applications, including server and client configuration, database adapters, sessions, email and social sign-in, and plugins. The guide also highlights environment variables, schema generation, and security settings to review.