generate sandbox policy

Security Community

Skill notes

Overview

This skill translates a user's plain-language policy intent into a valid sandbox policy. The amount of detail the user provides determines the granularity of the generated policy — from broad L4 or preset-based policies (just a host:port) up to fine-grained per-endpoint L7 rules (full API docs). The output is a network_policies YAML block (and optionally a full policy file) that conforms to the sandbox policy schema.

Determine the Detail Tier

The user's input falls into one of three tiers. Work with whatever the user provides — do not require a higher tier than needed. Tier · User provides · What you can generate Minimal · Host(s) and plain-language intent · L4-only policies, or L7 with access presets (read-only, read-write, full) Moderate · Host(s) + some known URL paths or resources · L7 with targeted glob rules for known paths, presets for the rest

Minimal Tier (host + intent only)

The user provides API endpoints and a broad intent. No API docs needed. Examples: "Allow curl to hit api.github.com, read-only" "Give claude full access to api.anthropic.com" "Let /usr/bin/myapp talk to internal-svc:8080 but only for reading"

Moderate Tier (host + partial path knowledge)

The user knows some API paths but doesn't have full docs. Examples: "Allow GET on /api/v1/models and POST on /api/v1/completions at integrate.api.nvidia.com" "Read-only on /repos/ at api.github.com, but also allow POST on /repos/*/issues" Generate explicit rules for the known paths. If the user also wants broader access beyond the specific paths, combine with a catch-all rule or suggest a preset instead.

Full Tier (complete API docs)

The user provides full API documentation. Accepted formats: Format · How to consume URL · Fetch with WebFetch and parse the endpoint list File path · Read the file (OpenAPI JSON/YAML, markdown, etc.) Pasted text · Parse inline from the conversation

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Security
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview generate-sandbox-policy.preview
# Step 7: Determine Output Mode

The policy needs to go somewhere. Determine which mode applies: | Signal | Mode | |--------|------| | User names an existing policy file (e.g., "add to my-sandbox-policy.yaml") | **Update existing file** | | User says "update my policy", "add this to my policy file" | **Update existing file** — ask which file to update | | User asks to modify an existing policy rule by name | **Update existing file** — edit the named policy in place | | User says "create a new policy file" or names a file that doesn't exist | **Create new file** | | No file context given | **Present only** — show the YAML and

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.