Jump To Category Page

Jump To Representative Detail

Capabilities Category View

Capability inventory should show which tools or skills actually matter to execution, where error or privilege makes them risky, and which ones are just background utility.

The category page should help a reviewer understand the effective tool surface quickly: what is used most, what is powerful, and which capabilities change the meaning of a session.

Use This Page When Asking

Which capability surfaces change what agents are allowed to do in meaningful ways?

Representative Detail

tool:builtin:bash

Open representative detail

Capabilities

Tools and skills mixed

High-power tools

File or shell reach

Error outliers

Worth surfacing above the table

Most-used lane

bash / read_file

Defines many sessions

Why This Page Exists

This category page should help the reviewer decide what matters in capabilities before the raw table takes over the reading experience.

What This Page Should Make Obvious

The reviewer should know what is routine, what is risky, and what deserves the next click.

Power matters as much as frequency

Rare but high-reach tools can matter more than common low-risk utilities.

Schema should stay tied to real use

A capability page is most useful when input shape and session use are visible together.

Show the effective tool lane

The reviewer should see which tool families define the inventory, not just a flat count.

Fastest Drill Paths

The next clicks should feel obvious and intentional.

Shell execution lane

A representative high-power tool used across multiple sessions.

Open representative detail

Best first page for understanding how direct execution changes session meaning.

Raw capability ledger

The exact tool and skill table still matters for invocation counts and error rates.

Open c6 raw list

Reviewers will still want the canonical inventory after the framing layer.

Capability-Centered Topology

A capability map should connect a tool or skill to its source, callers, sessions, and failure patterns.

Useful per capability: whether it is a tool or skill, who invokes it, where it comes from, which sessions depend on it, and whether volume or errors suggest attention.

Capability

read_file

Representative high-frequency tool; the same topology applies to skills by swapping source path for MCP or builtin origin.

22 sessions · 318 invocations

Type

tool

Callers

Who reaches for this capability.

3 nodes

Claude Codeprimary agent

Cursorsecondary agent

alice@company.comfrequent user

Source Surface

Where the capability originates.

3 nodes

builtintool source

filesystemcategory

write_fileadjacent tool

Session Context

Where it shows up inside work.

3 nodes

coding sessionsdominant workflow

/src/auth.tscommon target

session detailtrace invocations

Watch For

The operational and governance questions.

3 nodes

web_search 3.4%peer outlier

parameter misuseschema check

skill path driftfor skill variants

c6 Raw Reference

c6 shape: tool and skill inventory with invocation rates plus source-path provenance.

High-consequence tool path active

Filesystem and outbound-call capabilities are clustered around the most important sessions.

Capabilities

High-risk tools

Top source

Claude Code

Recent invocations

Why Keep The Raw Ledger

c12 should still flow back into the raw inventory model. This page frames the question and likely answer; the raw table proves it.

Open c6 Raw List

Use the original category ledger for exact rows, counts, and timestamps.

Open c6 raw list

Raw Capability Inventory

Name, category, source, sessions, invocations, and error rate.

Name	Category	Source	Sessions	Invocations
read_file	filesystem	Claude Code	6	48
bash	execution	Claude Code	6	34
web_fetch	network	Claude Code	3	8