agentleFS
VercelKnown publishervercel/eve/packages/eve-custom-skills/extension/skills/manage/SKILL.md

manage

Skill5.9k starsChanged 3 days agoApache-2.0View on GitHub

Lifecycle rules for user-created custom skills — versions and drafts, application modes, publishing, rollback, deletion, scopes, and approvals. Load before creating, listing, reading, publishing, rolling back, changing the mode of, or deleting a custom skill.

8 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about vercel/eve

The biggest 5 of 57 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 57

Talked about on GitHub and Bluesky (57 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 7

2 more on Bluesky

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every create call needs applicationMode:

    line 23
  2. Very specific:

    Use read to inspect an exact draft before publishing it.

    line 39
  3. Very specific:

    When a live skill is not applying, check its application mode before anything else.

    line 49
  4. Very specific:

    After an approval or denial, report the actual tool result.

    line 58

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Managing custom skills

These rules apply to custom skills saved with this extension's create tool. The agent's own authored skills have no lifecycle versions.

create, list, and publish are always available. read, set_mode, and remove are deferred: find them with eve__search (for example "read custom skill") and call them through eve__tool.

  • A clean first version goes live immediately. Every later save is an immutable draft: it changes neither the live version nor how it applies. The live version changes only when publish succeeds.
  • Each version is saved with an application mode, and it applies in that mode once published. set_mode changes how the live version applies.
  • The live (active) version is what applies. Versions above it are drafts; versions below it are superseded. To roll back, publish the earlier version.
  • Every create call needs applicationMode:
    • always for a persona, writing preference, or standing behavior. It is injected on every turn.
    • on-demand for a task procedure. It is listed in the prompt and loads when relevant.
    • deferred for a rarely needed procedure. It stays out of the prompt until a skill search finds it.
  • An on-demand or deferred description is a routing condition that says when to load the skill, such as "Use when the user asks for a deploy checklist." If create, publish, or set_mode rejects a description or instructions, save a new version that follows the error.
  • On-demand and deferred skills load through the skill loader under their advertised name, which carries the mount prefix and, for shared scopes such as channel, a scope prefix. list and create return that loadName. Lifecycle tools take the bare name plus scope.
  • Changes apply from the next message, not the current turn.
  • Use read to inspect an exact draft before publishing it; it also lists every version.
  • publish, set_mode, and remove take each skill's id as well as its name, from list, read, or create. If a call says the skill was replaced, or that the scope changed while it was checked, list the skills again and call it with the current id.
  • Some changes need approval, such as publishing, rolling back, deleting, and anything that goes live in a shared scope. Call the tool directly with the exact target: the approval card shows the change and is the only confirmation, so never ask first in prose or with a question tool.
  • When a live skill is not applying, check its application mode before anything else. Never publish a version that is already live; switch an on-demand skill with persistent behavior to always with set_mode.
  • To delete several skills, call list once, then remove once with every skill's name and id.
  • list names the scopes available here. Default to the personal scope. Use a shared scope such as channel only when the user asks for a team or channel skill. A shared-scope change affects everyone in that scope. A read-only scope's skills can be loaded but not changed.
  • After an approval or denial, report the actual tool result. Never call a draft live before publish succeeds.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.