TToolPickly
Skill examples · Official reference

Anthropic Skills

A strong official reference for skill structure, progressive disclosure, and complex document workflows. Do not treat the whole repository as one uniformly licensed, production-ready skill bundle.

Reviewed 2026-08-12Review due 2026-11-10GitHub ↗
Adoption statusReferenceBased on the evidence below
LicenseMixed by directoryCheck per-directory terms
Repository snapshotActive at review170,496 · Fork 20,280 · 2026-08-20
Last push 2026-08-18
Better fit
  • Developers learning Agent Skill structure and trigger descriptions
  • Teams studying document, spreadsheet, presentation, and PDF workflows
  • Teams willing to inspect each directory's license and validate in isolation
Think twice
  • Users wanting to install everything at once for sensitive production work
  • Organizations requiring one uniform open-source license across every directory
01

Adoption and exit evidence

A repository is a dependency decision, not only a download.

Compatibility

The repository documents Claude Code, Claude.ai, and the Claude API. Other systems may implement the Agent Skills standard, but client support must be confirmed separately.

Installation

Claude Code can register the repository as a marketplace and install document-skills or example-skills selectively. Do not default to copying the entire repository.

Removal

Removal depends on the Claude client or API surface. Record plugin name, install location, and rollback path before installation.

Permissions

A skill may bundle instructions, scripts, and resources. File, network, and command access depends on the individual skill and host environment and must be reviewed per skill.

Maintenance

The official repository is actively maintained, but its README describes the content as examples and educational material and advises thorough testing before critical use.

License boundary

Many examples use Apache 2.0, while document skills such as docx, pdf, pptx, and xlsx are source-available rather than uniformly open source. The license in each directory controls.

Primary risk

What can go wrong after installation?

The primary risks are treating examples as a production guarantee, missing directory-level licenses, and running bundled scripts in a sensitive workspace without isolation.

Evidence status

Official README, installation, license boundary, and risk documentation were reviewed. ToolPickly has not sandbox-tested every skill in the repository.

02

Run this controlled pilot

Do not use production credentials or sensitive customer data.

  1. 01

    Select one skill and install it in a temporary project with no sensitive data

  2. 02

    Record every file it reads, creates, and modifies

  3. 03

    Run one real task and compare it with the no-skill baseline

  4. 04

    After uninstalling, confirm configuration, scripts, and caches can be removed

Open the complete adoption checklist

Alternatives by decision

Awesome Copilot

Better for browsing a broader community collection of skills, agents, instructions, and plugins.

Superpowers

Better when a team wants a complete development methodology rather than individual examples.

Official sources and disclosure

Stars are a dated attention signal. They do not determine the verdict. ToolPickly reviewed public repository documentation and clearly identifies what has not been sandbox-tested.

Report a project change or correction