# Nanobot Use Cases — Analysis for lachtan

**Date:** 2026-06-18
**Model:** kimi-k2.7-code:cloud
**Scope:** Immediately practical + medium-term research ideas

---

## 1. Homelab / Sysadmin Automation

### 1.1 Proxmox / LXC Management
- **Container lifecycle:** Start/stop/restart LXC containers via SSH + `pct` commands wrapped in a skill
- **Snapshot scheduling:** Cron-triggered Proxmox snapshots with Telegram confirmation
- **Resource monitoring:** Query `pct status`, memory, CPU via Zabbix API or direct SSH
- **Auto-scaling (light):** Restart containers that exceed memory thresholds

### 1.2 Backup Orchestration
- **Priority pain point** — user explicitly named this as #1 priority
- **ZFS snapshot coordination:** Trigger `zfs snapshot` on nvidia.hell, wood.hell, pivo.hell
- **Offsite sync:** `rsync` / `rclone` to remote storage with verification
- **Backup verification:** Periodic restore tests of critical containers
- **Alerting:** Telegram notification on backup success/failure
- **Integration:** Hook into existing Zabbix for monitoring backup jobs

### 1.3 Ollama Cloud Management
- **Usage tracking:** Query Ollama Cloud API for session time, token usage
- **Model switching:** Auto-switch to cheaper/faster models based on task type
- **Session watchdog:** Alert when approaching 5h session limit or 7-day window
- **Cost alerts:** Notify when usage spikes unexpectedly

### 1.4 GPU Host Monitoring (nvidia.hell)
- **NVIDIA SMI queries:** GPU utilization, temperature, memory usage
- **Ollama queue monitoring:** Pending requests, model load status
- **Alerting:** GPU overheating, OOM conditions, model crash detection

---

## 2. Personal Knowledge Management

### 2.1 LLM Wiki (Existing — llm-wiki skill)
- **Status:** Already implemented and actively used
- **Use case:** Ingest articles, papers, transcripts → compile to structured markdown wiki
- **Automation:** Cron-driven compilation of `cml/raw/` sources
- **Graph metadata:** Auto-generate relationship graphs between concepts
- **Query interface:** Ask questions against accumulated knowledge base

### 2.2 Note System (Existing — note skill)
- **Status:** SQLite backend, deterministic operations
- **Use case:** Quick capture of ideas, links, observations
- **Integration:** Link notes to wiki entries, reminders, projects

### 2.3 Keep System (Existing — keep skill)
- **Status:** Immediate memory, deduplicated, compacted
- **Use case:** Facts the user explicitly wants remembered (preferences, dimensions, contacts)

### 2.4 Unified Personal Data Layer (Research Idea)
- **Concept:** Integrate remind + keep + note + todo into a single queryable system
- **Approach:** SQLite views or a lightweight graph connecting all four stores
- **Query examples:**
  - "What did I note about backups last month?"
  - "Show me all reminders related to the chicken coop"
  - "What was my last todo about 3D printer?"

---

## 3. Cryptocurrency Portfolio Tracking

### 3.1 Price Monitoring
- **Assets:** SOL, ETH, BNB, ADA, DOT (user's regular investments)
- **Implementation:** CoinGecko / CoinMarketCap API queries via cron
- **Alerts:** Price thresholds, significant moves (>5% in 1h, >10% in 24h)
- **Delivery:** Telegram notifications

### 3.2 Portfolio Summary
- **Weekly digest:** Current holdings value, weekly change, top movers
- **DCA tracking:** Log regular purchases, calculate average buy price
- **Exclusion:** Bitcoin explicitly ignored per user preference

### 3.3 Market Sentiment (Research)
- **Social metrics:** Reddit/Twitter sentiment for tracked coins
- **Fear & Greed Index:** Weekly capture and trend analysis

---

## 4. Personal Organization & Reminders

### 4.1 Reminder System (Existing — remind skill)
- **Status:** SQLite backend, 43 tests passing, cron-driven
- **Use cases:**
  - Weekly random-time reminders (skleničky, mapování klíčů, senzor chlívku, zálohy)
  - Fixed schedule reminders (kolenoskopie — weekdays 08:00)
  - One-off reminders with natural language parsing

### 4.2 Heartbeat Tasks (Existing — HEARTBEAT.md + cron)
- **Daily checks:** Nanobot Docker image updates, wiki compilation, backup status
- **Random delivery:** Within time windows (08:00–21:00) to avoid predictability

### 4.3 Todo Integration (Planned)
- **Status:** Mentioned in plans but not yet implemented
- **Use case:** Actionable tasks distinct from reminders (reminders = notify at time, todo = track until done)

---

## 5. Media & Entertainment

### 5.1 Radio 1 Stream Processing
- **Status:** Planned but not implemented
- **Use case:** Remove ads, cut songs from Radio 1 stream
- **Approach:** FFmpeg stream processing, ad detection (silence/sponsor markers), song segmentation
- **Delivery:** Clean stream or segmented MP3s

### 5.2 Movie Tracking
- **Use case:** Track watched movies, ratings, recommendations
- **Integration:** IMDB/Trakt API, personal wiki entries

---

## 6. IoT & Home Projects

### 6.1 Chicken Coop Temperature Sensor
- **Status:** Pending project (reminder #7)
- **Use case:** MQTT temperature display, alerting on extreme temperatures
- **Integration:** nanobot cron queries MQTT broker, sends Telegram alerts

### 6.2 Basement Key Mapping
- **Status:** Pending project (reminder #6)
- **Use case:** Digital inventory of basement keys with locations
- **Implementation:** Simple SQLite or markdown wiki page

---

## 7. Development & Tooling

### 7.1 Custom Command Dispatch (Research)
- **Status:** User wants deterministic `!command` or `:skillname` dispatch without LLM deliberation
- **Use case:** Fast, predictable execution of registered commands
- **Blocker:** Requires nanobot core patch (CommandRouter extension)

### 7.2 Skill Development
- **Use case:** Create custom skills for homelab-specific tasks
- **Examples:**
  - `proxmox` skill — container management
  - `backup` skill — backup orchestration and verification
  - `crypto` skill — portfolio tracking
  - `radio` skill — stream processing

### 7.3 Code Generation & Review
- **Use case:** Generate shell/Python scripts for ad-hoc tasks
- **Integration:** Save to `scripts/` directory per user convention

---

## 8. Communication & Notifications

### 8.1 Telegram as Primary Channel
- **Status:** Active, user ID 8826147089 configured
- **Use cases:**
  - All reminder deliveries
  - Backup status notifications
  - Crypto price alerts
  - Homelab anomaly alerts

### 8.2 Cross-Channel Session Continuity
- **Status:** Disabled by user choice
- **Note:** User prefers connecting to older sessions over unified mega-session

---

## Priority Matrix

| Priority | Use Case | Status | Effort |
|----------|----------|--------|--------|
| **P0** | Backup orchestration | Planned | Medium |
| **P0** | LLM Wiki maintenance | Active | Low |
| **P1** | Crypto portfolio tracking | Not started | Low |
| **P1** | Proxmox/LXC automation | Not started | Medium |
| **P1** | Ollama usage monitoring | Not started | Low |
| **P2** | Radio 1 stream processing | Planned | High |
| **P2** | Unified personal data layer | Research | High |
| **P2** | Custom command dispatch | Research | High |
| **P3** | Chicken coop sensor | Pending | Medium |
| **P3** | Movie tracking | Not started | Low |

---

## Immediate Next Steps

1. **Backup skill:** Design and implement backup orchestration skill (highest priority pain point)
2. **Crypto skill:** Quick win — CoinGecko API wrapper with price alerts
3. **Ollama monitoring:** Simple cron job querying Ollama Cloud usage endpoint
4. **Proxmox skill:** SSH-based LXC container management commands

---

## Research Directions

1. **Unified query layer:** How to cross-query remind/note/keep/todo without heavy architecture
2. **Deterministic commands:** Evaluate nanobot patch feasibility for `!command` dispatch
3. **Model routing:** Auto-select model based on task type (research vs quick query vs coding)
4. **MCP integration:** Connect nanobot to external tools via Model Context Protocol

---

*Generated by nanobot deep-research skill*