skill-author

AutoVault Skill Packager

Prepare an existing SKILL.md or skill directory for AutoVault admission. This skill is about AutoVault packaging: schema correctness, bundle membership, capability declarations, validation, deduplication, and signed installation.

Scope

Use this skill when:

• a workflow or draft already exists and needs valid AutoVault frontmatter;
• a bundle has support files that must be inventoried and declared;
• an AutoVault validation, security, or dedup result needs remediation; or
• a reviewed bundle is ready for propose_skill or add_skill.

Do not use it for open-ended workflow invention, trigger design, or general skill-writing pedagogy. Use the host-native skill-creator or equivalent design tool first, then return here once there is a concrete draft to package.

1. Check for an existing capability

If the AutoVault compatibility tools are connected, search with get_skill({query: "specific workflow nouns"}). Prefer extending or reusing a good match over adding another near-duplicate.

When the MCP tools are absent, inspect the host's normal visible skill directory instead. AutoVault-managed skills are synced into those native directories, so filesystem discovery is sufficient and the missing MCP server is not an error.

2. Inventory the complete bundle

Treat the skill directory as one unit:

• SKILL.md is the entry point.
• Every regular sibling file under the directory is a resource.
• Exclude OS/editor metadata and generated caches.
• Reject symlinks, path traversal, device files, and other non-regular entries.
• Review executable resources as carefully as the skill body.

For a GitHub source, AutoVault fetches all regular sibling files beneath the selected skill directory at one immutable commit. It does not rely on the upstream author having declared every file. Missing resources declarations are synthesized during normalization, and the install response reports inferred_resources for review.

3. Normalize frontmatter