perry-workspaces

What This Skill Does

The perry-workspaces skill enables OpenClaw users to provision, manage, and interact with isolated Docker-based development environments directly on their Tailscale tailnet. By automating the setup of remote workspaces, this skill provides a secure, consistent, and portable coding environment that is immediately accessible from anywhere in your network. Each workspace comes pre-configured with essential development tooling, including the Claude Code agent and the OpenCode interface, allowing you to move from environment creation to active coding in seconds.

Installation

To integrate this skill into your environment, run the following command within your terminal or OpenClaw interface: clawhub install openclaw/skills/skills/gricha/perry-workspaces Ensure you have Tailscale active and configured on your machine, as the connectivity model relies on the tailnet for secure, low-latency communication between your local machine and the remote container.

Use Cases

• Remote Development: Spin up a dedicated environment for a specific project without polluting your local system's package dependencies or shell configurations.
• Agentic Collaboration: Launch a workspace pre-loaded with Claude Code to perform autonomous refactoring or debugging tasks on a remote repository.
• Team Infrastructure: Provision standardized dev-environments for team members, ensuring that everyone operates within the same isolated Linux-based configuration.
• Isolated Experimentation: Test potentially unstable dependencies or system-level changes in an isolated container that can be destroyed with a single command.

Example Prompts

• "OpenClaw, please start a new Perry workspace named 'backend-fix' and clone the repository [email protected]:my-org/backend.git into it."
• "List all my active Perry workspaces and show me the status of the 'backend-fix' instance."
• "I need to debug the project in the 'backend-fix' workspace; can you open a shell session there for me?"

Tips & Limitations

• Project Pathing: Always remember that projects are cloned to the user directory (~/) inside the container, not the root level (/workspace). Navigate accordingly to avoid confusion.
• Connectivity: If hostname resolution fails, always refer to your Tailscale dashboard to retrieve the specific IP address of the container. The user context for all SSH operations must explicitly be 'workspace'.
• Performance: While initialization is generally rapid, large repositories may experience a slight delay during the initial clone and setup phase. Monitor the OpenCode web UI if you suspect the environment is taking longer than expected to initialize.