Skip to main content
Glama

Valet

by io.github.valetdotdev
OverviewDiscussionsAdmin

Publish an organization skill

publish_skill
DestructiveIdempotent

Create or replace an organization skill from files: a SKILL.md and any supporting files, each as a path and its text content. The skill's name and description come from the SKILL.md frontmatter. Publishing under a well-known name, such as governance, security, or design-system, replaces what Valet would otherwise supply for every agent in the organization from the next read on, so do it when the user has asked to change how the organization works, and show them the content first. Publishing under a new name adds a skill the default governance process finds through list_skills when its description applies.

Destructive because it replaces the previous version's content for every reader. Repeating a call with identical content mints no new version and reports deduped. Requires connecting a Valet account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesYesRequired. The skill's files as [{path, content}], text only, paths relative to the skill root. Must include SKILL.md, the complete definition with name and description frontmatter.
org_nameNoThe Valet organization to publish into. Omit to use the organization the account joined first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / files / description
      Previous value: -"Supporting files: [{path, content}], text only, paths relative to the skill root."New value: +"Required. The skill's files as [{path, content}], text only, paths relative to the skill root. Must include SKILL.md, the complete definition with name and description frontmatter."
    • addedInput schema / properties / files / minItems
      Added value: +1
    • removedInput schema / properties / skill_md
      Removed value: -{
-  "description": "Required. The complete SKILL.md, with name and description frontmatter.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "skill_md"
-]New value: +[
+  "files"
+]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description goes further: it explains WHY it is destructive (it replaces the previous version's content for every reader), scopes the blast radius to the whole organization from the next read on, and discloses the dedupe behavior of repeat calls plus the Valet account requirement. That is real context beyond the structured flags.

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?

Front-loaded with the action and input contract, then the override/dedup/auth caveats. Most sentences earn their place, though the first sentence is dense and the well-known-name examples could be trimmed without losing meaning.

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

Completeness5/5

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

For a destructive, org-wide publish operation with no output schema, the description covers input contract, override semantics, discovery via list_skills, dedupe behavior, and auth requirements. An agent has everything needed to decide whether and how to call it.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema cannot: the skill's name and description are derived from the SKILL.md frontmatter rather than passed as parameters. It does not elaborate further on org_name beyond what the schema already says.

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?

States a specific verb+resource ('Create or replace an organization skill') and immediately defines the input shape (SKILL.md plus supporting files). It is cleanly distinguishable from publish_agent, publish_app, publish_site, and from attach_skill/detach_skill, which the name alone could be confused with.

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?

Explicitly routes usage: publishing under a well-known name (governance, security, design-system) overrides Valet defaults org-wide, so do it 'when the user has asked to change how the organization works, and show them the content first'; publishing under a new name adds a skill that list_skills discovers by description. Both when-to-use and the sibling discovery path are named.

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

All Valet toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources