Loading...
Loading...
Found 803 Skills
Comprehensive map and workflows for the API domain. Triggers when users ask to 'design an API', 'secure the APIs', 'update endpoints', 'view the API ecosystem', or want to see all available API orchestration skills.
DocuSeal development reference. Embed signing forms and template builder into web and mobile apps (JS/React/Vue/Angular, WebView, JWT, CSS theming). REST API with all endpoints, request/response schemas, code examples (cURL, CLI, Node.js, TypeScript, Python, Ruby, PHP, Go, C#, Java), and webhooks. Use when the user wants to integrate DocuSeal document signing or template management into their application.
Verify that a developer-run feature behaved correctly by analyzing HTTP traffic captured by Fiddler Everywhere. Always use this skill when a developer asks whether their feature's HTTP calls completed correctly, wants to see what requests a feature made, needs to debug a failed API call, is checking traffic after running a feature, wants to confirm what each endpoint returned, or asks whether anything in the traffic looks wrong — even if they don't use the word "verify" or "Fiddler". Summarizes the capture by endpoint and flags likely issues such as failed calls, missing follow-up requests, retries, auth failures, timeouts, and suspicious status-code patterns. Requires Fiddler Everywhere to be running with its MCP server enabled.
Jamie platform help — bot-free AI meeting note-taker, REST API with personal and workspace keys, webhook automations, CRM sync to HubSpot/Salesforce/Attio, MCP server for Claude/ChatGPT/Cursor. Use when setting up Jamie for a sales team, connecting Jamie webhooks to Make.com or a custom endpoint, pulling meeting transcripts and summaries via Jamie API, syncing Jamie action items to Asana or CRM, troubleshooting Jamie not recording or missing speakers, comparing Jamie pricing tiers, or configuring Jamie speaker recognition. Do NOT use for choosing between note-takers (use /sales-note-taker) or reviewing a specific call for coaching (use /sales-call-review).
Image Generation Skill: Use this skill when users need to generate images, visual infographics, create graphics, or edit/modify/adjust existing images. Based on the official formal version of the ChatGPT Image 2 model (gpt-image-2) from Apiyi Platform (https://api.apiyi.com/). This model supports precise size/quality control (including 4K) and is billed by token. Key differences from gpt-image-2-all (official reverse version): Uses /v1/images/generations and /v1/images/edits endpoints; Has explicit size parameter; Has quality parameter; Billed by token; Uses multipart/form-data to upload reference images; b64_json is pure base64 without prefix.
Ensures frontend and backend agree on API request/response shapes using Apidog MCP as the single source of truth. Replaces manual contracts.md files. Use when implementing or reviewing API endpoints and their consumers. Automatically loaded by team-lead, backend-dev, web-dev, mobile-dev, and reviewer.
Use when the user wants to extract, generate, refine, or harden an OpenAPI or Swagger specification from an existing API application, service, project, repo, routes, controllers, handlers, or codebase. Select this skill for any request whose intent is to derive, extract, generate, reverse-engineer, infer, document, or harden an OpenAPI or Swagger contract from an existing application or source code. This includes generic prompts about producing an API spec/docs/schema/contract for an existing app, project, service, repo, endpoints, routes, or controllers. Prefer this skill over extraction-only skills when the prompt is about an existing application or codebase and the expected outcome is an accurate extracted contract plus post-extraction refinement.
This skill should be used when implementing, consuming, or debugging an Open Responses-compliant API — the open standard for multi-provider LLM interoperability. Covers protocol, items, state machines, streaming events, tools, the agentic loop pattern, and extensions. Triggers on: Open Responses, open-responses, /v1/responses endpoint, multi-provider LLM API, Open Responses compliance.
Query HTX (Huobi) spot market data — tickers, klines, depth, trades, symbols, reference data. Public endpoints, no API key required.
Every Trigger.dev management endpoint, plus offline FTS over runs, span-cost rollups, and zombie-schedule detection no other tool gives you. Trigger phrases: `trigger.dev failed runs`, `trigger.dev cost rollup`, `trigger.dev schedule health`, `audit trigger.dev env vars`, `watch trigger.dev failures`, `use trigger-dev`, `run trigger-dev`.
US overnight-eligible securities directory and HK broker participant directory via Longbridge Securities. `security-list` covers the US overnight-trading catalog only (this is the only category exposed through this endpoint). `participants` is the HK broker_id ↔ name dictionary. For non-US listed-stock lookups, route the user to `longbridge-quote` for individual symbol queries. Triggers: "美股 listed", "美股 overnight", "经纪商 ID", "broker_id", "港股经纪商", "港股經紀商", "經紀商 ID", "list of US stocks", "overnight tradable", "broker directory", "participant lookup".
Generate, write, or run an ad-hoc query against SigNoz observability data — metrics, logs, traces, or exceptions — without wrapping it in a dashboard panel or alert. Make sure to use this skill whenever the user asks "show me error rates", "query logs for timeout errors", "what's the p99 latency for the cart service", "how many requests hit the payment endpoint", "find slow traces", "errors in the last hour", or otherwise asks an exploratory question that needs live observability data — even if they don't say "query" or "search" explicitly.