system-rules

Enforce guardrails for Rawgrowth OS governing data loading, output quality, security, and logging.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/scanbott/claude-skills --skill system-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-rules
Source: https://github.com/scanbott/claude-skills/tree/main/system-rules
Command: npx skills add https://github.com/scanbott/claude-skills --skill system-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Strict guardrails for the Rawgrowth OS ensure safe, compliant, and auditable agent execution across data loading, output quality, security, and self-improvement workflows.

Core Features & Use Cases

  • Guardrails for data loading: restrict reading to relevant files, prefer grep/glob, and avoid data leakage.
  • Output quality and safety: enforce non-hallucination, require explicit approvals when necessary, and log activity for governance.
  • Compliance and auditing: enforce file placement rules, versioning, CLAUDE.md constraints, and activity logging.

Quick Start

Follow the guardrails whenever you build or audit an agent to ensure safe and auditable behavior.

Frequently Asked Questions about system-rules

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

FAQPage Schema
What are OS guardrails for safe automation and why do I need them?

OS guardrails for safe automation enforce strict rules for data loading, security, and output quality during agent execution. You need them to prevent data leakage, prohibit credential exposure, and ensure consistent, auditable behavior across automated tasks.

How do I enforce compliance and security guardrails during agent construction?

Enforce compliance and security guardrails during agent construction by applying rules that limit CLAUDE.md length, restrict file placement, ensure a single source of truth, and prohibit credential leakage. This ensures safe, auditable agent execution.

Can I use these system rules to restrict data loading and prevent data leakage?

Yes, you can use these system rules to restrict data loading by enforcing rules that limit reading to relevant files and prefer grep or glob searches. This approach actively prevents data leakage and ensures secure context handling.

Does this approach support logging all agent activity for auditing purposes?

Yes, this approach supports logging all agent activity for auditing purposes. It enforces continuous activity logging and requires explicit approvals when necessary, ensuring full governance and traceability across all automated workflows.

What are the limitations of applying strict OS guardrails to automated workflows?

Limitations of applying strict OS guardrails include constraints on directory and file placement, enforced CLAUDE.md length limits, and mandatory approval steps. These strict rules may restrict flexibility but ensure consistent compliance and security.