Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

tool-restraint

Sterne561

Forks103

Aktualisiert29. Juni 2026 um 22:25

Don't over-equip an agent with tools/MCP servers. More tools = more ways to fail and a higher cognitive load. Use when wiring tools or an agent underperforms.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

Archive228

Archive228/loopkit

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Sonstige ComputerberufeInformatik- und Mathematikberufe·SOC 15-1299

SKILL.md

readonly

name	tool-restraint
description	Don't over-equip an agent with tools/MCP servers. More tools = more ways to fail and a higher cognitive load. Use when wiring tools or an agent underperforms.
when_to_use	adding MCP servers, an agent with many tools, "give it access to everything"

Tool Restraint

Loading an agent with 14 MCP servers "just in case" makes it slower and dumber, not more capable — tool-use agents hit sharp capability cliffs as cognitive load rises.

Enable only the servers the current work actually uses. Remove the rest.
Prefer official servers for credentialed tools; never install five speculatively.
Each tool's description eats context on every turn — fewer, sharper tools beat a junk drawer.
Before adding a write-scoped server, add a hook that logs every call. If the agent picks the wrong tool or thrashes, the fix is usually fewer tools with clearer descriptions, not a smarter model.

Mehr aus diesem Repository

gleiches Repository

evaluator-calibration

Archive228/loopkit

Calibrate a reviewer persona with few-shot rubric examples so skepticism stays consistent and doesn't drift lenient over long runs.

2026-07-10561

feature-list-json

Archive228/loopkit

Enumerate every end-to-end feature as strict JSON entries with passes:false, editable-passes-only discipline, and priority order. The ledger fresh-context sessions read to know what's done, what's next, and what they're forbidden to touch.

2026-07-10561

harness-stripping

Archive228/loopkit

Systematically remove one harness component at a time and measure impact, killing scaffolding that no longer earns its complexity.

2026-07-10561

init-script-contract

Archive228/loopkit

Author idempotent init.sh under 120s plus sibling test.sh, stop.sh, reset.sh, serve.sh with fixed names the harness relies on.

2026-07-10561

planner-spec-expand

Archive228/loopkit

Expand a 1-4 sentence product brief into a full spec with a design language, acceptance surface, and an ordered feature list.

2026-07-10561

progress-reading-protocol

Archive228/loopkit

Run the fixed 6-step session-opening sequence — pwd, read progress, git log, count remaining features, init.sh, smoke-test last feature — before touching any new work. The orientation ritual that lets fresh-context sessions reconstruct project state in under a minute.

2026-07-10561

name	tool-restraint
description	Don't over-equip an agent with tools/MCP servers. More tools = more ways to fail and a higher cognitive load. Use when wiring tools or an agent underperforms.
when_to_use	adding MCP servers, an agent with many tools, "give it access to everything"

Tool Restraint

Loading an agent with 14 MCP servers "just in case" makes it slower and dumber, not more capable — tool-use agents hit sharp capability cliffs as cognitive load rises.

Enable only the servers the current work actually uses. Remove the rest.
Prefer official servers for credentialed tools; never install five speculatively.
Each tool's description eats context on every turn — fewer, sharper tools beat a junk drawer.
Before adding a write-scoped server, add a hook that logs every call. If the agent picks the wrong tool or thrashes, the fix is usually fewer tools with clearer descriptions, not a smarter model.