Skip to content

Built into the lpm desktop app

Create Claude Code & Codex skills. Without hand-writing SKILL.md.

lpm lists the skills Claude Code and Codex load in each project, shows what each one costs in context, and gives you one dialog to create and edit them, with AI drafting the fields from a plain-English description.

AI drafts the fieldsEdit skills in placeContext cost, visible

From dotfile spelunking to one dialog

A skill is a SKILL.md file in a dotfolder — easy for agents to read, fiddly for you to maintain. lpm turns it into a form, with an AI Draft bar that fills every field from one sentence.

Claude Code · Codex
Editing SKILL.md by hand in a terminal, crossed out, next to lpm's New skill dialog with AI drafting, folder, run mode, description, and instructions fields
  • Folder

    Saved straight into a folder the CLI you pick already reads — no wondering where the skill goes.

  • Who runs it

    Your agent, when the description fits, or manual-only, invoked with /name or $name.

  • Description

    The only part your agent reads before deciding to open the skill. lpm shows its per-turn token cost.

  • Instructions

    Read only once the skill runs, so their length costs nothing up front.

One dialog, both CLIs

Skills live in folders — lpm keeps track of them

Claude Code and Codex each read skills from their own folders. lpm lists the skills in each one, plugin skills included, and writes new skills where the CLI you pick will read them.

Claude Code

/skill-name

lpm writes a standard SKILL.md, so everything works exactly as if you had written it by hand.

  • Personal skills in ~/.claude/skills, project skills in the repo's .claude/skills
  • Auto-run when the description matches, or manual-only on request
  • Manual-only skills stay out of context entirely: zero tokens up front
  • Per-skill estimates of what each description costs every turn
Claude Code skills docs

Codex

$skill-name

The same dialog writes Codex skills, including the shared folder other agent CLIs read too.

  • The shared ~/.agents/skills folder, plus Codex's own ~/.codex/skills
  • Invoked with $name, and lpm shows the right token for each folder
  • Manual-only honored by Codex; in the shared folder, Gemini CLI and OpenCode still load it
  • Descriptions checked against what both CLIs accept
Codex skills docs
Made for daily agent work

Skills should be easy to write and cheap to keep

Describe it, AI drafts it

Type one sentence about the task. lpm reads your repository and drafts the name, description, and instructions to match how your project works, on the AI CLI and model you pick. Nothing is saved until you click Create.

Edit without breaking files

Reopen any skill in your personal or project folders, including ones you wrote by hand, and change its description, instructions, or who runs it. lpm rewrites only the fields you touched.

See what skills cost

Descriptions load before every turn; instructions only when a skill runs. lpm estimates what each description costs every turn and shows each skill's size on disk, so you know which deserve a manual-only switch.

Three steps in lpm

From idea to installed skill in a minute

01

Open Skills & tools

Press ⌘⇧K (Ctrl+Alt+Shift+K on Windows and Linux) in any project, or choose Skills & tools from the ⋯ menu in the terminal pane header. You can pin it to the toolbar from there.

02

Create a new skill

Click New skill, describe the task, and let AI draft the fields, or fill in the name, description, and instructions yourself.

03

Refine as you go

Pick who runs it and press Create. Reopen the skill any time to edit it, and a deleted skill goes to the Trash (the Recycle Bin on Windows), so you can get it back.

The Skills & tools pane

Skills are one tab of a bigger picture

The pane that creates skills also shows everything else Claude Code and Codex will load in that folder, and what it costs.

Everything each CLI loads

Skills sit next to subagents, slash commands, MCP servers, plugins, hooks, and CLAUDE.md or AGENTS.md files, for Claude Code and Codex, filterable by CLI, kind, or text.

A context budget bar

A running estimate of what the agent loads every turn, from instruction files and skill and subagent descriptions. MCP tool schemas are flagged as not counted.

Conflicts, called out

lpm warns when a name is already taken in that folder, or when your personal copy of a skill will win over the project's copy.

Plugin skills, read-only

Skills that ship inside a Claude Code plugin are listed and readable but not editable, and on SSH projects the whole pane is a read-only view.

Deletes you can undo

Before a skill is removed, a preview shows exactly what goes to the Trash (the Recycle Bin on Windows).

lpm's own skills

One click in Settings installs skills that teach Claude Code, Codex, Gemini CLI, and OpenCode to start, stop, and duplicate your lpm projects.

FAQ

What to know about agent skills

How skills work, what they cost in context, and what lpm writes to disk.

  • What is a Claude Code skill?
    A skill is a folder with a SKILL.md file: a short description the agent always sees, and instructions it reads only when the task matches. Claude Code loads skills from ~/.claude/skills and from .claude/skills inside a project; Codex reads the shared ~/.agents/skills folder. lpm lists those, Codex's own ~/.codex/skills folder, and skills that ship in Claude Code plugins, and you can filter the list by CLI.
  • How do I create a Claude Code skill in lpm?
    Open a project and press ⌘⇧K (Ctrl+Alt+Shift+K on Windows and Linux), or choose Skills & tools from the ⋯ (More options) menu in the terminal pane header, then click New skill. Name it, pick the folder for the CLI you want, choose who runs it, and write the description and instructions, or describe the task in one sentence and let AI draft every field.
  • Can AI write the skill for me?
    Yes. Describe what the skill should do and click Draft. lpm runs the AI CLI and model you pick, reads your repository without changing it, and fills in a suggested name, description, and instructions that match how your project works. Drafting only fills the form: nothing is written to disk until you click Create skill, and if a draft replaces text you typed, you can undo it.
  • Does it work with Codex?
    Yes. The same dialog writes Codex skills to the shared ~/.agents/skills folder or to ~/.codex/skills. Codex invokes skills with $name instead of /name, and lpm shows the right invocation for whichever folder you pick.
  • Can I use one skill with both Claude Code and Codex?
    Each CLI reads its own folders, so a skill lives where its CLI looks: Claude Code reads ~/.claude/skills and a project's .claude/skills, while Codex reads the shared ~/.agents/skills folder that Gemini CLI and OpenCode read too. The dialog is identical either way: pick a different folder and lpm writes the same SKILL.md format there.
  • What does the “Only you” run mode mean?
    A manual-only skill never triggers on its own and stays out of the agent's context, so it costs no tokens until you invoke it by name. Claude Code and Codex both honor it. In the shared ~/.agents/skills folder only Codex holds the skill back; Gemini CLI and OpenCode still pick it up on their own, and lpm says so in the dialog.
  • Can I edit skills I wrote by hand?
    Yes, for skills in your personal and project folders. Reopen one and change its description, instructions, or run mode; lpm rewrites only the fields you touched, so custom frontmatter and formatting in hand-written files survive. Skills that ship with a Claude Code plugin, and skills listed for SSH projects, are view-only.
  • Where is everything stored?
    In the same local folders the CLIs already read; nothing is uploaded or synced to a website. Deleting a skill first previews what will be removed, then moves its folder to the Trash (the Recycle Bin on Windows), so you can get it back.
  • What else does the Skills & tools pane show?
    Everything Claude Code and Codex will load in that folder: MCP servers, plugins, subagents, slash commands, hooks, and CLAUDE.md or AGENTS.md instruction files, with a context budget bar that estimates what loads every turn. It flags conflicts too, such as a personal skill that overrides the project's copy.