Discover
Discover and install skills, docs, and rules to enhance your AI agent's capabilities.
| Name | Contains | Score |
|---|---|---|
dlt-hub/dlt Enforces dlt import conventions and ordering. Use when writing or modifying Python imports in dlt/ or tests/. | Skills | |
sickn33/antigravity-awesome-skills Build content moderation applications using the Azure AI Content Safety SDK for Java. | Skills | |
freekmurze/dotfiles When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. | Skills | |
jeremylongshore/claude-code-plugins-plus-skills Security and privacy configuration for Granola meeting data. Use when reviewing data handling practices, configuring encryption, ensuring SOC 2/GDPR compliance, or securing meeting recordings. Trigger: "granola security", "granola privacy", "granola encryption", "granola SOC 2", "granola GDPR", "secure granola". | Skills | |
Query and display available GitHub Copilot AI models with their capabilities, context limits, and features. Use when: "what models are available", "show copilot models", "list github models", "check model capabilities", "switch models". Examples: - user: "What models can I use with GitHub Copilot?" → fetch and display available models - user: "Show me models with vision support" → filter models by capability - user: "Which model has the largest context window?" → compare model specifications - user: "List all GPT-5 models" → filter by model family Contains: github-copilot-models Query and display available GitHub Copilot AI models with their capabilities, context limits, and features. Use when: "what models are available", "show copilot models", "list github models", "check model capabilities", "switch models". Examples: - user: "What models can I use with GitHub Copilot?" → fetch and display available models - user: "Show me models with vision support" → filter models by capability - user: "Which model has the largest context window?" → compare model specifications - user: "List all GPT-5 models" → filter by model family | Skills | |
github/awesome-copilot Guides the Copilot CLI on how to use the WorkIQ CLI/MCP server to query Microsoft 365 Copilot data (emails, meetings, docs, Teams, people) for live context, summaries, and recommendations. | Skills | |
Dicklesworthstone/pi_agent_rust Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use when transitioning on-call responsibilities, documenting shift summaries, or improving on-call processes. | Skills | |
davepoon/buildwithclaude Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas. | Skills | |
davepoon/buildwithclaude Automate Google Analytics tasks via Rube MCP (Composio): run reports, list accounts/properties, funnels, pivots, key events. Always search tools first for current schemas. | Skills | |
davepoon/buildwithclaude Automate Canva tasks via Rube MCP (Composio): designs, exports, folders, brand templates, autofill. Always search tools first for current schemas. | Skills | |
quickwit-oss/quickwit Run `make fmt` to check the code format. | Skills | |
davepoon/buildwithclaude Automate ActiveCampaign tasks via Rube MCP (Composio): manage contacts, tags, list subscriptions, automation enrollment, and tasks. Always search tools first for current schemas. | Skills | |
trailofbits/skills OSS-Fuzz provides free continuous fuzzing for open source projects. Use when setting up continuous fuzzing infrastructure or enrolling projects. | Skills | |
jdrhyne/agent-skills Automatically recover working context after session compaction or when continuation is implied but context is missing. Works across Discord, Slack, Telegram, Signal, and other supported channels. | Skills | |
brianlovin/claude-config Sentry error monitoring and performance tracing patterns for Next.js applications. | Skills | |
obra/superpowers You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. | Skills | |
ceshine/ceshine-agent-skills Access up-to-date, version-specific documentation and code examples from Context7. Use this skill to verify library and framework details. | Skills | |
Demerzels-lab/elsamultiskillagent Performs web searches using DuckDuckGo to retrieve real-time information from the internet. Use when the user needs to search for current events, documentation, tutorials, or any information that requires web search capabilities. | Skills | |
google/mcp-security Expert guidance for security alert triage. Use this when the user asks to "triage" an alert or case. | Skills | |
A curated collection of Agent Skills for working with Orchestra, for agents to effectively implement standards, common workflows, and manage pipelines. Contains: configure-dbt-build-after Configure dbt model build_after for Orchestra state-aware orchestration — author the config.freshness.build_after block (count, period, updates_on) on dbt models so Orchestra rebuilds a model only after a minimum SLA window AND when its upstream data is fresh, then ensure use_state_orchestration is enabled on the Orchestra dbt task. Use when asked to set up build_after, configure per-model rebuild SLAs, gate model rebuilds on upstream freshness, stop unnecessary dbt rebuilds, or set up state-aware orchestration in Orchestra. Trigger on phrases like "configure build_after", "add build_after", "only rebuild when upstream is fresh", "per-model SLA", "updates_on any/all", or "stop rebuilding models that haven't changed" in a dbt or Orchestra context. build_after is warehouse-agnostic (same config for Snowflake, BigQuery, Databricks, MotherDuck) but depends on source freshness being configured — the source/freshness-signal half is the separate configure-dbt-source-freshness skill. configure-dbt-source-freshness Configure dbt source freshness for Orchestra state-aware orchestration — author warn_after/error_after thresholds and loaded_at_field/loaded_at_query in a dbt project's sources YAML, getting the warehouse details right for Snowflake, BigQuery, Databricks, or MotherDuck/DuckDB, then enable use_state_orchestration on the Orchestra dbt task. Use when asked to set up dbt source freshness, configure freshness checks, detect stale sources, set up state-aware orchestration in Orchestra, or make Orchestra skip downstream models when upstream data hasn't changed. Trigger on phrases like "add source freshness", "configure freshness", "set up state aware orchestration", "skip models when sources are stale", "loaded_at_field", or "warn_after/error_after" in a dbt or Orchestra context. This is the source/freshness-signal half of state-aware orchestration; configuring per-model rebuild SLAs (build_after) is the separate configure-dbt-build-after skill. create-orchestra-pipeline Create, validate, and remediate Orchestra pipeline YAML files. Use when asked to build a new pipeline, add tasks to an existing pipeline, fix pipeline validation errors, or author Orchestra workflow definitions from a description. Trigger on phrases like "create a pipeline", "add a dbt task", "write orchestra yaml", "fix validate errors", or when editing files under orchestra/ or similar pipeline directories. fix-orchestra-pipeline Automatically diagnose and fix failed Orchestra data pipelines. Use this skill whenever a user mentions Orchestra pipeline failures, broken pipelines, pipeline errors, task failures, pipeline debugging, or wants to understand why an Orchestra pipeline run failed. Also trigger when the user says things like "fix my pipeline", "what's broken", "why did my pipeline fail", "debug this run", "retry my pipeline", or references Orchestra pipeline runs, task runs, or pipeline errors. This skill handles the full lifecycle: identify failures, fetch logs and artifacts, diagnose the root cause, apply fixes where possible, retry, and learn from past fixes. It supports all Orchestra integrations including dbt, Snowflake, Python, HTTP, Fivetran, Airbyte, and more. Trigger this skill even if the user just pastes an Orchestra error message, pipeline run URL, pipeline run link from the Orchestra UI, a UUID, a Slack alert, or a pipeline name/alias. orchestra-dbt-slim-ci-setup Retrofits dbt Slim CI onto an existing Orchestra production dbt pipeline using latest_production, state:modified+, and --defer, with GitHub Actions run-pipeline as the primary CI trigger. Use when setting up Orchestra Slim CI, dbt CI/CD in Orchestra, run-pipeline for dbt, or latest_production defer state in a dbt repo or from outside it. review-orchestra-account Audit an Orchestra workspace/account against Orchestra's best practices and produce a read-only health report — findings grouped by area, each tagged with severity, evidence, and a fix recommendation, written to a markdown file plus a chat summary. Use whenever the user wants an "account review", "workspace audit", "health check", "best-practice review", "onboarding review", or asks "is my Orchestra set up correctly?", "what should I improve?", "are we following best practices?", "review my pipelines", or "audit my workspace". Also trigger when the user mentions reviewing pipeline design, environment/promotion setup, Git/CI-CD coverage, alerting coverage, connections/secrets hygiene, concurrency, cost, or RBAC across their Orchestra account. This skill only inspects and reports — it never edits pipelines or changes settings. run-snowflake-quality-tests Examines Snowflake data sources, infers appropriate data quality tests, builds a structured Orchestra YAML testing pipeline, and deploys and triggers it via Orchestra MCP tools. Use when the user asks about Snowflake data validation, data quality testing, pipeline deployment to Orchestra, orchestration of test workflows, data warehouse quality checks, or running Snowflake tests against fact and dimension tables. triage-orchestra-pipeline Diagnose a failed Orchestra pipeline, open a fix PR, validate it on a branch run, then present a human-readable triage summary and STOP for user approval before merging. Use this when the user wants to review the fix before it goes to main — not for fully automated fixes. Trigger on phrases like "triage my pipeline", "show me what's broken", "investigate but don't fix yet", "prepare a fix for review", or when the user explicitly wants a review gate before applying changes. Also trigger when the user describes a symptom in a downstream system ("dashboard looks wrong", "chart is stale", "dbt model has bad data") even if no pipeline error exists — the skill will trace the symptom upstream. | Skills |
Can't find what you're looking for? Evaluate a missing skill.