Skip to content
PlyloftDocs

Skills and the Library

A skill is a folder with a SKILL.md: written know-how an agent loads before it works. Plyloft keeps skills in one Library for Claude and Codex.

Where a skill lives

Section titled “Where a skill lives”

Open Library › Skills. Filter by All, Repository, Team, This Mac (This PC on Windows) or Plyloft.

Section What it is
In this repository Skills committed to the repo; everyone who opens it gets them
In the team library Shared by your team; loaded in every member’s sessions
On this Mac Yours only, on this computer
Comes with Plyloft Four built-in skills, switched on per Mac

Each row carries a chip for each CLI it reaches, Claude, Codex or both; the skill’s own page says it in words, for example Reaches Claude and Codex. A skill that also lives in another place says so: Also in this repository, Also in Team.

What you can do

Section titled “What you can do”
  • New skill…, beside the filter, creates a repository skill for Claude and Codex at once and opens it in Code.
  • A row’s ⋯ menu holds its actions, only those that apply: Open in Code, Update on main, Make available to both (a skill that reaches one CLI), Promote to Team, Compare (the same skill in two places) and, last, Remove from main….
  • A skill on this Mac has Promote, which brings it into the repository.
  • Compare shows two copies side by side, then Keep both, Align or Promote this one to Team.

You edit a skill in Code, or in your own editor; the Library shows, compares and moves skills.

The built-in skills

Section titled “The built-in skills”
Skill What it does
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

Each one has a switch on its row under Comes with Plyloft, and is switched on or off per Mac. They change only when Plyloft updates.

How each CLI gets them

Section titled “How each CLI gets them”
Plyloft hands skills to Claude Code as plugins for the session it starts. Your ~/.claude is not edited.

Reviews follow your skills

Section titled “Reviews follow your skills”

The Challenger, Claude or Codex, follows the skills on your branch during every review, and the result says which: Followed review-rules. A skill the Builder changed inside the card is not used for that card’s review. Write your team’s review rules as a skill in the repository, and every review applies them.

Improvement proposals

Section titled “Improvement proposals”

Improvement proposals are part of Pro and Team.

  1. You correct a card: Not right opens What’s wrong; write it in plain words and press Send it back.
  2. After the card is settled, the Challenger may propose one change to a skill. It quotes your correction: From your correction: “…”.
  3. The Improvement proposal appears at the top of Library › Skills and on the skill’s page, with the exact lines it would add, and the Inbox lists A skill wants to change.
  4. Press Approve and publish or Dismiss. Publishing reaches everyone who opens this repo. In a repository with no remote the button says Approve and commit to main: a commit on main, and nothing is pushed.
  5. Later reviews say Followed review-rules, and What the skill asked shows what they checked.

Only repository skills get a change you can publish; for other skills the proposal is words you can apply yourself. If a teammate changed the skill since your copy, Plyloft opens a pull request instead of writing over it.