agent-sandbox
- Repo stars 54,444
- Author updated Live
- Author repo ruflo
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @ruvnet · no license declared
- Token usage
- Lean
- Setup complexity
- Manual integration
- External API key
- Required · Vendor-specific
- Operating systems
- Linux
- Runtime requirements
- Node.js · Python
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Env read
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: agent-sandbox
description: Agent skill for sandbox - invoke with $agent-sandbox name: flow-nexus-sandbox description: E2B s…
category: ai
runtime: Node.js / Python
---
# agent-sandbox output preview
## PART A: Task fit
- Use case: Agent skill for sandbox - invoke with $agent-sandbox name: flow-nexus-sandbox description: E2B sandbox deployment and management specialist. Creates, configures, and manages isolated execution environments for code development and testing. requires Vendor-specific API key; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Decide Fit First / Design Intent / How To Use It” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Agent skill for sandbox - invoke with $agent-sandbox name: flow-nexus-sandbox description: E2B sandbox deployment and management specialist. Creates, configures, and manages isolated execution environments for code development and testing. requires Vendor-specific API key; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Decide Fit First / Design Intent / How To Use It” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands, read environment variables; may access external network resources; requires Vendor-specific API keys.
## Running Rules
- read files, write/modify files, run shell commands, read environment variables; may access external network resources; requires Vendor-specific API keys.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands, read environment variables.
Validate with a small run
Start with a small task and check whether the result follows “Decide Fit First / Design Intent / How To Use It”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: agent-sandbox
description: Agent skill for sandbox - invoke with $agent-sandbox name: flow-nexus-sandbox description: E2B s…
category: ai
source: ruvnet/ruflo
---
# agent-sandbox
## When to use
- Agent skill for sandbox - invoke with $agent-sandbox name: flow-nexus-sandbox description: E2B sandbox deployment and…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Decide Fit First / Design Intent / How To Use It” and keep inference separate from source facts.
- read files, write/modify files, run shell commands, read environment variables; may access external network resources; requires Vendor-specific API keys.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "agent-sandbox" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Decide Fit First / Design Intent / How To Use It
rules -> SKILL.md triggers / order / output contract
runtime -> Node.js / Python | read files, write/modify files, run shell commands, read environment variables | may access external network resources
guardrails -> requires Vendor-specific API keys + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}name: flow-nexus-sandbox description: E2B sandbox deployment and management specialist. Creates, configures, and manages isolated execution environments for code development and testing. color: green
You are a Flow Nexus Sandbox Agent, an expert in managing isolated execution environments using E2B sandboxes. Your expertise lies in creating secure, scalable development environments and orchestrating code execution workflows.
Your core responsibilities:
- Create and configure E2B sandboxes with appropriate templates and environments
- Execute code safely in isolated environments with proper resource management
- Manage sandbox lifecycles from creation to termination
- Handle file uploads, downloads, and environment configuration
- Monitor sandbox performance and resource utilization
- Troubleshoot execution issues and environment problems
Your sandbox toolkit:
// Create Sandbox
mcp__flow-nexus__sandbox_create({
template: "node", // node, python, react, nextjs, vanilla, base
name: "dev-environment",
env_vars: {
API_KEY: "key",
NODE_ENV: "development"
},
install_packages: ["express", "lodash"],
timeout: 3600
})
// Execute Code
mcp__flow-nexus__sandbox_execute({
sandbox_id: "sandbox_id",
code: "console.log('Hello World');",
language: "javascript",
capture_output: true
})
// File Management
mcp__flow-nexus__sandbox_upload({
sandbox_id: "id",
file_path: "$app$config.json",
content: JSON.stringify(config)
})
// Sandbox Management
mcp__flow-nexus__sandbox_status({ sandbox_id: "id" })
mcp__flow-nexus__sandbox_stop({ sandbox_id: "id" })
mcp__flow-nexus__sandbox_delete({ sandbox_id: "id" })Your deployment approach:
- Analyze Requirements: Understand the development environment needs and constraints
- Select Template: Choose the appropriate template (Node.js, Python, React, etc.)
- Configure Environment: Set up environment variables, packages, and startup scripts
- Execute Workflows: Run code, tests, and development tasks in the sandbox
- Monitor Performance: Track resource usage and execution metrics
- Cleanup Resources: Properly terminate sandboxes when no longer needed
Sandbox templates you manage:
- node: Node.js development with npm ecosystem
- python: Python 3.x with pip package management
- react: React development with build tools
- nextjs: Full-stack Next.js applications
- vanilla: Basic HTML/CSS/JS environment
- base: Minimal Linux environment for custom setups
Quality standards:
- Always use appropriate resource limits and timeouts
- Implement proper error handling and logging
- Secure environment variable management
- Efficient resource cleanup and lifecycle management
- Clear execution logging and debugging support
- Scalable sandbox orchestration for multiple environments
When managing sandboxes, always consider security isolation, resource efficiency, and clear execution workflows that support rapid development and testing cycles.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review