Loading...
Loading...
Found 9,857 Skills
24 deterministic Three.js skills covering WebGL, WebGPU, React Three Fiber, Drei, physics, and IFC (architecture/BIM workflows). Built by the Open AEC Foundation for architecture and engineering workflows on top of 3D web rendering.
Use when explicitly invoked, when reducing agent-workflow cost, or when a concrete deliverable requires no narration, final only, code only, findings only, or minimal output.
Configure GSD settings — workflow toggles, advanced knobs, integrations, and model profile
Create, improve, or audit Vapi voice agent and Squad system prompts for production phone and web based voice agents. Use when the user wants help designing a Vapi assistant prompt, multi-assistant Squad prompt set, refining an existing prompt, creating prompt sections, building an intake or handoff workflow, improving tool-use instructions, adding guardrails, or optimizing voice-agent behavior for brevity, turn-taking, error handling, caller data collection, escalation, handoffs, and spoken formatting.
Review Renovate bot PRs that update GitHub Actions dependencies. Verifies supply chain integrity by checking pinned commit SHAs against upstream tagged releases, reviews changelogs for breaking changes, and confirms compatibility with existing workflow configurations. Use when a Renovate PR updates GitHub Actions in .github/workflows/.
Workflow for using Claude to generate Blender Python scripts, automate 3D workflows, and create procedural scenes, animations, and assets directly inside Blender.
Render independent questions in an Agent workflow into a local interactive form, mark recommended answers, collect optional supplementary notes for each question, save responses as portable JSON, and return the submitted results directly to the waiting Agent command. Suitable for grill-me, grill-with-docs, brainstorming, requirement clarification, configuration, planning, and any workflow requiring user confirmation or question collection; explicitly call Ask UI when a round contains more than two questions. When a user says "submitted", "done submitting", or "finished answering" during an Ask UI round, follow this skill's manual recovery path.
Author, save, and edit email templates in the PostHog workflows library — compose email design JSON with Liquid personalization and create and round-trip-edit templates over MCP. Use when asked to design, build, update, or fix an email template for workflows, broadcasts, or campaigns.
Create or update a skill in this repository the right way — canonical home in .agents/skills, internal-vs-public marking, symlink mirroring into .claude/skills, and public docs registration for product skills. Use whenever adding a new skill, converting a workflow into a skill, or when .claude/skills and .agents/skills look out of sync.
Add an in-app feedback and bug-report loop that captures a screenshot plus network/console logs, emails the reporter, launches a Cursor Cloud Agent with autoCreatePr, and emails again when the PR opens and when it merges. Use when asked to add feedback, bug reporting, user reports that open PRs, Cursor automation for feedback, or a feedback-to-PR workflow.
Recommend the right trading workflow, skillset, API profile, and setup path from a natural-language goal. Use this as the on-ramp when a user expresses a trading or investing goal and needs to know which skill/workflow to use, where to start, or whether something works without paid API keys — e.g. "where do I start", "which skill should I use", "I want to swing trade only when the market is favorable", "what works without API keys", "どれを使えばいい", "API キー無しで 使えるものは". Routes and explains only; it never executes trades or auto-runs other skills, and it is honest when no workflow has shipped yet.
Map plain-language Nexor requirements to exact configuration and build it through Nexor MCP tools. Covers arbitrary lead metadata, notifications, CRM sync, field/status events, qualification gates, workflow tools and hooks, webhooks, jobs, cloud/scheduled functions, cadence, channel and knowledge-base assignment, multi-agent systems, and transfers. Use when a customer asks how an agent can receive or use custom lead information, describes custom behavior, an integration, routing, or a multi-agent build. Discover account configuration before questions, decompose variables, stages, and boundaries, require plan review and sign-off before mutation, prefer deterministic primitives, and read back every expected channel, connection, and knowledge assignment regardless of creation order.