Skip to main content
Glama
permanu

SuperSkill

by permanu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

write

Destructive

Create, append, or prepend Markdown content in an AI knowledge vault, adding optional YAML frontmatter to files.

Instructions

Write or append to a file in the AI knowledge vault.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoWrite mode (default append)
pathYesRelative path within vault
contentYesMarkdown content to write
frontmatterNoYAML frontmatter key-value pairs
workspace_pathNoAbsolute thread workspace directory; must map to this project. Omit only when the server cwd is the thread workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.1
    • addedInput schema / properties / workspace_path
      Added value: +{
+  "description": "Absolute thread workspace directory; must map to this project. Omit only when the server cwd is the thread workspace.",
+  "type": "string"
+}
  2. First observedv0.6.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already flag destructiveHint=true, so the safety profile is partly covered. However, the description adds nothing beyond that: it never warns that overwrite mode destroys existing file content, nor mentions workspace/permission requirements for this mutation.

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?

A single, front-loaded sentence with no filler. It is efficient, though its brevity shades into under-specification rather than crispness.

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

Completeness2/5

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

For a destructive write tool with five parameters, three write modes, and no output schema, one sentence is thin. The description does not cover what gets destroyed on overwrite, where the file lands, or what the caller gets back.

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 100%, so all five parameters including the mode enum and the workspace_path caveat are already fully documented in the schema. The description adds no format, syntax, or default detail beyond what the schema provides, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource: "Write or append to a file in the AI knowledge vault." The action and target are unambiguous, though it does not explicitly distinguish itself from siblings like read, capture, or template.

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

Usage Guidelines2/5

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

There is no indication of when to use this tool versus read, capture, template, or other vault-mutating siblings, nor any stated preconditions. 'Write or append' hints that modes exist but gives no guidance on choosing between them.

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