Loading...
Loading...
Found 2,026 Skills
Proactively summarize and consolidate knowledge from AI conversation sessions. Auto-triggers when: (1) Starting a new session after meaningful previous work, (2) Session contains significant learnings worth preserving. Captures debugging insights, architecture decisions, patterns, configs, and lessons learned into structured knowledge documents. Explicit triggers: 'summarize', 'consolidate', 'save knowledge', 'document this'.
CI-only self-improvement workflow using gh-aw (GitHub Agentic Workflows). Captures recurring failure patterns and quality signals from pull request checks, emits structured learning candidates, and proposes durable prevention rules without interactive prompts. Use when: you want automated learning capture in CI/headless pipelines.
Assess organizational capabilities using radar charts. Use for competitive analysis, gap identification, and strategic planning.
Style Compatibility and Adaptation Development Guide for Mpx Cross-Platform Output to RN (Mpx2RN or Mpx2DRN). This guide must be invoked when users ask questions related to Mpx cross-platform output to RN styles, including: Mpx2RN style adaptation, Mpx2RN style compatibility transformation, Mpx2RN style capability support, Mpx2RN style not taking effect, Mpx2RN style errors, Mpx2RN style development best practices, how to achieve a certain style effect in Mpx2RN, etc.
Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.
Answer customer questions about Apollo products (OSS and enterprise) using public documentation and GraphOS MCP Tools. Use this skill when: (1) a customer asks a question about Apollo Router, Server, Client, GraphOS, Federation, Connectors, Rover, or MCP Server, (2) triaging a support question from Slack, Jira, or another channel, (3) researching Apollo product capabilities or configuration, (4) helping a customer troubleshoot an Apollo-related issue.
Apply the Knowledge-Based View (Grant, 1996) and Nonaka and Takeuchi's SECI model to analyze how organizations create, transfer, and integrate knowledge for competitive advantage. Use this skill when the user needs to design knowledge management systems, understand why knowledge transfer fails across teams, evaluate knowledge creation processes, or when they ask 'how do we capture tacit knowledge', 'why does knowledge stay siloed', or 'how can we turn individual expertise into organizational capability'.
Apply supply and demand analysis to explain price determination, market equilibrium, and the effects of policy interventions. Use this skill when the user needs to analyze how prices are set in a market, predict the effect of taxes/subsidies/price controls, or understand shifts in supply or demand curves — even if they say 'why did the price go up', 'what happens if the government sets a price cap', or 'how does a tariff affect the market'.
Manages iOS Simulator devices and tests app behavior using xcrun simctl. Covers device lifecycle (create, boot, shutdown, erase, delete), app install and launch, push notification simulation, location simulation, permission grants via privacy subcommand, deep link testing via openurl, status bar overrides, screenshot and video recording, log streaming with os_log filtering, get_app_container paths, and #if targetEnvironment(simulator) compile-time checks. Use when creating or managing simulator devices, testing push notifications without APNs, simulating GPS locations, granting or resetting privacy permissions, capturing screenshots or screen recordings from the command line, streaming device logs, debugging simulator boot failures, troubleshooting CoreSimulator issues, or checking simulator hardware limitations.
Verify that a developer-run feature behaved correctly by analyzing HTTP traffic captured by Fiddler Everywhere. Always use this skill when a developer asks whether their feature's HTTP calls completed correctly, wants to see what requests a feature made, needs to debug a failed API call, is checking traffic after running a feature, wants to confirm what each endpoint returned, or asks whether anything in the traffic looks wrong — even if they don't use the word "verify" or "Fiddler". Summarizes the capture by endpoint and flags likely issues such as failed calls, missing follow-up requests, retries, auth failures, timeouts, and suspicious status-code patterns. Requires Fiddler Everywhere to be running with its MCP server enabled.
Documents the results of a time-boxed technical or design exploration (spike). Use after completing a spike to capture learnings, findings, and recommendations for the team.
Create Xmind mind maps with generated topic images via a contact-sheet workflow. Requires an image generation capability (built-in for Codex / Gemini CLI, or an external image API). Use for illustrated maps; for text-only maps, use xmind-file.