Loading...
Loading...
Found 1,000 Skills
Fetch GitHub PR review feedback, judge each comment, implement valid fixes, verify, and optionally reply.
Analyzes raw requirements into visual specs and generates artifacts. Invoke when user runs /vspec:new for analysis or /vspec:verify for models and prototypes.
Generates structured test assertions and failure diagnostics for skill packages from a definition and task prompt. Triggers on: "verify this skill", "generate assertions", "surrogate verification", "diagnose skill failure". NOT for code review, use pr-review.
Audit PostHog experiments and feature flags for configuration issues, staleness, and best-practice violations. Read when the user asks to audit, health-check, or review experiments or feature flags, check flag hygiene, or verify experiment setup.
Use this skill when > Test-Driven Development using red-green-refactor cycles with vertical slices. Tests verify behavior through public interfaces, not implementation details. Use when building new features or fixing bugs with a test-first discipline to produce well-designed, behavior-verified code.
Install cuOpt for Python, C, or as a server (pip, conda, Docker) — system requirements, install commands, and verification. Use when the user wants to install or verify cuOpt for any user-facing interface. For building cuOpt from source or contributing to cuOpt, see cuopt-developer.
Deploy open models or custom weights from Model Garden to Agent Platform endpoints, check deployment status, verify serving endpoints, or clean up resources by undeploying models and deleting endpoints. Use when asked to deploy models on Agent Platform, list available Model Garden models, check if a model is deployable, query deployment cost, troubleshoot deployment errors (like quota limits), or undeploy/clean up endpoints. Also use when copying and deploying a 1P Tuned Model. Don't use for public Vertex AI deployments (use the `vertex-deploy` skill) or for running model evaluations (use the `agent-platform-eval` skill).
Review generated or changed documentation before it ships — READMEs, API references, docstrings, PHPDoc/JSDoc, changelogs, tutorials, and doc sites. Best used reactively after an agent writes or edits docs, after code changes documented behavior, or before publishing docs. Use when the user says 'review the docs', 'is this documentation accurate', 'update the docs', 'write a README', 'document this API', 'add a docstring', or 'add a changelog entry'. Core job: verify every referenced function, flag, endpoint, config key, and code sample against the source; catch docs-vs-code drift; strip filler and unverifiable claims. DO NOT USE for production code review (use clean-code-guard), test review (use test-guard), marketing copy or blog posts, prose style editing of non-technical writing, or documentation site theming.
Use to configure, set up, or repair the Sales Management agent and Agentforce Pipeline Management in a Salesforce org. Automates metadata creation for flows, prompt templates, permission sets, and data source configuration. TRIGGER when: user wants to enable Pipeline Management, configure Sales pipeline features, set up the Sales Management agent for opportunity field updates (including autonomous updates), connect enabled data sources like Einstein Conversation Insights or Einstein Activity Capture, customize opportunity stage descriptions, configure post-meeting suggestions, verify or audit configuration status, fix partially configured orgs, or troubleshoot Pipeline Management metadata issues. DO NOT TRIGGER when: user wants to build a custom agent (use agentforce-generate), configure general Agentforce tracing (use platform-tracing-agentforce-configure), work with non-Sales agents, or enable Einstein Conversation Insights or Einstein Activity Capture from scratch (provisioning is out of scope).
General Chinese Creation and Revision Skill. Applicable to Zhihu answers, forum long posts, official account articles, blogs, comments, character stories, historical narratives, news and industry interpretations, popular science, tutorials, reviews, personal narratives, novels, stories, dialogues, oral broadcasts, and speeches. Defaults to writing in the voice of someone who has experienced things, checked materials, and is willing to explain the ins and outs clearly, focusing on retaining the authentic human touch and natural Chinese rhythm of long answers and posts on the Chinese internet, while avoiding empty institutional tones, slogan-style speech tones, marketing tones, and AI model tones. For non-fiction long articles, first check if the materials are sufficient; if not, conduct research, ask questions, or shorten the article, and never pad the word count with repetitive explanations. Verify facts, quotes, data, and user experiences for real-world content; for fictional content, characters, scenes, dialogues, psychology, and plots can be created. Colons, dashes, phrases like "not...but..." and similar counterargument structures are strictly prohibited in the final draft, and business jargon and AI model jargon should be removed. Do not create author profiles, personal rule libraries, or personal writing Skills.
Verify API contracts between services to ensure compatibility and prevent breaking changes. Use for contract testing, Pact, API contract validation, schema validation, and consumer-driven contracts.
Receive and verify Resend webhooks. Use when setting up Resend webhook handlers, debugging signature verification, handling email events like email.sent, email.delivered, email.bounced, or processing inbound emails.