SuperSkill

Overview Schema Source Related Servers Discussions Admin

link

Destructive

Connects two vault notes by appending a wiki-style reference to the source note, enabling graph_related to discover the relationship.

Instructions

Create a forward link between two vault notes. Appends a [[wikilink]] to the source note, enabling graph_related to discover the connection.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source": "<source>",
      "target": "<target>"
    },
    "name": "link"
  }
}

Input Schema

Name	Required	Description
`source`	Yes	Relative path to the source vault note
`target`	Yes	Relative path (or note name) to link to
`project`	No	Project slug (auto-detected if omitted)
`workspace_path`	No	Absolute 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.

Changed1 schema field changedv0.15.1Oct 15, 2026

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"
+}

First observedv0.6.1Aug 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the destructiveHint annotation, the description discloses the exact mutation ('Appends a [[wikilink]] to the source note') and, by calling it a *forward* link, implies the target note is not modified. That is meaningful effect-level context, though permissions/rate context is absent.

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 front-loaded sentences with zero filler: the action first, then the mechanism and its consequence. Nothing wastes space.

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

Completeness4/5

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

With a fully documented 4-parameter schema, a destructive annotation, and no output schema, the definition covers what an agent needs to call it. Only minor gaps remain, such as duplicate-link behavior or failure modes when the target note doesn't exist.

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 source, target, project, and workspace_path are already documented. The description adds no format or syntax detail (e.g., path vs note-name handling) beyond what the schema provides, so baseline 3 applies.

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 and resource ('Create a forward link between two vault notes') and names the downstream sibling it enables ('graph_related to discover the connection'). An agent can distinguish this linking operation from generic write/edit siblings without opening the schema.

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?

The phrase 'forward link' implies directionality and the graph_related mention hints at the goal, but there is no explicit when-to-use, when-not-to-use, or named alternative. Usage is inferred rather than stated.

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