autoworks-ai / autovault-skill

Hosted SKILL.mdFirst-party source skillv1.0.0MIT6,709 B

autoworks-ai/autovault/skills/autovault-skill/SKILL.md

Understand AutoVault-managed skills and when synced filesystem skills can be used without an MCP server.

InstallCLI + MCP

CLIRun from your local shell.

$autovault add autoworks-ai/autovault@85cea7424bfbc37901752600adf5eaab87e6b85a:skills/autovault-skill/SKILL.md --sync-profiles

MCPPaste into an agent MCP tool call.

>add_skill({ source: "github", identifier: "autoworks-ai/autovault@85cea7424bfbc37901752600adf5eaab87e6b85a: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 source skill

SKILL.mdview raw →

---

name: autovault-skill

version: 1.0.0

description: Understand AutoVault-managed skills.

category: meta

capabilities.filesystem: readonly

tools: none

---

autovault-skill

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

Documents the optional MCP compatibility tools and when agents should use synced skills directly.

When to use this skill

A user asks why an AutoVault-managed skill is visible.
An agent needs to decide whether MCP tools are required.
You are debugging stale profile sync or skill links.

Install

CLI: autovault add autoworks-ai/autovault@85cea7424bfbc37901752600adf5eaab87e6b85a:skills/autovault-skill/SKILL.md --sync-profiles

MCP: add_skill({ source: "github", identifier: "autoworks-ai/autovault@85cea7424bfbc37901752600adf5eaab87e6b85a:skills/autovault-skill/SKILL.md" })

Provenance

Published from the AutoVault source tree and mirrored here as a hosted SKILL.md example.