generate-policy

Generate sandbox policy YAML from Sigil scan results.

5|2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/NOMARJ/sigil --skill generate-policy-nomarj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: generate-policy
Source: https://github.com/NOMARJ/sigil/tree/main/plugins/claude-code/skills/generate-policy
Command: npx skills add https://github.com/NOMARJ/sigil --skill generate-policy-nomarj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates turning Sigil scan findings into a concrete sandbox policy YAML that constrains filesystem, network, process, and credential access so untrusted agent code can be executed safely.

Core Features & Use Cases

  • Automated Policy Synthesis: Maps scan findings to filesystem, network, process, and credential rules and emits a ready-to-review YAML policy.
  • Severity-based Enforcement: Applies different restriction levels based on scan verdicts (CLEAN → permissive, CRITICAL → deny-all).
  • Explainable Rules: Includes human-readable explanations tying each restriction to specific findings to support review and auditing.
  • Use Case: Generate a sandbox policy for third-party skills or CI-checked repositories before allowing runtime execution.

Quick Start

Generate a sigil sandbox policy for the project at ./project-path using the latest scan results and save it to sigil-policy.yaml for review.

Frequently Asked Questions about generate-policy

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

FAQPage Schema
How do I generate a sandbox policy YAML from security scan results?▼

To generate a sandbox policy YAML from security scan results, map scan findings to filesystem, network, process, and credential restrictions using severity-based mappings and output a ready-to-review sigil-policy.yaml file.

How do I restrict filesystem and network access for untrusted agent code?▼

Restrict filesystem and network access for untrusted agent code by synthesizing sandbox policies from scan verdicts, applying deny-all rules for critical findings and permissive rules for clean results to enforce safe execution.

What is severity-based enforcement in agent sandboxing?▼

Severity-based enforcement in agent sandboxing applies different restriction levels based on scan verdicts, mapping CLEAN findings to permissive access and CRITICAL findings to deny-all policies for filesystem, network, process, and credential controls.

Can I use sandbox policy generation for CI workflows and third-party skills?▼

Yes, you can use sandbox policy generation for CI workflows and third-party skills by producing a YAML policy containing filesystem, network, process, and credentials sections with severity-based mappings before allowing runtime execution.

How do I make sandbox policies explainable for auditing?▼

Make sandbox policies explainable for auditing by including human-readable explanations tying each filesystem, network, process, and credential restriction to specific scan findings to support review.

What are the limitations of automated policy synthesis from scan findings?▼

Automated policy synthesis from scan findings relies on severity-based mappings and requires human review of the generated sigil-policy.yaml to verify that filesystem, network, process, and credential restrictions match the intended enforcement scope.