mcpField
S
System

System

github.com/danielmiesslerAgent workflows19.7k115 installsUpdated 2d ago
Repository

About System

System is a skill for validating, documenting, and security-checking the PAI system. It provides workflows for integrity audits, session documentation, secret and privacy scans, and recall of past work.

Key features

  1. 01Checks system references and integrity
  2. 02Documents current and recent work
  3. 03Scans for secrets with TruffleHog
  4. 04Checks for sensitive data patterns
  5. 05Searches memory and git history

Use cases

  1. 01Auditing after a major refactor
  2. 02Recording a work session
  3. 03Scanning before a public commit
  4. 04Tracing the history of a past change

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/danielmiessler/lifeos --skill system

After installing, type/systemin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

Templates/
Update.md
Tools/
ExtractArchitectureUpdates.ts
UpdateSearch.ts
CreateUpdate.ts
UpdateIndex.ts
Workflows/
IntegrityCheck.md
DocumentRecent.md
PrivacyCheck.md
DocumentSession.md
SecretScanning.md
WorkContextRecall.md

Details

From the project README

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 Three)
WorkflowTriggerPurposeFile
IntegrityCheck"integrity check", "audit system", "check references", "system health"Find and fix broken references across the systemWorkflows/IntegrityCheck.md
DocumentSession"document session", "document today", "document this session", "log session"Document current session's work from transcriptWorkflows/DocumentSession.md
DocumentRecent"document recent", "catch up docs", "what's undocumented", "document since last update"Catch-up documentation for changes since last documented updateWorkflows/DocumentRecent.md

Composition Rules:

  • Integrity Check → may produce fixes → Document Session
  • After any session → Document Session
  • Periodic catch-up → Document Recent
Security Workflows
WorkflowTriggerFile
SecretScanning"check for secrets", "scan for credentials", "security scan"Workflows/SecretScanning.md
PrivacyCheck"privacy check", "check for sensitive data", "data isolation"Workflows/PrivacyCheck.md
Utility Workflows
WorkflowTriggerFile
WorkContextRecall"we just worked on", "what did we do with", "remember when we", "didn't we already"Workflows/WorkContextRecall.md

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/

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
Security Workflows

Example 4: Secret Scanning

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

Example 5: 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 Three Core Operations
OperationInputOutputDuration
IntegrityCheckCodebase scanList of broken refs found/fixed~2-5 min
DocumentSessionSession transcriptPAISYSTEMUPDATES entry~30s
DocumentRecentGit history since last updateMultiple PAISYSTEMUPDATES entries~1-2 min
Composition Patterns
End of Session:     DocumentSession
After Refactoring:  IntegrityCheck → DocumentSession
Catch-up:           DocumentRecent
Security Audits
Audit TypeToolScopeDuration
Secret ScanTruffleHogAny directory~30s-2min
Privacy Checkgrep/patternsskills/ (excl USER/WORK)~30s
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 user 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

ToolPurposeLocation
SecretScan.tsTruffleHog wrapper for credential detectionCORE/Tools/SecretScan.ts
CreateUpdate.tsCreate new system update entriesTools/CreateUpdate.ts
UpdateIndex.tsRegenerate index.json and CHANGELOG.mdTools/UpdateIndex.ts
UpdateSearch.tsSearch and query system updatesTools/UpdateSearch.ts
ExtractArchitectureUpdates.tsHistorical migration tool (one-time use)Tools/ExtractArchitectureUpdates.ts

Templates

TemplatePurposeLocation
Update.mdTemplate for system update entriesTemplates/Update.md

Output Locations

OutputLocation
Integrity ReportsMEMORY/STATE/integrity/YYYY-MM-DD.md
System UpdatesMEMORY/PAISYSTEMUPDATES/YYYY/MM/*.md
Update IndexMEMORY/PAISYSTEMUPDATES/index.json
ChangelogMEMORY/PAISYSTEMUPDATES/CHANGELOG.md

Related Skills

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

Comments

Markdown supported