Loading...
Loading...
Found 2,899 Skills
Plan a non-trivial code change end-to-end — size triage (XS–XL), slicing strategy, optional parallel subagent dispatch, per-slice Implement → Test → Verify → Commit discipline. Use for any multi-file change, refactor across files, executing a planned task from any planning source, cross-cutting modification (analytics sweep / i18n / library migration), or when about to write more than ~100 lines. 也用于增量实现 / 切片落地 / 推进已规划任务 / 跨切面改动。Skip only for trivial XS edits and pure documentation / configuration changes.
Printing Press CLI for Jira Cloud Platform. Jira Cloud Platform REST API documentation
Guides the agent through creating and maintaining Capacitor plugins from scratch. Covers scaffolding a new plugin project, designing the TypeScript API, implementing native iOS (Swift) and Android (Java/Kotlin) bridges, implementing the web layer, defining TypeScript type definitions, plugin configuration values, plugin hooks, development workflow with local testing, documentation generation, and publishing to npm. Do not use for installing existing plugins into an app, upgrading existing plugins to newer Capacitor versions, adding SPM support to plugins, or non-Capacitor plugin frameworks.
Provides comprehensive code review covering 6 focused aspects - architecture & design, code quality, security & dependencies, performance & scalability, testing coverage, and documentation & API design. Use this skill for deep analysis with actionable feedback after significant code changes.
You are a professional Customer Service Specialist and Communication Strategist. Use this skill when the user wants to write customer service scripts, support email templates, feedback responses, FAQ content, or help center articles. Activate when the user mentions "customer service," "support email," "support template," "help center," "knowledge base article," "FAQ for support," "chatbot script," "live chat script," "phone script," "customer feedback response," "review response," "refund email," "cancellation template," "late shipping response," "apology email," "product outage response," "billing email," "customer onboarding message," "troubleshooting guide," "password reset article," "support ticket," "macro," "saved reply," "customer service playbook," "internal support doc," "review reply," "3-star review," "negative review response," "positive review response," "customer loyalty message," "subscription cancellation script," "exchange template," "customer portal content," "chatbot flow," "in-app help copy," "social media response," "support documentation," or "customer service tone." Covers scripts for phone, chat, and messaging; email templates for all support scenarios; feedback and review responses; FAQ sections; and full help center articles with troubleshooting guides.
Research a vendor, product, or feature to collect all information needed before building an Elastic integration. Investigates data collection methods, API or log documentation, sample data formats, field schemas, ECS mapping candidates, and configuration requirements. Outputs a structured research brief to research_results/<product>/. Invoke manually with /research-integration.
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.
Vast.ai API Documentation - Affordable GPU Cloud Marketplace
Proactive quality guidance system that monitors artifact creation and provides real-time feedback on documentation quality
Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.
Creates Loop Page documents following company SOP standards. Use when user wants to create a new Loop page, meeting record, project document, or any documentation following company's Loop workspace conventions. Triggers on keywords like "Loop", "SOP", "create document", "meeting record", "project doc", or when user needs team documentation.
Autonomous feature development workflow using isolated worktrees. Use to autonomously implement features from task description through tested PR delivery. Handles worktree creation, implementation, testing, iteration, documentation, and PR creation. Triggers on autonomous feature development, end-to-end implementation, or "implement X autonomously."