System

Customization

Before executing, check for user customizations at: ~/.claude/skills/CORE/USER/SKILLCUSTOMIZATIONS/System/

If this directory exists, load and apply any PREFERENCES.md, configurations, or resources found there. These override default behavior. If the directory does not exist, proceed with skill defaults.

System Skill

System validation, integrity audits, documentation tracking, and security scanning for the PAI system.

Visibility

This skill runs in the foreground so you can see all output, progress, and hear voice notifications as work happens. Documentation updates, integrity checks, and other system operations should be visible to maintain transparency.

Voice Notification

When executing a workflow, do BOTH:

1. Send voice notification:

   curl -s -X POST http://localhost:8888/notify \
     -H "Content-Type: application/json" \
     -d '{"message": "Running WORKFLOWNAME workflow from System skill"}' \
     > /dev/null 2>&1 &
   

2. Output text notification:

   Running the **WorkflowName** workflow from the **System** skill...
   

Workflow Routing

Core Operations (The Four)

Composition Rules:

• Integrity Check → may produce fixes → Document Session → Git Push
• After any session → Document Session → Git Push
• Periodic catch-up → Document Recent → Git Push

Security Workflows

Utility Workflows

Note: For public PAI integrity ("check PAI integrity", "audit PAI packs"), use the PAI skill → PAIIntegrityCheck.md

Examples

Core Operations

Example 1: Integrity Check

User: "Run an integrity check"
→ Invokes IntegrityCheck workflow
→ Spawns parallel agents to audit ~/.claude
→ Finds broken references, missing files
→ Returns list of issues found/fixed

Example 2: Document Current Session

User: "Document this session"
→ Invokes DocumentSession workflow
→ Reads current session transcript
→ Uses AI to extract what changed and why
→ Creates entry in MEMORY/PAISYSTEMUPDATES/
→ Automatically calls GitPush

Example 3: Catch-up Documentation

User: "What's undocumented? Catch up the docs."
→ Invokes DocumentRecent workflow
→ Finds last documented update timestamp
→ Compares git history since then
→ Generates documentation for missed changes
→ Automatically calls GitPush

Example 4: Git Push

User: "Git Push"
→ Invokes GitPush workflow
→ Verifies we're in ~/.claude (PRIVATE repo)
→ git add + commit + push

Security Workflows

Example 5: Secret Scanning

User: "Check for secrets before I push"
→ Invokes SecretScanning workflow
→ Runs TruffleHog on specified directory
→ Reports any API keys, credentials found

Example 6: Cross-Repo Validation

User: "Make sure nothing leaked to public"
→ Invokes CrossRepoValidation workflow
→ Compares ~/.claude with ~/Projects/PAI
→ Reports private content in wrong place

Utility

Example 7: Recall Past Work

User: "We just worked on the status line - why broken again?"
→ Invokes WorkContextRecall workflow
→ Searches MEMORY/, git history for "status line"
→ Presents timeline of changes and possible regression

Quick Reference

The Four Core Operations

Composition Patterns

End of Session:     DocumentSession → GitPush
After Refactoring:  IntegrityCheck → DocumentSession → GitPush
Catch-up:           DocumentRecent → GitPush
Quick Push:         GitPush (if docs already created)

Security Audits

Documentation Format

Verbose Narrative Structure:

• The Story (1-3 paragraphs): Background, Problem, Resolution
• How It Used To Work: Previous state with bullet points
• How It Works Now: New state with improvements
• Going Forward: Future implications
• Verification: How we know it works

When to Use

Integrity Checks

• After major refactoring
• Before releasing updates
• Periodic system health checks
• When something "feels broken"
• Before pushing to public PAI repo

Documentation

• End of significant work sessions
• After creating new skills/workflows/tools
• When architectural decisions are made
• To maintain system history

Security Scanning

• Before any git commit to public repos
• When auditing for credential leaks
• Periodic security hygiene checks
• After receiving external code/content

Privacy Validation

• After working with USER/ or WORK/ content
• Before any public commits
• When creating new skills that might reference personal data
• Periodic audit to ensure data isolation

Work Context Recall

• When Daniel asks about past work ("we just fixed that")
• Questions about why decisions were made
• Finding artifacts from previous sessions
• Debugging something that was "already fixed"
• Resuming multi-session projects

Tools

Templates

Output Locations

Related Skills

• PAI - Public PAI repository management (includes PAIIntegrityCheck)
• CORE - System architecture and memory documentation
• Evals - Regression testing and capability verification