autoworks-ai / autovault-skill

Hosted SKILL.mdFirst-party hosted examplev1.2.0MIT8,354 B

public/skills/autovault-skill/SKILL.md

Understand AutoVault-managed skills, when synced filesystem skills can be used without MCP, and that vault writes must go through autovault add --source local or propose_skill/update_skill.

InstallCLI + MCP

CLIRun from your local shell.

$autovault add https://autovault.dev/skills/autovault-skill/SKILL.md --source url --sync-profiles

MCPPaste into an agent MCP tool call.

>add_skill({ source: "url", identifier: "https://autovault.dev/skills/autovault-skill/SKILL.md" })

Choose CLI for a shell install or MCP for an agent tool call.

Source

Example type

skill

hosted SKILL.md

Declared agents

from frontmatter

Gate stages

covered by tests

Permission rows

declared metadata

Source

autoworks-ai

First-party hosted example

SKILL.mdview raw →

---

name: autovault-skill

version: 1.2.0

description: Understand AutoVault-managed skills and how to install or update them.

category: meta

capabilities.filesystem: readonly

tools: shell.run

---

autovault-skill

Explains that AutoVault syncs skills into normal agent skill directories as filesystem links.

Treats ~/.autovault/skills as a signed store: author outside the vault, then autovault add --source local or MCP propose_skill/update_skill.

Documents optional MCP tools and when missing MCP means use the CLI, not a hand edit.

When to use this skill

A user asks why an AutoVault-managed skill is visible.
An agent is about to edit SKILL.md and needs the signed-store write path.
You are debugging stale profile sync, tampered integrity, or skill links.

Install

CLI: autovault add https://autovault.dev/skills/autovault-skill/SKILL.md --source url --sync-profiles

MCP: add_skill({ source: "url", identifier: "https://autovault.dev/skills/autovault-skill/SKILL.md" })

Provenance

Hosted by autovault.dev and parsed by the website catalog test before being shown.