AG

agent-versioning

Ensures consistent versioning for PilotSwarm agent definitions and builder templates.

Install

mkdir -p .claude/skills/agent-versioning && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10493" && unzip -o skill.zip -d .claude/skills/agent-versioning && rm skill.zip

Installs to .claude/skills/agent-versioning

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Use when creating or editing PilotSwarm .agent.md files, prompt-layer manifests, or builder templates that generate agents. Covers schemaVersion/version frontmatter, SemVer bump guidance, and session.prompt_layers expectations.
227 chars✓ has a “when” trigger
Beginner

Key capabilities

  • Manage agent frontmatter
  • Bump SemVer versions
  • Update prompt layers
  • Generate builder templates

How it works

Enforces versioning rules for agent manifests and templates to ensure consistent behavior tracking.

Inputs & outputs

You give it
Agent definition changes
You get back
Updated agent version

When to use agent-versioning

  • Update an agent version
  • Create a new agent manifest
  • Bump SemVer for an agent change

About this skill

Agent Versioning

Use this skill whenever you create or update PilotSwarm agent definitions in agents/*.agent.md, embedded agents under packages/sdk/plugins/**/agents/, or builder templates that generate agent files.

Required Frontmatter

Every authored .agent.md should include:

---
schemaVersion: 1
version: 1.0.0
name: example-agent
description: Example agent.
---
  • schemaVersion is the PilotSwarm agent schema version. Use 1 until the schema changes.
  • version is a string. PilotSwarm-authored agents use SemVer. App authors may use any non-empty string, but SemVer is recommended.

When To Bump version

For PilotSwarm-authored agents and templates, bump version whenever you change prompt behavior, tool expectations, workflow guidance, frontmatter metadata, or output/contract expectations.

Use SemVer intent:

  • Patch: wording clarifications or typo fixes that should not materially change behavior.
  • Minor: new capabilities, tools, guidance, examples, or backwards-compatible workflow behavior.
  • Major: changed role semantics, removed expectations, or incompatible output/contract changes.

If you only move a file without changing prompt behavior or metadata, a version bump is not required.

Builder Templates

When a builder agent creates a new app agent, it should include schemaVersion: 1 and version: 1.0.0 by default.

When it edits an existing app .agent.md, it should update the version string according to the change. If the existing app uses non-SemVer labels, preserve the user's style unless they ask to migrate.

Prompt Layers

PilotSwarm prompt-layer manifests have three authored layers:

PilotSwarm base -> App base -> Agent

Runtime context is not an agent layer; runtime behavior is tracked through orchestration version and session/runtime metadata.

session.prompt_layers records the effective layer names, types, schema versions, and versions used by the worker that created or resumed the Copilot session. During rolling deploys, absence of the event means legacy/unreported, and old workers may report old loaded versions until restarted.

When not to use it

  • When moving files without behavior changes

Limitations

  • Requires manual version bumping for behavior changes
  • Schema version is fixed at 1

How it compares

Provides a structured SemVer approach for agent evolution rather than manual versioning.

Compared to similar skills

agent-versioning side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
agent-versioning (this skill)02moNo flagsBeginner
skill-creator1283moReviewAdvanced
skill-development178moReviewIntermediate
agent-identifier158moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

skill-creator

anthropics

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

128200

skill-development

anthropics

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

17145

agent-identifier

anthropics

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

15122

llama-factory

zechenzhangAGI

Expert guidance for fine-tuning LLMs with LLaMA-Factory - WebUI no-code, 100+ models, 2/3/4/5/6/8-bit QLoRA, multimodal support

15112

dify-dsl-generator

wwwzhouhui

专业的 Dify 工作流 DSL/YML 文件生成器,根据用户业务需求自动生成完整的 Dify 工作流配置文件,支持各种节点类型和复杂工作流逻辑

18108

character-generator

Dexploarer

Generate complete elizaOS character configurations with personality, knowledge, and plugin setup. Triggers when user asks to "create character", "generate agent config", or "build elizaOS character"

583

Search skills

Search the agent skills registry