THE SIGNAL IN ONE SENTENCE

Claude Code can now show developers which loaded skills are consuming limited context without contributing to the current work.

01

WHAT ACTUALLY CHANGED

Anthropic released Claude Code 2.1.261 with a new command called skill-doctor. It reports which loaded skills go unused and how much context they cost, allowing developers to remove instructions that occupy the model's working space without helping the task.

The update also adds settings that can raise inline command and background-task output to 128,000 characters. Large subagent system prompts can now be read from files instead of squeezed into command-line arguments.

Several safety changes are tucked into the same release. Detection for dangerous removal commands now catches positional parameters and commands nested inside double-quoted shell scripts. Automatic permission mode no longer approves a link that packs content into a public diagram renderer's URL unless the user requested that upload.

Anthropic also repaired a long list of session, remote-control, connector, proxy, and interruption problems. Those fixes are not glamorous, but they determine whether a long-running agent actually stops, resumes, reconnects, and preserves the right context when a person returns.

02

WHY THIS MATTERS

Agent skills are beginning to resemble browser extensions. Each one promises a useful specialty. Install enough of them and the agent starts every job carrying a suitcase full of instructions, examples, tool descriptions, and policies it may never use.

A context window is not merely a maximum input size. It is the model's active workbench. Filling that bench with irrelevant material can raise cost, weaken attention, disturb caching, and make it harder to understand which instruction produced an odd behavior.

The skill doctor turns that invisible tax into something inspectable. As agent systems grow, developers will need the equivalent of task managers, dependency inspectors, and memory profilers for the model's working environment.

FIG. 048AUDIT THE AGENT WORKBENCH
1LOAD SKILLS→
2MEASURE CONTEXT→
3FIND UNUSED→
4PRUNE CAREFULLY→
5RETEST WORKFLOW
The useful question is not how many skills an agent owns. It is which instructions deserve space on the workbench for this job.

03

WHERE IT COULD HELP

  • Remove unused skills from long coding projects
  • Reduce context cost and conflicting instructions
  • Preserve larger tool output when details matter
  • Store substantial subagent instructions in versioned files

KEEP A HAND ON THE WHEEL

Anthropic has not published measurements showing how much pruning improves quality or cost. A skill that went unused in one session may still be essential in another. The diagnostic should inform maintenance, not encourage deleting every tool that had a quiet afternoon.

04

TERMS WORTH KEEPING

SOURCES AND VERIFICATION STATUS

This article was written from the materials below. Product claims and dates were checked against those sources on September 5, 2026.

PUBLICATION RECEIPT: Revision 1. Approved by Zak and published September 5, 2026.

THE PUBLICATION ENGINE

WANT A SIGNAL OF YOUR OWN?

We build source-grounded publications, private briefings, and editorial systems for organizations with something useful to say.

WORK WITH US