Loading...
Loading...
Found 5,611 Skills
Guides the agent through adding Swift Package Manager support to an existing Capacitor plugin. Covers Package.swift, CAPBridgedPlugin conversion, bridge cleanup, and package manifest updates. Do not use for app projects or non-Capacitor plugin frameworks.
Guides the agent through an Apple App Store preflight review for Capacitor apps before submission or after rejection. Covers guideline checklist selection, App Store metadata review, Capacitor and iOS project inspection, privacy manifests, Sign in with Apple, entitlements, and common rejection patterns. Do not use for Google Play review, generic store publishing only, or non-Apple mobile runtimes.
Guides the agent through migrating Capacitor apps from Ionic Enterprise SDK plugins to Capgo and Capacitor alternatives. Covers dependency detection, API replacement, local storage changes, and platform cleanup. Do not use for generic Capacitor version upgrades or Capgo live updates.
Eino framework overview, concepts, and navigation. Use when a user asks general questions about Eino, needs help getting started, wants to understand the architecture, or is unsure which Eino skill to use. Eino is a Go framework for building LLM applications with components, orchestration graphs, and an agent development kit.
When users ask for weekly reports, weekly summaries or work collections, collect multi-channel evidence around the target time range, merge them into work topics, and generate structured weekly reports. It is applicable to scenarios where multiple information sources such as collaboration platforms, Git, Agent, local documents coexist. Trigger phrases: "周报", "周总结", "工作汇总", "上周工作", "周工作", "weekly report", "work summary".
This skill should be used when the user asks to "improve my setup", "learn from this session", "fix my config", "stop asking for permissions", or reports friction with skills, agents, hooks, or permissions. Analyzes conversation history and proposes configuration improvements.
Checkpoint - Pre-publish review with multi-layer deep analysis. Triggers: Preparing to publish an npm package, requiring pre-release review, or checking code change quality. Review Layers: - Per-Change: In-depth analysis of each change group (up to 10 Agents) - Holistic: Parallel review by 5 roles (Architecture/Development/Testing/Security/Documentation) - Synthesis: 1 Agent summarizes review results Commands: - /把关 - Start pre-publish review - /把关 check - Check unpublished changes - /把关 version - Recommend version upgrade - /把关 report - Generate review report - /review - English command Capabilities: Unpublished change detection, in-depth per-change analysis, multi-role review, version recommendation, release risk assessment.
Manage AI coding agents on a visual Kanban board. Run parallel agents through a To Do→In Progress→Review→Done flow with automatic git worktree isolation and GitHub PR creation.
Braze platform help — Canvas Flow journey orchestration, email/push/in-app/SMS/WhatsApp/Content Cards campaigns, BrazeAI (predictive, generative, agentic), Braze Data Platform (CDI, Currents), real-time segmentation, Catalogs, Feature Flags, transactional email API, Liquid templating, Connected Content, Braze Alloys integrations, SCIM, REST API. Use when asking 'how do I do X in Braze', configuring Canvas flows, building segments, setting up Currents data streaming, using the Braze API, or migrating from Appboy. Do NOT use for building prospect lists (use /sales-prospect-list), designing outbound cadence strategy (use /sales-cadence), cross-platform deliverability (use /sales-deliverability), transactional email strategy (use /sales-transactional-email), push notification strategy (use /sales-push-notification), in-app messaging strategy (use /sales-in-app-messaging), or email marketing strategy (use /sales-email-marketing).
Search the web and scrape pages using the local tool stack: SearXNG (meta-search), Lightpanda (fast headless fetch), and Agent-Browser (full browser automation). This is your DEFAULT web skill — use it whenever you need to look something up, research a topic, fetch a webpage, extract content from a URL, check current information, find documentation, do competitive research, or answer any question that benefits from live web data. Triggers on any form of: search for, look up, google, find out, research, what's the latest on, fetch this page, scrape this site, check this URL, pull info from, web search, or any task where current web information would improve your answer. Even if the user doesn't explicitly ask you to search — if answering well requires current info you don't have, use this skill. NOT for interactive browser automation like form filling or clicking (use [[agent-browser]] or [[browser-use]]).
Guidelines for building AI-accessible web interfaces that work well with AI agents, automation tools, and screen readers. Use this skill whenever the user is building or reviewing a webpage, UI component, form, or frontend feature and any of these apply: they mention AI agents, automation, Playwright, web scraping, accessibility, a11y, aria, semantic HTML, or ask how to make their UI "agent-friendly", "AI-friendly", or "machine-readable". Also trigger when reviewing existing frontend code for accessibility or automation compatibility issues, even if the user doesn't explicitly mention AI.
Consult & operate against the Hyperliquid Names API. Use when your agent needs to resolve `.hl` names, reverse-resolve addresses, fetch HLN profiles or records, inspect owner or list queries, diagnose HLN API failures, prepare a mint-pass request, or guide HyperEVM dApp integration with HL Names.