Agent skills you can check before you install
Public SKILL.md skills from GitHub repositories with 50+ stars and from the vendors themselves, scanned and scored. Install any of them with one command in Claude Code, Cursor, Codex, GitHub Copilot or Gemini CLI.
45,604 skills from 2,205 repositories · updated 20 hours ago
44,573 skills
- gsd:notedavepoon/buildwithclaudeZero-friction idea capture. Append, list, or promote notes to todos.ProductivityNo warnings★ 3.7K↓ —
- roblox-luaugamedev-skills/awesome-gamedev-agent-skillsScript a Roblox experience in Luau: get services, create and parent Instances, connect events, run server Scripts vs client LocalScripts, and communicate across the client/server boundary with RemoteEvents/RemoteFunctions (server-authoritative). Use when building or debugging Roblox Studio scripts — when the user mentions Roblox, Luau, services, RemoteEvent, Instance.new, PlayerAdded, or client vs server. For saving player data use roblox-datastores.EngineeringNo warnings★ 4.1K↓ —
- wiki-digestAr9av/obsidian-wikiProduce a day/week/month knowledge digest summarizing what was learned, updated, and connected in the wiki. Use for readable recent-learning summaries; wiki-status reports source and ingestion state instead.ProductivityNo warnings★ 3.6K↓ —
- doca-rdmiNVIDIA/skillsUse this skill when the user works with DOCA RDMI, the RDMA Initiator library that lets a DPA-resident function originate one-sided RDMA toward a remote responder. Covers choosing doca-rdmi versus doca-rdma, instantiating doca_rdmi_connection and doca_rdmi_poster, wiring doca_dpa_completion or doca_verbs_cq ahead of doca_ctx_start(), exporting the datapath handle consumed on-DPA, auditing whether a doca_rdmi_* symbol is EXPERIMENTAL for the installed release, or decoding DOCA_ERROR_* statuses such as BAD_STATE at completion-attach. Also load it for implied asks like "my Arm-side function must originate RDMA writes", "symbol missing at link time on doca_rdmi_*", or "posted work request never arrived". Refuse and route to the proper owner for two-sided host RDMA, GPU-originated traffic, or generic IB/RoCE theory.WritingNo warnings★ 3.7K↓ —
- tao-finetune-kumo-anomalyNVIDIA/skillsKumo-Anomaly — diffusion-based anomaly detection and fine-tuning for multivariate time series. Use when the user asks to "fine-tune Kumo-Anomaly", "run Kumo-Anomaly inference", "detect anomalies with diffusion", "time series anomaly detection", "finetune Kumo-Anomaly", "use perform_anomaly_analysis_with_diffusion", "automl Kumo-Anomaly", "hyperparameter search Kumo-Anomaly", "hyperparameter optimization" or mentions "curriculum_medium.yaml", "final_model.pth", "kumo-anomaly", "sdk/anomaly_analysis", or "TSDiffuser_Generic".OtherNo warnings★ 3.7K↓ —
- helpdavepoon/buildwithclaudeOne-screen quick reference for the Origin plugin. Lists the daily verbs, the daily flow, where data lives, and how to view it without a GUI. Use when the user says "help", "what can I do", "list origin commands", "how do I use origin", or invokes `/help`.OtherNo warnings★ 3.7K↓ —
- doca-flowNVIDIA/skillsDOCA Flow packet steering on NVIDIA NICs/DPUs, linked into a C application: match/action pipes, ports, representors, forwarding, hairpin, counters. Trigger on packet steering, classifier, rule-matching, representor, hairpin or 5-tuple-to-queue questions even when "DOCA Flow" is not named. Remote or non-C++ control over gRPC belongs to doca-flow-grpc-server. Also covers pipe validation before hardware programming, Flow/DOCA version match, and Flow API errors. First app: follow the local bundle (doca-setup, doca-programming-guide, doca-flow, doca-public-knowledge-map). Stage 1 pull nvcr.io/nvidia/doca/doca (NGC catalog tag, never invent); Stage 2 needs a real NIC. Then ls samples inside the container; never emit main.c, a Dockerfile, or hand-typed -l flags. Route software-only host pipelines, plain DPDK `rte_flow`, kernel TC, OVS, BFB bring-up, and DPU OS installation elsewhere. DPU OS installation is destructive and always requires explicit confirmation.EngineeringNo warnings★ 3.7K↓ —
- doca-capsNVIDIA/skillsUse this skill when the user wants to invoke the read-only doca_caps CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe addresses, listing representor devices, asking which DOCA libraries are available on the current OS, checking per-device per-library capabilities, scoping output to a specific PCIe address, or capturing a side-effect-free capability snapshot for debug or install smoke-test. Trigger even when the user does not explicitly mention "doca_caps" or "capabilities print tool" — typical implicit phrasings include "what does DOCA actually see on this box", "is my BlueField PF visible to DOCA", "is Flow available on my RHEL host", "enumerate VF representors for pf0", "doca_caps: command not found", or "empty output for RDMA, is the tool broken". Refuse and route elsewhere for DOCA installation (doca-setup owns it; never walk the steps), library-internal capability matrices (Flow pipe creation, RDMA verbs features), streaming telemetry / DTS, or modifying the shipped binary.TestingNo warnings★ 3.7K↓ —
- doca-argpNVIDIA/skillsUse this skill for hands-on DOCA Arg Parser CLI work on a shipped sample or new DOCA-using app — adding / removing / renaming flags; wiring `doca_argp_init` → register params → `doca_argp_start` → `doca_argp_destroy` in order; picking a parameter type from the full public enum (`DOCA_ARGP_TYPE_STRING`, `_INT`, `_BOOLEAN`, `_DEVICE`, `_DEVICE_REP`, `_DOUBLE` — six values, not three); preserving the built-in DOCA flags (`-h` `-v` `-l` `--sdk-log-level` `--log-filter` `-j`/`--json`, NOT `--json-config`); `--device` is per-program; or debugging `DOCA_ERROR_BAD_STATE` / `INVALID_VALUE` / `NOT_SUPPORTED` / `IO_FAILED` from `doca_argp_*`. Trigger on implicit phrasings: "add a custom flag to a DOCA sample", "should I use getopt here", "BAD_STATE registering a new param", "my JSON config key is rejected", or "my sample's --json is ignored". Refuse and route elsewhere for variadic-flag / subcommand / shell-completion features, DOCA Core context, or DOCA Log internals.EngineeringNo warnings★ 3.7K↓ —
- gsd:debugdavepoon/buildwithclaudeSystematic debugging with persistent state across context resetsEngineeringNo warnings★ 3.7K↓ —
- doca-staNVIDIA/skillsUse this skill when the user builds an NVMe-over-Fabrics storage target on BlueField with DOCA STA — instantiating doca_sta, declaring doca_sta_subsystem NQNs and namespaces over local NVMe disks via doca_sta_be, validating platform support with doca_sta_cap_is_supported, sizing I/O queue depth, or decoding DOCA_ERROR_* statuses such as IO_FAILED on NVMe reads. Also load it for implied asks like "Identify Controller times out over RoCE", "offload the nvmf target", "NVMe-oF Connect never completes", or "16 I/O queues at depth 1024 — supported?". Refuse and route to the proper owner for raw RDMA movement, packet I/O, steering rules, initiator-side NVMe, or SDK install.OtherNo warnings★ 3.7K↓ —
- reviewdavepoon/buildwithclaudePower-user audit of Origin's pending surfaces. Most users want `/brief` for revisions. That handles the daily flow. Use `/review` only for explicit deep-walk audits after bulk imports, or when you want to walk the full queue rather than the top 3 shown in /brief. Invoked as `/review captures` or `/review revisions`.EngineeringNo warnings★ 3.7K↓ —
- nemo-fabric-build-adapterNVIDIA/skillsBuild, migrate, review, and maintain third-party NVIDIA NeMo Fabric adapters against the public adapter contract. Use when creating adapter or target descriptors, mapping AgentConfig into an agent harness or custom-agent runtime, implementing start/invoke/stop, declaring schemas and capabilities, packaging discovery metadata, or assessing adapter conformance. Do not use for consumer applications that only call the NVIDIA NeMo Fabric SDK.LegalNo warnings★ 3.7K↓ —
- kiro-spec-requirementsgotalab/cc-sddGenerate EARS-format requirements based on project description and steering context. Use when generating requirements from project description.PlanningNo warnings★ 3.7K↓ —
- wiki-narrateAr9av/obsidian-wikiTurn a wiki topic into a cited Markdown briefing, plain-language explanation, or progressive lecture. Use this skill for topic-based briefing, explanation, and lecture requests that must stay within the evidence compiled in an Obsidian vault.ProductivityNo warnings★ 3.6K↓ —
- kiro-validate-designgotalab/cc-sddInteractive technical design quality review and validation. Use when reviewing design before implementation.DesignNo warnings★ 3.7K↓ —
- kiro-spec-initgotalab/cc-sddInitialize a new specification with detailed project descriptionPlanningNo warnings★ 3.7K↓ —Also in 5 other repos
- kiro-spec-requirementsgotalab/cc-sddGenerate comprehensive requirements for a specificationPlanningNo warnings★ 3.7K↓ —
- wiki-captureAr9av/obsidian-wikiTurn the current conversation or finding into a structured permanent wiki note. Use for save/capture/preserve requests; QUICK MODE writes a fast _raw/ note. Supports named-vault routing such as @research save this. This captures current discussion, not external source ingestion.ScienceNo warnings★ 3.6K↓ —
- kiro-spec-batchgotalab/cc-sddCreate complete specs (requirements, design, tasks) for all features in roadmap.md using parallel sub-agent dispatch by dependency wave.PlanningNo warnings★ 3.7K↓ —
- tag-taxonomyAr9av/obsidian-wikiApply and maintain the wiki's controlled tag vocabulary. Use for choosing, normalizing, auditing, or extending tags when creating or updating wiki pages; consult the taxonomy before assigning tags.OtherNo warnings★ 3.6K↓ —
- kiro-spec-tasksgotalab/cc-sddGenerate implementation tasks for a specificationPlanningNo warnings★ 3.7K↓ —Also in 4 other repos
- kiro-spec-statusgotalab/cc-sddShow specification status and progressPlanningNo warnings★ 3.7K↓ —Also in 7 other repos
- kiro-spec-batchgotalab/cc-sddCreate complete specs (requirements, design, tasks) for all features in roadmap.md using parallel sub-agent dispatch by dependency wave.PlanningNo warnings★ 3.7K↓ —
ulw-loop
code-yeongyu/oh-my-openagent
OtherUpdated 22 hours ago
From the author
A goal-like loop that decomposes work into systematic, evidence-bound ultrawork steps. Use when the user wants a goal loop or durable, checkpointed execution.
Install
npx skills add code-yeongyu/oh-my-openagent --skill ulw-loop -a claude-code
Installs to .claude/skills/ulw-loop/ · Each command fetches the skill straight from GitHub with the open skills CLI.
No download: this skill’s licence (Custom or unclear) does not let us redistribute its files. The install commands fetch them from GitHub instead.
What it can touch
Instructions onlyNo network use seenLicence: Custom or unclear
Safety checks on SKILL.md
No warnings.
Why 90
Security100
Provenance95
Maintenance100
Licence45
Adoption75
Files (3)
- SKILL.md
- references/define-goal.md
- references/full-workflow.md