Skip to main content
Glama
po4erk91

Thread Keeper

by po4erk91
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

skill_manage

Destructive

Manage Thread Keeper's shared skills by creating, editing, patching, deleting, or restoring skill files, with frontmatter validation and automatic mirroring across all configured roots.

Instructions

Create, edit, patch, or delete skills under the primary skills root.

Atomic primary write with frontmatter validation before disk hits, then best-effort mirror into every configured skill root.

Actions: create — write a brand-new skill. Requires name + description + content (the body markdown WITHOUT frontmatter; the tool prepends a valid frontmatter block). Pass full content starting with '---' to skip the auto-frontmatter and supply your own. edit — overwrite SKILL.md wholesale. Requires name + content (full file including frontmatter). patch — find/replace within SKILL.md. Requires name, old_string, new_string. Result revalidated. write_file — add a support file. Requires name, sub_path (must start with references/, templates/, scripts/, or assets/), content. remove_file — remove a support file under one of the allowed subdirs. Requires name, sub_path. delete — remove a skill entirely. Pinned skills (in skill_usage) are refused. Foreground/unknown-origin skills require force from a foreground writer. Pass replacement_name during consolidation to repoint inbound [[wikilinks]]; otherwise the result lists dangling references. restore — restore the latest trashed copy for name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
forceNo
actionYes
contentNo
sub_pathNo
new_stringNo
old_stringNo
descriptionNo
replacement_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.17.0
    • addedInput schema / properties / force
      Added value: +{
+  "default": false,
+  "title": "Force",
+  "type": "boolean"
+}
    • addedInput schema / properties / replacement_name
      Added value: +{
+  "default": "",
+  "title": "Replacement Name",
+  "type": "string"
+}
  2. First observedv0.13.2

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses critical behaviors: atomic primary write with frontmatter validation, best-effort mirroring to configured skill roots, refusal to delete pinned skills, dangling reference consequences, and restore behavior. It also explains the auto-frontmatter mechanism and the condition for bypassing it, which is exactly the kind of context an agent needs.

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 long but appropriately structured into a summary line followed by a scannable action list. Every major behavior has a stated purpose. Slight redundancy exists ('write a brand-new skill' vs. 'overwrite SKILL.md wholesale'), but the complexity of nine actions justifies the length.

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 tool with nine parameters and nine action modes, the description covers all input requirements, edge cases, limitations, and side effects. It explains what happens in deletion, restoration, patching, and file management, and it includes constraints like allowed subdirectories and pinned-skill refusal. Since an output schema exists, the lack of return-value detail is not a gap.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates. It explains each meaningful parameter in context: content's frontmatter behavior, sub_path allowed prefixes, old_string/new_string as find/replace, force semantics, and replacement_name for repointing wikilinks. The action field is effectively enumerated even though the schema provides no enum.

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 opening line uses a specific verb set ('Create, edit, patch, or delete skills') and names the resource ('under the primary skills root'). The action list further disambiguates each operation, including write_file, remove_file, restore, and delete, which differentiates it from sibling tools like skill_list and skill_validate.

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

Usage Guidelines4/5

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

Each action is given explicit requirements ('Requires `name` + `description` + `content`'), which gives clear context on how to invoke the tool correctly. It does not explicitly name sibling alternatives or state when not to use this tool, but the action-specific conditions and examples of when force is needed ('Foreground/unknown-origin skills require force from a foreground writer') provide strong practical guidance.

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