Skip to main content
Glama
autoworks-ai

AutoVault

by autoworks-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

add_skill

Add a skill to AutoVault from GitHub, agentskills, URL, or local directory, with remote fetching, validation, and storage.

Instructions

Add a known skill from a source. For GitHub, agentskills, and URL sources, pass source plus identifier; remote bytes are fetched and validated before storage. Remote skills without agents frontmatter need target_agents for profile sync, or sync_profiles: false for vault-only install. For local bundles, pass source: "local" and skill_dir; identifier can override local provenance like CLI add-local --source, otherwise the normalized bundle root is recorded. Caller-authored SKILL.md bytes should use propose_skill, not add_skill.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYes
verboseNo
versionNo
skill_dirNo
identifierNo
profile_rootsNo
sync_profilesNo
target_agentsNo
discover_profile_rootsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • addedInput schema / properties / target_agents
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations present, the description carries the behavioral burden. It discloses that remote bytes are fetched and validated before storage, explains profile sync behavior, and notes how local provenance is handled. It could go further by covering return values or idempotency, but the core side effects are clear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but organized by source type and front-loaded with the main purpose. Every sentence adds operational detail, though the reference to 'CLI add-local --source' adds a mild assumption that could be clarified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 9 parameters, nested objects, no output schema, and no annotations, so the description has a heavy burden. It covers the main remote and local branches well, but omits return behavior, error cases, and several unexplained parameters, leaving the definition only partially complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It meaningfully explains source, identifier, skill_dir, target_agents, and sync_profiles. However, verbose, version, profile_roots, and discover_profile_roots are left entirely unexplained, leaving notable gaps for an agent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a clear verb and resource: 'Add a known skill from a source.' It then distinguishes itself from propose_skill by explicitly stating that caller-authored SKILL.md bytes should use propose_skill, not add_skill, which helps an agent pick the right tool among siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives concrete when-to-use guidance per source type: remote sources need source plus identifier, local bundles need source: 'local' and skill_dir. It also explains profile sync conditions and points to propose_skill as the correct alternative for caller-authored SKILL.md bytes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools