PlyloftAccountDownload free
Skills

Every rough card can leave
the next one easier.

Skills are the written know-how your agents load before they work: a folder with a SKILL.md. Plyloft keeps them in one library for Claude and Codex, improves them from your corrections with your approval, and shares them with your team.

The review catches a mistake

Codex, the Challenger, reads Claude’s build read-only and puts the finding under the line it names.

acme-web › Board › Session cookie expiry · The diff
Msrc/auth/session.ts
4141 httpOnly: true,
42− maxAge: 7 * DAY,
42+ maxAge: days * 24 * 60 * 60,
F1 · P1 — maxAge is in milliseconds in ExpressOpenRaised in round 1Express reads maxAge in milliseconds, so a 7-day session ends after about 10 minutes.
4343 sameSite: 'lax',
Round 1 · Codex · changes requested · 1 new

Proposals come only after a card is settled, one at a time per workspace. They treat your correction as the source of truth, cite it, and change nothing until you approve.

Reviews follow your rules.

Write your review rules as a skill in the repository. The Challenger, Claude or Codex, follows them on every review, on Mac and Windows.

  • Every review shows which skills it followed, and what each one asked
  • Reviews follow the rules on your branch, not the ones the Builder just wrote in the card
  • The Challenger stays read-only: it can follow a skill, never change one
acme-web › Board › Invoice totals · The result
The Challenger (Codex) reviewed the build read-only and requests changes.
Followedreview-rules
What the skill asked1 open findingF1 · P2 — New function lacks the required calc prefixShow on the diffRisk checklist of the last review (9 lines)

One library, four places a skill can live.

This is Library › Skills as the app draws it. Plyloft reads each CLI’s own folders and shows, for every skill, whether Claude, Codex or both will see it. Try the scope list, the filter, the proposal and each row’s ⋯ menu.

Skills

What the agents know how to do. Each one lives somewhere — in this repository, in the team library, on this Mac, or in Plyloft itself.

Improvement proposalfrom your correction · 4 hours ago
About review-rules · In this repositoryThe “Session cookie expiry” card showed the rules name no unit for durations, so a cookie lifetime in seconds passed the first build.From your correction: “Durations in cookies are milliseconds. Convert days explicitly, and test it.”
.claude/skills/review-rules/SKILL.md1 line added
8 - Every handler returns errors as { error, code }.
9+ - Durations stored in cookies are milliseconds: convert days explicitly, and test the real lifetime.
Publishing reaches everyone who opens this repo.
In this repository2 · everyone who opens this repo
review-rulesClaudeCodex
The team’s review rules.
backend-conventionsClaude
How this repository writes handlers, errors and cookies.
In the team library1 · every team workspace
release-checklistClaudeCodexAlso in this repository
The steps the team runs before a release.
Comes with Plyloft4 · switched on per Mac
Answer the Challenger
How the Builder replies when the Challenger pushes back.
Write a good card brief
Turns a rough idea into a brief an agent can work from.
Release and status notes
Writes the release note and the status line the same way every time.
Verify before saying done
Makes an agent check its own work before it reports back.
On this Mac1 · only here
Yours alone. Plyloft reads them but does not change them — promote one to share it.
my-shortcutsClaude
Your own shortcuts for this machine.

Made for both, in one stepNew skill… creates a repository skill that Claude and Codex both read, and opens it in Code.
Nothing touches your CLI settingsClaude gets skills as session plugins; Codex gets a private copy of its settings folder. Your ~/.claude and ~/.codex are never edited.
Four built in, each one optionalAnswer the Challenger, Write a good card brief, Release and status notes and Verify before saying done load in every session. Switch any of them off on this Mac.
Team

What one person learns, everyone starts with.

Promote a skill to the team and it loads in every Claude and Codex session of every member. It lives in your team’s private GitHub repository, not on a server of ours.

01Promote and installPromote to Team from a repository or your Mac; a team skill shows Also in this repository where a copy is installed.
02Compare before you replaceWhen the same skill exists in two places, Compare shows both, then Keep both, Align or Promote this one to Team.
03Never written overIf a teammate changed a skill in the meantime, Plyloft opens a pull request instead.
04No commands on teammates’ machinesSkills that carry hooks, which would run commands on other people’s computers, are refused, visibly.
See everything a team can do →

What skills don’t do (yet).

So you know exactly what you get.

Editing happens in CodeThe Library shows, compares and moves skills; you edit a skill in Plyloft’s Code view or your own editor.
No version history in the appRepository skills live in git, so their history is git’s.
Installed team copies don’t update by themselvesWhen the team’s version changes, the copy in your repository offers Replace in Team… or Compare instead.
No usage numbersPlyloft shows which skills a review followed, not how often each one is used.

Teach it once.
Every review remembers.

Download for MacDownload for Windows
Plyloft is a desktop app for Mac and Windows. Send yourself the link for later.One email with the link. No newsletter unless you ask.
Skills and the four built-ins are in every plan, Free included. Improvement proposals come with Pro and Team.

Get Pro

Seats, you included (2–50)
3
VAT included. Businesses in the EU can add a VAT number on the payment page.Founding price, kept for as long as your subscription runs.

Checking your sign-in…