Loading...
Loading...
Found 1,479 Skills
Audit and migrate existing Markdown rendering to Markstream. Use when Codex needs to replace another renderer, classify direct vs custom vs plugin-heavy usage, preserve behavior during adoption, migrate custom renderers into scoped Markstream overrides, or decide when `nodes` streaming is worth adopting.
Select, implement, or migrate between app architecture patterns for Apple platform apps. Use when choosing between MV (Model-View with @Observable), MVVM, MVI, TCA (The Composable Architecture), Clean Architecture, VIPER, or Coordinator patterns; when evaluating architecture fit for a feature's complexity; when migrating from one pattern to another; or when reviewing whether an app's current architecture is appropriate. Scoped to Apple-platform patterns using Swift 6.3, SwiftUI, and UIKit.
Shared Epismo operating model: CLI/MCP surface conventions, workspace and project scope, share URL resolution, selective fetch and pack reuse patterns, pack aliases, credits/payment handling, and common auth or permission errors. Load this alongside any Epismo skill, or trigger on Epismo usage questions, alias/credit issues, share URLs, workspace scope, or setup/auth problems blocking another Epismo task.
Bubbles platform help — async video messaging + AI meeting note-taker with screen recording, auto-join for Zoom/Meet/Teams, AI summaries and action items, and async video comments. Use when setting up Bubbles notetaker to auto-join meetings, configuring which meetings the Bubbles bot should join or skip, troubleshooting Bubbles recordings that lock after two weeks on the free plan, connecting Bubbles to Slack or Notion via Zapier automation, choosing between Bubbles Pro Personal and Pro Teams plans, comparing Bubbles to Loom or other async video tools, or evaluating whether Bubbles fits a sales team that needs CRM integration. Do NOT use for comparing AI note-takers across platforms (use /sales-note-taker) or reviewing a sales call for coaching (use /sales-call-review).
Fazier platform help — product discovery and launch platform for indie makers with daily launches and community voting. Covers free submission (DR81 dofollow backlink, 15-day review, badge required), Lite ($19 instant publish), Premium ($39 guaranteed DR81+ backlink + 15-day promo), Super ($99 top placement), daily launch feed, upvoting, leaderboards, and Substack newsletter (5,000+ subscribers). Use when you want your product listed on Fazier, wondering if the DR81 backlink justifies the cost, not sure whether free or paid tier is worth it, or deciding between Fazier and other indie maker directories. Do NOT use for multi-directory launch strategy (use /sales-launch-directory). Do NOT use for Product Hunt launches (use /product-hunt-launch).
LaunchDay platform help — curated 24-hour product launch events for indie makers by Dagobert Renouf. Covers $99 submission process (pay only if selected), event model (1-2/month, max 20 products), deal requirements (>40% discount), 30-min podcast interview, influencer promotion (100K+ followers), Slack community access, and permanent archive. Use when unsure if LaunchDay is worth the $99, want more exposure for your indie product but free directories aren't enough, or wondering how LaunchDay compares to other paid options. Do NOT use for multi-directory launch strategy (use /sales-launch-directory). Do NOT use for Product Hunt launches (use /product-hunt-launch).
Build modern data apps, dashboards, and interactive reports using either React + Vite or Streamlit. Includes optional Gemini Data Analytics chat integration for an AI powered "chat with your data" experience. Relevant when any of the following conditions are true: 1. User explicitly requests to build a data dashboard, data application, or visualization UI, and the UI pulls data from a GCP database (defaulting to BigQuery unless otherwise specified). 2. You need to generate a frontend web application to interact with, query, and visualize data from GCP data sources. 3. User wants to build a "chat with your data" experience or integrate the Gemini Data Analytics chat API into a web interface. Do NOT use when any of the following conditions are true: 1. The request is for building backend-only services. 2. The request is for simple CLI scripts or command-line applications. 3. The web application is not data-centric or does not involve visualizing/querying data from GCP sources.
Control timeBuzzer hardware LED via MIDI — set color, effects (pulse, strobe, rainbow, fade), and semantic status signals. Use when the user asks to change the buzzer LED color, signal status through the buzzer, or sync the buzzer with other lighting.
Turn approved storyboard logic, beat sheets, or prompt plans into provider-ready short-form video requests. Use this when the segment structure is already known and you need a model-agnostic request architecture that can later map cleanly into Seedance or other video generators.
Cross-chain bridging, swapping, and "bridge+call" via Relay through the OpenFinance backend. Use whenever the user wants to move tokens between chains or execute a destination-chain transaction funded from another chain. Triggers: "bridge X from Y to Z", "move my USDC to Base / Arbitrum / Optimism / Polygon / Solana", "swap ETH for USDC on Base", "cross-chain swap", "bridge and call", "how do I get to Solana / back from Solana", "my USDC is stuck on Solana", EVM-to-EVM, EVM-to-Solana, Solana-to-EVM, Bitcoin bridge, gas topup on destination, native-token sentinel 0x0, relay quote/preview/execute flow, poll intent status. Covers POST /agent/relay/quote, POST /agent/relay/execute, GET /agent/relay/status. Includes the chainId cheatsheet (1/137/8453/10/42161/... and Solana 792703809 specifically), tradeType semantics (EXACT_INPUT / EXACT_OUTPUT / EXPECTED_OUTPUT), why topupGas is auto-disabled on Solana routes, the Solana wallet delegation requirement for Solana-origin execute, and bridge+call payloads (txs array). Use together with openfin-setup (API key check) and openfin-troubleshooting (Blockhash not found, Custom:101, 412 delegation).
Use when extracting requirements from Azure DevOps work items using dxs devops commands: fetching work items, reviewing relations, downloading attachments, compiling raw requirements. This is a utility skill — it extracts and structures work item content but does not build reports, datasources, or other artifacts.
NCAA cross country and track & field athlete data via TFRRS (tfrrs.org) and news via The Stride Report. Fetch athlete profiles including all personal records (PRs), eligibility year, school, full season-by-season results history, and XC/TF news. Zero config, no API keys. Use when: user asks about NCAA cross country, NCAA track and field, college running, TFRRS athlete profiles, personal records, PRs, XC or TF season results, individual athlete performance history, or XC/TF news. Don't use when: user asks about professional track, Diamond League, or other sports — use nfl-data, nba-data, wnba-data, nhl-data, mlb-data, golf-data, cfb-data, cbb-data, tennis-data, fastf1, or volleyball-data. For betting use polymarket or kalshi.