Skip to content
Skill Harness

The right skills on every machine, getting better with every session

Skill Harness finds the skills each project needs, suggests the ones your team is missing and pushes them to every developer. What developers learn flows back, gets reviewed, and ships again as a better version.

01Skills Library

Start with 1,000+ approved skills

Search a library of more than 1,000 skills that are reviewed and approved before they are listed. Each one shows what it does, which category it belongs to and how many teams use it.

  • Every skill approved before it is listed
  • Browse by category or search by task
  • Install to one project or to the whole team

Skills Library

1,000+ approved
  • Stripe webhook handlerApproved

    Verify signatures, handle retries and process every event exactly once.

    Payments2.4k teams

  • React component testsApproved

    Write Testing Library tests that check behaviour, not markup.

    Testing5.1k teams

  • Postgres migration reviewApproved

    Check migrations for table locks, missing indexes and safe rollbacks.

    Databases3.2k teams

  • Secure API endpointApproved

    Add auth, input validation and rate limits to a new route.

    Security4.7k teams

02Skills Discovery

Find the skills that fit your project

Skills Discovery reads the context of each project, its languages, frameworks, services and CLAUDE.md rules, and matches it against the library. You get a short list of skills that fit, each with the reason it was picked.

  • Matched to the stack and services each project uses
  • Rules from CLAUDE.md and the Knowledge Base taken into account
  • A clear reason next to every match

Skills Discovery · payments-api

4 matches

Skills Discovery reads the payments-api project, which uses TypeScript, Express, Prisma, Stripe, Postgres and Redis, and suggests the Stripe webhook handler, Postgres migration review, idempotent job retries and money in integer cents skills.

03Suggested skills

Skills your team should write next

When the same prompt keeps coming back, or the same fix shows up in observations again and again, CloudByte AI suggests a new skill and writes the first draft for you to review.

  • Found from repeated prompts and observations across the team
  • Shows how often it came up and who asked
  • A ready-to-edit draft, never published without review

Suggested skills

3 new

A suggested skill for refunds on partial captures, found because the same request was asked 14 times by 4 developers and the same fix appeared in 6 observations, with a draft ready to review.

04Project skills

Create once, on every developer machine

Create skills for a single project and push them to the machine of every developer who works on it. The agent places them in the project, so developers can commit them with the code and keep them versioned alongside it.

  • Pushed to every developer on the project
  • Saved as plain skill files, ready to commit with the code
  • See who has the latest version and who is still behind

Project skills · payments-api

Pushed to 6 developers

Three project skills for payments-api, pushed to six developer machines. Four have the latest version, one is updating and one is still on the previous version. Each skill is saved as a file inside the project, ready to commit.

Two-way sync

A harness that keeps every skill sharp

Skills go out to developers, and what developers learn comes back. Every round makes the skill better, and a person approves every change before it ships.

  1. 01

    Push

    An approved skill goes out to every developer on the project.

  2. 02

    Use

    Developers work with it in their AI sessions, as part of daily work.

  3. 03

    Learn

    Prompts and observations show where the skill helps and where people still correct it by hand.

  4. 04

    Improve

    CloudByte AI drafts an updated version that covers what developers had to add themselves.

  5. 05

    Review

    A lead edits and approves the change in CloudByte AI. Nothing ships without that step.

  6. 06

    Push again

    The new version reaches every machine, and the loop starts over.

One skill, four better versions

Here is how the stripe-webhooks skill on payments-api improved over two months, from a suggestion to a version that covers what developers kept adding by hand.

  1. v1.3
    Learned from sessionsOct 6

    Verify the webhook signature before parsing the body. Three developers had added this step by hand.

  2. v1.2
    Edited by PriyaSep 18

    Clearer error handling when an event arrives twice.

  3. v1.1
    Learned from sessionsSep 2

    Added test fixtures for replayed events, after five sessions needed them.

  4. v1.0
    Created from a suggestionAug 12

    First version, drafted from 14 repeated prompts and approved by Alex.

  • Reviewed before release

    Library skills, suggestions and every improvement are approved by a person before they reach a developer.

  • Every version tracked

    Each change records where it came from, who approved it and when it was pushed.

  • Lives with your code

    Project skills are plain files developers commit, so they are reviewed and versioned like the rest of the repo.

  • Usage and overrides tracked

    See which skills get used, and where developers override them, so you know which ones to improve next.

FAQ

Skill Harness questions, answered

How skills are found, suggested, pushed and improved.

Everything about your team skills in one place: a library of 1,000+ approved skills, discovery of the ones that fit each project, suggestions for skills your team is missing, project skills pushed to every developer, and a two-way sync that keeps improving them.

A reusable instruction file that tells the AI how your team handles a task, such as processing a Stripe webhook or reviewing a database migration. The AI uses it whenever that task comes up, so every developer gets the same approach.

Every skill in the library is reviewed and approved before it is listed. You can read each one before installing it, and choose whether it goes to one project or the whole team.

It reads the context of each project, the languages, frameworks and services it uses, plus the rules in CLAUDE.md and the project Knowledge Base, and matches that against the library. Each match shows why it was picked.

From your own team activity. When the same kind of prompt keeps coming back, or observations show the same fix again and again, CloudByte AI suggests a skill, shows how often it came up and drafts a first version for you to review.

The agent pushes them to the machine of every developer on the project and saves them as skill files inside the project. Developers commit them with the code, and the dashboard shows who is on the latest version.

Skills go out to developers, and what developers learn comes back. Prompts and observations show where a skill falls short, CloudByte AI drafts an improvement, a lead edits and approves it, and the new version is pushed to every machine again.

The Skills Library is included from the Starter plan, and skills override tracking from the Team plan.

Put your best ways of working on every machine.

Install the agent once per laptop and start with skills matched to your projects.

  • Free for up to 5 developers
  • 10-minute setup
  • Your Anthropic key, your spend (Enterprise)