Skip to main content
Glama
permanu

SuperSkill

by permanu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

snapshot_repo_state

Destructive

Capture current Git branch, dirty files, and last commit into the vault to avoid repeating repository discovery across sessions.

Instructions

Snapshot current git state (branch, dirty files, last commit) into the vault. Helps avoid repeating repo discovery across sessions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
branchNoCurrent git branch
projectNoProject slug (auto-detected if omitted)
dirty_filesNoList of dirty/uncommitted files
last_commitNoLast commit hash or message
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

B3.3/5.0
Behavior2/5

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

The annotations declare destructiveHint=true, yet the description frames the operation purely as an additive write ('snapshot into the vault') and never says what the destruction is — presumably overwriting a prior snapshot or existing vault entry. With no auth, idempotency, or overwrite-semantics disclosure, an agent cannot judge the risk of re-running this on the same repo.

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?

Two compact sentences, front-loaded with the concrete action and followed by the payoff. No boilerplate or restated field definitions; every clause earns its place.

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?

No output schema exists and all parameters are documented, so the schema side is covered. However, for a tool flagged destructive with zero required parameters, the description should clarify what the snapshot replaces or overwrites; that gap keeps it at minimum-viable completeness.

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 are already documented, establishing a baseline of 3. The description echoes branch/dirty_files/last_commit but adds nothing about the auto-detection behavior of project or the workspace_path mapping constraint that the schema already covers.

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 — 'Snapshot current git state (branch, dirty files, last commit) into the vault' — and enumerates the captured fields, so the agent knows exactly what the tool produces. It does not differentiate itself from any named sibling, which keeps it short of a 5.

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

Usage Guidelines3/5

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

'Helps avoid repeating repo discovery across sessions' implies the usage context (session-start discovery caching) but never states when to prefer it or what the alternative is. There are no exclusions or prerequisites, leaving the agent to infer the trigger condition.

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