manage
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.
- License 许可
- Apache-2.0
- 所属仓库
- vercel/eve
- 最近更新
- 2026-11-15
- Stars
- ★ 5.9k
- Forks
- 656
01 前言 Front Matter
- name
- manage
- description
- 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.
03 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
publishsucceeds. - Each version is saved with an application mode, and it applies in that
mode once published.
set_modechanges 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,publishthe earlier version. - Every
createcall needsapplicationMode:alwaysfor a persona, writing preference, or standing behavior. It is injected on every turn.on-demandfor a task procedure. It is listed in the prompt and loads when relevant.deferredfor a rarely needed procedure. It stays out of the prompt until a skill search finds it.
- An
on-demandordeferreddescription is a routing condition that says when to load the skill, such as "Use when the user asks for a deploy checklist." Ifcreate,publish, orset_moderejects 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.listandcreatereturn thatloadName. Lifecycle tools take the bare name plusscope. - Changes apply from the next message, not the current turn.
- Use
readto inspect an exact draft before publishing it; it also lists every version. publish,set_mode, andremovetake each skill'sidas well as its name, fromlist,read, orcreate. 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-demandskill with persistent behavior toalwayswithset_mode. - To delete several skills, call
listonce, thenremoveonce with every skill's name and id. listnames the scopes available here. Default to the personal scope. Use a shared scope such aschannelonly 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
publishsucceeds.
04 同仓库更多 Skills
writing-quality
The review rubric: writing-quality rules and reference lists for judging a content draft, covering AI-sounding phrasing, bloated wording, structure, and web-content specs. Load at the start of every review.
writing-quality
Writing-quality guardrails for any prose the agent drafts or edits: blog posts, page copy, Notion drafts, release notes, marketing text. Use this skill whenever writing or revising content meant for humans to read, to keep the prose natural, plain, and free of AI-sounding phrasing. Not needed for code, queries, or structural CMS work.
seo-aeo-best-practices
SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces. Use this skill when implementing page SEO, technical SEO, schema markup, international SEO, AI-overview readiness, or improving content for Google, ChatGPT, Perplexity, and similar assistants.
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this skill whenever working with Sanity schemas, defineType or defineField, GROQ or defineQuery, content modeling, Presentation or preview setups, Sanity-powered frontend integrations, Sanity Functions, documentEventHandler, defineDocumentFunction, defineMediaLibraryAssetFunction, @sanity/functions, @sanity/blueprints, sanity.blueprint.ts, event-driven content automation, or when reviewing and fixing a Sanity codebase.
portable-text-serialization
Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.
portable-text-conversion
Convert HTML and Markdown content into Portable Text blocks for Sanity. Use when migrating content from legacy CMSs, importing HTML or Markdown into Sanity, building content pipelines that ingest external content, converting rich text between formats, or programmatically creating Portable Text documents. Covers @portabletext/markdown (markdownToPortableText), @portabletext/block-tools (htmlToBlocks), custom deserializers, and the Portable Text specification for manual block construction.