Loading...
Loading...
Found 5,601 Skills
Run an interactive naming session for a project. Use when the user wants to name a project, app, package, tool, or repo. Presents names in rounds, tracks preferences, and refines suggestions based on selections.
Build your app's primary user interface embedded in the Shopify admin. If the prompt just mentions `Polaris` and you can't tell based off of the context what API they meant, assume they meant this API.
Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.
USDC is Circle's stablecoin deployed across multiple blockchain ecosystems including EVM chains (Ethereum, Base, Arbitrum, Polygon, Arc) and Solana. Use this skill to check balances, send transfers, approve spending, and verify transactions. Triggers on: USDC balance, send USDC, transfer USDC, approve USDC, USDC allowance, verify USDC transfer, USDC contract address, USDC on Solana, Solana USDC, check balance, SPL token, Associated Token Account, ATA, ERC-20 USDC, parseUnits, formatUnits, 6 decimals, viem, @solana/kit.
Use when the user wants to update, refresh, or reinstall the CopilotKit agent SKILLS (the SKILL.md files that teach this agent about CopilotKit). NOT for updating the CopilotKit codebase or project — this is specifically about refreshing the skills/knowledge this agent has loaded. Triggers on "update copilotkit skills", "update skills", "refresh skills", "skills are stale", "skills are outdated", "get latest skills", "my copilotkit knowledge is wrong", "copilotkit APIs changed", "skills seem old", "wrong API names", "reinstall skills", "skills not working right", "update your copilotkit knowledge".
Run a full Dune app platform review against a React/TypeScript CDF codebase, following the cognitedata/dune-app-reviews scoring criteria. Produces three artifacts: review-files.md (per-file inventory), review-packages.md (dependency audit), and review-report.md (scored report with must/should/nice-fix items). Use when the user asks for a Dune app review, pre-submit review, approval review, app certification review, code quality audit, CDF platform review, or "run dune-review" on a codebase before submission.
Use this skill to bridge tokens, cross-chain swap/transfer, move assets between chains, get cross-chain quotes, compare bridge fees, find the cheapest/fastest route, build bridge calldata, check bridge status, track a cross-chain transaction, list supported chains or bridge protocols, or when the user mentions bridging ETH/USDC/tokens from one chain (Ethereum, BSC, Polygon, Arbitrum, Base, Optimism, Solana, etc.) to another. Routes through multiple bridge protocols (Stargate, Across, Relay, Gas.zip) for optimal execution. Supports fee comparison, destination address specification, approval management, and full lifecycle status tracking until fund arrival.
Issue Workflow Stage 1 — Convert the user's problem into a reproducible, traceable {slug}-report.md through conversation. The AI only asks "what you saw, how to reproduce it, what should happen" here, and does not guess the root cause for the user (that's Stage 2's responsibility). Meanwhile, this stage is the only official decision point for choosing between the fast track and standard path: Based on the user's description, first review the relevant code; if the root cause can be identified at a glance and the required changes are minor, directly inform the user to take the fast track. Trigger scenarios: The user says "file an issue", "record this bug", "I found a problem". This is the starting point of the issue workflow with no pre-dependencies.
When developing new features, follow this sub-process — take the vague idea of "add X capability" through to the acceptance closure, with solution documents archived so that both AI and users can later check the original thinking and decision rationale. Trigger scenarios are focused on adding new capabilities ("develop new feature", "add X", "implement XX"), and do not handle bugs in existing code. This skill only acts as a router, deciding which sub-skill to trigger next among brainstorm / design / fastforward / implement / acceptance based on existing artifacts.
Philip Tetlock's Superforecasting framework applied to a business decision, investment thesis, or strategic question. Spawns a team of specialist agents — Calibrator, Decomposer, Updater, Devil's Advocate, Scorekeeper — who each apply a different piece of the superforecasting methodology. The lead synthesizes into a calibrated probability estimate with Brier-scoreable predictions, explicit base rates, and an accountability structure for keeping score over time. Use when the user says "tetlock this", "what's the probability", "how confident should I be", "forecast this", "calibrate this", proposes a business thesis and wants probabilistic stress-testing, or wants to apply superforecasting to a decision. Works standalone or after /munger.
FLOW framework integration — evidence-led SEO using the Find → Leverage → Optimize → Win loop. Surfaces stage-specific AI prompts from the FLOW knowledge base (41 prompts, CC BY 4.0). Use when user says "FLOW", "FLOW framework", "seo flow", "evidence-led SEO", "find leverage optimize win", or wants stage-specific SEO prompts.
Standard workflow for pulling updates from main or other branches on multi-contributor projects (including Dune apps) without silently discarding work. Guides fetching/merging, requires listing merge conflicts explicitly, analyzing ours vs theirs using conversation history and repo context, presenting prioritized recommendations, and obtaining user answers before editing conflict markers or completing the merge. Triggers: pull main, merge main, merge origin, rebase, merge conflict, unmerged paths, both modified, integrate branch, sync with main, git merge abort, resolve conflicts, UU status, theirs vs ours, feat branch update.