Gary Club

Powers — install & publish AI skills

Install Gary Club skills into your AI agent, or publish your own to the Community Curated catalog.

Updated June 23, 20262 min read

Powers are AI skills you install into your own agent — Hermes, Claude, or another runtime. Each one teaches your agent to do real work, like booking podcast spots or summarizing your team's standup. They're free with your Gary Club membership.

Two kinds of Powers

The catalog at gary.club/dashboard/powers has two sections:

  • Gary Club Official — built and maintained by the Gary Club team.
  • Community Curated — built by fellow members and reviewed before listing. They carry a "Community" badge, and they run on your own machine with your own keys — so install ones from authors you trust.

Both install exactly the same way, and both are free with your membership.

Install a Power

  1. Open gary.club/dashboard/powers and mint your access key — one key works for every Power. Keep it secret, like a password.
  2. Find a Power and copy its install command.
  3. Paste it into your AI runtime. The skill downloads and is ready to use; some Powers include a quick setup step to add any keys they need.

Your key carries your membership, so your Powers keep working as long as you're a member. Lose the key? Just generate a new one.

Publish your own skill

Built a skill of your own? You can ship it to the Community Curated catalog for every member to install.

  1. Install the Publish to Powers skill from the catalog.
  2. Point it at your skill folder — publish <your-skill>. It bundles your skill (and deliberately leaves any secret files like .env behind) and uploads it with your membership key.
  3. An automated review agent scores it 1–100 on safety, structure, quality, functionality, and honesty, and lists anything to fix. You get the score back right away.
  4. Once the team approves it, it goes live under Community Curated for everyone — with your name on it.

Skills that read credentials they don't need, send your data somewhere it shouldn't go, or do anything destructive are rejected automatically. Keep it bring-your-own-keys — read secrets from the installer's own environment, never hardcode them — and declare what your skill needs in its SKILL.md. Do that and you'll sail through.

Is it safe to install community skills?

Every Community Curated skill is reviewed before it's listed, and the badge tells you it's member-made rather than built by us. Because skills run on your own machine with your own keys, install ones from authors you recognize — the same common sense you'd use with any tool you add to your stack.

Was this page helpful?