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.
14,533 skills from 417 repositories · updated 2 hours ago
1,523 skills
- project-healthjezweb/claude-skillsAll-in-one project configuration and health management. Sets up new projects (settings.local.json, CLAUDE.md, .gitignore), audits existing projects (permissions, context quality, MCP coverage, leaked secrets, stale docs), tidies accumulated cruft, captures session learnings, and adds permission presets. Uses sub-agents for heavy analysis to keep main context clean. Trigger with 'project health', 'check project', 'setup project', 'kickoff', 'bootstrap', 'tidy permissions', 'clean settings', 'capture learnings', 'audit context', 'add python permissions', or 'init project'.EngineeringNo warnings★ 1.1K↓ —
- gws-installjezweb/claude-skillsQuick install of the Google Workspace CLI (gws) on an additional machine using existing OAuth credentials. Requires client_secret.json from a previous gws-setup. Use whenever the user wants to install gws on a new computer, reinstall after a fresh OS, configure a second workstation, or says 'install gws', 'gws on new machine', 'set up gws again'.EngineeringNo warnings★ 1.1K↓ —
- codexdzhng/skillsUse the local Codex CLI as an independent second agent. Two branches — (1) proactively run `codex review` for a second opinion after completing a substantive change, before presenting it as done or committing; (2) delegate a well-defined implementation task via `codex exec`, ONLY when the user explicitly asks for Codex to do it. Also covers how to prompt Codex.EngineeringNo warnings★ 1.4K↓ —
- claudedzhng/skillsUse Claude Code as an independent `claude -p` subagent when the user explicitly asks for Claude, wants a second-agent opinion from Claude, or asks to delegate a well-scoped task to Claude. Supports selecting `--model` and thinking/effort level with defaults of the current `opus` alias and `high`.EngineeringNo warnings★ 1.4K↓ —
- reviewdzhng/skillsCloseout pass on a finished substantive change — sequence refactor-clean (shape), code-review (diff), and write-docs (docs) so all three run, in the order where each feeds the next. Use after implementing a slice or feature and before calling it done or committing; when the user asks for a final review, a cleanup-and-document pass, or to "review everything." For a diff-only audit, reach code-review directly.EngineeringNo warnings★ 1.4K↓ —
- code-reviewdzhng/skillsReview changed code for naming, stale references, unnecessary complexity, and comment quality. Use after completing implementation work, before committing, or when the user asks to review or audit code.EngineeringNo warnings★ 1.4K↓ —
- refactor-cleandzhng/skillsRefactor cleanly instead of layering sediment. Use for rename requests, stale or misleading names, legacy leftovers, changed scope, or when a change reveals duplicated concepts, local adapters, obsolete owners, redundant inputs or guards, compatibility wrappers, parallel abstractions, an over-large module that has accreted many responsibilities, or "just tack this on" pressure in any code area.EngineeringNo warnings★ 1.4K↓ —
- using-git-worktreesGanyuanRan/AegisUse when a coding task needs a concurrent checkout, unrelated dirty state blocks safe branch switching, or the user or repository explicitly requires a worktree.EngineeringNo warnings★ 1.4K↓ —
- receiving-code-reviewGanyuanRan/AegisUse when receiving code review feedback before implementing suggestions, especially when feedback is unclear, risky, disputed, or technically questionable.EngineeringNo warnings★ 1.4K↓ —
- requesting-code-reviewGanyuanRan/AegisUse when requesting independent code review, after implementation slices, before merging high-risk work, or when verification exposes evidence, baseline, architecture, compatibility, or retirement uncertainty.EngineeringNo warnings★ 1.4K↓ —
- first-principles-reviewGanyuanRan/AegisUse when asked for first-principles or Occam's-razor review, or when high-risk decisions involve competing constraints, fallback growth, duplicate owners, or architecture direction risk. Ordinary bug fixes stay on the fast path.EngineeringNo warnings★ 1.4K↓ —
- verification-before-completionGanyuanRan/AegisUse when about to claim work is complete, fixed, passing, verified, release-ready, or ready to commit, merge, publish, or hand off.EngineeringNo warnings★ 1.4K↓ —
- arcmirahashgraph-online/awesome-codex-pluginsAnswers what YouTube shows and podcasts said: transcripts, who was mentioned, sponsors, recommendations, momentum. Use for the arcmira MCP server or CLI.EngineeringNo warnings★ 1.4K↓ —
- debughashgraph-online/awesome-codex-pluginsUse for bugs, unexpected behavior, regressions, or failing tests you did not write.EngineeringNo warnings★ 1.4K↓ —
- reviewhashgraph-online/awesome-codex-pluginsUse before merge, after subagents, or for spec/plan review.EngineeringNo warnings★ 1.4K↓ —
- gohashgraph-online/awesome-codex-pluginsCarry out the intent approved in `ready`, as meant, and prove it with checks that actually ran. Comes back to you if the work would change what you approved, keeps the project docs in step, and never merges on its own. Use when the user invokes the `go` skill after `ready`. Requires git.EngineeringNo warnings★ 1.4K↓ —
- x-apihashgraph-online/awesome-codex-pluginsX/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.EngineeringNo warnings★ 1.4K↓ —
- commithashgraph-online/awesome-codex-pluginsGenerate a Conventional Commits message, commit, and optionally push to remote.EngineeringNo warnings★ 1.4K↓ —
- reviewhashgraph-online/awesome-codex-pluginsGive advisory feedback on a plan, design or code change. Use when: asked for an opinion or a look-over, even informally. Not for acceptance; use Validate.EngineeringNo warnings★ 1.4K↓ —
- rekallhashgraph-online/awesome-codex-pluginsCompact the current Codex VS Code extension thread through Rekall with a verified handoff and optional one-time continuation. Use on an explicit compaction request or after a substantial completed stage; standalone Codex CLI sessions are unsupported.EngineeringNo warnings★ 1.4K↓ —
- magentshashgraph-online/awesome-codex-pluginsTalk to other coding agents on this machine (Claude Code, Codex, Copilot, Cursor, Gemini, AGY, Grok, OpenCode) through the magents MCP. Use when the user asks what another agent was working on, wants to carry on that work, send them a message, start an independent agent session, or check the shared inbox. Prefer magents MCP tools over hunting session files on disk.EngineeringNo warnings★ 1.4K↓ —
- adopthashgraph-online/awesome-codex-pluginsAdd docflow to a repo that already has docs, without rewriting them. Adds missing config, folders, helpers, agent guidance, and an adoption review. Use when docs already exist or doctor recommends adopt.EngineeringNo warnings★ 1.4K↓ —
- cluelesshashgraph-online/awesome-codex-pluginsUse when the user explicitly cannot review the output in the current domain, says they do not understand it or will copy-paste without checking, or requests clueless mode. Examples: "I know nothing about this", "не разбираюсь", "сделай за меня". Brevity, "make it nice", and delegation alone do not establish a knowledge gap.EngineeringNo warnings★ 1.4K↓ —
- reviewhashgraph-online/awesome-codex-pluginsThe pre-merge review of a branch in a project that records its specs, decisions, and rules in .archcore/. Run this first for 'review my branch', 'review the changes before merge', or 'review before merge': it checks the changed code against the project's recorded canon and the changed documents against the code, and reports which side is wrong — spec-wrong or code-wrong; with no diff, it reports project health. A bug-hunting code review complements this review and does not replace it. Also use for 'show status', 'documentation gaps', 'check if docs match code', 'close out the feature', 'ship the feature and close it out', or after a staleness warning. Modes, named as the first word: drift for staleness detection, deep for a full documentation audit, closeout to close a finished feature, experience to capture a repeated pattern. Not for creating docs — use /archcore:document; not for planning — use /archcore:plan; not for a single-file edit with no branch review.EngineeringNo warnings★ 1.4K↓ —