@intentsolutionsio/fairdb-operations-kit 1.0.0 → 1.0.5

package/README.md

@@ -67,6 +67,7 @@ The `fairdb-automation-agent` provides intelligent automation for:
 ### FairDB Backup Manager
 
 An Agent Skill that automatically activates when working with backups:
+
 - Manages pgBackRest configurations
 - Executes scheduled backups
 - Performs test restores
@@ -98,6 +99,7 @@ FairDB Infrastructure Stack
 This plugin implements three core SOPs:
 
 ### SOP-001: VPS Hardening
+
 - OS security updates
 - Firewall configuration (UFW)
 - Intrusion prevention (Fail2ban)
@@ -105,6 +107,7 @@ This plugin implements three core SOPs:
 - Monitoring setup
 
 ### SOP-002: PostgreSQL Installation
+
 - PostgreSQL 16 from official repos
 - Production configuration tuning
 - SSL certificate generation
@@ -112,6 +115,7 @@ This plugin implements three core SOPs:
 - Performance optimization
 
 ### SOP-003: Backup Configuration
+
 - pgBackRest installation
 - Wasabi S3 integration
 - Retention policy setup
@@ -122,7 +126,7 @@ This plugin implements three core SOPs:
 
 Required environment variables:
 
-```bash
+```text
 # Contabo API
 CONTABO_API_KEY=<your-api-key>
 
@@ -214,6 +218,7 @@ Active: 87/200 (43.5%)
 ## Best Practices
 
 ### Security
+
 - Always use SSL/TLS connections
 - Rotate passwords quarterly
 - Keep IP allowlists updated
@@ -221,6 +226,7 @@ Active: 87/200 (43.5%)
 - Encrypted backups only
 
 ### Performance
+
 - Monitor connection pools
 - Regular VACUUM ANALYZE
 - Index optimization
@@ -228,6 +234,7 @@ Active: 87/200 (43.5%)
 - Resource usage tracking
 
 ### Reliability
+
 - Test restores monthly
 - Document all procedures
 - Maintain runbooks
@@ -239,6 +246,7 @@ Active: 87/200 (43.5%)
 ### Common Issues
 
 **PostgreSQL Won't Start**
+
 ```bash
 # Check logs
 sudo journalctl -u postgresql -n 50
@@ -251,6 +259,7 @@ sudo netstat -tulpn | grep 5432
 ```
 
 **Backup Failures**
+
 ```bash
 # Check pgBackRest status
 sudo -u postgres pgbackrest --stanza=fairdb check
@@ -263,6 +272,7 @@ tail -f /var/log/pgbackrest/fairdb-backup.log
 ```
 
 **High Connection Usage**
+
 ```bash
 # View active connections
 sudo -u postgres psql -c "SELECT * FROM pg_stat_activity;"
@@ -295,4 +305,4 @@ Jeremy Longshore (jeremy@intentsolutions.io)
 
 ---
 
-*Part of the Claude Code Plugins ecosystem - https://claudecodeplugins.io*
+*Part of the Claude Code Plugins ecosystem - https://claudecodeplugins.io*

package/agents/fairdb-automation-agent.md

@@ -1,9 +1,36 @@
 ---
 name: fairdb-automation-agent
 description: Intelligent automation agent for FairDB PostgreSQL operations
+tools:
+- Read
+- Write
+- Edit
+- Bash
+- Glob
+- Grep
+- WebFetch
+- WebSearch
+- Task
+- TodoWrite
 model: sonnet
+color: pink
+version: 1.0.0
+author: Jeremy Longshore <jeremy@intentsolutions.io>
+tags:
+- devops
+- fairdb
+- automation
+disallowedTools: []
+skills: []
+background: false
+# ── upgrade levers — uncomment + set when tuning this agent ──
+# effort: high            # reasoning depth: low/medium/high/xhigh/max (omit = inherit session)
+# maxTurns: 50            # cap the agentic loop (omit = engine default)
+# memory: project         # persistent scope: user/project/local (omit = ephemeral)
+# isolation: worktree     # run in an isolated git worktree
+# initialPrompt: "…"      # seed the agent's first turn
+# hooks / mcpServers / permissionMode → set at the PLUGIN level, not on a plugin agent
 ---
-
 # FairDB Automation Agent
 
 I am an intelligent automation agent specialized in managing FairDB PostgreSQL as a Service operations. I can analyze situations, make decisions, and execute complex workflows autonomously.
@@ -11,24 +38,28 @@ I am an intelligent automation agent specialized in managing FairDB PostgreSQL a
 ## Core Capabilities
 
 ### 1. Proactive Monitoring
+
 - Continuously analyze system health metrics
 - Predict potential issues before they occur
 - Automatically trigger preventive maintenance
 - Optimize performance based on usage patterns
 
 ### 2. Intelligent Problem Resolution
+
 - Diagnose issues using pattern recognition
 - Apply appropriate fixes based on historical data
 - Escalate to humans only when necessary
 - Learn from each incident for future prevention
 
 ### 3. Resource Optimization
+
 - Dynamically adjust PostgreSQL parameters
 - Manage connection pools efficiently
 - Balance workload across customers
 - Optimize query performance automatically
 
 ### 4. Automated Operations
+
 - Handle routine maintenance tasks
 - Execute backup and recovery procedures
 - Manage customer provisioning workflows
@@ -173,18 +204,21 @@ I predict and prevent issues:
 ## Integration Points
 
 ### Monitoring Systems
+
 - Prometheus metrics collection
 - Grafana dashboard updates
 - Alert manager integration
 - Custom webhook notifications
 
 ### Ticketing Systems
+
 - Auto-create tickets for issues
 - Update ticket status automatically
 - Attach diagnostic information
 - Close tickets when resolved
 
 ### Communication Channels
+
 - Slack notifications for team
 - Email alerts for customers
 - SMS for critical issues
@@ -193,13 +227,16 @@ I predict and prevent issues:
 ## Learning Mechanisms
 
 ### Knowledge Base Updates
+
 After each significant event, I update:
+
 - Incident patterns database
 - Resolution strategies
 - Performance baselines
 - Security threat signatures
 
 ### Continuous Improvement
+
 - Track success rates of automated fixes
 - Measure time to resolution
 - Analyze false positive rates
@@ -208,6 +245,7 @@ After each significant event, I update:
 ## Safety Constraints
 
 I will NEVER automatically:
+
 - Delete customer data
 - Modify backup retention policies
 - Change security settings without approval
@@ -215,6 +253,7 @@ I will NEVER automatically:
 - Alter billing or plan settings
 
 I will ALWAYS:
+
 - Create backups before major changes
 - Test in staging when possible
 - Document all actions taken
@@ -224,6 +263,7 @@ I will ALWAYS:
 ## Activation Triggers
 
 I activate automatically when:
+
 - System metrics exceed thresholds
 - Scheduled tasks are due
 - Incidents are detected
@@ -233,6 +273,7 @@ I activate automatically when:
 ## Example Scenarios
 
 ### Scenario 1: High Connection Usage
+
 ```
 Detected: Connection usage at 85%
 Analysis: Spike from customer_xyz database
@@ -242,6 +283,7 @@ Followup: Contact customer about upgrading plan
 ```
 
 ### Scenario 2: Disk Space Warning
+
 ```
 Detected: /var/lib/postgresql at 88% capacity
 Analysis: Unexpected growth in analytics_db
@@ -251,6 +293,7 @@ Followup: Schedule discussion about archiving strategy
 ```
 
 ### Scenario 3: Slow Query Impact
+
 ```
 Detected: Query running >30 minutes blocking others
 Analysis: Missing index on large table join
@@ -264,6 +307,7 @@ Followup: Add to index recommendation report
 I generate these reports automatically:
 
 ### Daily Report
+
 - System health summary
 - Customer usage statistics
 - Incident summary
@@ -271,6 +315,7 @@ I generate these reports automatically:
 - Backup status
 
 ### Weekly Report
+
 - Capacity trends
 - Security audit results
 - Customer growth metrics
@@ -278,6 +323,7 @@ I generate these reports automatically:
 - Maintenance schedule
 
 ### Monthly Report
+
 - SLA compliance
 - Cost analysis
 - Growth projections
@@ -287,6 +333,7 @@ I generate these reports automatically:
 ## Human Interaction
 
 When I need human assistance, I provide:
+
 - Clear problem description
 - All diagnostic data collected
 - Actions already attempted
@@ -298,10 +345,11 @@ I learn from human interventions to handle similar situations autonomously in th
 ## Continuous Operation
 
 I operate 24/7 with these cycles:
+
 - Health checks every 5 minutes
 - Performance analysis every hour
 - Security scans every 4 hours
 - Backup verification daily
 - Capacity planning weekly
 
-My goal is to maintain 99.99% uptime for all FairDB customers while continuously improving efficiency and reducing manual intervention requirements.
+My goal is to maintain 99.99% uptime for all FairDB customers while continuously improving efficiency and reducing manual intervention requirements.

package/commands/fairdb-emergency-response.md

@@ -11,6 +11,7 @@ You are responding to a critical incident in the FairDB PostgreSQL infrastructur
 ## Incident Classification
 
 First, identify the incident type:
+
 - **P1 Critical**: Complete service outage, data loss risk
 - **P2 High**: Major degradation, affecting multiple customers
 - **P3 Medium**: Single customer impact, performance issues
@@ -450,6 +451,7 @@ echo "================================================" | tee -a $INCIDENT_LOG
 ## Emergency Contacts
 
 Keep these contacts readily available:
+
 - PostgreSQL Expert: [Contact info]
 - Infrastructure Team: [Contact info]
 - Customer Success: [Contact info]
@@ -477,4 +479,4 @@ sudo -u postgres vacuumdb --all --analyze-in-stages
 
 # Check data checksums
 sudo -u postgres /usr/lib/postgresql/16/bin/pg_checksums -D /var/lib/postgresql/16/main --check
-```
+```

package/commands/fairdb-health-check.md

@@ -428,6 +428,7 @@ echo -e "\nFull report saved to: $REPORT_FILE"
 ## Actions Based on Results
 
 ### If Critical Issues Found:
+
 1. Check PostgreSQL service status
 2. Review disk space availability
 3. Verify backup integrity
@@ -435,6 +436,7 @@ echo -e "\nFull report saved to: $REPORT_FILE"
 5. Review security vulnerabilities
 
 ### If Warnings Found:
+
 1. Schedule maintenance window
 2. Plan capacity upgrades
 3. Review query performance
@@ -442,6 +444,7 @@ echo -e "\nFull report saved to: $REPORT_FILE"
 5. Document issues for trending
 
 ### Regular Maintenance Tasks:
+
 1. Run VACUUM ANALYZE on large tables
 2. Update table statistics
 3. Review and optimize slow queries
@@ -456,4 +459,4 @@ echo "30 */6 * * * root /usr/local/bin/fairdb-health-check > /dev/null 2>&1" | \
     sudo tee /etc/cron.d/fairdb-health-check
 
 echo "Health checks scheduled every 6 hours"
-```
+```

package/commands/fairdb-onboard-customer.md

@@ -11,6 +11,7 @@ You are onboarding a new customer for FairDB PostgreSQL as a Service. This compr
 ## Step 1: Gather Customer Information
 
 Collect these details:
+
 1. **Customer Name**: Company/organization name
 2. **Database Name**: Preferred database name (lowercase, no spaces)
 3. **Primary Contact**: Name and email
@@ -410,6 +411,7 @@ Next Actions:
 ## Onboarding Checklist
 
 Verify completion:
+
 - [ ] Database created
 - [ ] Users created with secure passwords
 - [ ] Network access configured
@@ -424,6 +426,7 @@ Verify completion:
 ## Rollback Procedure
 
 If onboarding fails:
+
 ```bash
 # Remove database and users
 sudo -u postgres psql << EOF
@@ -443,4 +446,4 @@ sudo rm -rf /etc/postgresql/16/main/ssl/${CUSTOMER_NAME}
 sudo ufw delete allow from ${CUSTOMER_IP} to any port 5432
 
 echo "Customer ${CUSTOMER_NAME} rollback complete"
-```
+```

package/commands/fairdb-setup-backup.md

@@ -11,6 +11,7 @@ You are configuring pgBackRest with Wasabi S3 storage for automated PostgreSQL b
 ## Prerequisites Check
 
 Verify before starting:
+
 1. PostgreSQL 16 is installed and running
 2. Wasabi S3 account is active with bucket created
 3. AWS CLI credentials are available
@@ -163,9 +164,11 @@ sudo -u postgres pgbackrest --stanza=fairdb --repo=1 info 2>&1 | tee -a $LOG_FIL
 echo "Full backup completed at $(date)" | tee -a $LOG_FILE
 
 # Send notification (implement webhook/email here)
-curl -X POST $FAIRDB_MONITORING_WEBHOOK \
-  -H 'Content-Type: application/json' \
-  -d "{\"text\":\"FairDB full backup completed successfully\"}" 2>/dev/null || true
+if [[ -n "${FAIRDB_MONITORING_WEBHOOK:-}" ]]; then
+  curl -X POST "$FAIRDB_MONITORING_WEBHOOK" \
+    -H 'Content-Type: application/json' \
+    -d '{"text":"FairDB full backup completed successfully"}' 2>/dev/null || true
+fi
 EOF
 
 # Incremental backup script
@@ -374,6 +377,7 @@ EOF
 ## Verification Checklist
 
 Confirm these items:
+
 - [ ] pgBackRest installed and configured
 - [ ] Wasabi S3 credentials configured
 - [ ] Stanza created and verified
@@ -396,6 +400,7 @@ Confirm these items:
 ## Output Summary
 
 Provide the user with:
+
 1. Backup stanza status: `pgbackrest --stanza=fairdb info`
 2. Next full backup time from cron schedule
 3. Location of backup scripts and logs
@@ -417,4 +422,4 @@ sudo -u postgres pgbackrest --stanza=fairdb check
 # Restore commands
 sudo -u postgres pgbackrest --stanza=fairdb restore                 # Latest
 sudo -u postgres pgbackrest --stanza=fairdb --type=time --target="2024-01-01 12:00:00" restore  # PITR
-```
+```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@intentsolutionsio/fairdb-operations-kit",
-  "version": "1.0.0",
+  "version": "1.0.5",
   "description": "Complete operations kit for FairDB PostgreSQL as a Service - VPS setup, PostgreSQL management, customer provisioning, monitoring, and backup automation",
   "keywords": [
     "fairdb",

package/skills/fairdb-backup-manager/SKILL.md

@@ -1,17 +1,24 @@
 ---
 name: fairdb-backup-manager
-description: |
-  Manage use when you need to work with backup and recovery.
-  This skill provides backup automation and disaster recovery with comprehensive guidance and automation.
+description: 'Manage use when you need to work with backup and recovery.
+
+  This skill provides backup automation and disaster recovery with comprehensive guidance
+  and automation.
+
   Trigger with phrases like "create backups", "automate backups",
+
   or "implement disaster recovery".
 
+  '
 allowed-tools: Read, Write, Edit, Grep, Glob, Bash(tar:*), Bash(rsync:*), Bash(aws:s3:*)
 version: 1.0.0
 author: Jeremy Longshore <jeremy@intentsolutions.io>
 license: MIT
-compatible-with: claude-code, codex, openclaw
-tags: [devops, backup, disaster-recovery]
+tags:
+- devops
+- backup
+- disaster-recovery
+compatibility: Designed for Claude Code, also compatible with Codex and OpenClaw
 ---
 # FairDB Backup Manager
 
@@ -69,4 +76,4 @@ Automate backup and recovery operations for FairDB database instances. Generate
 - AWS S3 CLI: https://docs.aws.amazon.com/cli/latest/reference/s3/
 - rsync documentation: https://rsync.samba.org/documentation.html
 - Backup automation patterns: https://www.veeam.com/blog/321-backup-rule.html
-- Linux cron scheduling: https://crontab.guru/
+- Linux cron scheduling: https://crontab.guru/

package/skills/fairdb-backup-manager/assets/README.md

@@ -5,6 +5,7 @@ This directory contains static assets used by this skill.
 ## Purpose
 
 Assets can include:
+
 - Configuration files (JSON, YAML)
 - Data files
 - Templates

package/skills/fairdb-backup-manager/references/README.md

@@ -5,6 +5,7 @@ This directory contains reference materials that enhance this skill's capabiliti
 ## Purpose
 
 References can include:
+
 - Code examples
 - Style guides
 - Best practices documentation

package/skills/fairdb-backup-manager/scripts/README.md

@@ -5,6 +5,7 @@ This directory contains optional helper scripts that support this skill's functi
 ## Purpose
 
 Scripts here can be:
+
 - Referenced by the skill for automation
 - Used as examples for users
 - Executed during skill activation

package/skills/skill-adapter/assets/README.md

@@ -1,4 +1,3 @@
 # Assets
 
 Bundled resources for fairdb-operations-kit skill
-

package/skills/skill-adapter/references/README.md

@@ -1,4 +1,3 @@
 # References
 
 Bundled resources for fairdb-operations-kit skill
-

package/skills/skill-adapter/references/examples.md

@@ -7,11 +7,13 @@ This document provides practical examples of how to use this skill effectively.
 ### Example 1: Simple Activation
 
 **User Request:**
+
 ```
 [Describe trigger phrase here]
 ```
 
 **Skill Response:**
+
 1. Analyzes the request
 2. Performs the required action
 3. Returns results
@@ -19,11 +21,13 @@ This document provides practical examples of how to use this skill effectively.
 ### Example 2: Complex Workflow
 
 **User Request:**
+
 ```
 [Describe complex scenario]
 ```
 
 **Workflow:**
+
 1. Step 1: Initial analysis
 2. Step 2: Data processing
 3. Step 3: Result generation
@@ -34,6 +38,7 @@ This document provides practical examples of how to use this skill effectively.
 ### Pattern 1: Chaining Operations
 
 Combine this skill with other tools:
+
 ```
 Step 1: Use this skill for [purpose]
 Step 2: Chain with [other tool]
@@ -43,6 +48,7 @@ Step 3: Finalize with [action]
 ### Pattern 2: Error Handling
 
 If issues occur:
+
 - Check trigger phrase matches
 - Verify context is available
 - Review allowed-tools permissions

package/skills/skill-adapter/scripts/validation.sh

@@ -1,32 +0,0 @@
-#!/bin/bash
-# Skill validation helper
-# Validates skill activation and functionality
-
-set -e
-
-echo "🔍 Validating skill..."
-
-# Check if SKILL.md exists
-if [ ! -f "../SKILL.md" ]; then
-    echo "❌ Error: SKILL.md not found"
-    exit 1
-fi
-
-# Validate frontmatter
-if ! grep -q "^---$" "../SKILL.md"; then
-    echo "❌ Error: No frontmatter found"
-    exit 1
-fi
-
-# Check required fields
-if ! grep -q "^name:" "../SKILL.md"; then
-    echo "❌ Error: Missing 'name' field"
-    exit 1
-fi
-
-if ! grep -q "^description:" "../SKILL.md"; then
-    echo "❌ Error: Missing 'description' field"
-    exit 1
-fi
-
-echo "✅ Skill validation passed"