{"id":"faab0d6c-677a-4313-82e8-9de79fc1466e","entityType":"agent","slug":"clawhub-bytesagain-lab-raspberry-pi-manager","name":"Raspberry Pi Manager","canonicalUrl":"https://www.xpersona.co/agent/clawhub-bytesagain-lab-raspberry-pi-manager","canonicalPath":"/agent/clawhub-bytesagain-lab-raspberry-pi-manager","generatedAt":"2026-10-10T13:29:43.233Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-10T11:16:07.463Z","emptyReason":null},"description":"Manage Raspberry Pi devices — GPIO control, system monitoring (CPU/temp/memory), service management, sensor data reading. Skill: Raspberry Pi Manager Owner: bytesagain-lab Summary: Manage Raspberry Pi devices — GPIO control, system monitoring (CPU/temp/memory), service management, sensor data reading. Tags: chinese:1.0.0, latest:2.0.1, productivity:1.0.0 Version history: v2.0.1 | 2026-03-18T10:49:20.575Z | user update v2.0.0 | 2026-03-17T18:50:33.066Z | user v2.5 standard: Use-when desc, homepage, source, security fix v2.3.6 | 2026-03-1","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.5K downloads reported by the source. Last updated 10/10/2026.","installCommand":"clawhub skill install s174pq5f3gzez3838vt2642fmx848f1d:raspberry-pi-manager","sourceUrl":"https://clawhub.ai/bytesagain-lab/raspberry-pi-manager","homepage":"https://clawhub.ai/bytesagain-lab/skills/raspberry-pi-manager","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/bytesagain-lab/raspberry-pi-manager","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/bytesagain-lab/skills/raspberry-pi-manager","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":63,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Manage Raspberry Pi devices — GPIO control, system monitoring (CPU/temp/memory), service management, sensor data reading. Skill: Raspberry Pi Manager Owner: byt"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-10T11:16:07.463Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T11:16:07.463Z","emptyReason":null},"stars":null,"forks":null,"downloads":1471,"packageName":null,"latestVersion":"2.0.1","tractionLabel":"1.5K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T11:16:07.403Z","emptyReason":null},"lastUpdatedAt":"2026-10-10T11:16:07.463Z","lastCrawledAt":"2026-10-10T11:16:07.403Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-11T11:16:07.403Z","lastVerifiedAt":null,"highlights":[{"version":"2.0.1","createdAt":"2026-03-18T10:49:20.575Z","changelog":"update","fileCount":4,"zipByteSize":6287},{"version":"2.0.0","createdAt":"2026-03-17T18:50:33.066Z","changelog":"v2.5 standard: Use-when desc, homepage, source, security fix","fileCount":5,"zipByteSize":11115},{"version":"2.3.6","createdAt":"2026-03-16T12:27:37.249Z","changelog":"old template -> domain-specific v2.0.0","fileCount":5,"zipByteSize":11126},{"version":"2.3.5","createdAt":"2026-03-16T11:47:59.512Z","changelog":"old template -> domain-specific v2.0.0","fileCount":5,"zipByteSize":11126},{"version":"2.3.4","createdAt":"2026-03-15T22:39:56.160Z","changelog":"Quality upgrade","fileCount":5,"zipByteSize":11158},{"version":"2.3.3","createdAt":"2026-03-15T21:54:26.956Z","changelog":"Quality upgrade: custom functionality","fileCount":5,"zipByteSize":11158},{"version":"2.3.2","createdAt":"2026-03-15T12:44:17.200Z","changelog":"Standards compliance: unique content, no template text","fileCount":5,"zipByteSize":9322},{"version":"2.3.1","createdAt":"2026-03-15T01:46:14.714Z","changelog":"Quality update: docs, examples, standards compliance","fileCount":4,"zipByteSize":8840}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s174pq5f3gzez3838vt2642fmx848f1d:raspberry-pi-manager","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bytesagain-lab-raspberry-pi-manager/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bytesagain-lab-raspberry-pi-manager/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bytesagain-lab-raspberry-pi-manager/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-bytesagain-lab-raspberry-pi-manager/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-bytesagain-lab-raspberry-pi-manager/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-bytesagain-lab-raspberry-pi-manager/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T13:29:43.231Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bytesagain-lab-raspberry-pi-manager/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bytesagain-lab-raspberry-pi-manager/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bytesagain-lab-raspberry-pi-manager/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bytesagain-lab-raspberry-pi-manager/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-10T11:16:07.463Z","emptyReason":null},"readme":"Skill: Raspberry Pi Manager\n\nOwner: bytesagain-lab\n\nSummary: Manage Raspberry Pi devices — GPIO control, system monitoring (CPU/temp/memory), service management, sensor data reading.\n\nTags: chinese:1.0.0, latest:2.0.1, productivity:1.0.0\n\nVersion history:\n\nv2.0.1 | 2026-03-18T10:49:20.575Z | user\n\nupdate\n\nv2.0.0 | 2026-03-17T18:50:33.066Z | user\n\nv2.5 standard: Use-when desc, homepage, source, security fix\n\nv2.3.6 | 2026-03-16T12:27:37.249Z | user\n\nold template -> domain-specific v2.0.0\n\nv2.3.5 | 2026-03-16T11:47:59.512Z | user\n\nold template -> domain-specific v2.0.0\n\nv2.3.4 | 2026-03-15T22:39:56.160Z | user\n\nQuality upgrade\n\nv2.3.3 | 2026-03-15T21:54:26.956Z | user\n\nQuality upgrade: custom functionality\n\nv2.3.2 | 2026-03-15T12:44:17.200Z | user\n\nStandards compliance: unique content, no template text\n\nv2.3.1 | 2026-03-15T01:46:14.714Z | user\n\nQuality update: docs, examples, standards compliance\n\nv2.3.0 | 2026-03-14T00:21:01.349Z | user\n\nQuality fixes: removed third-party references, aligned docs with implementation\n\nv2.2.0 | 2026-03-13T17:08:43.850Z | user\n\nEnhanced descriptions for better AI triggering\n\nv2.1.0 | 2026-03-13T16:54:23.008Z | user\n\nEnhanced descriptions for better AI triggering\n\nv1.0.1 | 2026-03-13T00:26:35.309Z | user\n\nAdd runtime declaration + security compliance\n\nv1.0.0 | 2026-03-11T12:17:36.942Z | auto\n\nInitial release of raspberry-pi-manager.\n\n- Manage Raspberry Pi devices with script-based commands for local or SSH-connected boards.\n- Features system monitoring (CPU, temperature, memory, disk, network), GPIO control, and hardware sensor support.\n- Includes service management (systemd control and logging).\n- Offers remote deployment, fleet management, backup, overclocking, and system maintenance utilities.\n- Provides threshold-based monitoring alerts and historical data logging.\n- Supports both single-Pi and multi-Pi workflows.\n\nArchive index:\n\nArchive v2.0.1: 4 files, 6287 bytes\n\nFiles: scripts/script.sh (12094b), skill-card.md (2085b), SKILL.md (6181b), _meta.json (139b)\n\nFile v2.0.1:SKILL.md\n\n---\nversion: \"2.0.0\"\nname: raspberry-pi-manager\ndescription: \"Manage Raspberry Pi devices — GPIO control, system monitoring (CPU/temp/memory), service management, sensor data reading.\"\nauthor: BytesAgain\nhomepage: https://bytesagain.com\nsource: https://github.com/bytesagain/ai-skills\n---\n\n# Raspberry Pi Manager\n\nA command-line toolkit for managing Raspberry Pi operations. Log, track, and organize entries across multiple operational categories — from device connections and syncing to monitoring, automation, notifications, and reporting. All data is stored locally with timestamped history, full-text search, and multi-format export.\n\n## Commands\n\nThe following commands are available via `raspberry-pi-manager [args]`:\n\n### Core Operations\n\n| Command | Description |\n|---------|-------------|\n| `connect ` | Log a connection event (e.g. SSH session, network link, peripheral attach). Called without args, shows recent connect entries. |\n| `sync ` | Record a sync operation (e.g. file sync, config push, backup mirror). Called without args, shows recent sync entries. |\n| `monitor ` | Log a monitoring observation (e.g. CPU temp spike, disk usage alert). Called without args, shows recent monitor entries. |\n| `automate ` | Record an automation task (e.g. cron job setup, GPIO script trigger). Called without args, shows recent automate entries. |\n| `notify ` | Log a notification event (e.g. email alert sent, Telegram ping). Called without args, shows recent notify entries. |\n| `report ` | Save a report note (e.g. weekly summary, incident write-up). Called without args, shows recent report entries. |\n| `schedule ` | Record a scheduled task (e.g. reboot at 3 AM, backup every Sunday). Called without args, shows recent schedule entries. |\n| `template ` | Store a template entry (e.g. config template, deploy script skeleton). Called without args, shows recent template entries. |\n| `webhook ` | Log a webhook event (e.g. incoming POST, IFTTT trigger). Called without args, shows recent webhook entries. |\n| `status ` | Record a status update (e.g. Pi online, service healthy). Called without args, shows recent status entries. |\n| `analytics ` | Log an analytics data point (e.g. uptime percentage, request count). Called without args, shows recent analytics entries. |\n| `export ` | Record an export action. Called without args, shows recent export entries. |\n\n### Utility Commands\n\n| Command | Description |\n|---------|-------------|\n| `stats` | Show summary statistics — entry counts per category, total entries, data size, and earliest record timestamp. |\n| `export ` | Export all data in `json`, `csv`, or `txt` format. Output file saved to the data directory. |\n| `search ` | Full-text search across all log files (case-insensitive). |\n| `recent` | Show the 20 most recent activity entries from the global history log. |\n| `status` | Health check — version, data directory path, total entries, disk usage, last activity, and OK status. |\n| `help` | Display the full command reference. |\n| `version` | Print the current version (`v2.0.0`). |\n\n## Data Storage\n\nAll data is persisted locally in `~/.local/share/raspberry-pi-manager/`:\n\n- **Per-command logs** — Each command (connect, sync, monitor, etc.) writes to its own `.log` file with `YYYY-MM-DD HH:MM|` format.\n- **Global history** — Every action is also appended to `history.log` with `MM-DD HH:MM : ` format for unified audit trail.\n- **Export files** — Generated exports are saved as `export.json`, `export.csv`, or `export.txt` in the same directory.\n\nNo external services, databases, or network connections are required. Everything runs locally via bash.\n\n## Requirements\n\n- **Bash 4+** (uses `local` variables, `set -euo pipefail`)\n- Standard Unix utilities: `date`, `wc`, `du`, `head`, `tail`, `grep`, `basename`, `cat`\n- No root privileges needed\n- No external dependencies or package installs\n\n## When to Use\n\n1. **Tracking Pi fleet operations** — Log connect/sync/monitor events across multiple Raspberry Pi devices to maintain an operational journal.\n2. **Building an automation audit trail** — Record every automation task and webhook trigger so you can trace what happened and when.\n3. **Generating operational reports** — Use `stats`, `recent`, and `export` to produce summaries for weekly reviews or incident investigations.\n4. **Organizing scheduled maintenance** — Use `schedule` to document planned tasks (reboots, updates, backups) and `notify` to log alert dispatches.\n5. **Searching historical records** — Use `search` to quickly find past events across all categories when troubleshooting an issue.\n\n## Examples\n\n```bash\n# Log a new SSH connection to a Pi\nraspberry-pi-manager connect \"SSH to pi@192.168.1.50 — firmware update session\"\n\n# Record a file sync event\nraspberry-pi-manager sync \"rsync /home/pi/data → NAS backup completed, 2.3GB transferred\"\n\n# Log a temperature monitoring alert\nraspberry-pi-manager monitor \"CPU temp 72°C on pi-node-3 — fan triggered\"\n\n# Record an automation task\nraspberry-pi-manager automate \"Cron job added: /home/pi/scripts/backup.sh every Sunday 02:00\"\n\n# View summary statistics\nraspberry-pi-manager stats\n\n# Export all data as JSON\nraspberry-pi-manager export json\n\n# Search for all entries mentioning 'backup'\nraspberry-pi-manager search backup\n\n# Check overall health status\nraspberry-pi-manager status\n\n# View the 20 most recent activities\nraspberry-pi-manager recent\n```\n\n## How It Works\n\nEach command follows the same pattern:\n\n1. **With arguments** — Timestamps the input, appends it to the command-specific log file, increments the entry count, and writes to the global history log.\n2. **Without arguments** — Displays the 20 most recent entries from that command's log file.\n\nThe `stats` command aggregates counts across all log files. The `export` command iterates through all logs and produces a unified output in your chosen format. The `search` command performs a case-insensitive grep across every log file.\n\n---\n\nPowered by BytesAgain | bytesagain.com | hello@bytesagain.com\n\nFile v2.0.1:_meta.json\n\n{\n \"ownerId\": \"kn76vqrf94wk924mddj8fp4p5x8497tb\",\n \"slug\": \"raspberry-pi-manager\",\n \"version\": \"2.0.1\",\n \"publishedAt\": 1773830960575\n}\n\nFile v2.0.1:skill-card.md\n\n## Description:\n\nA local bash command-line journal for recording Raspberry Pi-related operational notes, searching saved entries, viewing recent activity, and exporting logs.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[bytesagain-lab](https://clawhub.ai/user/bytesagain-lab)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal developers and operators can use this skill as a local operations journal for Raspberry Pi fleet notes, automation records, status observations, searches, and exports. It should not be treated as a device management or monitoring interface.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill is advertised as Raspberry Pi management, but evidence shows it records local notes and exports logs rather than controlling GPIO, services, sensors, or devices.\n\nMitigation: Use it only as an operations journal and verify any real device-management needs with separate trusted tooling.\n\nRisk: Operational entries are stored in plaintext under ~/.local/share/raspberry-pi-manager and can be searched or exported.\n\nMitigation: Do not enter credentials, tokens, private host details, or other sensitive information into logged entries.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/bytesagain-lab/skills/raspberry-pi-manager)\n- [BytesAgain homepage](https://bytesagain.com)\n\n## Skill Output:\n\n**Output Type(s):** [Shell commands, Text, Files, Guidance]\n\n**Output Format:** [Markdown guidance with inline bash commands and local text, JSON, CSV, or TXT export files]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Stores entries in plaintext under ~/.local/share/raspberry-pi-manager.]\n\n## Skill Version(s):\n\n2.0.1 (source: ClawHub release evidence; artifact frontmatter reports 2.0.0)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v2.0.0: 5 files, 11115 bytes\n\nFiles: scripts/rpi.sh (11809b), scripts/script.sh (12094b), SKILL.md (7569b), tips.md (2697b), _meta.json (139b)\n\nFile v2.0.0:SKILL.md\n\n---\nversion: \"2.0.0\"\nname: raspberry-pi-manager\ndescription: \"Manage Raspberry Pi devices — GPIO control, system monitoring (CPU/temp/memory), service management, sensor data reading.\"\nauthor: BytesAgain\nhomepage: https://bytesagain.com\nsource: https://github.com/bytesagain/ai-skills\n---\n\n# Raspberry Pi Manager\n\nA Swiss Army knife for Raspberry Pi administration. Whether you're running a single Pi as a home server or managing a fleet of IoT nodes, this toolkit gives you instant access to system stats, GPIO pins, services, sensors, and deployment workflows.\n\nThe script runs locally on the Pi or connects remotely via SSH. For local use, just execute the script directly. For remote management, configure SSH access.\n\n### Local Usage\n\n```bash\nbash scripts/pi-manager.sh system\nbash scripts/pi-manager.sh gpio read 17\n```\n\n### Remote Usage\n\n```bash\nexport PI_HOST=\"pi@192.168.1.200\"\nexport PI_SSH_KEY=\"~/.ssh/id_rsa\"\n\nbash scripts/pi-manager.sh --remote system\nbash scripts/pi-manager.sh --remote gpio read 17\n```\n\nMultiple Pi support:\n\n```bash\nexport PI_HOSTS=\"pi@node1.local,pi@node2.local,pi@node3.local\"\nbash scripts/pi-manager.sh --fleet system\n```\n\n## System Monitoring\n\nReal-time insight into your Pi's health.\n\n```bash\n# Full system dashboard\n$ bash scripts/pi-manager.sh system\n\n┌─ Raspberry Pi 4 Model B (4GB) ─────────────────────┐\n│ │\n│ CPU: 4× ARM Cortex-A72 @ 1.5GHz │\n│ Load: 0.42, 0.38, 0.31 │\n│ Temp: 48.3°C / 118.9°F [████░░░░░░ OK] │\n│ Memory: 1.2GB / 3.7GB [████████░░ 32%] │\n│ Disk: 12.4GB / 29.1GB [█████████░ 43%] │\n│ Swap: 0MB / 100MB [░░░░░░░░░░ 0%] │\n│ Uptime: 14 days, 7:23:41 │\n│ OS: Raspberry Pi OS (Bookworm) 64-bit │\n│ │\n│ Network: │\n│ eth0: 192.168.1.200 (1000 Mbps) │\n│ wlan0: 192.168.1.201 (72 Mbps, -42 dBm) │\n└──────────────────────────────────────────────────────┘\n```\n\n### Individual Metrics\n\n```bash\n# Temperature with threshold warning\nbash scripts/pi-manager.sh temp\nbash scripts/pi-manager.sh temp --warn 70 --crit 80\n\n# CPU usage (snapshot or continuous)\nbash scripts/pi-manager.sh cpu\nbash scripts/pi-manager.sh cpu --watch 5 # Update every 5s\n\n# Memory breakdown\nbash scripts/pi-manager.sh memory\n\n# Disk usage by mount point\nbash scripts/pi-manager.sh disk\n\n# Network interfaces and traffic\nbash scripts/pi-manager.sh network\n\n# Top processes by CPU/memory\nbash scripts/pi-manager.sh top 10\n```\n\n### Historical Data\n\n```bash\n# Log system metrics to CSV (for graphing)\nbash scripts/pi-manager.sh monitor --interval 60 --output metrics.csv\n\n# View logged metrics\nbash scripts/pi-manager.sh monitor --view metrics.csv --last 24h\n```\n\n## GPIO Control\n\nDirect pin manipulation for hardware projects.\n\n```bash\n# Pin layout reference\nbash scripts/pi-manager.sh gpio pinout\n\n# Read a pin state\nbash scripts/pi-manager.sh gpio read 17\n\n# Set pin output\nbash scripts/pi-manager.sh gpio write 17 high\nbash scripts/pi-manager.sh gpio write 17 low\n\n# Set pin mode\nbash scripts/pi-manager.sh gpio mode 17 output\nbash scripts/pi-manager.sh gpio mode 18 input --pull up\n\n# PWM output (hardware PWM on supported pins)\nbash scripts/pi-manager.sh gpio pwm 18 75 # 75% duty cycle\n\n# Watch pin for changes\nbash scripts/pi-manager.sh gpio watch 17 --edge both\n\n# Bulk operations\nbash scripts/pi-manager.sh gpio write 17,18,27,22 high\nbash scripts/pi-manager.sh gpio read 17,18,27,22\n\n# GPIO status overview\nbash scripts/pi-manager.sh gpio status\n```\n\n## Service Management\n\nControl systemd services running on the Pi.\n\n```bash\n# List all services (active, failed, inactive)\nbash scripts/pi-manager.sh service list\nbash scripts/pi-manager.sh service list --failed\n\n# Service operations\nbash scripts/pi-manager.sh service status nginx\nbash scripts/pi-manager.sh service start nginx\nbash scripts/pi-manager.sh service stop nginx\nbash scripts/pi-manager.sh service restart nginx\nbash scripts/pi-manager.sh service enable nginx\nbash scripts/pi-manager.sh service disable nginx\n\n# View service logs\nbash scripts/pi-manager.sh service logs nginx --lines 50\nbash scripts/pi-manager.sh service logs nginx --follow\n\n# Create a new service from a script\nbash scripts/pi-manager.sh service create my-app /home/pi/app/start.sh \\\n --description \"My Application\" \\\n --restart always \\\n --user pi\n```\n\n## Sensor Data\n\nRead common sensors connected to your Pi.\n\n```bash\n# DHT11/DHT22 temperature & humidity\nbash scripts/pi-manager.sh sensor dht22 4 # GPIO pin 4\n\n# DS18B20 temperature sensor (1-Wire)\nbash scripts/pi-manager.sh sensor ds18b20\n\n# BMP280/BME280 (I2C)\nbash scripts/pi-manager.sh sensor bme280\n\n# HC-SR04 ultrasonic distance\nbash scripts/pi-manager.sh sensor distance 23 24 # Trigger/Echo pins\n\n# PIR motion sensor\nbash scripts/pi-manager.sh sensor pir 17 --watch\n\n# Light sensor (analog via MCP3008 ADC)\nbash scripts/pi-manager.sh sensor light 0 # ADC channel 0\n\n# Log sensor readings\nbash scripts/pi-manager.sh sensor dht22 4 --log --interval 300 --output temp_log.csv\n```\n\n## Remote Deployment\n\nDeploy applications and configurations to your Pi.\n\n```bash\n# Copy files to Pi\nbash scripts/pi-manager.sh deploy push ./app/ /home/pi/app/\n\n# Pull files from Pi\nbash scripts/pi-manager.sh deploy pull /home/pi/logs/ ./local-logs/\n\n# Run a script on the Pi\nbash scripts/pi-manager.sh deploy exec ./setup.sh\n\n# Full deployment workflow\nbash scripts/pi-manager.sh deploy run ./deploy.yml\n```\n\n### Deploy manifest (`deploy.yml`):\n\n```yaml\ntarget: pi@192.168.1.200\nsteps:\n - copy: ./app/ → /home/pi/app/\n - run: cd /home/pi/app && pip3 install -r requirements.txt\n - run: sudo systemctl restart my-app\n - verify: curl -s http://localhost:8080/health\n```\n\n```bash\n# Fleet deployment\nbash scripts/pi-manager.sh --fleet deploy run ./deploy.yml\n# Deploys to all configured Pi hosts sequentially\n```\n\n## Maintenance\n\n```bash\n# System update\nbash scripts/pi-manager.sh update\n\n# Firmware update check\nbash scripts/pi-manager.sh firmware\n\n# Reboot / shutdown\nbash scripts/pi-manager.sh reboot\nbash scripts/pi-manager.sh shutdown\n\n# Backup SD card (creates compressed image)\nbash scripts/pi-manager.sh backup /path/to/backup.img.gz\n\n# Overclock profiles\nbash scripts/pi-manager.sh overclock show\nbash scripts/pi-manager.sh overclock mild # 1.8GHz\nbash scripts/pi-manager.sh overclock medium # 2.0GHz\n```\n\n## Monitoring Alerts\n\nSet up threshold-based alerts:\n\n```bash\n# Alert if temperature exceeds 75°C\nbash scripts/pi-manager.sh alert temp 75\n\n# Alert if disk usage exceeds 90%\nbash scripts/pi-manager.sh alert disk 90\n\n# Alert if a service goes down\nbash scripts/pi-manager.sh alert service nginx\n\n# All alerts — suitable for cron\nbash scripts/pi-manager.sh alert check\n```\n\nDesigned to be used standalone or as part of a larger IoT management workflow. Pair with `homeassistant-toolkit` for full smart home integration.\n---\n💬 Feedback & Feature Requests: https://bytesagain.com/feedback\nPowered by BytesAgain | bytesagain.com\n\n## Commands\n\nRun `raspberry-pi-manager help` to see all available commands.\n\nFile v2.0.0:_meta.json\n\n{\n \"ownerId\": \"kn76vqrf94wk924mddj8fp4p5x8497tb\",\n \"slug\": \"raspberry-pi-manager\",\n \"version\": \"2.0.0\",\n \"publishedAt\": 1773773433066\n}\n\nFile v2.0.0:tips.md\n\n# Tips for Raspberry Pi Manager\n\n## System Health\n\n1. **Keep the CPU temperature below 70°C.** Throttling starts at 80°C and significantly impacts performance. Use a heatsink + fan if running heavy workloads.\n\n2. **Monitor disk usage proactively.** SD cards fill up silently — logs, temp files, and package caches are common culprits. Set up a cron alert at 80%.\n\n3. **Use `--watch` mode for debugging performance issues.** Real-time CPU and memory monitoring helps identify spikes and memory leaks.\n\n4. **Log metrics to CSV** for long-term trend analysis. A weekly review of temperature and load patterns can prevent failures before they happen.\n\n## GPIO Best Practices\n\n- **Always double-check pin numbering.** BCM numbering (GPIO17) and physical pin numbering (pin 11) are different. The script uses BCM by default.\n- **Use pull-up/pull-down resistors** for input pins to avoid floating values\n- **Don't draw more than 16mA per GPIO pin** — use a transistor or relay for higher-power devices\n- **The `pinout` command** is your quick reference — no need to Google the diagram every time\n\n## Sensor Tips\n\n- **DHT22 > DHT11** for accuracy (±0.5°C vs ±2°C), but DHT11 is cheaper\n- **DS18B20** requires 1-Wire to be enabled: `sudo raspi-config` → Interface Options → 1-Wire\n- **BME280 via I2C** — enable I2C first: `sudo raspi-config` → Interface Options → I2C\n- **Log sensor data to CSV** and use `chart-generator` skill for visualization\n\n## Remote Management\n\n- **Set up SSH key authentication** — password auth over the internet is risky\n- **Use a reverse SSH tunnel or VPN** for remote access without port forwarding\n- **The `--fleet` mode** is powerful but runs commands sequentially — for large fleets, consider parallel execution with `xargs -P`\n\n## SD Card Longevity\n\n- **Use log2ram** to reduce SD card writes (logs stay in RAM, flushed periodically)\n- **Set `noatime` mount option** in `/etc/fstab` to reduce unnecessary writes\n- **Move heavy I/O to a USB drive** — databases, media, downloads\n- **Keep a backup image** — use the `backup` command monthly\n\n## Security Hardening\n\n- Change the default password immediately\n- Disable password-based SSH login\n- Keep the system updated: `bash scripts/pi-manager.sh update`\n- Disable unused services to reduce attack surface\n- Consider running `fail2ban` for SSH brute-force protection\n\n## Performance Tuning\n\n- **Overclock cautiously.** Start with \"mild\" and test stability under load before going higher.\n- **Disable the GUI** if running headless: saves ~200MB RAM\n- **Use zram** for swap instead of SD card swap — faster and reduces card wear\n- **64-bit OS** uses more RAM but gives access to >4GB on Pi 4/5\n\nArchive v2.3.6: 5 files, 11126 bytes\n\nFiles: scripts/rpi.sh (11809b), scripts/script.sh (12094b), SKILL.md (7599b), tips.md (2697b), _meta.json (139b)\n\nFile v2.3.6:SKILL.md\n\n---\nversion: \"2.0.0\"\nname: raspberry-pi-manager\ndescription: \"Manage Raspberry Pi devices — GPIO control, system monitoring (CPU/temp/memory), service management, sensor data reading, and remote deployment. Use when you need raspberry pi manager capabilities. Triggers on: raspberry pi manager.\"\nauthor: BytesAgain\n---\n\n# Raspberry Pi Manager\n\nA Swiss Army knife for Raspberry Pi administration. Whether you're running a single Pi as a home server or managing a fleet of IoT nodes, this toolkit gives you instant access to system stats, GPIO pins, services, sensors, and deployment workflows.\n\nThe script runs locally on the Pi or connects remotely via SSH. For local use, just execute the script directly. For remote management, configure SSH access.\n\n### Local Usage\n\n```bash\nbash scripts/pi-manager.sh system\nbash scripts/pi-manager.sh gpio read 17\n```\n\n### Remote Usage\n\n```bash\nexport PI_HOST=\"pi@192.168.1.200\"\nexport PI_SSH_KEY=\"~/.ssh/id_rsa\"\n\nbash scripts/pi-manager.sh --remote system\nbash scripts/pi-manager.sh --remote gpio read 17\n```\n\nMultiple Pi support:\n\n```bash\nexport PI_HOSTS=\"pi@node1.local,pi@node2.local,pi@node3.local\"\nbash scripts/pi-manager.sh --fleet system\n```\n\n## System Monitoring\n\nReal-time insight into your Pi's health.\n\n```bash\n# Full system dashboard\n$ bash scripts/pi-manager.sh system\n\n┌─ Raspberry Pi 4 Model B (4GB) ─────────────────────┐\n│ │\n│ CPU: 4× ARM Cortex-A72 @ 1.5GHz │\n│ Load: 0.42, 0.38, 0.31 │\n│ Temp: 48.3°C / 118.9°F [████░░░░░░ OK] │\n│ Memory: 1.2GB / 3.7GB [████████░░ 32%] │\n│ Disk: 12.4GB / 29.1GB [█████████░ 43%] │\n│ Swap: 0MB / 100MB [░░░░░░░░░░ 0%] │\n│ Uptime: 14 days, 7:23:41 │\n│ OS: Raspberry Pi OS (Bookworm) 64-bit │\n│ │\n│ Network: │\n│ eth0: 192.168.1.200 (1000 Mbps) │\n│ wlan0: 192.168.1.201 (72 Mbps, -42 dBm) │\n└──────────────────────────────────────────────────────┘\n```\n\n### Individual Metrics\n\n```bash\n# Temperature with threshold warning\nbash scripts/pi-manager.sh temp\nbash scripts/pi-manager.sh temp --warn 70 --crit 80\n\n# CPU usage (snapshot or continuous)\nbash scripts/pi-manager.sh cpu\nbash scripts/pi-manager.sh cpu --watch 5 # Update every 5s\n\n# Memory breakdown\nbash scripts/pi-manager.sh memory\n\n# Disk usage by mount point\nbash scripts/pi-manager.sh disk\n\n# Network interfaces and traffic\nbash scripts/pi-manager.sh network\n\n# Top processes by CPU/memory\nbash scripts/pi-manager.sh top 10\n```\n\n### Historical Data\n\n```bash\n# Log system metrics to CSV (for graphing)\nbash scripts/pi-manager.sh monitor --interval 60 --output metrics.csv\n\n# View logged metrics\nbash scripts/pi-manager.sh monitor --view metrics.csv --last 24h\n```\n\n## GPIO Control\n\nDirect pin manipulation for hardware projects.\n\n```bash\n# Pin layout reference\nbash scripts/pi-manager.sh gpio pinout\n\n# Read a pin state\nbash scripts/pi-manager.sh gpio read 17\n\n# Set pin output\nbash scripts/pi-manager.sh gpio write 17 high\nbash scripts/pi-manager.sh gpio write 17 low\n\n# Set pin mode\nbash scripts/pi-manager.sh gpio mode 17 output\nbash scripts/pi-manager.sh gpio mode 18 input --pull up\n\n# PWM output (hardware PWM on supported pins)\nbash scripts/pi-manager.sh gpio pwm 18 75 # 75% duty cycle\n\n# Watch pin for changes\nbash scripts/pi-manager.sh gpio watch 17 --edge both\n\n# Bulk operations\nbash scripts/pi-manager.sh gpio write 17,18,27,22 high\nbash scripts/pi-manager.sh gpio read 17,18,27,22\n\n# GPIO status overview\nbash scripts/pi-manager.sh gpio status\n```\n\n## Service Management\n\nControl systemd services running on the Pi.\n\n```bash\n# List all services (active, failed, inactive)\nbash scripts/pi-manager.sh service list\nbash scripts/pi-manager.sh service list --failed\n\n# Service operations\nbash scripts/pi-manager.sh service status nginx\nbash scripts/pi-manager.sh service start nginx\nbash scripts/pi-manager.sh service stop nginx\nbash scripts/pi-manager.sh service restart nginx\nbash scripts/pi-manager.sh service enable nginx\nbash scripts/pi-manager.sh service disable nginx\n\n# View service logs\nbash scripts/pi-manager.sh service logs nginx --lines 50\nbash scripts/pi-manager.sh service logs nginx --follow\n\n# Create a new service from a script\nbash scripts/pi-manager.sh service create my-app /home/pi/app/start.sh \\\n --description \"My Application\" \\\n --restart always \\\n --user pi\n```\n\n## Sensor Data\n\nRead common sensors connected to your Pi.\n\n```bash\n# DHT11/DHT22 temperature & humidity\nbash scripts/pi-manager.sh sensor dht22 4 # GPIO pin 4\n\n# DS18B20 temperature sensor (1-Wire)\nbash scripts/pi-manager.sh sensor ds18b20\n\n# BMP280/BME280 (I2C)\nbash scripts/pi-manager.sh sensor bme280\n\n# HC-SR04 ultrasonic distance\nbash scripts/pi-manager.sh sensor distance 23 24 # Trigger/Echo pins\n\n# PIR motion sensor\nbash scripts/pi-manager.sh sensor pir 17 --watch\n\n# Light sensor (analog via MCP3008 ADC)\nbash scripts/pi-manager.sh sensor light 0 # ADC channel 0\n\n# Log sensor readings\nbash scripts/pi-manager.sh sensor dht22 4 --log --interval 300 --output temp_log.csv\n```\n\n## Remote Deployment\n\nDeploy applications and configurations to your Pi.\n\n```bash\n# Copy files to Pi\nbash scripts/pi-manager.sh deploy push ./app/ /home/pi/app/\n\n# Pull files from Pi\nbash scripts/pi-manager.sh deploy pull /home/pi/logs/ ./local-logs/\n\n# Run a script on the Pi\nbash scripts/pi-manager.sh deploy exec ./setup.sh\n\n# Full deployment workflow\nbash scripts/pi-manager.sh deploy run ./deploy.yml\n```\n\n### Deploy manifest (`deploy.yml`):\n\n```yaml\ntarget: pi@192.168.1.200\nsteps:\n - copy: ./app/ → /home/pi/app/\n - run: cd /home/pi/app && pip3 install -r requirements.txt\n - run: sudo systemctl restart my-app\n - verify: curl -s http://localhost:8080/health\n```\n\n```bash\n# Fleet deployment\nbash scripts/pi-manager.sh --fleet deploy run ./deploy.yml\n# Deploys to all configured Pi hosts sequentially\n```\n\n## Maintenance\n\n```bash\n# System update\nbash scripts/pi-manager.sh update\n\n# Firmware update check\nbash scripts/pi-manager.sh firmware\n\n# Reboot / shutdown\nbash scripts/pi-manager.sh reboot\nbash scripts/pi-manager.sh shutdown\n\n# Backup SD card (creates compressed image)\nbash scripts/pi-manager.sh backup /path/to/backup.img.gz\n\n# Overclock profiles\nbash scripts/pi-manager.sh overclock show\nbash scripts/pi-manager.sh overclock mild # 1.8GHz\nbash scripts/pi-manager.sh overclock medium # 2.0GHz\n```\n\n## Monitoring Alerts\n\nSet up threshold-based alerts:\n\n```bash\n# Alert if temperature exceeds 75°C\nbash scripts/pi-manager.sh alert temp 75\n\n# Alert if disk usage exceeds 90%\nbash scripts/pi-manager.sh alert disk 90\n\n# Alert if a service goes down\nbash scripts/pi-manager.sh alert service nginx\n\n# All alerts — suitable for cron\nbash scripts/pi-manager.sh alert check\n```\n\nDesigned to be used standalone or as part of a larger IoT management workflow. Pair with `homeassistant-toolkit` for full smart home integration.\n---\n💬 Feedback & Feature Requests: https://bytesagain.com/feedback\nPowered by BytesAgain | bytesagain.com\n\n## Commands\n\nRun `raspberry-pi-manager help` to see all available commands.\n\nFile v2.3.6:_meta.json\n\n{\n \"ownerId\": \"kn76vqrf94wk924mddj8fp4p5x8497tb\",\n \"slug\": \"raspberry-pi-manager\",\n \"version\": \"2.3.6\",\n \"publishedAt\": 1773664057249\n}\n\nFile v2.3.6:tips.md\n\n# Tips for Raspberry Pi Manager\n\n## System Health\n\n1. **Keep the CPU temperature below 70°C.** Throttling starts at 80°C and significantly impacts performance. Use a heatsink + fan if running heavy workloads.\n\n2. **Monitor disk usage proactively.** SD cards fill up silently — logs, temp files, and package caches are common culprits. Set up a cron alert at 80%.\n\n3. **Use `--watch` mode for debugging performance issues.** Real-time CPU and memory monitoring helps identify spikes and memory leaks.\n\n4. **Log metrics to CSV** for long-term trend analysis. A weekly review of temperature and load patterns can prevent failures before they happen.\n\n## GPIO Best Practices\n\n- **Always double-check pin numbering.** BCM numbering (GPIO17) and physical pin numbering (pin 11) are different. The script uses BCM by default.\n- **Use pull-up/pull-down resistors** for input pins to avoid floating values\n- **Don't draw more than 16mA per GPIO pin** — use a transistor or relay for higher-power devices\n- **The `pinout` command** is your quick reference — no need to Google the diagram every time\n\n## Sensor Tips\n\n- **DHT22 > DHT11** for accuracy (±0.5°C vs ±2°C), but DHT11 is cheaper\n- **DS18B20** requires 1-Wire to be enabled: `sudo raspi-config` → Interface Options → 1-Wire\n- **BME280 via I2C** — enable I2C first: `sudo raspi-config` → Interface Options → I2C\n- **Log sensor data to CSV** and use `chart-generator` skill for visualization\n\n## Remote Management\n\n- **Set up SSH key authentication** — password auth over the internet is risky\n- **Use a reverse SSH tunnel or VPN** for remote access without port forwarding\n- **The `--fleet` mode** is powerful but runs commands sequentially — for large fleets, consider parallel execution with `xargs -P`\n\n## SD Card Longevity\n\n- **Use log2ram** to reduce SD card writes (logs stay in RAM, flushed periodically)\n- **Set `noatime` mount option** in `/etc/fstab` to reduce unnecessary writes\n- **Move heavy I/O to a USB drive** — databases, media, downloads\n- **Keep a backup image** — use the `backup` command monthly\n\n## Security Hardening\n\n- Change the default password immediately\n- Disable password-based SSH login\n- Keep the system updated: `bash scripts/pi-manager.sh update`\n- Disable unused services to reduce attack surface\n- Consider running `fail2ban` for SSH brute-force protection\n\n## Performance Tuning\n\n- **Overclock cautiously.** Start with \"mild\" and test stability under load before going higher.\n- **Disable the GUI** if running headless: saves ~200MB RAM\n- **Use zram** for swap instead of SD card swap — faster and reduces card wear\n- **64-bit OS** uses more RAM but gives access to >4GB on Pi 4/5\n\nArchive v2.3.5: 5 files, 11126 bytes\n\nFiles: scripts/rpi.sh (11809b), scripts/script.sh (12094b), SKILL.md (7599b), tips.md (2697b), _meta.json (139b)\n\nFile v2.3.5:SKILL.md\n\n---\nversion: \"2.0.0\"\nname: raspberry-pi-manager\ndescription: \"Manage Raspberry Pi devices — GPIO control, system monitoring (CPU/temp/memory), service management, sensor data reading, and remote deployment. Use when you need raspberry pi manager capabilities. Triggers on: raspberry pi manager.\"\nauthor: BytesAgain\n---\n\n# Raspberry Pi Manager\n\nA Swiss Army knife for Raspberry Pi administration. Whether you're running a single Pi as a home server or managing a fleet of IoT nodes, this toolkit gives you instant access to system stats, GPIO pins, services, sensors, and deployment workflows.\n\nThe script runs locally on the Pi or connects remotely via SSH. For local use, just execute the script directly. For remote management, configure SSH access.\n\n### Local Usage\n\n```bash\nbash scripts/pi-manager.sh system\nbash scripts/pi-manager.sh gpio read 17\n```\n\n### Remote Usage\n\n```bash\nexport PI_HOST=\"pi@192.168.1.200\"\nexport PI_SSH_KEY=\"~/.ssh/id_rsa\"\n\nbash scripts/pi-manager.sh --remote system\nbash scripts/pi-manager.sh --remote gpio read 17\n```\n\nMultiple Pi support:\n\n```bash\nexport PI_HOSTS=\"pi@node1.local,pi@node2.local,pi@node3.local\"\nbash scripts/pi-manager.sh --fleet system\n```\n\n## System Monitoring\n\nReal-time insight into your Pi's health.\n\n```bash\n# Full system dashboard\n$ bash scripts/pi-manager.sh system\n\n┌─ Raspberry Pi 4 Model B (4GB) ─────────────────────┐\n│ │\n│ CPU: 4× ARM Cortex-A72 @ 1.5GHz │\n│ Load: 0.42, 0.38, 0.31 │\n│ Temp: 48.3°C / 118.9°F [████░░░░░░ OK] │\n│ Memory: 1.2GB / 3.7GB [████████░░ 32%] │\n│ Disk: 12.4GB / 29.1GB [█████████░ 43%] │\n│ Swap: 0MB / 100MB [░░░░░░░░░░ 0%] │\n│ Uptime: 14 days, 7:23:41 │\n│ OS: Raspberry Pi OS (Bookworm) 64-bit │\n│ │\n│ Network: │\n│ eth0: 192.168.1.200 (1000 Mbps) │\n│ wlan0: 192.168.1.201 (72 Mbps, -42 dBm) │\n└──────────────────────────────────────────────────────┘\n```\n\n### Individual Metrics\n\n```bash\n# Temperature with threshold warning\nbash scripts/pi-manager.sh temp\nbash scripts/pi-manager.sh temp --warn 70 --crit 80\n\n# CPU usage (snapshot or continuous)\nbash scripts/pi-manager.sh cpu\nbash scripts/pi-manager.sh cpu --watch 5 # Update every 5s\n\n# Memory breakdown\nbash scripts/pi-manager.sh memory\n\n# Disk usage by mount point\nbash scripts/pi-manager.sh disk\n\n# Network interfaces and traffic\nbash scripts/pi-manager.sh network\n\n# Top processes by CPU/memory\nbash scripts/pi-manager.sh top 10\n```\n\n### Historical Data\n\n```bash\n# Log system metrics to CSV (for graphing)\nbash scripts/pi-manager.sh monitor --interval 60 --output metrics.csv\n\n# View logged metrics\nbash scripts/pi-manager.sh monitor --view metrics.csv --last 24h\n```\n\n## GPIO Control\n\nDirect pin manipulation for hardware projects.\n\n```bash\n# Pin layout reference\nbash scripts/pi-manager.sh gpio pinout\n\n# Read a pin state\nbash scripts/pi-manager.sh gpio read 17\n\n# Set pin output\nbash scripts/pi-manager.sh gpio write 17 high\nbash scripts/pi-manager.sh gpio write 17 low\n\n# Set pin mode\nbash scripts/pi-manager.sh gpio mode 17 output\nbash scripts/pi-manager.sh gpio mode 18 input --pull up\n\n# PWM output (hardware PWM on supported pins)\nbash scripts/pi-manager.sh gpio pwm 18 75 # 75% duty cycle\n\n# Watch pin for changes\nbash scripts/pi-manager.sh gpio watch 17 --edge both\n\n# Bulk operations\nbash scripts/pi-manager.sh gpio write 17,18,27,22 high\nbash scripts/pi-manager.sh gpio read 17,18,27,22\n\n# GPIO status overview\nbash scripts/pi-manager.sh gpio status\n```\n\n## Service Management\n\nControl systemd services running on the Pi.\n\n```bash\n# List all services (active, failed, inactive)\nbash scripts/pi-manager.sh service list\nbash scripts/pi-manager.sh service list --failed\n\n# Service operations\nbash scripts/pi-manager.sh service status nginx\nbash scripts/pi-manager.sh service start nginx\nbash scripts/pi-manager.sh service stop nginx\nbash scripts/pi-manager.sh service restart nginx\nbash scripts/pi-manager.sh service enable nginx\nbash scripts/pi-manager.sh service disable nginx\n\n# View service logs\nbash scripts/pi-manager.sh service logs nginx --lines 50\nbash scripts/pi-manager.sh service logs nginx --follow\n\n# Create a new service from a script\nbash scripts/pi-manager.sh service create my-app /home/pi/app/start.sh \\\n --description \"My Application\" \\\n --restart always \\\n --user pi\n```\n\n## Sensor Data\n\nRead common sensors connected to your Pi.\n\n```bash\n# DHT11/DHT22 temperature & humidity\nbash scripts/pi-manager.sh sensor dht22 4 # GPIO pin 4\n\n# DS18B20 temperature sensor (1-Wire)\nbash scripts/pi-manager.sh sensor ds18b20\n\n# BMP280/BME280 (I2C)\nbash scripts/pi-manager.sh sensor bme280\n\n# HC-SR04 ultrasonic distance\nbash scripts/pi-manager.sh sensor distance 23 24 # Trigger/Echo pins\n\n# PIR motion sensor\nbash scripts/pi-manager.sh sensor pir 17 --watch\n\n# Light sensor (analog via MCP3008 ADC)\nbash scripts/pi-manager.sh sensor light 0 # ADC channel 0\n\n# Log sensor readings\nbash scripts/pi-manager.sh sensor dht22 4 --log --interval 300 --output temp_log.csv\n```\n\n## Remote Deployment\n\nDeploy applications and configurations to your Pi.\n\n```bash\n# Copy files to Pi\nbash scripts/pi-manager.sh deploy push ./app/ /home/pi/app/\n\n# Pull files from Pi\nbash scripts/pi-manager.sh deploy pull /home/pi/logs/ ./local-logs/\n\n# Run a script on the Pi\nbash scripts/pi-manager.sh deploy exec ./setup.sh\n\n# Full deployment workflow\nbash scripts/pi-manager.sh deploy run ./deploy.yml\n```\n\n### Deploy manifest (`deploy.yml`):\n\n```yaml\ntarget: pi@192.168.1.200\nsteps:\n - copy: ./app/ → /home/pi/app/\n - run: cd /home/pi/app && pip3 install -r requirements.txt\n - run: sudo systemctl restart my-app\n - verify: curl -s http://localhost:8080/health\n```\n\n```bash\n# Fleet deployment\nbash scripts/pi-manager.sh --fleet deploy run ./deploy.yml\n# Deploys to all configured Pi hosts sequentially\n```\n\n## Maintenance\n\n```bash\n# System update\nbash scripts/pi-manager.sh update\n\n# Firmware update check\nbash scripts/pi-manager.sh firmware\n\n# Reboot / shutdown\nbash scripts/pi-manager.sh reboot\nbash scripts/pi-manager.sh shutdown\n\n# Backup SD card (creates compressed image)\nbash scripts/pi-manager.sh backup /path/to/backup.img.gz\n\n# Overclock profiles\nbash scripts/pi-manager.sh overclock show\nbash scripts/pi-manager.sh overclock mild # 1.8GHz\nbash scripts/pi-manager.sh overclock medium # 2.0GHz\n```\n\n## Monitoring Alerts\n\nSet up threshold-based alerts:\n\n```bash\n# Alert if temperature exceeds 75°C\nbash scripts/pi-manager.sh alert temp 75\n\n# Alert if disk usage exceeds 90%\nbash scripts/pi-manager.sh alert disk 90\n\n# Alert if a service goes down\nbash scripts/pi-manager.sh alert service nginx\n\n# All alerts — suitable for cron\nbash scripts/pi-manager.sh alert check\n```\n\nDesigned to be used standalone or as part of a larger IoT management workflow. Pair with `homeassistant-toolkit` for full smart home integration.\n---\n💬 Feedback & Feature Requests: https://bytesagain.com/feedback\nPowered by BytesAgain | bytesagain.com\n\n## Commands\n\nRun `raspberry-pi-manager help` to see all available commands.\n\nFile v2.3.5:_meta.json\n\n{\n \"ownerId\": \"kn76vqrf94wk924mddj8fp4p5x8497tb\",\n \"slug\": \"raspberry-pi-manager\",\n \"version\": \"2.3.5\",\n \"publishedAt\": 1773661679512\n}\n\nFile v2.3.5:tips.md\n\n# Tips for Raspberry Pi Manager\n\n## System Health\n\n1. **Keep the CPU temperature below 70°C.** Throttling starts at 80°C and significantly impacts performance. Use a heatsink + fan if running heavy workloads.\n\n2. **Monitor disk usage proactively.** SD cards fill up silently — logs, temp files, and package caches are common culprits. Set up a cron alert at 80%.\n\n3. **Use `--watch` mode for debugging performance issues.** Real-time CPU and memory monitoring helps identify spikes and memory leaks.\n\n4. **Log metrics to CSV** for long-term trend analysis. A weekly review of temperature and load patterns can prevent failures before they happen.\n\n## GPIO Best Practices\n\n- **Always double-check pin numbering.** BCM numbering (GPIO17) and physical pin numbering (pin 11) are different. The script uses BCM by default.\n- **Use pull-up/pull-down resistors** for input pins to avoid floating values\n- **Don't draw more than 16mA per GPIO pin** — use a transistor or relay for higher-power devices\n- **The `pinout` command** is your quick reference — no need to Google the diagram every time\n\n## Sensor Tips\n\n- **DHT22 > DHT11** for accuracy (±0.5°C vs ±2°C), but DHT11 is cheaper\n- **DS18B20** requires 1-Wire to be enabled: `sudo raspi-config` → Interface Options → 1-Wire\n- **BME280 via I2C** — enable I2C first: `sudo raspi-config` → Interface Options → I2C\n- **Log sensor data to CSV** and use `chart-generator` skill for visualization\n\n## Remote Management\n\n- **Set up SSH key authentication** — password auth over the internet is risky\n- **Use a reverse SSH tunnel or VPN** for remote access without port forwarding\n- **The `--fleet` mode** is powerful but runs commands sequentially — for large fleets, consider parallel execution with `xargs -P`\n\n## SD Card Longevity\n\n- **Use log2ram** to reduce SD card writes (logs stay in RAM, flushed periodically)\n- **Set `noatime` mount option** in `/etc/fstab` to reduce unnecessary writes\n- **Move heavy I/O to a USB drive** — databases, media, downloads\n- **Keep a backup image** — use the `backup` command monthly\n\n## Security Hardening\n\n- Change the default password immediately\n- Disable password-based SSH login\n- Keep the system updated: `bash scripts/pi-manager.sh update`\n- Disable unused services to reduce attack surface\n- Consider running `fail2ban` for SSH brute-force protection\n\n## Performance Tuning\n\n- **Overclock cautiously.** Start with \"mild\" and test stability under load before going higher.\n- **Disable the GUI** if running headless: saves ~200MB RAM\n- **Use zram** for swap instead of SD card swap — faster and reduces card wear\n- **64-bit OS** uses more RAM but gives access to >4GB on Pi 4/5\n\nArchive v2.3.4: 5 files, 11158 bytes\n\nFiles: scripts/rpi.sh (11809b), scripts/script.sh (7111b), SKILL.md (7563b), tips.md (2697b), _meta.json (139b)\n\nFile v2.3.4:SKILL.md\n\n---\nname: raspberry-pi-manager\ndescription: \"Manage Raspberry Pi devices — GPIO control, system monitoring (CPU/temp/memory), service management, sensor data reading, and remote deployment. Use when you need raspberry pi manager capabilities. Triggers on: raspberry pi manager.\"\n---\n\n# Raspberry Pi Manager\n\nA Swiss Army knife for Raspberry Pi administration. Whether you're running a single Pi as a home server or managing a fleet of IoT nodes, this toolkit gives you instant access to system stats, GPIO pins, services, sensors, and deployment workflows.\n\nThe script runs locally on the Pi or connects remotely via SSH. For local use, just execute the script directly. For remote management, configure SSH access.\n\n### Local Usage\n\n```bash\nbash scripts/pi-manager.sh system\nbash scripts/pi-manager.sh gpio read 17\n```\n\n### Remote Usage\n\n```bash\nexport PI_HOST=\"pi@192.168.1.200\"\nexport PI_SSH_KEY=\"~/.ssh/id_rsa\"\n\nbash scripts/pi-manager.sh --remote system\nbash scripts/pi-manager.sh --remote gpio read 17\n```\n\nMultiple Pi support:\n\n```bash\nexport PI_HOSTS=\"pi@node1.local,pi@node2.local,pi@node3.local\"\nbash scripts/pi-manager.sh --fleet system\n```\n\n## System Monitoring\n\nReal-time insight into your Pi's health.\n\n```bash\n# Full system dashboard\n$ bash scripts/pi-manager.sh system\n\n┌─ Raspberry Pi 4 Model B (4GB) ─────────────────────┐\n│ │\n│ CPU: 4× ARM Cortex-A72 @ 1.5GHz │\n│ Load: 0.42, 0.38, 0.31 │\n│ Temp: 48.3°C / 118.9°F [████░░░░░░ OK] │\n│ Memory: 1.2GB / 3.7GB [████████░░ 32%] │\n│ Disk: 12.4GB / 29.1GB [█████████░ 43%] │\n│ Swap: 0MB / 100MB [░░░░░░░░░░ 0%] │\n│ Uptime: 14 days, 7:23:41 │\n│ OS: Raspberry Pi OS (Bookworm) 64-bit │\n│ │\n│ Network: │\n│ eth0: 192.168.1.200 (1000 Mbps) │\n│ wlan0: 192.168.1.201 (72 Mbps, -42 dBm) │\n└──────────────────────────────────────────────────────┘\n```\n\n### Individual Metrics\n\n```bash\n# Temperature with threshold warning\nbash scripts/pi-manager.sh temp\nbash scripts/pi-manager.sh temp --warn 70 --crit 80\n\n# CPU usage (snapshot or continuous)\nbash scripts/pi-manager.sh cpu\nbash scripts/pi-manager.sh cpu --watch 5 # Update every 5s\n\n# Memory breakdown\nbash scripts/pi-manager.sh memory\n\n# Disk usage by mount point\nbash scripts/pi-manager.sh disk\n\n# Network interfaces and traffic\nbash scripts/pi-manager.sh network\n\n# Top processes by CPU/memory\nbash scripts/pi-manager.sh top 10\n```\n\n### Historical Data\n\n```bash\n# Log system metrics to CSV (for graphing)\nbash scripts/pi-manager.sh monitor --interval 60 --output metrics.csv\n\n# View logged metrics\nbash scripts/pi-manager.sh monitor --view metrics.csv --last 24h\n```\n\n## GPIO Control\n\nDirect pin manipulation for hardware projects.\n\n```bash\n# Pin layout reference\nbash scripts/pi-manager.sh gpio pinout\n\n# Read a pin state\nbash scripts/pi-manager.sh gpio read 17\n\n# Set pin output\nbash scripts/pi-manager.sh gpio write 17 high\nbash scripts/pi-manager.sh gpio write 17 low\n\n# Set pin mode\nbash scripts/pi-manager.sh gpio mode 17 output\nbash scripts/pi-manager.sh gpio mode 18 input --pull up\n\n# PWM output (hardware PWM on supported pins)\nbash scripts/pi-manager.sh gpio pwm 18 75 # 75% duty cycle\n\n# Watch pin for changes\nbash scripts/pi-manager.sh gpio watch 17 --edge both\n\n# Bulk operations\nbash scripts/pi-manager.sh gpio write 17,18,27,22 high\nbash scripts/pi-manager.sh gpio read 17,18,27,22\n\n# GPIO status overview\nbash scripts/pi-manager.sh gpio status\n```\n\n## Service Management\n\nControl systemd services running on the Pi.\n\n```bash\n# List all services (active, failed, inactive)\nbash scripts/pi-manager.sh service list\nbash scripts/pi-manager.sh service list --failed\n\n# Service operations\nbash scripts/pi-manager.sh service status nginx\nbash scripts/pi-manager.sh service start nginx\nbash scripts/pi-manager.sh service stop nginx\nbash scripts/pi-manager.sh service restart nginx\nbash scripts/pi-manager.sh service enable nginx\nbash scripts/pi-manager.sh service disable nginx\n\n# View service logs\nbash scripts/pi-manager.sh service logs nginx --lines 50\nbash scripts/pi-manager.sh service logs nginx --follow\n\n# Create a new service from a script\nbash scripts/pi-manager.sh service create my-app /home/pi/app/start.sh \\\n --description \"My Application\" \\\n --restart always \\\n --user pi\n```\n\n## Sensor Data\n\nRead common sensors connected to your Pi.\n\n```bash\n# DHT11/DHT22 temperature & humidity\nbash scripts/pi-manager.sh sensor dht22 4 # GPIO pin 4\n\n# DS18B20 temperature sensor (1-Wire)\nbash scripts/pi-manager.sh sensor ds18b20\n\n# BMP280/BME280 (I2C)\nbash scripts/pi-manager.sh sensor bme280\n\n# HC-SR04 ultrasonic distance\nbash scripts/pi-manager.sh sensor distance 23 24 # Trigger/Echo pins\n\n# PIR motion sensor\nbash scripts/pi-manager.sh sensor pir 17 --watch\n\n# Light sensor (analog via MCP3008 ADC)\nbash scripts/pi-manager.sh sensor light 0 # ADC channel 0\n\n# Log sensor readings\nbash scripts/pi-manager.sh sensor dht22 4 --log --interval 300 --output temp_log.csv\n```\n\n## Remote Deployment\n\nDeploy applications and configurations to your Pi.\n\n```bash\n# Copy files to Pi\nbash scripts/pi-manager.sh deploy push ./app/ /home/pi/app/\n\n# Pull files from Pi\nbash scripts/pi-manager.sh deploy pull /home/pi/logs/ ./local-logs/\n\n# Run a script on the Pi\nbash scripts/pi-manager.sh deploy exec ./setup.sh\n\n# Full deployment workflow\nbash scripts/pi-manager.sh deploy run ./deploy.yml\n```\n\n### Deploy manifest (`deploy.yml`):\n\n```yaml\ntarget: pi@192.168.1.200\nsteps:\n - copy: ./app/ → /home/pi/app/\n - run: cd /home/pi/app && pip3 install -r requirements.txt\n - run: sudo systemctl restart my-app\n - verify: curl -s http://localhost:8080/health\n```\n\n```bash\n# Fleet deployment\nbash scripts/pi-manager.sh --fleet deploy run ./deploy.yml\n# Deploys to all configured Pi hosts sequentially\n```\n\n## Maintenance\n\n```bash\n# System update\nbash scripts/pi-manager.sh update\n\n# Firmware update check\nbash scripts/pi-manager.sh firmware\n\n# Reboot / shutdown\nbash scripts/pi-manager.sh reboot\nbash scripts/pi-manager.sh shutdown\n\n# Backup SD card (creates compressed image)\nbash scripts/pi-manager.sh backup /path/to/backup.img.gz\n\n# Overclock profiles\nbash scripts/pi-manager.sh overclock show\nbash scripts/pi-manager.sh overclock mild # 1.8GHz\nbash scripts/pi-manager.sh overclock medium # 2.0GHz\n```\n\n## Monitoring Alerts\n\nSet up threshold-based alerts:\n\n```bash\n# Alert if temperature exceeds 75°C\nbash scripts/pi-manager.sh alert temp 75\n\n# Alert if disk usage exceeds 90%\nbash scripts/pi-manager.sh alert disk 90\n\n# Alert if a service goes down\nbash scripts/pi-manager.sh alert service nginx\n\n# All alerts — suitable for cron\nbash scripts/pi-manager.sh alert check\n```\n\nDesigned to be used standalone or as part of a larger IoT management workflow. Pair with `homeassistant-toolkit` for full smart home integration.\n---\n💬 Feedback & Feature Requests: https://bytesagain.com/feedback\nPowered by BytesAgain | bytesagain.com\n\n## Commands\n\nRun `raspberry-pi-manager help` to see all available commands.\n\nFile v2.3.4:_meta.json\n\n{\n \"ownerId\": \"kn76vqrf94wk924mddj8fp4p5x8497tb\",\n \"slug\": \"raspberry-pi-manager\",\n \"version\": \"2.3.4\",\n \"publishedAt\": 1773614396160\n}\n\nFile v2.3.4:tips.md\n\n# Tips for Raspberry Pi Manager\n\n## System Health\n\n1. **Keep the CPU temperature below 70°C.** Throttling starts at 80°C and significantly impacts performance. Use a heatsink + fan if running heavy workloads.\n\n2. **Monitor disk usage proactively.** SD cards fill up silently — logs, temp files, and package caches are common culprits. Set up a cron alert at 80%.\n\n3. **Use `--watch` mode for debugging performance issues.** Real-time CPU and memory monitoring helps identify spikes and memory leaks.\n\n4. **Log metrics to CSV** for long-term trend analysis. A weekly review of temperature and load patterns can prevent failures before they happen.\n\n## GPIO Best Practices\n\n- **Always double-check pin numbering.** BCM numbering (GPIO17) and physical pin numbering (pin 11) are different. The script uses BCM by default.\n- **Use pull-up/pull-down resistors** for input pins to avoid floating values\n- **Don't draw more than 16mA per GPIO pin** — use a transistor or relay for higher-power devices\n- **The `pinout` command** is your quick reference — no need to Google the diagram every time\n\n## Sensor Tips\n\n- **DHT22 > DHT11** for accuracy (±0.5°C vs ±2°C), but DHT11 is cheaper\n- **DS18B20** requires 1-Wire to be enabled: `sudo raspi-config` → Interface Options → 1-Wire\n- **BME280 via I2C** — enable I2C first: `sudo raspi-config` → Interface Options → I2C\n- **Log sensor data to CSV** and use `chart-generator` skill for visualization\n\n## Remote Management\n\n- **Set up SSH key authentication** — password auth over the internet is risky\n- **Use a reverse SSH tunnel or VPN** for remote access without port forwarding\n- **The `--fleet` mode** is powerful but runs commands sequentially — for large fleets, consider parallel execution with `xargs -P`\n\n## SD Card Longevity\n\n- **Use log2ram** to reduce SD card writes (logs stay in RAM, flushed periodically)\n- **Set `noatime` mount option** in `/etc/fstab` to reduce unnecessary writes\n- **Move heavy I/O to a USB drive** — databases, media, downloads\n- **Keep a backup image** — use the `backup` command monthly\n\n## Security Hardening\n\n- Change the default password immediately\n- Disable password-based SSH login\n- Keep the system updated: `bash scripts/pi-manager.sh update`\n- Disable unused services to reduce attack surface\n- Consider running `fail2ban` for SSH brute-force protection\n\n## Performance Tuning\n\n- **Overclock cautiously.** Start with \"mild\" and test stability under load before going higher.\n- **Disable the GUI** if running headless: saves ~200MB RAM\n- **Use zram** for swap instead of SD card swap — faster and reduces card wear\n- **64-bit OS** uses more RAM but gives access to >4GB on Pi 4/5\n\nArchive v2.3.3: 5 files, 11158 bytes\n\nFiles: scripts/rpi.sh (11809b), scripts/script.sh (7111b), SKILL.md (7563b), tips.md (2697b), _meta.json (139b)\n\nFile v2.3.3:SKILL.md\n\n---\nname: raspberry-pi-manager\ndescription: \"Manage Raspberry Pi devices — GPIO control, system monitoring (CPU/temp/memory), service management, sensor data reading, and remote deployment. Use when you need raspberry pi manager capabilities. Triggers on: raspberry pi manager.\"\n---\n\n# Raspberry Pi Manager\n\nA Swiss Army knife for Raspberry Pi administration. Whether you're running a single Pi as a home server or managing a fleet of IoT nodes, this toolkit gives you instant access to system stats, GPIO pins, services, sensors, and deployment workflows.\n\nThe script runs locally on the Pi or connects remotely via SSH. For local use, just execute the script directly. For remote management, configure SSH access.\n\n### Local Usage\n\n```bash\nbash scripts/pi-manager.sh system\nbash scripts/pi-manager.sh gpio read 17\n```\n\n### Remote Usage\n\n```bash\nexport PI_HOST=\"pi@192.168.1.200\"\nexport PI_SSH_KEY=\"~/.ssh/id_rsa\"\n\nbash scripts/pi-manager.sh --remote system\nbash scripts/pi-manager.sh --remote gpio read 17\n```\n\nMultiple Pi support:\n\n```bash\nexport PI_HOSTS=\"pi@node1.local,pi@node2.local,pi@node3.local\"\nbash scripts/pi-manager.sh --fleet system\n```\n\n## System Monitoring\n\nReal-time insight into your Pi's health.\n\n```bash\n# Full system dashboard\n$ bash scripts/pi-manager.sh system\n\n┌─ Raspberry Pi 4 Model B (4GB) ─────────────────────┐\n│ │\n│ CPU: 4× ARM Cortex-A72 @ 1.5GHz │\n│ Load: 0.42, 0.38, 0.31 │\n│ Temp: 48.3°C / 118.9°F [████░░░░░░ OK] │\n│ Memory: 1.2GB / 3.7GB [████████░░ 32%] │\n│ Disk: 12.4GB / 29.1GB [█████████░ 43%] │\n│ Swap: 0MB / 100MB [░░░░░░░░░░ 0%] │\n│ Uptime: 14 days, 7:23:41 │\n│ OS: Raspberry Pi OS (Bookworm) 64-bit │\n│ │\n│ Network: │\n│ eth0: 192.168.1.200 (1000 Mbps) │\n│ wlan0: 192.168.1.201 (72 Mbps, -42 dBm) │\n└──────────────────────────────────────────────────────┘\n```\n\n### Individual Metrics\n\n```bash\n# Temperature with threshold warning\nbash scripts/pi-manager.sh temp\nbash scripts/pi-manager.sh temp --warn 70 --crit 80\n\n# CPU usage (snapshot or continuous)\nbash scripts/pi-manager.sh cpu\nbash scripts/pi-manager.sh cpu --watch 5 # Update every 5s\n\n# Memory breakdown\nbash scripts/pi-manager.sh memory\n\n# Disk usage by mount point\nbash scripts/pi-manager.sh disk\n\n# Network interfaces and traffic\nbash scripts/pi-manager.sh network\n\n# Top processes by CPU/memory\nbash scripts/pi-manager.sh top 10\n```\n\n### Historical Data\n\n```bash\n# Log system metrics to CSV (for graphing)\nbash scripts/pi-manager.sh monitor --interval 60 --output metrics.csv\n\n# View logged metrics\nbash scripts/pi-manager.sh monitor --view metrics.csv --last 24h\n```\n\n## GPIO Control\n\nDirect pin manipulation for hardware projects.\n\n```bash\n# Pin layout reference\nbash scripts/pi-manager.sh gpio pinout\n\n# Read a pin state\nbash scripts/pi-manager.sh gpio read 17\n\n# Set pin output\nbash scripts/pi-manager.sh gpio write 17 high\nbash scripts/pi-manager.sh gpio write 17 low\n\n# Set pin mode\nbash scripts/pi-manager.sh gpio mode 17 output\nbash scripts/pi-manager.sh gpio mode 18 input --pull up\n\n# PWM output (hardware PWM on supported pins)\nbash scripts/pi-manager.sh gpio pwm 18 75 # 75% duty cycle\n\n# Watch pin for changes\nbash scripts/pi-manager.sh gpio watch 17 --edge both\n\n# Bulk operations\nbash scripts/pi-manager.sh gpio write 17,18,27,22 high\nbash scripts/pi-manager.sh gpio read 17,18,27,22\n\n# GPIO status overview\nbash scripts/pi-manager.sh gpio status\n```\n\n## Service Management\n\nControl systemd services running on the Pi.\n\n```bash\n# List all services (active, failed, inactive)\nbash scripts/pi-manager.sh service list\nbash scripts/pi-manager.sh service list --failed\n\n# Service operations\nbash scripts/pi-manager.sh service status nginx\nbash scripts/pi-manager.sh service start nginx\nbash scripts/pi-manager.sh service stop nginx\nbash scripts/pi-manager.sh service restart nginx\nbash scripts/pi-manager.sh service enable nginx\nbash scripts/pi-manager.sh service disable nginx\n\n# View service logs\nbash scripts/pi-manager.sh service logs nginx --lines 50\nbash scripts/pi-manager.sh service logs nginx --follow\n\n# Create a new service from a script\nbash scripts/pi-manager.sh service create my-app /home/pi/app/start.sh \\\n --description \"My Application\" \\\n --restart always \\\n --user pi\n```\n\n## Sensor Data\n\nRead common sensors connected to your Pi.\n\n```bash\n# DHT11/DHT22 temperature & humidity\nbash scripts/pi-manager.sh sensor dht22 4 # GPIO pin 4\n\n# DS18B20 temperature sensor (1-Wire)\nbash scripts/pi-manager.sh sensor ds18b20\n\n# BMP280/BME280 (I2C)\nbash scripts/pi-manager.sh sensor bme280\n\n# HC-SR04 ultrasonic distance\nbash scripts/pi-manager.sh sensor distance 23 24 # Trigger/Echo pins\n\n# PIR motion sensor\nbash scripts/pi-manager.sh sensor pir 17 --watch\n\n# Light sensor (analog via MCP3008 ADC)\nbash scripts/pi-manager.sh sensor light 0 # ADC channel 0\n\n# Log sensor readings\nbash scripts/pi-manager.sh sensor dht22 4 --log --interval 300 --output temp_log.csv\n```\n\n## Remote Deployment\n\nDeploy applications and configurations to your Pi.\n\n```bash\n# Copy files to Pi\nbash scripts/pi-manager.sh deploy push ./app/ /home/pi/app/\n\n# Pull files from Pi\nbash scripts/pi-manager.sh deploy pull /home/pi/logs/ ./local-logs/\n\n# Run a script on the Pi\nbash scripts/pi-manager.sh deploy exec ./setup.sh\n\n# Full deployment workflow\nbash scripts/pi-manager.sh deploy run ./deploy.yml\n```\n\n### Deploy manifest (`deploy.yml`):\n\n```yaml\ntarget: pi@192.168.1.200\nsteps:\n - copy: ./app/ → /home/pi/app/\n - run: cd /home/pi/app && pip3 install -r requirements.txt\n - run: sudo systemctl restart my-app\n - verify: curl -s http://localhost:8080/health\n```\n\n```bash\n# Fleet deployment\nbash scripts/pi-manager.sh --fleet deploy run ./deploy.yml\n# Deploys to all configured Pi hosts sequentially\n```\n\n## Maintenance\n\n```bash\n# System update\nbash scripts/pi-manager.sh update\n\n# Firmware update check\nbash scripts/pi-manager.sh firmware\n\n# Reboot / shutdown\nbash scripts/pi-manager.sh reboot\nbash scripts/pi-manager.sh shutdown\n\n# Backup SD card (creates compressed image)\nbash scripts/pi-manager.sh backup /path/to/backup.img.gz\n\n# Overclock profiles\nbash scripts/pi-manager.sh overclock show\nbash scripts/pi-manager.sh overclock mild # 1.8GHz\nbash scripts/pi-manager.sh overclock medium # 2.0GHz\n```\n\n## Monitoring Alerts\n\nSet up threshold-based alerts:\n\n```bash\n# Alert if temperature exceeds 75°C\nbash scripts/pi-manager.sh alert temp 75\n\n# Alert if disk usage exceeds 90%\nbash scripts/pi-manager.sh alert disk 90\n\n# Alert if a service goes down\nbash scripts/pi-manager.sh alert service nginx\n\n# All alerts — suitable for cron\nbash scripts/pi-manager.sh alert check\n```\n\nDesigned to be used standalone or as part of a larger IoT management workflow. Pair with `homeassistant-toolkit` for full smart home integration.\n---\n💬 Feedback & Feature Requests: https://bytesagain.com/feedback\nPowered by BytesAgain | bytesagain.com\n\n## Commands\n\nRun `raspberry-pi-manager help` to see all available commands.\n\nFile v2.3.3:_meta.json\n\n{\n \"ownerId\": \"kn76vqrf94wk924mddj8fp4p5x8497tb\",\n \"slug\": \"raspberry-pi-manager\",\n \"version\": \"2.3.3\",\n \"publishedAt\": 1773611666956\n}\n\nFile v2.3.3:tips.md\n\n# Tips for Raspberry Pi Manager\n\n## System Health\n\n1. **Keep the CPU temperature below 70°C.** Throttling starts at 80°C and significantly impacts performance. Use a heatsink + fan if running heavy workloads.\n\n2. **Monitor disk usage proactively.** SD cards fill up silently — logs, temp files, and package caches are common culprits. Set up a cron alert at 80%.\n\n3. **Use `--watch` mode for debugging performance issues.** Real-time CPU and memory monitoring helps identify spikes and memory leaks.\n\n4. **Log metrics to CSV** for long-term trend analysis. A weekly review of temperature and load patterns can prevent failures before they happen.\n\n## GPIO Best Practices\n\n- **Always double-check pin numbering.** BCM numbering (GPIO17) and physical pin numbering (pin 11) are different. The script uses BCM by default.\n- **Use pull-up/pull-down resistors** for input pins to avoid floating values\n- **Don't draw more than 16mA per GPIO pin** — use a transistor or relay for higher-power devices\n- **The `pinout` command** is your quick reference — no need to Google the diagram every time\n\n## Sensor Tips\n\n- **DHT22 > DHT11** for accuracy (±0.5°C vs ±2°C), but DHT11 is cheaper\n- **DS18B20** requires 1-Wire to be enabled: `sudo raspi-config` → Interface Options → 1-Wire\n- **BME280 via I2C** — enable I2C first: `sudo raspi-config` → Interface Options → I2C\n- **Log sensor data to CSV** and use `chart-generator` skill for visualization\n\n## Remote Management\n\n- **Set up SSH key authentication** — password auth over the internet is risky\n- **Use a reverse SSH tunnel or VPN** for remote access without port forwarding\n- **The `--fleet` mode** is powerful but runs commands sequentially — for large fleets, consider parallel execution with `xargs -P`\n\n## SD Card Longevity\n\n- **Use log2ram** to reduce SD card writes (logs stay in RAM, flushed periodically)\n- **Set `noatime` mount option** in `/etc/fstab` to reduce unnecessary writes\n- **Move heavy I/O to a USB drive** — databases, media, downloads\n- **Keep a backup image** — use the `backup` command monthly\n\n## Security Hardening\n\n- Change the default password immediately\n- Disable password-based SSH login\n- Keep the system updated: `bash scripts/pi-manager.sh update`\n- Disable unused services to reduce attack surface\n- Consider running `fail2ban` for SSH brute-force protection\n\n## Performance Tuning\n\n- **Overclock cautiously.** Start with \"mild\" and test stability under load before going higher.\n- **Disable the GUI** if running headless: saves ~200MB RAM\n- **Use zram** for swap instead of SD card swap — faster and reduces card wear\n- **64-bit OS** uses more RAM but gives access to >4GB on Pi 4/5\n\nArchive v2.3.2: 5 files, 9322 bytes\n\nFiles: scripts/rpi.sh (11809b), scripts/script.sh (681b), SKILL.md (7563b), tips.md (2697b), _meta.json (139b)\n\nFile v2.3.2:SKILL.md\n\n---\nname: raspberry-pi-manager\ndescription: \"Manage Raspberry Pi devices — GPIO control, system monitoring (CPU/temp/memory), service management, sensor data reading, and remote deployment. Use when you need raspberry pi manager capabilities. Triggers on: raspberry pi manager.\"\n---\n\n# Raspberry Pi Manager\n\nA Swiss Army knife for Raspberry Pi administration. Whether you're running a single Pi as a home server or managing a fleet of IoT nodes, this toolkit gives you instant access to system stats, GPIO pins, services, sensors, and deployment workflows.\n\nThe script runs locally on the Pi or connects remotely via SSH. For local use, just execute the script directly. For remote management, configure SSH access.\n\n### Local Usage\n\n```bash\nbash scripts/pi-manager.sh system\nbash scripts/pi-manager.sh gpio read 17\n```\n\n### Remote Usage\n\n```bash\nexport PI_HOST=\"pi@192.168.1.200\"\nexport PI_SSH_KEY=\"~/.ssh/id_rsa\"\n\nbash scripts/pi-manager.sh --remote system\nbash scripts/pi-manager.sh --remote gpio read 17\n```\n\nMultiple Pi support:\n\n```bash\nexport PI_HOSTS=\"pi@node1.local,pi@node2.local,pi@node3.local\"\nbash scripts/pi-manager.sh --fleet system\n```\n\n## System Monitoring\n\nReal-time insight into your Pi's health.\n\n```bash\n# Full system dashboard\n$ bash scripts/pi-manager.sh system\n\n┌─ Raspberry Pi 4 Model B (4GB) ─────────────────────┐\n│ │\n│ CPU: 4× ARM Cortex-A72 @ 1.5GHz │\n│ Load: 0.42, 0.38, 0.31 │\n│ Temp: 48.3°C / 118.9°F [████░░░░░░ OK] │\n│ Memory: 1.2GB / 3.7GB [████████░░ 32%] │\n│ Disk: 12.4GB / 29.1GB [█████████░ 43%] │\n│ Swap: 0MB / 100MB [░░░░░░░░░░ 0%] │\n│ Uptime: 14 days, 7:23:41 │\n│ OS: Raspberry Pi OS (Bookworm) 64-bit │\n│ │\n│ Network: │\n│ eth0: 192.168.1.200 (1000 Mbps) │\n│ wlan0: 192.168.1.201 (72 Mbps, -42 dBm) │\n└──────────────────────────────────────────────────────┘\n```\n\n### Individual Metrics\n\n```bash\n# Temperature with threshold warning\nbash scripts/pi-manager.sh temp\nbash scripts/pi-manager.sh temp --warn 70 --crit 80\n\n# CPU usage (snapshot or continuous)\nbash scripts/pi-manager.sh cpu\nbash scripts/pi-manager.sh cpu --watch 5 # Update every 5s\n\n# Memory breakdown\nbash scripts/pi-manager.sh memory\n\n# Disk usage by mount point\nbash scripts/pi-manager.sh disk\n\n# Network interfaces and traffic\nbash scripts/pi-manager.sh network\n\n# Top processes by CPU/memory\nbash scripts/pi-manager.sh top 10\n```\n\n### Historical Data\n\n```bash\n# Log system metrics to CSV (for graphing)\nbash scripts/pi-manager.sh monitor --interval 60 --output metrics.csv\n\n# View logged metrics\nbash scripts/pi-manager.sh monitor --view metrics.csv --last 24h\n```\n\n## GPIO Control\n\nDirect pin manipulation for hardware projects.\n\n```bash\n# Pin layout reference\nbash scripts/pi-manager.sh gpio pinout\n\n# Read a pin state\nbash scripts/pi-manager.sh gpio read 17\n\n# Set pin output\nbash scripts/pi-manager.sh gpio write 17 high\nbash scripts/pi-manager.sh gpio write 17 low\n\n# Set pin mode\nbash scripts/pi-manager.sh gpio mode 17 output\nbash scripts/pi-manager.sh gpio mode 18 input --pull up\n\n# PWM output (hardware PWM on supported pins)\nbash scripts/pi-manager.sh gpio pwm 18 75 # 75% duty cycle\n\n# Watch pin for changes\nbash scripts/pi-manager.sh gpio watch 17 --edge both\n\n# Bulk operations\nbash scripts/pi-manager.sh gpio write 17,18,27,22 high\nbash scripts/pi-manager.sh gpio read 17,18,27,22\n\n# GPIO status overview\nbash scripts/pi-manager.sh gpio status\n```\n\n## Service Management\n\nControl systemd services running on the Pi.\n\n```bash\n# List all services (active, failed, inactive)\nbash scripts/pi-manager.sh service list\nbash scripts/pi-manager.sh service list --failed\n\n# Service operations\nbash scripts/pi-manager.sh service status nginx\nbash scripts/pi-manager.sh service start nginx\nbash scripts/pi-manager.sh service stop nginx\nbash scripts/pi-manager.sh service restart nginx\nbash scripts/pi-manager.sh service enable nginx\nbash scripts/pi-manager.sh service disable nginx\n\n# View service logs\nbash scripts/pi-manager.sh service logs nginx --lines 50\nbash scripts/pi-manager.sh service logs nginx --follow\n\n# Create a new service from a script\nbash scripts/pi-manager.sh service create my-app /home/pi/app/start.sh \\\n --description \"My Application\" \\\n --restart always \\\n --user pi\n```\n\n## Sensor Data\n\nRead common sensors connected to your Pi.\n\n```bash\n# DHT11/DHT22 temperature & humidity\nbash scripts/pi-manager.sh sensor dht22 4 # GPIO pin 4\n\n# DS18B20 temperature sensor (1-Wire)\nbash scripts/pi-manager.sh sensor ds18b20\n\n# BMP280/BME280 (I2C)\nbash scripts/pi-manager.sh sensor bme280\n\n# HC-SR04 ultrasonic distance\nbash scripts/pi-manager.sh sensor distance 23 24 # Trigger/Echo pins\n\n# PIR motion sensor\nbash scripts/pi-manager.sh sensor pir 17 --watch\n\n# Light sensor (analog via MCP3008 ADC)\nbash scripts/pi-manager.sh sensor light 0 # ADC channel 0\n\n# Log sensor readings\nbash scripts/pi-manager.sh sensor dht22 4 --log --interval 300 --output temp_log.csv\n```\n\n## Remote Deployment\n\nDeploy applications and configurations to your Pi.\n\n```bash\n# Copy files to Pi\nbash scripts/pi-manager.sh deploy push ./app/ /home/pi/app/\n\n# Pull files from Pi\nbash scripts/pi-manager.sh deploy pull /home/pi/logs/ ./local-logs/\n\n# Run a script on the Pi\nbash scripts/pi-manager.sh deploy exec ./setup.sh\n\n# Full deployment workflow\nbash scripts/pi-manager.sh deploy run ./deploy.yml\n```\n\n### Deploy manifest (`deploy.yml`):\n\n```yaml\ntarget: pi@192.168.1.200\nsteps:\n - copy: ./app/ → /home/pi/app/\n - run: cd /home/pi/app && pip3 install -r requirements.txt\n - run: sudo systemctl restart my-app\n - verify: curl -s http://localhost:8080/health\n```\n\n```bash\n# Fleet deployment\nbash scripts/pi-manager.sh --fleet deploy run ./deploy.yml\n# Deploys to all configured Pi hosts sequentially\n```\n\n## Maintenance\n\n```bash\n# System update\nbash scripts/pi-manager.sh update\n\n# Firmware update check\nbash scripts/pi-manager.sh firmware\n\n# Reboot / shutdown\nbash scripts/pi-manager.sh reboot\nbash scripts/pi-manager.sh shutdown\n\n# Backup SD card (creates compressed image)\nbash scripts/pi-manager.sh backup /path/to/backup.img.gz\n\n# Overclock profiles\nbash scripts/pi-manager.sh overclock show\nbash scripts/pi-manager.sh overclock mild # 1.8GHz\nbash scripts/pi-manager.sh overclock medium # 2.0GHz\n```\n\n## Monitoring Alerts\n\nSet up threshold-based alerts:\n\n```bash\n# Alert if temperature exceeds 75°C\nbash scripts/pi-manager.sh alert temp 75\n\n# Alert if disk usage exceeds 90%\nbash scripts/pi-manager.sh alert disk 90\n\n# Alert if a service goes down\nbash scripts/pi-manager.sh alert service nginx\n\n# All alerts — suitable for cron\nbash scripts/pi-manager.sh alert check\n```\n\nDesigned to be used standalone or as part of a larger IoT management workflow. Pair with `homeassistant-toolkit` for full smart home integration.\n---\n💬 Feedback & Feature Requests: https://bytesagain.com/feedback\nPowered by BytesAgain | bytesagain.com\n\n## Commands\n\nRun `raspberry-pi-manager help` to see all available commands.\n\nFile v2.3.2:_meta.json\n\n{\n \"ownerId\": \"kn76vqrf94wk924mddj8fp4p5x8497tb\",\n \"slug\": \"raspberry-pi-manager\",\n \"version\": \"2.3.2\",\n \"publishedAt\": 1773578657200\n}\n\nFile v2.3.2:tips.md\n\n# Tips for Raspberry Pi Manager\n\n## System Health\n\n1. **Keep the CPU temperature below 70°C.** Throttling starts at 80°C and significantly impacts performance. Use a heatsink + fan if running heavy workloads.\n\n2. **Monitor disk usage proactively.** SD cards fill up silently — logs, temp files, and package caches are common culprits. Set up a cron alert at 80%.\n\n3. **Use `--watch` mode for debugging performance issues.** Real-time CPU and memory monitoring helps identify spikes and memory leaks.\n\n4. **Log metrics to CSV** for long-term trend analysis. A weekly review of temperature and load patterns can prevent failures before they happen.\n\n## GPIO Best Practices\n\n- **Always double-check pin numbering.** BCM numbering (GPIO17) and physical pin numbering (pin 11) are different. The script uses BCM by default.\n- **Use pull-up/pull-down resistors** for input pins to avoid floating values\n- **Don't draw more than 16mA per GPIO pin** — use a transistor or relay for higher-power devices\n- **The `pinout` command** is your quick reference — no need to Google the diagram every time\n\n## Sensor Tips\n\n- **DHT22 > DHT11** for accuracy (±0.5°C vs ±2°C), but DHT11 is cheaper\n- **DS18B20** requires 1-Wire to be enabled: `sudo raspi-config` → Interface Options → 1-Wire\n- **BME280 via I2C** — enable I2C first: `sudo raspi-config` → Interface Options → I2C\n- **Log sensor data to CSV** and use `chart-generator` skill for visualization\n\n## Remote Management\n\n- **Set up SSH key authentication** — password auth over the internet is risky\n- **Use a reverse SSH tunnel or VPN** for remote access without port forwarding\n- **The `--fleet` mode** is powerful but runs commands sequentially — for large fleets, consider parallel execution with `xargs -P`\n\n## SD Card Longevity\n\n- **Use log2ram** to reduce SD card writes (logs stay in RAM, flushed periodically)\n- **Set `noatime` mount option** in `/etc/fstab` to reduce unnecessary writes\n- **Move heavy I/O to a USB drive** — databases, media, downloads\n- **Keep a backup image** — use the `backup` command monthly\n\n## Security Hardening\n\n- Change the default password immediately\n- Disable password-based SSH login\n- Keep the system updated: `bash scripts/pi-manager.sh update`\n- Disable unused services to reduce attack surface\n- Consider running `fail2ban` for SSH brute-force protection\n\n## Performance Tuning\n\n- **Overclock cautiously.** Start with \"mild\" and test stability under load before going higher.\n- **Disable the GUI** if running headless: saves ~200MB RAM\n- **Use zram** for swap instead of SD card swap — faster and reduces card wear\n- **64-bit OS** uses more RAM but gives access to >4GB on Pi 4/5\n\nArchive v2.3.1: 4 files, 8840 bytes\n\nFiles: scripts/rpi.sh (11809b), SKILL.md (7580b), tips.md (2697b), _meta.json (139b)\n\nFile v2.3.1:SKILL.md\n\n---\nname: raspberry-pi-manager\ndescription: \"Manage Raspberry Pi devices — GPIO control, system monitoring (CPU/temp/memory), service management, sensor data reading, and remote deployment. Use when you need raspberry pi manager capabilities. Triggers on: raspberry pi manager.\"\n---\n\n# Raspberry Pi Manager\n\nA Swiss Army knife for Raspberry Pi administration. Whether you're running a single Pi as a home server or managing a fleet of IoT nodes, this toolkit gives you instant access to system stats, GPIO pins, services, sensors, and deployment workflows.\n\n## How It Works\n\nThe script runs locally on the Pi or connects remotely via SSH. For local use, just execute the script directly. For remote management, configure SSH access.\n\n### Local Usage\n\n```bash\nbash scripts/pi-manager.sh system\nbash scripts/pi-manager.sh gpio read 17\n```\n\n### Remote Usage\n\n```bash\nexport PI_HOST=\"pi@192.168.1.200\"\nexport PI_SSH_KEY=\"~/.ssh/id_rsa\"\n\nbash scripts/pi-manager.sh --remote system\nbash scripts/pi-manager.sh --remote gpio read 17\n```\n\nMultiple Pi support:\n\n```bash\nexport PI_HOSTS=\"pi@node1.local,pi@node2.local,pi@node3.local\"\nbash scripts/pi-manager.sh --fleet system\n```\n\n## System Monitoring\n\nReal-time insight into your Pi's health.\n\n```bash\n# Full system dashboard\n$ bash scripts/pi-manager.sh system\n\n┌─ Raspberry Pi 4 Model B (4GB) ─────────────────────┐\n│ │\n│ CPU: 4× ARM Cortex-A72 @ 1.5GHz │\n│ Load: 0.42, 0.38, 0.31 │\n│ Temp: 48.3°C / 118.9°F [████░░░░░░ OK] │\n│ Memory: 1.2GB / 3.7GB [████████░░ 32%] │\n│ Disk: 12.4GB / 29.1GB [█████████░ 43%] │\n│ Swap: 0MB / 100MB [░░░░░░░░░░ 0%] │\n│ Uptime: 14 days, 7:23:41 │\n│ OS: Raspberry Pi OS (Bookworm) 64-bit │\n│ │\n│ Network: │\n│ eth0: 192.168.1.200 (1000 Mbps) │\n│ wlan0: 192.168.1.201 (72 Mbps, -42 dBm) │\n└──────────────────────────────────────────────────────┘\n```\n\n### Individual Metrics\n\n```bash\n# Temperature with threshold warning\nbash scripts/pi-manager.sh temp\nbash scripts/pi-manager.sh temp --warn 70 --crit 80\n\n# CPU usage (snapshot or continuous)\nbash scripts/pi-manager.sh cpu\nbash scripts/pi-manager.sh cpu --watch 5 # Update every 5s\n\n# Memory breakdown\nbash scripts/pi-manager.sh memory\n\n# Disk usage by mount point\nbash scripts/pi-manager.sh disk\n\n# Network interfaces and traffic\nbash scripts/pi-manager.sh network\n\n# Top processes by CPU/memory\nbash scripts/pi-manager.sh top 10\n```\n\n### Historical Data\n\n```bash\n# Log system metrics to CSV (for graphing)\nbash scripts/pi-manager.sh monitor --interval 60 --output metrics.csv\n\n# View logged metrics\nbash scripts/pi-manager.sh monitor --view metrics.csv --last 24h\n```\n\n## GPIO Control\n\nDirect pin manipulation for hardware projects.\n\n```bash\n# Pin layout reference\nbash scripts/pi-manager.sh gpio pinout\n\n# Read a pin state\nbash scripts/pi-manager.sh gpio read 17\n\n# Set pin output\nbash scripts/pi-manager.sh gpio write 17 high\nbash scripts/pi-manager.sh gpio write 17 low\n\n# Set pin mode\nbash scripts/pi-manager.sh gpio mode 17 output\nbash scripts/pi-manager.sh gpio mode 18 input --pull up\n\n# PWM output (hardware PWM on supported pins)\nbash scripts/pi-manager.sh gpio pwm 18 75 # 75% duty cycle\n\n# Watch pin for changes\nbash scripts/pi-manager.sh gpio watch 17 --edge both\n\n# Bulk operations\nbash scripts/pi-manager.sh gpio write 17,18,27,22 high\nbash scripts/pi-manager.sh gpio read 17,18,27,22\n\n# GPIO status overview\nbash scripts/pi-manager.sh gpio status\n```\n\n## Service Management\n\nControl systemd services running on the Pi.\n\n```bash\n# List all services (active, failed, inactive)\nbash scripts/pi-manager.sh service list\nbash scripts/pi-manager.sh service list --failed\n\n# Service operations\nbash scripts/pi-manager.sh service status nginx\nbash scripts/pi-manager.sh service start nginx\nbash scripts/pi-manager.sh service stop nginx\nbash scripts/pi-manager.sh service restart nginx\nbash scripts/pi-manager.sh service enable nginx\nbash scripts/pi-manager.sh service disable nginx\n\n# View service logs\nbash scripts/pi-manager.sh service logs nginx --lines 50\nbash scripts/pi-manager.sh service logs nginx --follow\n\n# Create a new service from a script\nbash scripts/pi-manager.sh service create my-app /home/pi/app/start.sh \\\n --description \"My Application\" \\\n --restart always \\\n --user pi\n```\n\n## Sensor Data\n\nRead common sensors connected to your Pi.\n\n```bash\n# DHT11/DHT22 temperature & humidity\nbash scripts/pi-manager.sh sensor dht22 4 # GPIO pin 4\n\n# DS18B20 temperature sensor (1-Wire)\nbash scripts/pi-manager.sh sensor ds18b20\n\n# BMP280/BME280 (I2C)\nbash scripts/pi-manager.sh sensor bme280\n\n# HC-SR04 ultrasonic distance\nbash scripts/pi-manager.sh sensor distance 23 24 # Trigger/Echo pins\n\n# PIR motion sensor\nbash scripts/pi-manager.sh sensor pir 17 --watch\n\n# Light sensor (analog via MCP3008 ADC)\nbash scripts/pi-manager.sh sensor light 0 # ADC channel 0\n\n# Log sensor readings\nbash scripts/pi-manager.sh sensor dht22 4 --log --interval 300 --output temp_log.csv\n```\n\n## Remote Deployment\n\nDeploy applications and configurations to your Pi.\n\n```bash\n# Copy files to Pi\nbash scripts/pi-manager.sh deploy push ./app/ /home/pi/app/\n\n# Pull files from Pi\nbash scripts/pi-manager.sh deploy pull /home/pi/logs/ ./local-logs/\n\n# Run a script on the Pi\nbash scripts/pi-manager.sh deploy exec ./setup.sh\n\n# Full deployment workflow\nbash scripts/pi-manager.sh deploy run ./deploy.yml\n```\n\n### Deploy manifest (`deploy.yml`):\n\n```yaml\ntarget: pi@192.168.1.200\nsteps:\n - copy: ./app/ → /home/pi/app/\n - run: cd /home/pi/app && pip3 install -r requirements.txt\n - run: sudo systemctl restart my-app\n - verify: curl -s http://localhost:8080/health\n```\n\n```bash\n# Fleet deployment\nbash scripts/pi-manager.sh --fleet deploy run ./deploy.yml\n# Deploys to all configured Pi hosts sequentially\n```\n\n## Maintenance\n\n```bash\n# System update\nbash scripts/pi-manager.sh update\n\n# Firmware update check\nbash scripts/pi-manager.sh firmware\n\n# Reboot / shutdown\nbash scripts/pi-manager.sh reboot\nbash scripts/pi-manager.sh shutdown\n\n# Backup SD card (creates compressed image)\nbash scripts/pi-manager.sh backup /path/to/backup.img.gz\n\n# Overclock profiles\nbash scripts/pi-manager.sh overclock show\nbash scripts/pi-manager.sh overclock mild # 1.8GHz\nbash scripts/pi-manager.sh overclock medium # 2.0GHz\n```\n\n## Monitoring Alerts\n\nSet up threshold-based alerts:\n\n```bash\n# Alert if temperature exceeds 75°C\nbash scripts/pi-manager.sh alert temp 75\n\n# Alert if disk usage exceeds 90%\nbash scripts/pi-manager.sh alert disk 90\n\n# Alert if a service goes down\nbash scripts/pi-manager.sh alert service nginx\n\n# All alerts — suitable for cron\nbash scripts/pi-manager.sh alert check\n```\n\nDesigned to be used standalone or as part of a larger IoT management workflow. Pair with `homeassistant-toolkit` for full smart home integration.\n---\n💬 Feedback & Feature Requests: https://bytesagain.com/feedback\nPowered by BytesAgain | bytesagain.com\n\n## Commands\n\nRun `raspberry-pi-manager help` to see all available commands.\n\nFile v2.3.1:_meta.json\n\n{\n \"ownerId\": \"kn76vqrf94wk924mddj8fp4p5x8497tb\",\n \"slug\": \"raspberry-pi-manager\",\n \"version\": \"2.3.1\",\n \"publishedAt\": 1773539174714\n}\n\nFile v2.3.1:tips.md\n\n# Tips for Raspberry Pi Manager\n\n## System Health\n\n1. **Keep the CPU temperature below 70°C.** Throttling starts at 80°C and significantly impacts performance. Use a heatsink + fan if running heavy workloads.\n\n2. **Monitor disk usage proactively.** SD cards fill up silently — logs, temp files, and package caches are common culprits. Set up a cron alert at 80%.\n\n3. **Use `--watch` mode for debugging performance issues.** Real-time CPU and memory monitoring helps identify spikes and memory leaks.\n\n4. **Log metrics to CSV** for long-term trend analysis. A weekly review of temperature and load patterns can prevent failures before they happen.\n\n## GPIO Best Practices\n\n- **Always double-check pin numbering.** BCM numbering (GPIO17) and physical pin numbering (pin 11) are different. The script uses BCM by default.\n- **Use pull-up/pull-down resistors** for input pins to avoid floating values\n- **Don't draw more than 16mA per GPIO pin** — use a transistor or relay for higher-power devices\n- **The `pinout` command** is your quick reference — no need to Google the diagram every time\n\n## Sensor Tips\n\n- **DHT22 > DHT11** for accuracy (±0.5°C vs ±2°C), but DHT11 is cheaper\n- **DS18B20** requires 1-Wire to be enabled: `sudo raspi-config` → Interface Options → 1-Wire\n- **BME280 via I2C** — enable I2C first: `sudo raspi-config` → Interface Options → I2C\n- **Log sensor data to CSV** and use `chart-generator` skill for visualization\n\n## Remote Management\n\n- **Set up SSH key authentication** — password auth over the internet is risky\n- **Use a reverse SSH tunnel or VPN** for remote access without port forwarding\n- **The `--fleet` mode** is powerful but runs commands sequentially — for large fleets, consider parallel execution with `xargs -P`\n\n## SD Card Longevity\n\n- **Use log2ram** to reduce SD card writes (logs stay in RAM, flushed periodically)\n- **Set `noatime` mount option** in `/etc/fstab` to reduce unnecessary writes\n- **Move heavy I/O to a USB drive** — databases, media, downloads\n- **Keep a backup image** — use the `backup` command monthly\n\n## Security Hardening\n\n- Change the default password immediately\n- Disable password-based SSH login\n- Keep the system updated: `bash scripts/pi-manager.sh update`\n- Disable unused services to reduce attack surface\n- Consider running `fail2ban` for SSH brute-force protection\n\n## Performance Tuning\n\n- **Overclock cautiously.** Start with \"mild\" and test stability under load before going higher.\n- **Disable the GUI** if running headless: saves ~200MB RAM\n- **Use zram** for swap instead of SD card swap — faster and reduces card wear\n- **64-bit OS** uses more RAM but gives access to >4GB on Pi 4/5\n\nArchive v2.3.0: 4 files, 8802 bytes\n\nFiles: scripts/rpi.sh (11809b), SKILL.md (7503b), tips.md (2697b), _meta.json (139b)\n\nFile v2.3.0:SKILL.md\n\n---\nname: raspberry-pi-manager\ndescription: \"Manage Raspberry Pi devices — GPIO control, system monitoring (CPU/temp/memory), service management, sensor data reading, and remote deployment. Use when you need raspberry pi manager capabilities. Triggers on: raspberry pi manager.\"\n---\n\n# Raspberry Pi Manager\n\nA Swiss Army knife for Raspberry Pi administration. Whether you're running a single Pi as a home server or managing a fleet of IoT nodes, this toolkit gives you instant access to system stats, GPIO pins, services, sensors, and deployment workflows.\n\n## How It Works\n\nThe script runs locally on the Pi or connects remotely via SSH. For local use, just execute the script directly. For remote management, configure SSH access.\n\n### Local Usage\n\n```bash\nbash scripts/pi-manager.sh system\nbash scripts/pi-manager.sh gpio read 17\n```\n\n### Remote Usage\n\n```bash\nexport PI_HOST=\"pi@192.168.1.200\"\nexport PI_SSH_KEY=\"~/.ssh/id_rsa\"\n\nbash scripts/pi-manager.sh --remote system\nbash scripts/pi-manager.sh --remote gpio read 17\n```\n\nMultiple Pi support:\n\n```bash\nexport PI_HOSTS=\"pi@node1.local,pi@node2.local,pi@node3.local\"\nbash scripts/pi-manager.sh --fleet system\n```\n\n## System Monitoring\n\nReal-time insight into your Pi's health.\n\n```bash\n# Full system dashboard\n$ bash scripts/pi-manager.sh system\n\n┌─ Raspberry Pi 4 Model B (4GB) ─────────────────────┐\n│ │\n│ CPU: 4× ARM Cortex-A72 @ 1.5GHz │\n│ Load: 0.42, 0.38, 0.31 │\n│ Temp: 48.3°C / 118.9°F [████░░░░░░ OK] │\n│ Memory: 1.2GB / 3.7GB [████████░░ 32%] │\n│ Disk: 12.4GB / 29.1GB [█████████░ 43%] │\n│ Swap: 0MB / 100MB [░░░░░░░░░░ 0%] │\n│ Uptime: 14 days, 7:23:41 │\n│ OS: Raspberry Pi OS (Bookworm) 64-bit │\n│ │\n│ Network: │\n│ eth0: 192.168.1.200 (1000 Mbps) │\n│ wlan0: 192.168.1.201 (72 Mbps, -42 dBm) │\n└──────────────────────────────────────────────────────┘\n```\n\n### Individual Metrics\n\n```bash\n# Temperature with threshold warning\nbash scripts/pi-manager.sh temp\nbash scripts/pi-manager.sh temp --warn 70 --crit 80\n\n# CPU usage (snapshot or continuous)\nbash scripts/pi-manager.sh cpu\nbash scripts/pi-manager.sh cpu --watch 5 # Update every 5s\n\n# Memory breakdown\nbash scripts/pi-manager.sh memory\n\n# Disk usage by mount point\nbash scripts/pi-manager.sh disk\n\n# Network interfaces and traffic\nbash scripts/pi-manager.sh network\n\n# Top processes by CPU/memory\nbash scripts/pi-manager.sh top 10\n```\n\n### Historical Data\n\n```bash\n# Log system metrics to CSV (for graphing)\nbash scripts/pi-manager.sh monitor --interval 60 --output metrics.csv\n\n# View logged metrics\nbash scripts/pi-manager.sh monitor --view metrics.csv --last 24h\n```\n\n## GPIO Control\n\nDirect pin manipulation for hardware projects.\n\n```bash\n# Pin layout reference\nbash scripts/pi-manager.sh gpio pinout\n\n# Read a pin state\nbash scripts/pi-manager.sh gpio read 17\n\n# Set pin output\nbash scripts/pi-manager.sh gpio write 17 high\nbash scripts/pi-manager.sh gpio write 17 low\n\n# Set pin mode\nbash scripts/pi-manager.sh gpio mode 17 output\nbash scripts/pi-manager.sh gpio mode 18 input --pull up\n\n# PWM output (hardware PWM on supported pins)\nbash scripts/pi-manager.sh gpio pwm 18 75 # 75% duty cycle\n\n# Watch pin for changes\nbash scripts/pi-manager.sh gpio watch 17 --edge both\n\n# Bulk operations\nbash scripts/pi-manager.sh gpio write 17,18,27,22 high\nbash scripts/pi-manager.sh gpio read 17,18,27,22\n\n# GPIO status overview\nbash scripts/pi-manager.sh gpio status\n```\n\n## Service Management\n\nControl systemd services running on the Pi.\n\n```bash\n# List all services (active, failed, inactive)\nbash scripts/pi-manager.sh service list\nbash scripts/pi-manager.sh service list --failed\n\n# Service operations\nbash scripts/pi-manager.sh service status nginx\nbash scripts/pi-manager.sh service start nginx\nbash scripts/pi-manager.sh service stop nginx\nbash scripts/pi-manager.sh service restart nginx\nbash scripts/pi-manager.sh service enable nginx\nbash scripts/pi-manager.sh service disable nginx\n\n# View service logs\nbash scripts/pi-manager.sh service logs nginx --lines 50\nbash scripts/pi-manager.sh service logs nginx --follow\n\n# Create a new service from a script\nbash scripts/pi-manager.sh service create my-app /home/pi/app/start.sh \\\n --description \"My Application\" \\\n --restart always \\\n --user pi\n```\n\n## Sensor Data\n\nRead common sensors connected to your Pi.\n\n```bash\n# DHT11/DHT22 temperature & humidity\nbash scripts/pi-manager.sh sensor dht22 4 # GPIO pin 4\n\n# DS18B20 temperature sensor (1-Wire)\nbash scripts/pi-manager.sh sensor ds18b20\n\n# BMP280/BME280 (I2C)\nbash scripts/pi-manager.sh sensor bme280\n\n# HC-SR04 ultrasonic distance\nbash scripts/pi-manager.sh sensor distance 23 24 # Trigger/Echo pins\n\n# PIR motion sensor\nbash scripts/pi-manager.sh sensor pir 17 --watch\n\n# Light sensor (analog via MCP3008 ADC)\nbash scripts/pi-manager.sh sensor light 0 # ADC channel 0\n\n# Log sensor readings\nbash scripts/pi-manager.sh sensor dht22 4 --log --interval 300 --output temp_log.csv\n```\n\n## Remote Deployment\n\nDeploy applications and configurations to your Pi.\n\n```bash\n# Copy files to Pi\nbash scripts/pi-manager.sh deploy push ./app/ /home/pi/app/\n\n# Pull files from Pi\nbash scripts/pi-manager.sh deploy pull /home/pi/logs/ ./local-logs/\n\n# Run a script on the Pi\nbash scripts/pi-manager.sh deploy exec ./setup.sh\n\n# Full deployment workflow\nbash scripts/pi-manager.sh deploy run ./deploy.yml\n```\n\n### Deploy manifest (`deploy.yml`):\n\n```yaml\ntarget: pi@192.168.1.200\nsteps:\n - copy: ./app/ → /home/pi/app/\n - run: cd /home/pi/app && pip3 install -r requirements.txt\n - run: sudo systemctl restart my-app\n - verify: curl -s http://localhost:8080/health\n```\n\n```bash\n# Fleet deployment\nbash scripts/pi-manager.sh --fleet deploy run ./deploy.yml\n# Deploys to all configured Pi hosts sequentially\n```\n\n## Maintenance\n\n```bash\n# System update\nbash scripts/pi-manager.sh update\n\n# Firmware update check\nbash scripts/pi-manager.sh firmware\n\n# Reboot / shutdown\nbash scripts/pi-manager.sh reboot\nbash scripts/pi-manager.sh shutdown\n\n# Backup SD card (creates compressed image)\nbash scripts/pi-manager.sh backup /path/to/backup.img.gz\n\n# Overclock profiles\nbash scripts/pi-manager.sh overclock show\nbash scripts/pi-manager.sh overclock mild # 1.8GHz\nbash scripts/pi-manager.sh overclock medium # 2.0GHz\n```\n\n## Monitoring Alerts\n\nSet up threshold-based alerts:\n\n```bash\n# Alert if temperature exceeds 75°C\nbash scripts/pi-manager.sh alert temp 75\n\n# Alert if disk usage exceeds 90%\nbash scripts/pi-manager.sh alert disk 90\n\n# Alert if a service goes down\nbash scripts/pi-manager.sh alert service nginx\n\n# All alerts — suitable for cron\nbash scripts/pi-manager.sh alert check\n```\n\nDesigned to be used standalone or as part of a larger IoT management workflow. Pair with `homeassistant-toolkit` for full smart home integration.\n---\n💬 Feedback & Feature Requests: https://bytesagain.com/feedback\nPowered by BytesAgain | bytesagain.com\n\nFile v2.3.0:_meta.json\n\n{\n \"ownerId\": \"kn76vqrf94wk924mddj8fp4p5x8497tb\",\n \"slug\": \"raspberry-pi-manager\",\n \"version\": \"2.3.0\",\n \"publishedAt\": 1773447661349\n}\n\nFile v2.3.0:tips.md\n\n# Tips for Raspberry Pi Manager\n\n## System Health\n\n1. **Keep the CPU temperature below 70°C.** Throttling starts at 80°C and significantly impacts performance. Use a heatsink + fan if running heavy workloads.\n\n2. **Monitor disk usage proactively.** SD cards fill up silently — logs, temp files, and package caches are common culprits. Set up a cron alert at 80%.\n\n3. **Use `--watch` mode for debugging performance issues.** Real-time CPU and memory monitoring helps identify spikes and memory leaks.\n\n4. **Log metrics to CSV** for long-term trend analysis. A weekly review of temperature and load patterns can prevent failures before they happen.\n\n## GPIO Best Practices\n\n- **Always double-check pin numbering.** BCM numbering (GPIO17) and physical pin numbering (pin 11) are different. The script uses BCM by default.\n- **Use pull-up/pull-down resistors** for input pins to avoid floating values\n- **Don't draw more than 16mA per GPIO pin** — use a transistor or relay for higher-power devices\n- **The `pinout` command** is your quick reference — no need to Google the diagram every time\n\n## Sensor Tips\n\n- **DHT22 > DHT11** for accuracy (±0.5°C vs ±2°C), but DHT11 is cheaper\n- **DS18B20** requires 1-Wire to be enabled: `sudo raspi-config` → Interface Options → 1-Wire\n- **BME280 via I2C** — enable I2C first: `sudo raspi-config` → Interface Options → I2C\n- **Log sensor data to CSV** and use `chart-generator` skill for visualization\n\n## Remote Management\n\n- **Set up SSH key authentication** — password auth over the internet is risky\n- **Use a reverse SSH tunnel or VPN** for remote access without port forwarding\n- **The `--fleet` mode** is powerful but runs commands sequentially — for large fleets, consider parallel execution with `xargs -P`\n\n## SD Card Longevity\n\n- **Use log2ram** to reduce SD card writes (logs stay in RAM, flushed periodically)\n- **Set `noatime` mount option** in `/etc/fstab` to reduce unnecessary writes\n- **Move heavy I/O to a USB drive** — databases, media, downloads\n- **Keep a backup image** — use the `backup` command monthly\n\n## Security Hardening\n\n- Change the default password immediately\n- Disable password-based SSH login\n- Keep the system updated: `bash scripts/pi-manager.sh update`\n- Disable unused services to reduce attack surface\n- Consider running `fail2ban` for SSH brute-force protection\n\n## Performance Tuning\n\n- **Overclock cautiously.** Start with \"mild\" and test stability under load before going higher.\n- **Disable the GUI** if running headless: saves ~200MB RAM\n- **Use zram** for swap instead of SD card swap — faster and reduces card wear\n- **64-bit OS** uses more RAM but gives access to >4GB on Pi 4/5\n\nArchive v2.2.0: 4 files, 8701 bytes\n\nFiles: scripts/rpi.sh (11809b), SKILL.md (7319b), tips.md (2697b), _meta.json (139b)\n\nFile v2.2.0:SKILL.md\n\n---\nname: raspberry-pi-manager\nversion: 1.0.0\ndescription: Manage Raspberry Pi devices — GPIO control, system monitoring (CPU/temp/memory), service management, sensor data reading, and remote deployment.\n---\n\n# Raspberry Pi Manager\n\nA Swiss Army knife for Raspberry Pi administration. Whether you're running a single Pi as a home server or managing a fleet of IoT nodes, this toolkit gives you instant access to system stats, GPIO pins, services, sensors, and deployment workflows.\n\n## How It Works\n\nThe script runs locally on the Pi or connects remotely via SSH. For local use, just execute the script directly. For remote management, configure SSH access.\n\n### Local Usage\n\n```bash\nbash scripts/pi-manager.sh system\nbash scripts/pi-manager.sh gpio read 17\n```\n\n### Remote Usage\n\n```bash\nexport PI_HOST=\"pi@192.168.1.200\"\nexport PI_SSH_KEY=\"~/.ssh/id_rsa\"\n\nbash scripts/pi-manager.sh --remote system\nbash scripts/pi-manager.sh --remote gpio read 17\n```\n\nMultiple Pi support:\n\n```bash\nexport PI_HOSTS=\"pi@node1.local,pi@node2.local,pi@node3.local\"\nbash scripts/pi-manager.sh --fleet system\n```\n\n## System Monitoring\n\nReal-time insight into your Pi's health.\n\n```bash\n# Full system dashboard\n$ bash scripts/pi-manager.sh system\n\n┌─ Raspberry Pi 4 Model B (4GB) ─────────────────────┐\n│ │\n│ CPU: 4× ARM Cortex-A72 @ 1.5GHz │\n│ Load: 0.42, 0.38, 0.31 │\n│ Temp: 48.3°C / 118.9°F [████░░░░░░ OK] │\n│ Memory: 1.2GB / 3.7GB [████████░░ 32%] │\n│ Disk: 12.4GB / 29.1GB [█████████░ 43%] │\n│ Swap: 0MB / 100MB [░░░░░░░░░░ 0%] │\n│ Uptime: 14 days, 7:23:41 │\n│ OS: Raspberry Pi OS (Bookworm) 64-bit │\n│ │\n│ Network: │\n│ eth0: 192.168.1.200 (1000 Mbps) │\n│ wlan0: 192.168.1.201 (72 Mbps, -42 dBm) │\n└──────────────────────────────────────────────────────┘\n```\n\n### Individual Metrics\n\n```bash\n# Temperature with threshold warning\nbash scripts/pi-manager.sh temp\nbash scripts/pi-manager.sh temp --warn 70 --crit 80\n\n# CPU usage (snapshot or continuous)\nbash scripts/pi-manager.sh cpu\nbash scripts/pi-manager.sh cpu --watch 5 # Update every 5s\n\n# Memory breakdown\nbash scripts/pi-manager.sh memory\n\n# Disk usage by mount point\nbash scripts/pi-manager.sh disk\n\n# Network interfaces and traffic\nbash scripts/pi-manager.sh network\n\n# Top processes by CPU/memory\nbash scripts/pi-manager.sh top 10\n```\n\n### Historical Data\n\n```bash\n# Log system metrics to CSV (for graphing)\nbash scripts/pi-manager.sh monitor --interval 60 --output metrics.csv\n\n# View logged metrics\nbash scripts/pi-manager.sh monitor --view metrics.csv --last 24h\n```\n\n## GPIO Control\n\nDirect pin manipulation for hardware projects.\n\n```bash\n# Pin layout reference\nbash scripts/pi-manager.sh gpio pinout\n\n# Read a pin state\nbash scripts/pi-manager.sh gpio read 17\n\n# Set pin output\nbash scripts/pi-manager.sh gpio write 17 high\nbash scripts/pi-manager.sh gpio write 17 low\n\n# Set pin mode\nbash scripts/pi-manager.sh gpio mode 17 output\nbash scripts/pi-manager.sh gpio mode 18 input --pull up\n\n# PWM output (hardware PWM on supported pins)\nbash scripts/pi-manager.sh gpio pwm 18 75 # 75% duty cycle\n\n# Watch pin for changes\nbash scripts/pi-manager.sh gpio watch 17 --edge both\n\n# Bulk operations\nbash scripts/pi-manager.sh gpio write 17,18,27,22 high\nbash scripts/pi-manager.sh gpio read 17,18,27,22\n\n# GPIO status overview\nbash scripts/pi-manager.sh gpio status\n```\n\n## Service Management\n\nControl systemd services running on the Pi.\n\n```bash\n# List all services (active, failed, inactive)\nbash scripts/pi-manager.sh service list\nbash scripts/pi-manager.sh service list --failed\n\n# Service operations\nbash scripts/pi-manager.sh service status nginx\nbash scripts/pi-manager.sh service start nginx\nbash scripts/pi-manager.sh service stop nginx\nbash scripts/pi-manager.sh service restart nginx\nbash scripts/pi-manager.sh service enable nginx\nbash scripts/pi-manager.sh service disable nginx\n\n# View service logs\nbash scripts/pi-manager.sh service logs nginx --lines 50\nbash scripts/pi-manager.sh service logs nginx --follow\n\n# Create a new service from a script\nbash scripts/pi-manager.sh service create my-app /home/pi/app/start.sh \\\n --description \"My Application\" \\\n --restart always \\\n --user pi\n```\n\n## Sensor Data\n\nRead common sensors connected to your Pi.\n\n```bash\n# DHT11/DHT22 temperature & humidity\nbash scripts/pi-manager.sh sensor dht22 4 # GPIO pin 4\n\n# DS18B20 temperature sensor (1-Wire)\nbash scripts/pi-manager.sh sensor ds18b20\n\n# BMP280/BME280 (I2C)\nbash scripts/pi-manager.sh sensor bme280\n\n# HC-SR04 ultrasonic distance\nbash scripts/pi-manager.sh sensor distance 23 24 # Trigger/Echo pins\n\n# PIR motion sensor\nbash scripts/pi-manager.sh sensor pir 17 --watch\n\n# Light sensor (analog via MCP3008 ADC)\nbash scripts/pi-manager.sh sensor light 0 # ADC channel 0\n\n# Log sensor readings\nbash scripts/pi-manager.sh sensor dht22 4 --log --interval 300 --output temp_log.csv\n```\n\n## Remote Deployment\n\nDeploy applications and configurations to your Pi.\n\n```bash\n# Copy files to Pi\nbash scripts/pi-manager.sh deploy push ./app/ /home/pi/app/\n\n# Pull files from Pi\nbash scripts/pi-manager.sh deploy pull /home/pi/logs/ ./local-logs/\n\n# Run a script on the Pi\nbash scripts/pi-manager.sh deploy exec ./setup.sh\n\n# Full deployment workflow\nbash scripts/pi-manager.sh deploy run ./deploy.yml\n```\n\n### Deploy manifest (`deploy.yml`):\n\n```yaml\ntarget: pi@192.168.1.200\nsteps:\n - copy: ./app/ → /home/pi/app/\n - run: cd /home/pi/app && pip3 install -r requirements.txt\n - run: sudo systemctl restart my-app\n - verify: curl -s http://localhost:8080/health\n```\n\n```bash\n# Fleet deployment\nbash scripts/pi-manager.sh --fleet deploy run ./deploy.yml\n# Deploys to all configured Pi hosts sequentially\n```\n\n## Maintenance\n\n```bash\n# System update\nbash scripts/pi-manager.sh update\n\n# Firmware update check\nbash scripts/pi-manager.sh firmware\n\n# Reboot / shutdown\nbash scripts/pi-manager.sh reboot\nbash scripts/pi-manager.sh shutdown\n\n# Backup SD card (creates compressed image)\nbash scripts/pi-manager.sh backup /path/to/backup.img.gz\n\n# Overclock profiles\nbash scripts/pi-manager.sh overclock show\nbash scripts/pi-manager.sh overclock mild # 1.8GHz\nbash scripts/pi-manager.sh overclock medium # 2.0GHz\n```\n\n## Monitoring Alerts\n\nSet up threshold-based alerts:\n\n```bash\n# Alert if temperature exceeds 75°C\nbash scripts/pi-manager.sh alert temp 75\n\n# Alert if disk usage exceeds 90%\nbash scripts/pi-manager.sh alert disk 90\n\n# Alert if a service goes down\nbash scripts/pi-manager.sh alert service nginx\n\n# All alerts — suitable for cron\nbash scripts/pi-manager.sh alert check\n```\n\nDesigned to be used standalone or as part of a larger IoT management workflow. Pair with `homeassistant-toolkit` for full smart home integration.\n\nFile v2.2.0:_meta.json\n\n{\n \"ownerId\": \"kn76vqrf94wk924mddj8fp4p5x8497tb\",\n \"slug\": \"raspberry-pi-manager\",\n \"version\": \"2.2.0\",\n \"publishedAt\": 1773421723850\n}\n\nFile v2.2.0:tips.md\n\n# Tips for Raspberry Pi Manager\n\n## System Health\n\n1. **Keep the CPU temperature below 70°C.** Throttling starts at 80°C and significantly impacts performance. Use a heatsink + fan if running heavy workloads.\n\n2. **Monitor disk usage proactively.** SD cards fill up silently — logs, temp files, and package caches are common culprits. Set up a cron alert at 80%.\n\n3. **Use `--watch` mode for debugging performance issues.** Real-time CPU and memory monitoring helps identify spikes and memory leaks.\n\n4. **Log metrics to CSV** for long-term trend analysis. A weekly review of temperature and load patterns can prevent failures before they happen.\n\n## GPIO Best Practices\n\n- **Always double-check pin numbering.** BCM numbering (GPIO17) and physical pin numbering (pin 11) are different. The script uses BCM by default.\n- **Use pull-up/pull-down resistors** for input pins to avoid floating values\n- **Don't draw more than 16mA per GPIO pin** — use a transistor or relay for higher-power devices\n- **The `pinout` command** is your quick reference — no need to Google the diagram every time\n\n## Sensor Tips\n\n- **DHT22 > DHT11** for accuracy (±0.5°C vs ±2°C), but DHT11 is cheaper\n- **DS18B20** requires 1-Wire to be enabled: `sudo raspi-config` → Interface Options → 1-Wire\n- **BME280 via I2C** — enable I2C first: `sudo raspi-config` → Interface Options → I2C\n- **Log sensor data to CSV** and use `chart-generator` skill for visualization\n\n## Remote Management\n\n- **Set up SSH key authentication** — password auth over the internet is risky\n- **Use a reverse SSH tunnel or VPN** for remote access without port forwarding\n- **The `--fleet` mode** is powerful but runs commands sequentially — for large fleets, consider parallel execution with `xargs -P`\n\n## SD Card Longevity\n\n- **Use log2ram** to reduce SD card writes (logs stay in RAM, flushed periodically)\n- **Set `noatime` mount option** in `/etc/fstab` to reduce unnecessary writes\n- **Move heavy I/O to a USB drive** — databases, media, downloads\n- **Keep a backup image** — use the `backup` command monthly\n\n## Security Hardening\n\n- Change the default password immediately\n- Disable password-based SSH login\n- Keep the system updated: `bash scripts/pi-manager.sh update`\n- Disable unused services to reduce attack surface\n- Consider running `fail2ban` for SSH brute-force protection\n\n## Performance Tuning\n\n- **Overclock cautiously.** Start with \"mild\" and test stability under load before going higher.\n- **Disable the GUI** if running headless: saves ~200MB RAM\n- **Use zram** for swap instead of SD card swap — faster and reduces card wear\n- **64-bit OS** uses more RAM but gives access to >4GB on Pi 4/5","readmeExcerpt":"Skill: Raspberry Pi Manager Owner: bytesagain-lab Summary: Manage Raspberry Pi devices — GPIO control, system monitoring (CPU/temp/memory), service management, sensor data reading. Tags: chinese:1.0.0, latest:2.0.1, productivity:1.0.0 Version history: v2.0.1 | 2026-03-18T10:49:20.575Z | user update v2.0.0 | 2026-03-17T18:50:33.066Z | user v2.5 standard: Use-when desc, homepage, source, security fix v2.3.6 | 2026-03-1","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"# Log a new SSH connection to a Pi\nraspberry-pi-manager connect \"SSH to pi@192.168.1.50 — firmware update session\"\n\n# Record a file sync event\nraspberry-pi-manager sync \"rsync /home/pi/data → NAS backup completed, 2.3GB transferred\"\n\n# Log a temperature monitoring alert\nraspberry-pi-manager monitor \"CPU temp 72°C on pi-node-3 — fan triggered\"\n\n# Record an automation task\nraspberry-pi-manager automate \"Cron job added: /home/pi/scripts/backup.sh every Sunday 02:00\"\n\n# View summary statistics\nraspberry-pi-manager stats\n\n# Export all data as JSON\nraspberry-pi-manager export json\n\n# Search for all entries mentioning 'backup'\nraspberry-pi-manager search backup\n\n# Check overall health status\nraspberry-pi-manager status\n\n# View the 20 most recent activities\nraspberry-pi-manager recent"},{"language":"bash","snippet":"bash scripts/pi-manager.sh system\nbash scripts/pi-manager.sh gpio read 17"},{"language":"bash","snippet":"export PI_HOST=\"pi@192.168.1.200\"\nexport PI_SSH_KEY=\"~/.ssh/id_rsa\"\n\nbash scripts/pi-manager.sh --remote system\nbash scripts/pi-manager.sh --remote gpio read 17"},{"language":"bash","snippet":"export PI_HOSTS=\"pi@node1.local,pi@node2.local,pi@node3.local\"\nbash scripts/pi-manager.sh --fleet system"},{"language":"bash","snippet":"# Full system dashboard\n$ bash scripts/pi-manager.sh system\n\n┌─ Raspberry Pi 4 Model B (4GB) ─────────────────────┐\n│ │\n│ CPU: 4× ARM Cortex-A72 @ 1.5GHz │\n│ Load: 0.42, 0.38, 0.31 │\n│ Temp: 48.3°C / 118.9°F [████░░░░░░ OK] │\n│ Memory: 1.2GB / 3.7GB [████████░░ 32%] │\n│ Disk: 12.4GB / 29.1GB [█████████░ 43%] │\n│ Swap: 0MB / 100MB [░░░░░░░░░░ 0%] │\n│ Uptime: 14 days, 7:23:41 │\n│ OS: Raspberry Pi OS (Bookworm) 64-bit │\n│ │\n│ Network: │\n│ eth0: 192.168.1.200 (1000 Mbps) │\n│ wlan0: 192.168.1.201 (72 Mbps, -42 dBm) │\n└──────────────────────────────────────────────────────┘"},{"language":"bash","snippet":"# Temperature with threshold warning\nbash scripts/pi-manager.sh temp\nbash scripts/pi-manager.sh temp --warn 70 --crit 80\n\n# CPU usage (snapshot or continuous)\nbash scripts/pi-manager.sh cpu\nbash scripts/pi-manager.sh cpu --watch 5 # Update every 5s\n\n# Memory breakdown\nbash scripts/pi-manager.sh memory\n\n# Disk usage by mount point\nbash scripts/pi-manager.sh disk\n\n# Network interfaces and traffic\nbash scripts/pi-manager.sh network\n\n# Top processes by CPU/memory\nbash scripts/pi-manager.sh top 10"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nversion: \"2.0.0\"\nname: raspberry-pi-manager\ndescription: \"Manage Raspberry Pi devices — GPIO control, system monitoring (CPU/temp/memory), service management, sensor data reading.\"\nauthor: BytesAgain\nhomepage: https://bytesagain.com\nsource: https://github.com/bytesagain/ai-skills\n---\n\n# Raspberry Pi Manager\n\nA command-line toolkit for managing Raspberry Pi operations. Log, track, and organize entries across multiple operational categories — from device connections and syncing to monitoring, automation, notifications, and reporting. All data is stored locally with timestamped history, full-text search, and multi-format export.\n\n## Commands\n\nThe following commands are available via `raspberry-pi-manager [args]`:\n\n### Core Operations\n\n| Command | Description |\n|---------|-------------|\n| `connect ` | Log a connection event (e.g. SSH session, network link, peripheral attach). Called without args, shows recent connect entries. |\n| `sync ` | Record a sync operation (e.g. file sync, config push, backup mirror). Called without args, shows recent sync entries. |\n| `monitor ` | Log a monitoring observation (e.g. CPU temp spike, disk usage alert). Called without args, shows recent monitor entries. |\n| `automate ` | Record an automation task (e.g. cron job setup, GPIO script trigger). Called without args, shows recent automate entries. |\n| `notify ` | Log a notification event (e.g. email alert sent, Telegram ping). Called without args, shows recent notify entries. |\n| `report ` | Save a report note (e.g. weekly summary, incident write-up). Called without args, shows recent report entries. |\n| `schedule ` | Record a scheduled task (e.g. reboot at 3 AM, backup every Sunday). Called without args, shows recent schedule entries. |\n| `template ` | Store a template entry (e.g. config template, deploy script skeleton). Called without args, shows recent template entries. |\n| `webhook ` | Log a webhook event (e.g. incoming POST, IFTTT trigger). Called without args, shows recent webhook entries. |\n| `status ` | Record a status update (e.g. Pi online, service healthy). Called without args, shows recent status entries. |\n| `analytics ` | Log an analytics data point (e.g. uptime percentage, request count). Called without args, shows recent analytics entries. |\n| `export ` | Record an export action. Called without args, shows recent export entries. |\n\n### Utility Commands\n\n| Command | Description |\n|---------|-------------|\n| `stats` | Show summary statistics — entry counts per category, total entries, data size, and earliest record timestamp. |\n| `export ` | Export all data in `json`, `csv`, or `txt` format. Output file saved to the data directory. |\n| `search ` | Full-text search across all log files (case-insensitive). |\n| `recent` | Show the 20 most recent activity entries from the global history log. |\n| `status` | Health check — version, data directory path, t"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn76vqrf94wk924mddj8fp4p5x8497tb\",\n \"slug\": \"raspberry-pi-manager\",\n \"version\": \"2.0.1\",\n \"publishedAt\": 1773830960575\n}"},{"path":"skill-card.md","content":"## Description:\n\nA local bash command-line journal for recording Raspberry Pi-related operational notes, searching saved entries, viewing recent activity, and exporting logs.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[bytesagain-lab](https://clawhub.ai/user/bytesagain-lab)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal developers and operators can use this skill as a local operations journal for Raspberry Pi fleet notes, automation records, status observations, searches, and exports. It should not be treated as a device management or monitoring interface.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill is advertised as Raspberry Pi management, but evidence shows it records local notes and exports logs rather than controlling GPIO, services, sensors, or devices.\n\nMitigation: Use it only as an operations journal and verify any real device-management needs with separate trusted tooling.\n\nRisk: Operational entries are stored in plaintext under ~/.local/share/raspberry-pi-manager and can be searched or exported.\n\nMitigation: Do not enter credentials, tokens, private host details, or other sensitive information into logged entries.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/bytesagain-lab/skills/raspberry-pi-manager)\n- [BytesAgain homepage](https://bytesagain.com)\n\n## Skill Output:\n\n**Output Type(s):** [Shell commands, Text, Files, Guidance]\n\n**Output Format:** [Markdown guidance with inline bash commands and local text, JSON, CSV, or TXT export files]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Stores entries in plaintext under ~/.local/share/raspberry-pi-manager.]\n\n## Skill Version(s):\n\n2.0.1 (source: ClawHub release evidence; artifact frontmatter reports 2.0.0)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Manage Raspberry Pi devices — GPIO control, system monitoring (CPU/temp/memory), service management, sensor data reading. Skill: Raspberry Pi Manager Owner: bytesagain-lab Summary: Manage Raspberry Pi devices — GPIO control, system monitoring (CPU/temp/memory), service management, sensor data reading. Tags: chinese:1.0.0, latest:2.0.1, productivity:1.0.0 Version history: v2.0.1 | 2026-03-18T10:49:20.575Z | user update v2.0.0 | 2026-03-17T18:50:33.066Z | user v2.5 standard: Use-when desc, homepage, source, security fix v2.3.6 | 2026-03-1","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1076,"uniquenessScore":53,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-10T11:16:07.463Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-10T11:16:07.463Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T13:29:43.233Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}