Loading...
Loading...
Found 11,864 Skills
Apply context-driven testing principles where practices are chosen based on project context, not universal 'best practices'. Use when making testing decisions, questioning dogma, or adapting approaches to specific project needs.
Expert knowledge for Azure Analysis Services development including troubleshooting. Use when testing server connections, debugging gateway or firewall blocks, or checking connection strings and ports, and other Azure Analysis Services related development tasks. Not for Azure Synapse Analytics (use azure-synapse-analytics), Azure SQL Database (use azure-sql-database), Azure SQL Managed Instance (use azure-sql-managed-instance), SQL Server on Azure Virtual Machines (use azure-sql-virtual-machines).
Use when starting work on a new or unfamiliar project, when encountering unexpected patterns, when user corrects your assumptions, or when explicitly invoked via /learn - auto-discovers and remembers project context through structured codebase analysis
Use when starting any conversation, receiving a new task, or when uncertain which skill applies - establishes how to find and use all 64 toolkit skills, requiring Skill tool invocation before ANY response including clarifying questions
Use this skill to query Solana blockchain data via the Solscan Pro API. Triggers: look up wallet address, check token price, analyze NFT collection, inspect transaction, explore DeFi activities, get account metadata/label/tags, fetch block info, monitor API usage, search token by keyword.
Canonical pointer to Armani Ferrante’s X (Twitter) post at status id 1411589629384355840 for primary-source citation in Solana/Anchor/Coral-adjacent discussions. Use when the user cites this exact URL or needs a stable bookmark alongside sealevel-attacks-solana—not as a substitute for opening the post for verbatim text, thread context, or current Anchor documentation.
Reviews spec documents for text quality issues without knowledge of the feature description. Fixes errors directly. Invoked by spec-writer, not directly.
Generate a phase-based task breakdown in tasks.md from spec.md and plan.md
Resolve ambiguities in spec.md through targeted Q&A before planning
Fix all open GitHub issues labeled `internal request` in isolated worktrees, then open PRs
Update .specify/ scripts and templates from upstream github/spec-kit
Transform a feature description into a structured spec.md