Best AI Skills Tools 2026
This directory focuses on AI skills as installable skill file packages: folders that contain a SKILL.md file, optional scripts, references, and assets that Claude Code, OpenAI Codex, and compatible agents can load when the task matches. It is not a generic AI tools list. Use it to find official skill catalogs, package installers, community marketplaces, workflow packs, and safety checks before adding third-party skills to your coding agent.
What counts as an AI skill?
A skill is a task-specific package. The common pattern is a directory with SKILL.md plus optional helper scripts, reference docs, assets, and templates.
Where do skills live?
Claude Code commonly uses .claude/skills/. Codex supports personal, project, plugin, and marketplace skill locations with progressive loading.
Before installing
Read the SKILL.md, inspect scripts, prefer official sources for sensitive workflows, and keep third-party skills scoped to the project that needs them.
Official Sources
5 toolsStart here when you need authoritative skill formats, supported install paths, and vendor-maintained skill examples.
OpenAI's public skills catalog for Codex-style skill packages, including reusable workflows such as document, spreadsheet, slide, image, and browser automation skills.
Best for: Codex users who want vendor-maintained examples before installing community skills.
Visit →Anthropic's official skill repository for Claude, with example skill folders and practical packages for document, spreadsheet, PDF, presentation, and creative workflows.
Best for: Claude Code teams that want skills aligned with Anthropic's documented format.
Visit →Current Codex documentation for skill structure, progressive disclosure, installation locations, marketplace skills, plugin skills, and authoring guidance.
Best for: Learning how Codex discovers, loads, installs, and shares skills.
Visit →Anthropic's Claude Code skill documentation for discovery, required frontmatter, installation folders, plugin marketplace distribution, and the skills command.
Best for: Validating whether a skill pack is structured correctly for Claude Code.
Visit →A higher-level Anthropic support overview of what Claude skills are, how they package instructions and files, and when users should apply them.
Best for: Explaining skills to non-technical stakeholders before rollout.
Visit →Installers & Package Managers
5 toolsUse these when you need a repeatable way to add, sync, or scaffold skills across personal and project environments.
Codex's built-in skill installation flow, triggered with $skill-installer, for curated skills, GitHub repo skills, and marketplace/plugin skill sources.
Best for: Installing Codex-compatible skills without hand-copying folders.
Visit →Claude Code's in-product skills command for browsing, installing, and managing skills from supported skill locations and plugins.
Best for: Teams standardizing Claude Code skill installation.
Visit →A registry and open standard initiative for sharing agent skill packages across compatible AI coding tools.
Best for: Discovering cross-agent skill packages with a consistent vocabulary.
Visit →Community helper for creating Claude-compatible skill packages from guided prompts and packaging them for reuse.
Best for: Turning internal SOPs into repeatable skill folders.
Browse →Template repositories and generators that scaffold SKILL.md, references, scripts, and test fixtures for new custom skills.
Best for: Building private skills before publishing them to a team repo.
Browse →Marketplaces & Indexes
5 toolsThese are useful for discovery. Treat any third-party listing as a starting point, then inspect the actual skill files before installation.
Community-maintained lists of Claude skill packages, example repositories, and specialized workflow packs.
Best for: Finding new skill ideas before choosing a vetted source.
Browse →GitHub topic page for agent skill repositories, including Claude, Codex, and cross-agent SKILL.md projects.
Best for: Broad discovery when you know the workflow category but not the package name.
Visit →Searchable registry experience for browsing skill packages by use case, compatible agent, and source repository.
Best for: Comparing installable skill packages across agent ecosystems.
Visit →Community directories that organize skills as plain Markdown packages, often optimized for easy copying into agent skill folders.
Best for: Lightweight private experiments and small team workflows.
Browse →Curated lists and newsletters tracking new Claude Code and Codex skill packages as the ecosystem changes.
Best for: Monitoring new skill packs without installing them immediately.
Browse →Workflow Skill Packs
7 toolsPractical packs for teams that want skills around documents, design, browsers, data, development, content, or internal SOPs.
Skill packages for working with spreadsheets, slide decks, Word documents, PDFs, and other office files through agent workflows.
Best for: Finance, operations, reporting, and content production teams.
Browse →Skills that teach an agent how to use browser automation for navigation, screenshots, form testing, visual QA, and local app checks.
Best for: Frontend verification and repeatable product checks.
Browse →Skill packs that encode frontend implementation preferences, design-system rules, screenshot QA, and UI delivery checklists.
Best for: Product teams that want consistent agent-built interfaces.
Browse →Skills for analysis workflows that combine instructions with reusable scripts for charts, CSV cleanup, notebooks, spreadsheets, and reports.
Best for: Analysts who want reliable repeated transformations.
Browse →Custom skills for code review, bug reproduction, test writing, migration playbooks, release checks, and repository-specific engineering standards.
Best for: Teams turning senior engineering habits into repeatable agent behavior.
Browse →Skills that package editorial rules, SEO templates, content briefs, citation workflows, image generation steps, and publishing QA.
Best for: Content teams building consistent AI-assisted production pipelines.
Browse →Your own skill folders for internal SOPs, brand rules, deployment runbooks, compliance checks, and repository-specific practices.
Best for: Teams that need durable agent behavior tied to local context.
Learn →Safety & QA
3 toolsSkills can contain instructions, scripts, and assets. That makes them powerful, and also worth reviewing before a team-wide install.
A practical pre-install review: read frontmatter, inspect scripts, check external commands, verify references, and install into the narrowest scope needed.
Best for: Avoiding risky third-party skill installs.
Learn →Use repository metadata, commit history, issue activity, license files, and script diffs to judge whether a public skill pack is safe enough to try.
Best for: Screening community skill repositories.
Learn →Keep sample inputs, expected outputs, and short acceptance checks beside custom skills so teams can verify behavior after edits.
Best for: Maintaining private skills over time.
Learn →Sources Checked
This page was compiled from official documentation and public repositories. Because third-party skill packages can change quickly, use the links below as discovery sources and inspect each package before installing it.
- OpenAI Codex skills documentation and OpenAI skills catalog.
- Claude Code skills documentation, Anthropic skills repository, and Claude Skills help center.
- AgentSkills, GitHub topics for Claude skills and agent skills, plus repository searches for public
SKILL.mdcollections.