Discover and install skills to enhance your AI agent's capabilities.
| Name | Contains | Score |
|---|---|---|
luzmo-official/agent-skills Luzmo MCP Server (hosted at /0.1.0/mcp) - connect Claude, Cursor, ChatGPT, Codex, or your own agent to Luzmo, or expose a white-labeled, per-user MCP server to your own end users. Use for MCP client config, Luzmo login (OAuth) vs API key-token vs embed key-token, which tools a session gets and how to enable more (tools, permissions), saved Agent MCP URLs (agentId), product name and chart theme, MCP App chart and dashboard previews, and setting up a workspace through MCP tools (connections, datasets, metadata and AI context, formulas, dashboards, docs search). Triggers on: "Luzmo MCP", "/mcp", "MCP server", "MCP connector for our customers", answer_question, create_chart, generate_dashboard, search_docs, update_dataset_metadata, "agentId in the MCP URL", "tool missing in Claude/Cursor". Not for direct /aiprompt calls, IQ Chat/Answer components, or creating saved Agents and Rules (use ai-analytics), or tenant row isolation in the embed token (use multitenancy). | Skills | |
luzmo-official/agent-skills Triage router for all Luzmo problems. Use first whenever anything is broken, not working, or behaving unexpectedly. Triggers on: "not working", "broken", "why is X failing", "debug", chart "0 height", "chart not loading", "wrong data showing", API errors. Diagnoses root cause by symptom and routes to the right implementation skill. Does NOT implement fixes. Use this skill first - even if you think you know the fix - for any Luzmo error, rendering failure, data anomaly, or unexpected behavior. | Skills | |
AppsVortex/arness This skill should be used when the user says "pick issue", "work on issue", "arness code pick", "arness code pick issue", "arn-code-pick-issue", "grab issue", "pick from backlog", "what should I work on", "show issues", "find issue", "browse issues", "next issue", "select issue", "choose issue", "what's unblocked", "work on next feature", "pick from feature tracker", or wants to browse issues filtered by Arness labels, select one, and route it to the appropriate Arness pipeline skill for implementation. Supports local-first dependency resolution from a greenfield feature backlog when available. Requires an issue tracker (GitHub or Jira) to be configured for remote issue browsing. Do NOT use this for creating new issues — use /arn-code-create-issue for that. | Skills | |
confluentinc/agent-skills Write and debug Flink SQL that runs on Confluent Cloud, enforcing the CC-vs-Apache-Flink (OSS) dialect boundary. Use when the working directory is a Confluent Cloud Flink workspace, when a Flink SQL statement needs checking before it runs on a CC compute pool, or when the user mentions CC Flink, Confluent Cloud Flink SQL, the `confluent flink` CLI, a CFU compute pool, `CREATE CONNECTION`, or asks to check or debug Flink SQL whose runtime is Confluent Cloud. Also trigger when a Flink SQL question is posed and nothing establishes an Apache Flink OSS runtime. Do NOT trigger for: building or deploying Flink UDFs in Java (UDF/UDTF/PTF — use flink-udf); a full CDC pipeline from a database through Flink into Tableflow/Iceberg/Delta Lake (use confluent-cloud-cdc-tableflow); Kafka Streams topology work (use kafka-streams-programming); or Flink SQL confirmed to run on Apache Flink OSS, not Confluent Cloud. | Skills | |
menkesu/awesome-pm-skills Diagnoses product-market fit from survey, usage and pipeline data and returns a scored verdict with the next moves. Use when you ask 'do we have product-market fit', 'is our PMF survey good enough', 'what does 35% very disappointed mean', 'should we scale yet', 'why is growth stalling', or need a Sean Ellis survey, retention check, or PMF level read. Draws on 137 insights from 66 Lenny's Podcast guests incl. Sean Ellis, Todd Jackson and Rahul Vohra. | Skills | |
jscraik/Agent-Skills Plan AI-native hackathon scope, demo pitch, and judge Q&A. Use when the user needs 1-hour pitch prep, 24-hour build scoping, AI Native DevCon-style track choice, idea pressure tests, or a spec-led hack plan. Do not use for code generation, implementation support, or non-hackathon DevRel content. | Skills | |
jscraik/Agent-Skills Review local dirty changes, committed branches, and PR diffs with Codex CLI; report findings, validation, blockers, and merge-readiness evidence. Use when the user asks for Codex review, autoreview, independent model review, or pre-ship validation. | Skills | |
jscraik/Agent-Skills Answers questions about, retrieves safe excerpts from, explains concepts from, and summarizes key arguments in Birgitta Böckeler's talk "State of Play: AI Coding Assistants" (AI Native Dev conference, 2026). Use when the user asks about the last 12 months in AI coding assistants, model-task fit, LLM statelessness, context window and attention trade-offs, coding harnesses, harness engineering/context engineering, skills/MCP/sub-agents/plugins/hooks, guide-and-sensor feedback loops, background agents and swarms, review bottlenecks, AI coding costs, cognitive surrender, or risk-based supervision of coding agents. | Skills | |
affaan-m/ECC Direct PubMed and NCBI E-utilities search workflows for biomedical literature, MeSH queries, PMID lookup, citation retrieval, and API-backed literature monitoring. Use when a task needs biomedical literature from PubMed rather than general web search. | Skills | |
affaan-m/ECC Orchestrate bootstrapping a working MVP from a design or spec document — ingest the SDD/PRD, plan thin vertical slices, scaffold the first end-to-end slice, then drive a generator-evaluator build loop with review and gated feat commits. Use when a design or spec document must become a running MVP through planned vertical slices. | Skills | |
affaan-m/ECC Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured "explain how this works" requests. Use when the user asks for a code tour, onboarding walkthrough, PR tour, or an explanation of how a subsystem works. | Skills | |
mthines/agent-skills Ships coding work to a tested draft PR from one opt-in entry point: detects the tier, runs Micro/Lite here, and on Full writes a short brief with sealed checks, works to them here, and converges once with a local review loop before the PR; prints a paste-ready /goal. Use when asked to "implement autonomously", "independently", "in isolation", "in a worktree", "end-to-end", "all the way to a PR", "ship this", "land this", "take care of this", "handle this without me", or /aw. | Skills | |
administrakt0r/AI-Agents-Safe-Coding-Skills Git-aware undo by logical work unit (track, phase, or task) | Skills | |
administrakt0r/AI-Agents-Safe-Coding-Skills Git-aware undo by logical work unit (track, phase, or task) | Skills | |
administrakt0r/AI-Agents-Safe-Coding-Skills Git-aware undo by logical work unit (track, phase, or task) | Skills | |
UiPath/skills UiPath StudioAdmin AOps (`uip aops`) — SourceControl discovery plus CICD pipelines. Drives `aops connection` / `repo` / `project` / `solution` to resolve a GitHub or Azure source binding, `aops pipeline processes` to pick an already-published Orchestrator process, then composes a PipelineDto for `pipeline create` / `save-and-run` and follows runs via `aops execution logs --follow`. Replaces the retired `uip sc` and `uip cicd` tools. For AOps governance policies (`uip gov aops-policy`)→uipath-governance. For `uip solution pack/publish/deploy`→uipath-platform. For workflow authoring (.xaml/.cs)→uipath-rpa. | Skills | |
PostHog/posthog Debugs failing GitHub Actions CI runs for PostHog PRs, commits, and branches, and answers broad CI-health questions ("is CI red?", "is master green today?", "what's broken right now?"). Use when the user asks why CI is red, asks for the current CI or master status, or mentions a failing check, GitHub Actions run, Depot runner, Depot CI run, workflow, job, shard, merge queue kick, flaky test, lint failure, typecheck failure, snapshot diff, migration check, generated types drift, or skills build failure. Interactive runs start with the `hogli ci:insights` digest (cross-run CI history from engineering analytics), then use read-only inspection, failure classification, the smallest local reproduction with hogli, and safe reporting without rerunning CI or posting to GitHub. Running unattended as the "Master-red diagnosis" workflow: see references/master-red-incident.md for its sandbox-compatible first step. | Skills | |
MapleTechLabs/maple Trace Pydantic AI agents with Maple: export Pydantic AI's built-in OpenTelemetry spans (with or without Logfire) so each conversation is one Maple Agent Session with transcript, tool calls, sub-agent lanes and tokens. Triggers on 'trace my pydantic ai agent', 'add Maple to pydantic ai', 'agent sessions for pydantic ai', 'OpenTelemetry for pydantic ai'. | Skills | |
ollygarden/ollygarden-cli Design command-line interface parameters and UX: arguments, flags, subcommands, help text, output formats, error messages, exit codes, prompts, config/env precedence, and safe/dry-run behavior. Use when you’re designing a CLI spec (before implementation) or refactoring an existing CLI’s surface area for consistency, composability, and discoverability. | Skills | |
meshtastic/Meshtastic-Android Apply the Meshtastic design standards on Android - brand colors, Material 3 tokens, MeshtasticIcons and accessibility - with the upstream `meshtastic/design` standards as the source of truth. Use this whenever you choose a color, icon, spacing value or contrast level, and before claiming a screen matches the design. | Skills |
Can't find what you're looking for? Evaluate a missing skill.