Software Mansion's guide for migrating Expo SDK apps to Meta Quest using expo-horizon packages. Use when adding Meta Quest or Meta Horizon OS support to an existing Expo or React Native project. Trigger on: Meta Quest, Horizon OS, Quest 2, Quest 3, Quest 3S, VR app, expo-horizon-core, expo-horizon-location, expo-horizon-notifications, build flavors for Quest, panel sizing, VR headtracking, Horizon App ID, quest build variant, isHorizonDevice, isHorizonBuild, migrate expo-location to Quest, migrate expo-notifications to Quest, Meta Horizon Store publishing, or any task involving running an Expo app on Meta Quest hardware.
Interact with GitHub using the gh CLI restricted to REST API only (no GraphQL). Use when the user wants to work with GitHub issues, pull requests, repos, releases, or Actions — especially in sandboxed environments where the GraphQL endpoint may be blocked. Trigger keywords - github, gh, pull request, PR, github issue, github actions, workflow, release, gh api.
Ask any question about Claude Code features — setup, best practices, automation, models, plugins, MCP, configuration, and more. Reads relevant reference docs to give accurate, detailed answers.
Answer a question about a GRACE project using full project context. Use when the user has a question about the codebase, architecture, modules, or implementation — loads all GRACE artifacts, navigates the knowledge graph, and provides a grounded answer with citations.
- 📁 agents/
- 📁 references/
- 📄 SKILL.md
세션 종료 시 Memory, Handoff를 자동 정리. /pack
- 📁 agents/
- 📁 references/
- 📄 SKILL.md
Help integrate Grip Connect in web, Capacitor, React Native, runtime, and CLI projects. Use for package selection, supported device setup, Bluetooth constraints, streaming and export workflows, CLI and runtime usage, connection troubleshooting, and unsupported custom device guidance. --- # Grip Connect Use this skill when a user is building with Grip Connect packages, choosing a platform, wiring a supported device, or debugging connection and setup issues. ## Start with platform and device
- 📁 references/
- 📁 scripts/
- 📄 SKILL.md
广告合规审核技能，用于审核广告素材是否符合中国广告法及相关法规。适用场景：(1) 用户提交广告文案、广告素材要求合规审核时；(2) 用户提到"广告审核""广告合规""广告法审查"等关键词时；(3) 用户要求检查广告内容是否存在违法违规风险时；(4) 用户提交房地产、食品、医疗、药品、互联网等行业广告要求专项审核时。审核依据涵盖《广告法》《反不正当竞争法》及行业专项法规。
Create GitHub Pull Request for feature request from specification file using pull_request_template.md template.
审查代码中的错误、风格问题和最佳实践
Communicate with remote agents via A2A protocol, discover available agents, and ask the human owner for clarification via the A2A Hub. Use when asked to send messages to other agents, discover what agents are available, or when you need human input to proceed. **Triggers — use this skill when:** - You need human input to proceed (approval, decision, clarification) - User asks to "send a message to another agent" - User asks to "discover agents" or "what agents are available" - You're stuck and need to escalate to the owner - A long-running task needs human approval before continuing --- # A2A — Agent-to-Agent Communication & Human-in-the-Loop ## Tools | Tool | Purpose | |------|---------| | `a2a_discover` | Find remote agents on the hub or static registry | | `a2a_send` | Send a message to a remote agent by name, ID, or URL | | `ask_owner` | Ask the human owner a question (non-blocking) | --- ## ask_owner — Human-in-the-Loop Use `ask_owner` when you **genuinely cannot proceed** without human input. The tool submits your question to the hub and **returns immediately** — it does NOT block your session. When the owner responds, a **fresh pi subprocess** is automatically spawned with your handoff context + the owner's answer to continue the work. ### How It Works 1. You call `ask_owner` with a question + handoff context 2. The question is submitted to the A2A Hub — you get an immediate confirmation 3. You continue with other work or end your session 4. The owner answers through the hub's web UI (could be minutes or hours later) 5. A background poller detects the response 6. A fresh `pi` subprocess is spawned with a self-contained prompt containing: - The original question - The owner's response - Your full handoff context (done, remaining, decisions, etc.) 7. The new session picks up where you left off — no prior conversation context needed ### When to Use - **Approval needed** — destructive operations, merging PRs, deploying - **Ambiguous requirements** — multiple vali
Use when building any system where email content triggers actions — AI agent inboxes, automated support handlers, email-to-task pipelines, or any workflow processing untrusted inbound email. Always use this skill when the user wants to receive emails and act on them programmatically, even if they don't mention "agent" — the skill contains critical security patterns (sender allowlists, content filtering, sandboxed processing) that prevent untrusted email from controlling your system.
This skill SHOULD be used when the user asks to "review code", "find dead code", "check for duplication", "simplify the codebase", "find refactoring opportunities", "do code cleanup", "check naming consistency", "analyze test organization", "run codebase health check", "review my PR", "refactor this code", "extract method", "rename variable", "consolidate duplicates", "adversarial review", "red team review", "find ways to break this", "multi-model review", "get multiple AI opinions on this code", "hunt bugs", "find bugs", "bug hunt", or "adversarial bug hunt". Routes to specialized analysis agents, refactoring workflow, multi-model adversarial review, or adversarial bug hunt based on the type of request.
