golem-view-agent-files

List files and directories in an agent's virtual filesystem with optional JSON output.

Updated May 17, 2026
One-click install
npx skills add https://github.com/Rust-soham/golem-claw --skill golem-view-agent-files-rust-soham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golem-view-agent-files
Source: https://github.com/Rust-soham/golem-claw/tree/main/packages/golem/.agents/skills/golem-view-agent-files
Command: npx skills add https://github.com/Rust-soham/golem-claw --skill golem-view-agent-files-rust-soham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You need to understand what files and directories an agent instance can access in its virtual filesystem, especially when debugging behavior or verifying outputs.

Core Features & Use Cases

  • List files and folders in an agent’s directory: Quickly view the contents of a specific path or the filesystem root.
  • Path-focused inspection: Drill into subdirectories by providing a target path.
  • Structured output option: Request results in JSON for easier downstream parsing or tooling.

Quick Start

Use the skill to list everything under the root directory for a specific agent instance by running: golem agent files 'CounterAgent("c1")'

Frequently Asked Questions about golem-view-agent-files

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I list files and directories in an agent's virtual filesystem?

You can list files and directories in an agent's virtual filesystem by providing the target agent identifier and an optional filesystem path, which defaults to the root directory, to quickly browse accessible state.

Can I get JSON output for an agent filesystem inspection?

Yes, agent filesystem inspection supports a JSON output mode. Requesting this structured format provides results that are easier for downstream parsing and tooling to consume.

How do I check what files a running agent can access for debugging?

To check what files a running agent can access for debugging, inspect its virtual filesystem by targeting the specific agent identifier to resolve uncertainty about its available state and outputs.

What's the best way to browse a specific subdirectory in an agent's filesystem?

The best way to browse a specific subdirectory is path-focused inspection, where you provide the target agent identifier along with the desired filesystem path to drill into subdirectories.

Do I need any dependencies to inspect an agent's virtual filesystem?

No dependencies are required to inspect an agent's virtual filesystem. You only need the target agent identifier and an optional path to start listing files and directories for auditing or debugging.

Why does my agent output not match the expected files during auditing?

Agent output mismatches during auditing often occur because of inaccessible files. Listing the virtual filesystem contents verifies what the agent instance can actually access and resolves this uncertainty.