Loading...
Loading...
Found 3,817 Skills
Use this skill when the user asks about current events, real-time information, recent news, live scores, financial data, price updates, recent changes, or any question that may require up-to-date web information. This skill first determines if web search is necessary using Gemini, then attempts Google Search Grounding via Gemini, and automatically falls back to Tavily if any failure occurs.
Run Gemini CLI to take a screenshot for a specific page.
Use when a user mentions Jupiter token verification, VRFD eligibility, paying 1000 JUP to verify a token, submitting a verification request, or updating metadata via the Jupiter express verification flow.
Drives interactive requirement discovery to produce spec files. Use when the user says "spec this", "write specs", "create specs", or "run the spec skill".
Activates when the user asks about Agent Skills, wants to find reusable AI capabilities, needs to install skills, or mentions skills for Claude. Use for discovering, retrieving, and installing skills.
Create subtasks in Jira from a previously generated task plan. Reads the plan from docs/<TICKET_KEY>-tasks.md and creates one Jira subtask per task under the parent ticket. Use when the user says "create subtasks", "push tasks to Jira", "sync plan to Jira", "create Jira tickets", "make subtasks for PROJECT-1234", or anything about turning a plan into Jira issues. Also triggered by the orchestrating-jira-workflow skill as Phase 4. Requires the task plan to already exist (run planning-jira-tasks first if it does not). Use this skill even if the user just says "push to Jira" or "create the tickets" after a planning phase — those are subtask creation requests.
Guidelines for creating AI agent skills. Use when writing new skills, documenting coding patterns, or reviewing skill files. Triggers when creating or modifying files in the skills/ directory.
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).
Reviews and validates agent skills against best practices. Triggers on "review this skill", "check my skill", "validate skill", "is this skill well-written", or when creating/editing skills.
Use Collabute MCP for organization-specific context retrieval and proposal-safe actions. Trigger when users ask about meetings, memory, Linear, Slack, or Vercel data from their Collabute workspace, or ask to create tasks from meeting context.
Run Codex planning via the CLI and report the planning results.
Scan the host repo a set of agent skills is installed into and reconcile every installed skill's config.json with detected facts — base branch, monorepo package roots, changelog directory, Linear issue-key prefixes, review bots, protected branches — plus the Linear team name and workspace slug fetched via the Linear MCP. Use when first installing these skills into a repo, or to refresh the configs after the skill set or repo layout changes. Also emits a committed `.claude/skills.lock` inventory of installed skill versions, and ensures the preflight skill's `.preflight-summary.json` scratch output is gitignored. Idempotent and safe to re-run: it reconciles drift rather than clobbering deliberate manual edits, presents a dry-run diff first, and only writes after confirmation — preserving each config's key order and formatting so a no-op run leaves files byte-identical.