skills.rest
the-agency-ai
the-agency-aiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

sandbox-list

List sandbox commands, hooks, tools, and scripts with activation statuses across engineers.

39|6|Updated Jan 5, 2026
Search Tags:#automation#status#sandbox#system#listing#engineers
One-click install
npx skills add https://github.com/the-agency-ai/the-agency --skill sandbox-list
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sandbox-list
Source: https://github.com/the-agency-ai/the-agency/tree/main/.claude/skills/sandbox-list
Command: npx skills add https://github.com/the-agency-ai/the-agency --skill sandbox-list

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of auditing and monitoring sandbox contents across all engineers, providing instant visibility into available commands, hooks, tools, and scripts with their current activation states.

Core Features & Use Cases

  • Comprehensive Listings: Detects and displays sandbox items such as commands, hooks, tools, scripts, and hookify files across multiple user directories.
  • Status Checking: Checks for existing symlinks to determine whether each item is active or inactive.
  • Use Case: For a developer managing a multi-engineer environment, easily listing all sandbox elements helps maintain control and update workflows efficiently.

Quick Start

Run the sandbox-list skill to generate an up-to-date report of all sandbox items and their activation statuses for current engineer.

Frequently Asked Questions about sandbox-list

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

FAQPage Schema
How do I list all sandbox commands and hooks across multiple engineers?▼

To list sandbox commands and hooks across engineers, this Skill scans user directories to detect commands, tools, scripts, and hookify files, grouping them by engineer for quick oversight and configuration auditing.

How can I check the activation status of sandbox scripts in a multi-user environment?▼

Checking sandbox script activation status involves scanning for existing symlinks in user directories to determine whether each command, hook, or tool is currently active or inactive across the multi-user system.

What is the best way to audit sandbox tools and configurations for multiple engineers?▼

Auditing sandbox tools across engineers is best handled by generating an up-to-date report that scans all user directories, grouping available resources and their activation states to maintain configuration control.

Does this sandbox listing process work for multi-user systems without additional dependencies?▼

Yes, this sandbox listing process operates in multi-user systems without requiring additional dependencies, directly scanning user directories to map available commands and scripts with their current activation states.

Why are my sandbox commands showing as inactive when listing engineer environments?▼

Sandbox commands show as inactive during listing when the scan checks for existing symlinks in the engineer's directory and fails to find the required symlink to activate the specific command, hook, or tool.

Related Skills

Explore More Software Engineering Skills→
photonics-dhlphotonics-dhl

hermes-project-discovery

Locate real user projects outside sandboxed workspaces by scanning home-adjacent paths.

Community
Intermediate
Hex-4Hex-4

plugin-settings

Manages Claude Code plugin settings via YAML frontmatter in .local.md files.

Community
Advanced
ProyectoG007ProyectoG007

command-center

Monitor OpenClaw AI agents with a real-time dashboard.

Community
Advanced
gatovillanogatovillano
5

execute_command

Execute shell commands with real-time stdout and stderr streaming.

Community
Advanced