Execution power
What can it do?
shell commands
broad execution
package + file ops
wide reach
Tools & Skills meaning layer
Capability inventory should surface which tools widen power, accelerate consequence, or cross boundaries before it behaves like a flat tool catalog.
The important question is what agents can do, not just what tools are registered.
1 capability lane dominates leverage
Which capabilities most change the meaning of a session?
Capabilities
42
Only a few change the security picture
High-leverage tool
NaN
Broad execution and file reach
Skills
8
Usually less urgent than broad tools
Background tools
NaN
Useful after the first read
Meaning anchors
Why tools & skills matter before the raw catalog
3 anchors
Anchor | Summary | Operator note |
|---|---|---|
Capabilities describe power, not inventory trivia | Security needs to see which tools widen leverage before looking at every schema row. | That is the value of a meaning layer here. |
Routine can still be the biggest risk multiplier | Bash matters because it is normal, broad, and frequently adjacent to sensitive context. | Normality is part of why it deserves stronger framing. |
Capability detail should explain leverage | The page should say what this tool changes in the story, not only how many times it ran. | That makes the tool catalog operationally useful. |
Priority queue
Fastest drill paths for this entity type
Significance
Story | Summary | Why it matters |
|---|---|---|
tool:builtin:bash | Broad execution power reused across the most important recent sessions. | The best capability example for leverage and blast radius. |
Filesystem helper tools | Lower-level surfaces that often appear beside bash. | Useful follow-up once the main leverage lane is understood. |
Prompt-only skills | Less operationally urgent baseline. | Good contrast against broad execution tools. |
c6 reference
Raw Capability Inventory
42
High-consequence tool path active
Filesystem and outbound-call capabilities are clustered around the most important sessions.
Capabilities
42
High-risk tools
2
Top source
NaN
Recent invocations
84
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 |
Representative detail
tool:builtin:bash
Bash should be treated as a high-leverage execution surface: broad power, shared reuse, and a short path into sensitive context.
Name :
read_file
Type :
tool
Source :
Claude Code
Category :
filesystem
Agent :
claude-code@1.2.0
Capability ID :
tool:builtin:read_file
Capability leverage map
The capability story should show how one tool widens power across many sessions.
capability
Use the map to connect bash to sessions, files, agents, and boundary-linked work.
Focus
tool:builtin:bash
Broad execution surface reused in many important lanes.
high-leverage tool
Agent lanes
Who uses it?
Claude Code
dominant lane
Cursor
secondary lane
Sensitive context
Why does it matter?
.env + config files
adjacent often
auth repos
common nearby context
Boundary stories
What comes after?
provider traffic
seen in follow-on sequence
secondary calls
some sessions continue outward
sessions
18
leverage
high
boundary role
supporting hinge
next drill
session story