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.
49,492 skills from 2,391 repositories · updated 19 hours ago
48,451 skills
- ase-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when shaping the prose and structure of an ASE (IEEE/ACM Automated Software Engineering) research paper, covering the automation-first first-page arc, stating the automated task precisely, keeping the tool runnable and the model-swap test in mind, threats-as-argument, and the 10+2 page discipline on the ACM acmart template.WritingNo warnings★ 1.4K↓ —
- colm-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the empirical core of a COLM paper — contamination analysis for evaluation data, fair baselines under matched prompting and compute, pinned model versions and decoding parameters, uncertainty over runs and samples, scaling coverage, and honest reporting of API-model comparisons.ScienceNo warnings★ 1.4K↓ —
- chi-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when drafting or revising the prose of an ACM CHI paper — contribution statements, structure for mixed reviewer audiences, participant voice, calibrated claims, accessible and bias-free writing, and length discipline in a venue that reviews words against contribution instead of pages.WritingNo warnings★ 1.4K↓ —
- colt-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when deciding whether a COLT (Conference on Learning Theory) paper needs numerical content at all — COLT has no experiments requirement — and, when numerics genuinely help, designing small illustrative simulations that visualize a proved bound, a separation, or a phase transition without diluting the theory.MediaNo warnings★ 1.4K↓ —
- cikm-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the empirical program of a CIKM paper — matching evidence to the claim's lanes across retrieval, mining, and knowledge-management evaluation cultures, choosing datasets and baselines that survive a blended panel, isolating the boundary mechanism, and meeting applied-track deployment-evidence bars.DevOpsNo warnings★ 1.4K↓ —
- cav-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when revising a CAV (Computer Aided Verification) paper for a precise verification contribution on the first page, an explicit soundness/completeness statement, theorem-and-proof discipline in the LNCS page budget, fair benchmark claims, honest scope and limits, and double-blind wording for the anonymized categories.WritingNo warnings★ 1.4K↓ —
- openspec-apply-changeMemeMeow-Studio/MemeMeowImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.ProductivityNo warnings★ 1.3K↓ —Also in 1 other repo
- openspec-exploreMemeMeow-Studio/MemeMeowEnter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.FinanceNo warnings★ 1.3K↓ —Also in 1 other repo
- openspec-archive-changeMemeMeow-Studio/MemeMeowArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.ProductivityNo warnings★ 1.3K↓ —
- openspec-apply-changeMemeMeow-Studio/MemeMeowImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.ProductivityNo warnings★ 1.3K↓ —
- openspec-update-changeMemeMeow-Studio/MemeMeowUpdate an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.WritingNo warnings★ 1.3K↓ —
- openspec-update-changeMemeMeow-Studio/MemeMeowUpdate an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.WritingNo warnings★ 1.3K↓ —
- openspec-update-changeMemeMeow-Studio/MemeMeowUpdate an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.WritingNo warnings★ 1.3K↓ —
- cloudbase-declarative-deployTencentCloudBase/CloudBase-AI-ToolkitCloudBase declarative deployment from a cloudbaserc config (声明式部署, 配置式部署, cloudbaserc 部署) through the deployBuild / deployPlan / deployApply MCP tools. Use when deploying database, functions, app, hosting, or gateway resources described in cloudbaserc.json/yaml as a single desired-state config, when a user wants to build static hosting artifacts locally first (deployBuild), or wants a dry-run plan before applying (deployPlan), or when handling multi-environment deploys via mode / envOverrides. Covers build-plan-apply flow (deployBuild local build → deployPlan dry-run → deployApply confirm=true), hosting build-output neutralization, envId resolution priority, only/skip filtering, concurrency, and continueOnError. Prefer deployBuild (when hosting declares a buildCommand) and deployPlan before deployApply; do not confuse with per-resource tcb CLI deploy or single-function deploy.DevOpsNo warnings★ 1.2K↓ —Also in 5 other repos
- Invalid_Namefirst-fluke/oh-my-agentA specialist team for the coding agent you already use: 12 roles, 21 workflows and 33 skills that plan, build in parallel, review and debug, leaving plans, ADRs and results as files. Gates wait for your own tests. Also research, slides and video. One .agents/ folder for Claude Code, Codex, Cursor and 11 more.TestingNo warnings★ 1.4K↓ —
- oma-observabilityfirst-fluke/oh-my-agentDesign or troubleshoot telemetry, SLOs, and incident diagnostics. Route to the relevant signal, system boundary, or vendor guide.DevOpsNo warnings★ 1.4K↓ —Also in 1 other repo
- email-lifecycle-lifecycle-auditgooseworks-ai/goose-skillsStep of the email-lifecycle playbook: audits list, consent, live flows, recent sends and sending setup, marking every item verified, from-you or unknown. Run email-lifecycle instead; not for direct use.ProductivityNo warnings★ 1.3K↓ —
- folded-desc-skillfirst-fluke/oh-my-agentA fixture whose description uses a YAML folded scalar, which parses with an embedded trailing newline unless normalized before use in Markdown tables.OtherNo warnings★ 1.4K↓ —
- improve-architecturedaveebbelaar/bamaArchitecture check-in for a growing macOS Swift codebase. Finds hot spots, proposes deeper modules, and refactors one step per commit with behavior proven unchanged. Use at the end of a milestone, before a big feature, when a file passes 600 lines, when one feature touches many files, when bugs repeat in one area, or when the user asks to refactor or clean up the code.PlanningNo warnings★ 1.5K↓ —
- setupfcakyon/claude-codex-settingsThis skill should be used when user encounters "ADC not found", "gcloud auth error", "GCloud MCP error", "Application Default Credentials", "project not set", or needs help configuring GCloud integration.OtherNo warnings★ 1.2K↓ —
- k2fcakyon/claude-codex-settingsBuild and troubleshoot Cloudflare K2 or K2 Streams durable logs. Use for stream setup, producing from Workers or HTTP, configuring retention and inputs, and consuming through subscriptions.DevOpsNo warnings★ 1.2K↓ —
- reading-livekit-docsfcakyon/claude-codex-settingsLooks up current LiveKit facts (API signatures, CLI flags, config options, model and provider support, SDK changelogs, pricing) from the docs instead of answering from memory. Use whenever a question touches LiveKit specifics: "does LiveKit support X", "what changed in agents 1.8", "what are the arguments to Y", "how much does LiveKit cost", "find an example of Z in the LiveKit repos", or before writing any LiveKit code. Other LiveKit skills load this one first. Covers the LiveKit Docs MCP server and the `lk docs` CLI.WritingNo warnings★ 1.2K↓ —Also in 1 other repo
- resolve-entity-identitysno-ai/sno-stationResolve a new entity display name to an existing entity id or to a new entity.OtherNo warnings★ 1.1K↓ —
- analyze-performance-diagnosegooseworks-ai/goose-skillsStep of the analyze-performance playbook: flags tracking breaks with fixes and explains each big metric move with evidence, confidence and ruled-out causes. Run analyze-performance instead; not for direct use.OtherNo warnings★ 1.3K↓ —
mcp-oauth-triage
alirezarezvani/claude-skills
EngineeringUpdated 2 days ago
From the author
Use when an MCP connector that used to authenticate now fails (tool calls 401 after a good token exchange, breaks after refresh, returns another account's data), before changing code. Classifies the fault with oauth_triage.py.
Install
npx skills add alirezarezvani/claude-skills --skill mcp-oauth-triage -a claude-code
Installs to .claude/skills/mcp-oauth-triage/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
What it can touch
Runs bundled scriptsNo network use seenLicence: MIT
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 88
Security85
Provenance94
Maintenance100
Licence100
Adoption69
Files (17)
- README.md
- SKILL.md
- assets/fixtures/binding_record.json
- assets/fixtures/clean_events.jsonl
- assets/fixtures/clean_record.json
- assets/fixtures/envelope_record.json
- assets/fixtures/expiry_record.json
- assets/fixtures/negative_cache_events.jsonl
- assets/fixtures/negative_cache_record.json
- assets/fixtures/rotation_events.jsonl
- assets/fixtures/rotation_record.json
- examples/rotation-clobber-walkthrough.md
- +5 more