Loading...
Loading...
Found 996 Skills
Create OpenCode plugins using the @opencode-ai/plugin SDK. Use for building custom tools, event hooks, auth providers, or tool execution interception. Use proactively when developing new plugins in .opencode/plugin/ or ~/.config/opencode/plugin/. Examples: - user: "Create a plugin to block dangerous commands" → implement tool execution before hook with blocking logic - user: "Add a custom tool for jira" → design tool schema and implementation using SDK context - user: "Show toast on file edit" → react to file edit events and display status message - user: "Build a custom auth provider" → implement auth flow for new model provider - user: "Intercept git commits" → add hook to validate commit messages before execution
Expert renewal management guidance for maximizing retention and expansion revenue. Use when building renewal playbooks, forecasting renewal pipeline, structuring multi-year deals, developing pricing strategies, mitigating churn risk, defending against competitive displacement, negotiating contracts, attaching expansion to renewals, or optimizing renewal operations. Covers high-touch and tech-touch renewal motions, early renewal strategies, and save plays.
Display session efficiency report showing token savings, cache performance, and optimization recommendations. Use when user asks "show my stats", "how efficient am I?", "show session metrics", or wants to see Navigator's impact.
Use when working with Infrastructure as Code tools and platforms. Covers Terraform, Pulumi, CloudFormation, Bicep, ARM, Kubernetes, Helm, Docker, Crossplane, and Dagger. USE FOR: choosing IaC tools, comparing Terraform vs Pulumi vs CloudFormation, infrastructure strategy DO NOT USE FOR: specific tool syntax (use the sub-skills: terraform, pulumi, bicep, etc.)
Titanium SDK UI/UX patterns and components expert. Use when working with, reviewing, analyzing, or examining Titanium layouts, ListView/TableView performance optimization, event handling and bubbling, gestures (swipe, pinch), animations, accessibility (VoiceOver/TalkBack), orientation changes, custom fonts/icons, app icons/splash screens, or platform-specific UI (Action Bar, Navigation Bar).
Adapt a single master creator brief into platform-specific versions for TikTok, Instagram Reels, and YouTube Shorts with correct specs, safe zones, and platform-native guidance. This skill should be used when converting a brief for multiple platforms, adapting a campaign brief from TikTok to Reels, creating platform-specific content briefs from a master brief, adjusting video specs for different short-form platforms, building TikTok and Reels and Shorts versions of one brief, formatting creator deliverables by platform, splitting a campaign brief into platform versions, or generating platform-adapted briefs for a multi-platform creator campaign. For writing the master brief itself, see content-brief-builder. For generating content concepts before briefing, see creator-content-concept-generator. For checking submitted content against a brief, see content-to-brief-compliance-checker.
Implement WCAG 2.2 accessibility patterns in Shopify Liquid themes. Covers e-commerce-specific components including product cards, carousels, cart drawers, price display, forms, filters, and modals. Use when building accessible theme components, fixing accessibility issues, or reviewing ARIA patterns in .liquid files.
PDF processing API for conversion, extraction, merging, splitting and more
Implements WPF data validation using ValidationRule, IDataErrorInfo, and INotifyDataErrorInfo. Use when building forms, validating user input, or displaying validation errors in UI.
Retrieve and display all calendar events scheduled for today. Use this skill when the user asks to check their calendar, see today's schedule, view appointments, or find out what events are coming up today. Works with the native Calendar application on macOS.
[Must Read · Mandatory] Mandatory specifications for company front-end development. You must read this skill before writing or modifying any front-end code. It covers all development constraints including mandatory Composition API specifications, naming conventions, API calling rules, Pinia state management, component splitting, etc.
When the user wants to design, optimize, or audit card layouts for content display. Also use when the user mentions "card layout," "card component," "card grid," "product cards," "template cards," "tool cards," "feature cards," "gallery cards," "integration cards," or "card design."