Skip to main content
Glama
Sign In
omni-dev

omni-dev

by rust-works
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

claude_skills_clean

Revert your project to a clean state by removing skill symlinks and the managed exclude block created by a prior sync, leaving real files untouched.

Instructions

Remove the skill symlinks under .claude/skills/ and the managed exclude block created by a prior claude_skills_sync — the inverse of that tool. MUTATES THE FILESYSTEM. Real files (non-symlinks) are preserved, never deleted. Operates relative to the server process's cwd. Use claude_skills_status first if you want to see what would be removed. Mirrors omni-dev ai claude skills clean.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "claude_skills_clean"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format: `"text"` (default) or `"yaml"`.
worktreesNoWhen true, also operate on every worktree belonging to the target repository.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.40.0
  2. Removedv0.39.0
  3. Changed2 schema fields changedv0.33.0
    • removedInput schema / description
      Removed value: -"Parameters shared by `claude_skills_sync` and `claude_skills_clean`."
    • removedInput schema / title
      Removed value: -"ClaudeSkillsMutateParams"
  4. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description fully carries the behavioral disclosure burden. It explicitly warns 'MUTATES THE FILESYSTEM', states that real files are never deleted ('Real files (non-symlinks) are preserved, never deleted'), and clarifies scope ('Operates relative to the server process's cwd'). This is exemplary transparency for a destructive tool.

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

Conciseness5/5

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

The description is four sentences, each serving a distinct purpose: state the action, warn about mutation, assure safety, and reference related tools. It is front-loaded with the verb 'Remove' and contains zero fluff.

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?

Given the tool's complexity (2 optional params, no output schema), the description is complete: it explains what is removed, side effects, safety behavior, cwd scope, and how to preview. No essential information is missing for an agent to select and invoke it safely.

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%, with both parameters (`format` and `worktrees`) already explained in the input schema. The tool description adds no additional parameter semantics, so the baseline 3 applies per the rubric.

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 clearly states the tool's function: 'Remove the skill symlinks under `.claude/skills/` and the managed exclude block created by a prior `claude_skills_sync`'. It uses a specific verb ('Remove'), identifies the exact resources, and explicitly notes it is the inverse of `claude_skills_sync`, distinguishing it from 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?

Provides explicit usage guidance: 'Use `claude_skills_status` first if you want to see what would be removed.' It also frames the tool as the inverse of `claude_skills_sync`, clarifying when it should be used (to undo a sync) and when to use an alternative (status for preview).

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