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,415 skills from 2,407 repositories · updated 1 hour ago
49,415 skills
- creating-agent-skillsAgentWorkforce/relayUse when creating Agent Skills packages (SKILL.md format) for Codex CLI, GitHub Copilot, or Amp - provides the agentskills.io specification with frontmatter constraints, directory structure, and validation rulesPlanningNo warnings★ 1.1K↓ —
- aeofcakyon/claude-codex-settingsThis skill should be used when the user asks to "build an AEO strategy", "improve AI search visibility", "track buyer prompts", "analyze AI citations", or "plan content for answer engines". Apply an evidence-led answer engine optimization (AEO/GEO) feedback loop to any product or service, prioritizing discovery by buyers who have not heard of it.PlanningNo warnings★ 1.2K↓ —
- setupfcakyon/claude-codex-settingsThis skill should be used when user encounters "Tavily MCP error", "Tavily API key invalid", "web search not working", "Tavily failed", or needs help configuring Tavily integration.EngineeringNo warnings★ 1.2K↓ —
- creating-claude-agentsAgentWorkforce/relayUse when creating or improving Claude Code agents. Expert guidance on agent file structure, frontmatter, persona definition, tool access, model selection, and validation against schema.EngineeringNo warnings★ 1.1K↓ —
- orchestrating-agent-relayAgentWorkforce/relayThe canonical way to run agent-relay - self-bootstrap the local broker and autonomously spawn, monitor, and coordinate a team of worker agents without human intervention. Covers infrastructure startup, agent spawning, lifecycle monitoring, message-based reading via the relay MCP, and team coordination.DevOpsNo warnings★ 1.1K↓ —
- fix-what-i-pointed-atreticlehq/reticlePick up the bugs a human flagged by pointing at them in the running app, each arriving with the element, the note they typed, and the source file and line. Use when the user says they marked or flagged something, when starting a session on an app someone has been clicking through, when a designer or PM has left feedback in the UI, or when the user describes a problem as "that button there" without saying which file.DesignNo warnings★ 1.2K↓ —
- verify-language-switchreticlehq/reticleProve a language switch translates what the user sees, keeps what they had already typed, and is still in force after a reload. Use when i18n, a locale picker, a language menu or translation files were added or changed, when a string is suspected of staying in the old language or showing a raw translation key, or when a user reports losing their form or their language choice after switching or refreshing.OtherNo warnings★ 1.2K↓ —
- orchestrating-agent-relayAgentWorkforce/relayThe canonical way to run agent-relay - self-bootstrap the local broker and autonomously spawn, monitor, and coordinate a team of worker agents without human intervention. Covers infrastructure startup, agent spawning, lifecycle monitoring, message-based reading via the relay MCP, and team coordination.DevOpsNo warnings★ 1.1K↓ —
- verify-unattendedreticlehq/reticleInstall, instrument and verify a web app end to end without pausing for a human. Use in an autonomous or goal-mode agent, in CI, or in any client that asks for approval on every command: it never says "restart your client" or "open a browser", because it takes a route that needs neither. Prefer the normal reticle skill when a human is present and can answer.BrowserNo warnings★ 1.2K↓ —
- verify-paginationreticlehq/reticleProve the next page of a list, or the next batch of an infinite scroll, loads NEW rows from the server, repeats none, and that the end of the list is handled. Use when pagination or infinite scroll was added or changed, when a list shows the same rows twice or skips some, or when the last page still offers a next control.OtherNo warnings★ 1.2K↓ —
- review-fix-signoff-loopAgentWorkforce/relayUse when writing Agent Relay or Ricky workflows that must loop review, fix, and validation with fresh agent context until independent signoff agents, typically Claude and Codex, both agree the work is comprehensively complete. Covers fresh-context iterations, repairable gates, dual reviewer verdict contracts, iteration-count reporting, PR signoff comments, and blocked-state handling.EngineeringNo warnings★ 1.1K↓ —
- design-system-compliancereticlehq/reticleCheck that the UI you actually rendered uses the design system, by reading computed styles in the running app against the project's design tokens. Catches hardcoded hex colors, off-palette backgrounds, invisible or unusable controls, and animations that never ran. Use after building or restyling a component, when a design review is wanted, when a UI looks slightly off but nobody can say why, or when a design system exists and nothing checks whether the code follows it.DesignNo warnings★ 1.2K↓ —
- relay-80-100-workflowAgentWorkforce/relayUse when writing agent-relay workflows that must fully validate features end-to-end before merging. Covers the 80-to-100 pattern - going beyond "code compiles" to "feature works, tested E2E locally." Includes repair-before-failure validation gates, review-depth fresh-eyes review/fix loops with test hardening, PGlite for in-memory Postgres testing, mock sandbox patterns, test-fix-rerun loops, verify gates after every edit, and the full lifecycle from implementation through passing tests to commit.ProductivityNo warnings★ 1.1K↓ —
- setupmicrosoft/power-platform-skillsUse when Process Intelligence needs building, explicit cloud/account/environment configuration, sign-in, connection diagnostics, or recovery from an authentication error.OtherNo warnings★ 1.1K↓ —
- writing-relayflowsAgentWorkforce/relayUse when authoring a Relayflows flow (@relayflows/surface / @relayflows/sdk, the journal-based v2 engine — the CLI is `flows`, package versions 2.0.x) in TypeScript or YAML/JSON. Covers the three-rung ladder (run/llm/agent), the resident verbs (human/dispatch/done), verification gates, TypeScript vs YAML authoring, per-step cli/model selection and its resolution order, flows.json, and `flows check`/`run`/`resume` with their real refusal shapes and exit codes. Not for the older, unrelated `@relayflows/core` WorkflowBuilder engine (`.pattern('dag')`/.agent()/.step() chains) that `writing-agent-relay-workflows` and `migrating-persona-to-relayflow` cover — that's a different product despite the similar name.WritingNo warnings★ 1.1K↓ —
- false-green-testsreticlehq/reticleFind out why the tests pass but the app is broken. Catches false greens: a green suite over a feature that does not work, a mocked API standing in for a real one, an assertion that holds no matter what the app does, a click handler wired to nothing. Use when the suite is green and the user says it is broken, when a test never fails, when coverage looks fine but bugs still ship, or before trusting a passing run you did not watch.TestingNo warnings★ 1.2K↓ —
- setting-up-relayfileAgentWorkforce/relayUse when an agent or human needs to set up relayfile end-to-end so agents can read and write provider files through a local mount. Covers `relayfile setup`, dynamic integration discovery with `relayfile integration available/search`, Nango and Composio backend selection, Atlassian site selection and metadata, cloud login, OAuth/connect flows, mount verification, `RELAYFILE_LOCAL_DIR` handoff, writeback status and retry commands, and key May 2026 cloud-mount gotchas.WritingNo warnings★ 1.1K↓ —
- replay-user-flowsreticlehq/reticleTurn a user journey you just clicked through into a saved regression check that re-runs deterministically, with no model in the loop and no test code to write. Use when you have driven the same flow twice, when the user wants regression coverage without a Playwright suite, when a refactor needs proving against every existing journey, or when re-verifying by hand is costing a full drive every time.TestingNo warnings★ 1.2K↓ —
- verify-ui-changereticlehq/reticleCheck that a change to a web app actually works in the running app before calling it done. Drives the real page and returns a pass/fail verdict with the request that fired, the state that moved, and the file:line to fix. Use after editing a component, a form, a route, or an API call; when you have said "fixed" but have not opened the app; when the user asks "does it actually work?"; or when a change looks right on screen and you cannot prove it.DesignNo warnings★ 1.2K↓ —
- url-structurekostja94/marketing-skillsWhen the user wants to optimize URL structure, fix URL issues, or plan URL hierarchy. Also use when the user mentions "URL structure," "URL optimization," "slug," "clean URLs," "URL hierarchy," "URL path," "permalink structure," "URL best practices," "dynamic URLs," or "URL parameters." For per-page slug wording, use url-slug-generator. For canonical consolidation, use canonical-tag.PlanningNo warnings★ 1.1K↓ —
- stock-analysisalirezarezvani/claude-skillsAnalyze, research or value a listed stock or company (US, global, NSE or BSE) with verified data, ratios, scores and valuation. Use whenever asked if a stock is a buy, what it is worth, or how a company looks.FinanceNo warnings★ 29.3K↓ —
- using-agent-relayAgentWorkforce/relayUse when you are a registered relay agent (a spawned worker, or a lead that called register_agent) coordinating with peers in real time over current Agent Relay MCP tools - messaging, channels, threads, reactions, search, inbox, actions, and worker spawn/release. For role selection and orchestrator startup instructions, use https://agentrelay.com/skill and the orchestrating-agent-relay skill.OtherNo warnings★ 1.1K↓ —
- twitter-cardskostja94/marketing-skillsWhen the user wants to add, audit, implement, or optimize Twitter Card metadata for X link previews, including twitter:card, twitter:title, twitter:description, twitter:image, or X previews. For a full metadata lifecycle use page-metadata; for broader social previews use open-graph.MediaNo warnings★ 1.1K↓ —
- improve-search-visibility-page-and-foundation-checkgooseworks-ai/goose-skillsStep of the improve-search-visibility playbook: audits site indexing, crawling, technical and page issues at the requested scope, or checks pages behind lost visibility questions. Run improve-search-visibility instead; not for direct use.BrowserNo warnings★ 1.3K↓ —
planning-with-files
OthmanAdi/planning-with-files
PlanningUpdated yesterday
From the author
Persistent file-based planning for multi-step AI-agent work. Keeps task_plan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and emits aggregate counts only; --replay may emit bounded nonce-framed excerpts. Optional gated mode can request continuation only when the host supports it and never runs commands declared in Markdown. The skill has no network upload path. Use for research or work needing 5+ tool calls.
Install
npx skills add OthmanAdi/planning-with-files --skill planning-with-files -a claude-code
Installs to .claude/skills/planning-with-files/ · 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
Provenance93
Maintenance100
Licence100
Adoption69
Files (27)
- SKILL.md
- references/examples.md
- references/plan-inventory.md
- references/reference.md
- scripts/attest-plan.ps1
- scripts/attest-plan.sh
- scripts/check-complete.ps1
- scripts/check-complete.sh
- scripts/gate-stop.sh
- scripts/init-session.ps1
- scripts/init-session.sh
- scripts/inject-plan.py
- +15 more