Happycapy Skills

A set of ready-to-copy Claude Code skill folders: PDF, slides, Next.js, image and video generation and social publishing.

  • 138 ★ on the repository
  • Last commit
  • MIT
Skill

Extended access

Why this level

  • Social publishing skills such as `happycapy-social-publisher` post on your behalf.
  • Scripts inside the skills run code and call external APIs.
All reasons and checks

happycapy-ai/happycapy-skills

Install

Manual install

git clone https://github.com/happycapy-ai/Happycapy-skills.git

The first quick start command. Then copy the folders you want from `skills/` into `~/.claude/skills`.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Social publishing skills such as `happycapy-social-publisher` post on your behalf.
  • Scripts inside the skills run code and call external APIs.

This is third-party code. Review the repository files before installing.

What it does

The repository gathers more than fifty ready Claude Code skills. Each sits in its own `skills/<name>` folder with a `SKILL.md` file, so it installs by copying into `~/.claude/skills`. Topics include agent workflows (finding and creating skills, orchestrating agent teams), Next.js, Expo and Supabase development, PDF, PPTX and LaTeX documents, image and video generation and social publishing. A separate group of nine skills locks a visual style onto PPTX output. The user names a style, answers three questions about topic, slide count and images, and receives an editable `.pptx` file. Some skills are adapted for the Happycapy environment, for example `happycapy-feishu` for Feishu and Lark through MCP. Source and license stay in each skill folder.

Who it is for. Developers and content authors assembling a Claude Code skill set from ready-made folders.

Good fit when

  • The agent needs the `pdf` skill: extract text, merge files, fill a form or OCR a scan.
  • A deck is built in one of nine fixed styles and comes out as an editable `.pptx`.
  • A Next.js team takes `next-best-practices` instead of hunting for rules across repositories.
  • In the Happycapy environment Claude is connected to Feishu or Lark through `happycapy-feishu`.
  • No suitable skill exists, so one is created with `happycapy-skill-creator` on proven upstream patterns.

Not a fit when

  • You need the newest version of a specific skill: check the original source named in its folder.
  • Posts must not go out without manual review, while `happycapy-social-publisher` cross-posts to several platforms.
  • Copying the whole `skills/*` folder at once is unwise: dozens of descriptions bloat the agent's skill list.

Example request

Use the pptx skill in the olive-rose style and build a 12-slide deck about a new fragrance launch.

Limitations

The set consists of copies and adaptations of other authors' skills, so quality and usage terms differ: read the license and source in the folder of the skill you want. Installation is manual by copying folders, with no version manager or auto-update. Some skills rely on Happycapy, Feishu or external models and paid APIs and will not work without them. Social publishing skills and `video-downloader` act on external services, so read their `SKILL.md` before running.

How to disable. Delete the skill folders from `~/.claude/skills`. The repository clone can be removed separately.

FAQ

How do I install one skill from the set?

Copy its folder: `cp -r skills/pdf ~/.claude/skills/`. Scripts, references and assets live inside the folder and move with it.

Which styles do the PPTX skills have?

Nine fixed styles, among them `olive-rose` (exhibition poster), `coral-geyser` (field guide) and `azure-host` (forums and panel events). A style is invoked by name in the request.

What does the find-skills skill do?

It looks up installable skills when a user asks how to do something. It belongs to the agent workflow group alongside `skill-creator` and `llm-council`.

Do the skills work without Happycapy?

Skills use the `SKILL.md` format and install into `~/.claude/skills`, so most run in Claude Code. Happycapy and MCP specific ones such as `happycapy-feishu` need that environment.

Can I submit my own skill to the set?

Yes. The Submit a skill link in the README leads to the repository issues, where skill suggestions are accepted.

Discussion

No questions or reviews yet.

Skills

A working folder for Claude Code where the agent asks questions and writes a new skill by Anthropic's guidance, not from memory.

SkillExtended access242Repository stars

11 skills for Claude Code: SKILL.md authoring, prompt tuning, refactoring, change review and planning in files.

SkillMinimal access286Repository stars

A Claude Code reference plus a collection of over 70 skills for development, security, data and docs, with agent configs

SkillBroad access4.7KRepository stars

A personal Claude Code marketplace with 100+ skills: charts, codebase mapping, video, GitHub work and subagent dispatch.

PluginExtended access375Repository stars

A personal collection of about 130 Claude Code and Codex skills: media pipelines, Cloudflare, YouTube, design and task review

SkillBroad access198Repository stars

Skills, mods, subagents and hooks for Claude Code: the agent inspects your setup and installs what fits after your approval.

SkillExtended access98Repository stars

README in short

The collection splits into seven groups: agent workflows, web and apps, documents, media, social, Happycapy integrations and PPTX styles. Each group lists skills with a one-line description, plus a quick start by copying folders.

README badge

Report a problem