# jezweb/claude-skills: a marketplace of workflow recipes for Claude Code

> A plugin marketplace that installs ten bundles of Claude Code skills for shipping real work, from Cloudflare Workers to regional business English, with a README whose own numbers disagree with each other.

**jezweb/claude-skills** — Skills for Claude Code CLI such as full stack dev Cloudflare, React, Tailwind v4, and AI integrations.

- Repository: https://github.com/jezweb/claude-skills
- Website: https://jezweb.com.au
- Stars: 1,017 · Forks: 102
- Language: Python
- License: MIT
- Published: 2026-10-07 · Updated: 2026-10-07 · Language: en
- Canonical page: https://hysenlabs.com/projects/jezweb-claude-skills

## What you actually install when you add the marketplace

This is a Claude Code plugin marketplace rather than a library or a framework. The installation is two commands: a one-time add of the marketplace itself, then an install of whichever bundle you want by name.

```bash
# Add the marketplace (one-time)
/plugin marketplace add jezweb/claude-skills

# Install what you need
/plugin install cloudflare@jezweb-skills
/plugin install dev-tools@jezweb-skills
```

The bundle name in the install command and the marketplace suffix are both part of the address, which is a small thing to trip over. After that the README makes one claim about activation: you ask Claude what you need in ordinary language and installed skills trigger on their own. There is no invocation syntax to memorise and no config file to write.

The positioning sentence at the top of the README is the argument for the whole repository. Each skill guides Claude through a recipe to produce tangible output, and the outputs named are scaffolded projects, generated assets, professional documents and deployed services. That is a narrower and more defensible claim than making the assistant smarter. The repository is listed as Python, which is worth flagging early because it is not what most visitors expect from a directory of prompt-shaped files, and it points at the `bin/` and `tools/` directories doing real work behind the prose.

## Counting the skills against the README's own numbers

The README advertises ten plugins and a section headed All 60 Skills. Counting the skill names in the tables above that heading gives sixty-one, and the most recent release notes say something different again. The v10.0.0 notes, dated 2026-02-18, close with the line 24 skills total alongside the new testing bundle, which was true of the distribution at that moment rather than a claim about the current tree.

None of this is a reason to distrust the project. Skill collections grow, and headings written once drift from tables updated many times. But it does mean the totals in the prose are marketing copy rather than a reliable inventory, so if you are counting skills to decide whether the collection covers your stack, you need to count the table rows yourself.

The second structural point is more interesting than the arithmetic. The README says the thinking skills, naming planning, prompt-writing, verification doctrine and brains-trust, live in their own framework at the dotjez repository. So the collection is deliberately scoped to production output, and the meta-work of how to prompt and how to verify has been moved somewhere else. That is a defensible split, and it is also the first thing to check when you install and find that nothing here tells Claude how to plan.

## The Cloudflare bundle is the deepest part of the tree

The Build and Deploy group holds cloudflare, shopify and wordpress, and the cloudflare bundle is where the real depth sits. Eight skills cover the Worker scaffold, a Vite starter, TanStack Start, a Hono API scaffolder, D1 schemas through Drizzle, migrations, database seeding and direct REST API calls for bulk or fleet operations.

That is a full path rather than a single touchpoint. Someone building an edge service can go from empty directory to a Worker with a D1 schema, a migration path and seeded demo data without leaving the plugin, and the presence of a dedicated migration skill suggests the author hit the real failure modes rather than only the happy path. The v12.0.0 notes added d1-migration explicitly with a workflow the release describes as generate, inspect, apply, fix stuck migrations, which is the kind of detail you usually only get after something got stuck.

Shopify and WordPress are narrower by comparison. Shopify covers setup, product creation including bulk CSV, content pages, blog posts and SEO metadata. WordPress covers WP-CLI and REST API access, content management and Elementor page editing. Both read as competent coverage of the platform surface rather than a substitute for the official APIs, and for either one the honest comparison is against writing the API calls yourself with the vendor docs open.

## Writing skills expanded from one to eight in a single release

The Writing and Documents group is where the release history shows real movement. The v12.0.0 notes, published 2026-03-13, describe the writing plugin expanding from one skill to eight, adding regional business English guides for the United States, the United Kingdom and New Zealand alongside resumes and cover letters, client proposals, award submissions, and strategy documents covering SWOT analysis, business plans and OKRs.

The README plugin table also lists an Australian variant in that set, so read the release bullets as what changed that day rather than the finished roster. The regional guides are the interesting part because they encode the kind of detail a general model gets wrong: spelling convention, directness versus understatement, and for the New Zealand variant te reo Maori greetings. Those are preferences a prompt can carry, which is a reasonable fit for this format. Award applications and proposals are similar, since both are documents where structure matters more than prose and a reusable outline genuinely saves work.

The social-media plugin is a single skill by comparison, covering platform-formatted posts for LinkedIn, Facebook, Instagram and Reddit with character limits, hashtag strategy and campaign sequences. One skill covering four platforms with different constraints is a thinner proposition than the writing bundle, and it is the kind of thing to check against the platform's own current limits before trusting.

## Developer tooling that reads and reviews your own repository

The Developer Tools group is the largest by skill count, with sixteen entries in dev-tools and nine in integrations. The dev-tools list includes project health checks, documentation generation, app user guides, team updates, release cutting, a Codex review skill, git workflow, several UX skills, responsiveness checking, deep research, onboarding review and Vitest setup.

Two of those are about looking at work rather than writing it. The ux-audit skill, introduced in v10.0.0, walks a live web app as a first-time user in one of three modes, a UX walkthrough with ranked findings, a page-by-page QA sweep, or a targeted check on one feature, and it drives Chrome MCP for authenticated sessions or Playwright otherwise. The fork-discipline skill checks the boundary between core and client code, which is a review task rather than a build task. Both output artefacts, ranked findings and a summary table, which is the pattern the rest of the collection follows.

Integrations reaches outward to Google Workspace setup, Google Chat webhooks, Apps Script, ElevenLabs voice agents, MCP server construction with fastmcp, parcel tracking and Stripe payments covering checkout, subscriptions, webhooks and a billing portal. The v11.0.0 notes show this area evolving: the memory manager was renamed context-manager and widened to audit four layers of markdown at once, covering CLAUDE.md and rules files, project docs, session files and public files, with a KB footprint total and overlap detection between them.

## What the repository contains beyond the README

The file tree explains how a marketplace is wired. `.claude-plugin/` holds the plugin manifest that the marketplace add command reads, `plugins/` holds the bundles themselves, `.claude/` and `.jez/` hold project-level configuration, `bin/` and `tools/` hold the scripts, and `CLAUDE.md` plus `SKILL_SHAPE.md` sit at the root as instructions for working on the repository and for the expected structure of a skill.

`SKILL_SHAPE.md` is the file to read first if you intend to contribute, because it is the closest thing here to a specification for how a skill should be written. The trigger-phrase table in the README shows the convention from the outside: a backticked skill name mapped to the phrasings that activate it, such as scaffold a worker or new cloudflare project. That mapping is the real interface, and it is what makes the difference between a skill that fires at the right moment and one that never does.

Scale and activity are worth stating plainly. The repository has around a thousand stars, a little over a hundred forks and twenty open issues. The last recorded push was 2026-07-02, and the newest release in the tree is v12.0.0 from 2026-03-13, with v10.0.0 and v11.0.0 both dated 2026-02-18. So the code was touched more recently than the last tagged release, and the gap between those two dates is the honest measure of how settled this collection is. The homepage is jezweb.com.au and the licence is MIT, so the skills are free to read, copy and modify.

## Conclusion

The useful thing here is not any single skill but the shape of the collection: bundles organised by the artefact you want at the end, each carrying the trigger phrases that wake it up. Cloudflare, Shopify, WordPress, Stripe and the writing suite are concrete enough to install and try this week. The gaps are equally concrete, since the README gives you a list of names rather than the recipes inside them, and the thinking skills a developer might expect here live in a separate framework repository instead. Start by adding the marketplace, install one bundle, and read the installed skill file before you trust it with a production task.

## FAQ

### Is a Claude skill just a prompt?

A skill in this marketplace is closer to a workflow document than to a single prompt. Each one carries the steps for a job with a real output, plus the trigger phrases that tell Claude Code when to reach for it. The repository holds a `SKILL_SHAPE.md` at its root that describes the expected structure, which is the file to read if you want to know how they are meant to be written.

### How do I build a Claude skill?

Start by reading `SKILL_SHAPE.md` and one installed skill in `plugins/` to copy the layout, then write the recipe as ordered steps that end in a concrete artefact. Add the natural language phrasings you want to trigger on, since the trigger list is what decides whether the skill fires. Publishing one to this marketplace means adding it to a bundle and updating the manifest under `.claude-plugin/`.

### How many skills are in jezweb/claude-skills?

The README advertises ten plugins and a section headed All 60 Skills, and the tables list sixty-one skill names. The v10.0.0 release notes instead say 24 skills total, which described the distribution at that point in February 2026. Count the table rows rather than trusting the prose totals.

### Where did the planning and thinking skills go?

They were moved out on purpose. The README says the thinking skills, covering planning, prompt-writing, verification doctrine and brains-trust, live in a separate framework called dotjez rather than in this marketplace. If you install this collection expecting planning behaviour, look at that repository instead.

### Can I use these skills with anything other than Claude Code?

The skills are written as Claude Code plugins, installed through the plugin marketplace commands and triggered from natural language inside that CLI, so that is the environment they target. Because they are plain files on disk, the text of any individual skill can be read and reused elsewhere, but the trigger wiring does not travel with it.

## Sources

- [jezweb/claude-skills on GitHub](https://github.com/jezweb/claude-skills)
- [License: MIT](https://github.com/jezweb/claude-skills/blob/main/LICENSE)
- [Project website](https://jezweb.com.au)
- [README](https://github.com/jezweb/claude-skills/blob/main/README.md)
- [Releases](https://github.com/jezweb/claude-skills/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/jezweb-claude-skills