{
"session_id": "20260622_132931_b44504",
"model": "gemini-3-flash-preview",
"base_url": "https://ollama.com/v1",
"platform": "curator",
"session_start": "2026-06-22T13:29:31.241929",
"last_updated": "2026-06-22T13:32:29.639654",
"system_prompt": "You are Hermes Agent, an intelligent AI assistant created by Nous Research. You are helpful, knowledgeable, and direct. You assist users with a wide range of tasks including answering questions, writing and editing code, analyzing information, creative work, and executing actions via your tools. You communicate clearly, admit uncertainty when appropriate, and prioritize being genuinely useful over being verbose unless otherwise directed below. Be targeted and efficient in your exploration and investigations.\n\nIf the user asks about configuring, setting up, or using Hermes Agent itself, load the `hermes-agent` skill with skill_view(name='hermes-agent') before answering. Docs: https://hermes-agent.nousresearch.com/docs\n\nYou have persistent memory across sessions. Save durable facts using the memory tool: user preferences, environment details, tool quirks, and stable conventions. Memory is injected into every turn, so keep it compact and focused on facts that will still matter later.\nPrioritize what reduces future user steering — the most valuable memory is one that prevents the user from having to correct or remind you again. User preferences and recurring corrections matter more than procedural task details.\nDo NOT save task progress, session outcomes, completed-work logs, or temporary TODO state to memory; use session_search to recall those from past transcripts. If you've discovered a new way to do something, solved a problem that could be necessary later, save it as a skill with the skill tool.\nWrite memories as declarative facts, not instructions to yourself. 'User prefers concise responses' ✓ — 'Always respond concisely' ✗. 'Project uses pytest with xdist' ✓ — 'Run tests with pytest -n 4' ✗. Imperative phrasing gets re-read as a directive in later sessions and can cause repeated work or override the user's current request. Procedures and workflows belong in skills, not memory. When the user references something from a past conversation or you suspect relevant cross-session context exists, use session_search to recall it before asking them to repeat themselves. After completing a complex task (5+ tool calls), fixing a tricky error, or discovering a non-trivial workflow, save the approach as a skill with skill_manage so you can reuse it next time.\nWhen using a skill and finding it outdated, incomplete, or wrong, patch it immediately with skill_manage(action='patch') — don't wait to be asked. Skills that aren't maintained become liabilities.\n\n# Tool-use enforcement\nYou MUST use your tools to take action — do not describe what you would do or plan to do without actually doing it. When you say you will perform an action (e.g. 'I will run the tests', 'Let me check the file', 'I will create the project'), you MUST immediately make the corresponding tool call in the same response. Never end your turn with a promise of future action — execute it now.\nKeep working until the task is actually complete. Do not stop with a summary of what you plan to do next time. If you have tools available that can accomplish the task, use them instead of telling the user what you would do.\nEvery response should either (a) contain tool calls that make progress, or (b) deliver a final result to the user. Responses that only describe intentions without acting are not acceptable.\n\n# Google model operational directives\nFollow these operational rules strictly:\n- **Absolute paths:** Always construct and use absolute file paths for all file system operations. Combine the project root with relative paths.\n- **Verify first:** Use read_file/search_files to check file contents and project structure before making changes. Never guess at file contents.\n- **Dependency checks:** Never assume a library is available. Check package.json, requirements.txt, Cargo.toml, etc. before importing.\n- **Conciseness:** Keep explanatory text brief — a few sentences, not paragraphs. Focus on actions and results over narration.\n- **Parallel tool calls:** When you need to perform multiple independent operations (e.g. reading several files), make all the tool calls in a single response rather than sequentially.\n- **Non-interactive commands:** Use flags like -y, --yes, --non-interactive to prevent CLI tools from hanging on prompts.\n- **Keep going:** Work autonomously until the task is fully resolved. Don't stop with a plan — execute it.\n\n## Skills (mandatory)\nBefore replying, scan the skills below. If a skill matches or is even partially relevant to your task, you MUST load it with skill_view(name) and follow its instructions. Err on the side of loading — it is always better to have context you don't need than to miss critical steps, pitfalls, or established workflows. Skills contain specialized knowledge — API endpoints, tool-specific commands, and proven workflows that outperform general-purpose approaches. Load the skill even if you think you could handle the task with basic tools like web_search or terminal. Skills also encode the user's preferred approach, conventions, and quality standards for tasks like code review, planning, and testing — load them even for tasks you already know how to do, because the skill defines how it should be done here.\nWhenever the user asks you to configure, set up, install, enable, disable, modify, or troubleshoot Hermes Agent itself — its CLI, config, models, providers, tools, skills, voice, gateway, plugins, or any feature — load the `hermes-agent` skill first. It has the actual commands (e.g. `hermes config set …`, `hermes tools`, `hermes setup`) so you don't have to guess or invent workarounds.\nIf a skill has issues, fix it with skill_manage(action='patch').\nAfter difficult/iterative tasks, offer to save as a skill. If a skill you loaded was missing steps, had wrong commands, or needed pitfalls you discovered, update it before finishing.\n\n\n 3d-printing:\n - 3d-druck-kiwi: Vollständiger Workflow zum Erstellen druckbarer 3D-Modell...\n autonomous-ai-agents: Skills for spawning and orchestrating autonomous AI coding agents and multi-agent workflows — running independent agent processes, delegating tasks, and coordinating parallel workstreams.\n - claude-code: Delegate coding to Claude Code CLI (features, PRs).\n - hermes-agent: Configure, extend, or contribute to Hermes Agent.\n - opencode: Delegate coding to OpenCode CLI (features, PR review).\n cad-3d-print:\n - cad-3d-print: Parametric 3D modeling with trimesh for FDM printing. Gen...\n creative: Creative content generation — ASCII art, hand-drawn style diagrams, and visual design tools.\n - ai-video-production: AI-gestützte Videoproduktion: Skript, Bildgenerierung (DA...\n - architecture-diagram: Dark-themed SVG architecture/cloud/infra diagrams as HTML.\n - ascii-art: ASCII art: pyfiglet, cowsay, boxes, image-to-ascii.\n - ascii-video: ASCII video: convert video/audio to colored ASCII MP4/GIF.\n - baoyu-comic: Knowledge comics (知识漫画): educational, biography, tutorial.\n - baoyu-infographic: Infographics: 21 layouts x 21 styles (信息图, 可视化).\n - claude-design: Design one-off HTML artifacts (landing, deck, prototype).\n - comfyui: Generate images, video, and audio with ComfyUI — install,...\n - design-md: Author/validate/export Google's DESIGN.md token spec files.\n - excalidraw: Hand-drawn Excalidraw JSON diagrams (arch, flow, seq).\n - humanizer: Humanize text: strip AI-isms and add real voice.\n - ideation: Generate project ideas via creative constraints.\n - manim-video: Manim CE animations: 3Blue1Brown math/algo videos.\n - p5js: p5.js sketches: gen art, shaders, interactive, 3D.\n - pixel-art: Pixel art w/ era palettes (NES, Game Boy, PICO-8).\n - popular-web-designs: 54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.\n - pretext: Use when building creative browser demos with @chenglou/p...\n - sketch: Throwaway HTML mockups: 2-3 design variants to compare.\n - songwriting-and-ai-music: Songwriting craft and Suno AI music prompts.\n - touchdesigner-mcp: Control a running TouchDesigner instance via twozero MCP ...\n data-science: Skills for data science workflows — interactive exploration, Jupyter notebooks, data analysis, and visualization.\n - jupyter-live-kernel: Iterative Python via live Jupyter kernel (hamelnb).\n devops:\n - casaos-app-troubleshoot: CasaOS-App-Probleme diagnostizieren und beheben — Legacy,...\n - kanban-orchestrator: Decomposition playbook + specialist-roster conventions + ...\n - kanban-worker: Pitfalls, examples, and edge cases for Hermes Kanban work...\n - local-server-public-access: Expose a local HTTP service (website, dashboard, dev serv...\n - safe-volume-migration: Anonyme Docker-Volumes (Hash-Namen) sicher zu Bind-Mounts...\n - webhook-subscriptions: Webhook subscriptions: event-driven agent runs.\n - zimaos-app-install: Neue App/Container auf ZimaOS sauber per Docker Compose i...\n - zimaos-camofox-browser: Camofox-Browser als persistenten Docker-Dienst auf ZimaOS...\n - zimaos-platform: Build, deploy, administer, inspect, and debug application...\n - zimaos-quirks: ZimaOS-Eigenheiten — read-only Root-FS, DOCKER_CONFIG, HO...\n dogfood:\n - dogfood: Exploratory QA of web apps: find bugs, evidence, reports.\n email: Skills for sending, receiving, searching, and managing email from the terminal.\n - himalaya: Himalaya CLI: IMAP/SMTP email from terminal.\n gaming: Skills for setting up, configuring, and managing game servers, modpacks, and gaming-related infrastructure.\n - minecraft-modpack-server: Host modded Minecraft servers (CurseForge, Modrinth).\n - pokemon-player: Play Pokemon via headless emulator + RAM reads.\n github: GitHub workflow skills for managing repositories, pull requests, code reviews, issues, and CI/CD pipelines using the gh CLI and git via terminal.\n - codebase-inspection: Inspect codebases w/ pygount: LOC, languages, ratios.\n - github-auth: GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login.\n - github-code-review: Review PRs: diffs, inline comments via gh or REST.\n - github-issues: Create, triage, label, assign GitHub issues via gh or REST.\n - github-pr-workflow: GitHub PR lifecycle: branch, commit, open, CI, merge.\n - github-repo-management: Clone/create/fork repos; manage remotes, releases.\n maker-electronics:\n - esp32-desk-dashboard: ESP32-basierte Desk-Dashboards mit AMOLED, LVGL und BLE. ...\n mcp: Skills for working with MCP (Model Context Protocol) servers, tools, and integrations. Documents the built-in native MCP client — configure servers in config.yaml for automatic tool discovery.\n - native-mcp: MCP client: connect servers, register tools (stdio/HTTP).\n media: Skills for working with media content — YouTube transcripts, GIF search, music generation, and audio visualization.\n - gif-search: Search/download GIFs from Tenor via curl + jq.\n - heartmula: HeartMuLa: Suno-like song generation from lyrics + tags.\n - media-file-management: Organize and normalize local media files (movies, TV show...\n - music-resources: Find sheet music, chords, tabs, and notation online — sea...\n - songsee: Audio spectrograms/features (mel, chroma, MFCC) via CLI.\n - spotify: Spotify: play, search, queue, manage playlists and devices.\n - youtube-content: YouTube transcripts to summaries, threads, blogs.\n - youtube-headless-pipeline: Vollautomatische YouTube-Shorts-Pipeline: Reddit-Stories ...\n mlops: Knowledge and Tools for Machine Learning Operations - tools and frameworks for training, fine-tuning, deploying, and optimizing ML/AI models\n - huggingface-hub: HuggingFace hf CLI: search/download/upload models, datasets.\n mlops/evaluation: Model evaluation benchmarks, experiment tracking, data curation, tokenizers, and interpretability tools.\n - evaluating-llms-harness: lm-eval-harness: benchmark LLMs (MMLU, GSM8K, etc.).\n - weights-and-biases: W&B: log ML experiments, sweeps, model registry, dashboards.\n mlops/inference: Model serving, quantization (GGUF/GPTQ), structured output, inference optimization, and model surgery tools for deploying and running LLMs.\n - llama-cpp: llama.cpp local GGUF inference + HF Hub model discovery.\n - obliteratus: OBLITERATUS: abliterate LLM refusals (diff-in-means).\n - outlines: Outlines: structured JSON/regex/Pydantic LLM generation.\n - serving-llms-vllm: vLLM: high-throughput LLM serving, OpenAI API, quantization.\n mlops/models: Specific model architectures and tools — image segmentation (Segment Anything / SAM) and audio generation (AudioCraft / MusicGen). Additional model skills (CLIP, Stable Diffusion, Whisper, LLaVA) are available as optional skills.\n - audiocraft-audio-generation: AudioCraft: MusicGen text-to-music, AudioGen text-to-sound.\n - segment-anything-model: SAM: zero-shot image segmentation via points, boxes, masks.\n mlops/research: ML research frameworks for building and optimizing AI systems with declarative programming.\n - dspy: DSPy: declarative LM programs, auto-optimize prompts, RAG.\n mlops/training: Fine-tuning, RLHF/DPO/GRPO training, distributed training frameworks, and optimization tools for training LLMs and other models.\n - axolotl: Axolotl: YAML LLM fine-tuning (LoRA, DPO, GRPO).\n - fine-tuning-with-trl: TRL: SFT, DPO, PPO, GRPO, reward modeling for LLM RLHF.\n - unsloth: Unsloth: 2-5x faster LoRA/QLoRA fine-tuning, less VRAM.\n note-taking: Note taking skills, to save information, assist with research, and collab on multi-session planning and information sharing.\n - obsidian: Read, search, create, and edit notes in the Obsidian vaul...\n productivity: Skills for document creation, presentations, spreadsheets, and other productivity workflows.\n - airtable: Airtable REST API via curl. Records CRUD, filters, upserts.\n - docmaster-access: Direkter Zugriff auf DocMaster-Dokumente auf ZimaOS — API...\n - google-workspace: Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python.\n - linear: Linear: manage issues, projects, teams via GraphQL + curl.\n - maps: Geocode, POIs, routes, timezones via OpenStreetMap/OSRM.\n - mnemo-access: Direkter Zugriff auf Mnemo (Cartographer's Zettelkasten) ...\n - nano-pdf: Edit PDF text/typos/titles via nano-pdf CLI (NL prompts).\n - notion: Notion API via curl: pages, databases, blocks, search.\n - ocr-and-documents: Extract text from PDFs/scans (pymupdf, marker-pdf).\n - pdf-generation: Generate PDF documents from markdown/text using fpdf2 wit...\n - powerpoint: Create, read, edit .pptx decks, slides, notes, templates.\n - zimaos-productivity: Productivity apps on ZimaOS — DailyDose activity tracking...\n red-teaming:\n - godmode: Jailbreak LLMs: Parseltongue, GODMODE, ULTRAPLINIAN.\n research: Skills for academic research, paper discovery, literature review, domain reconnaissance, market data, content monitoring, and scientific knowledge retrieval.\n - arxiv: Search arXiv papers by keyword, author, category, or ID.\n - blogwatcher: Monitor blogs and RSS/Atom feeds via blogwatcher-cli tool.\n - llm-wiki: Karpathy's LLM Wiki: build/query interlinked markdown KB.\n - polymarket: Query Polymarket: markets, prices, orderbooks, history.\n - research-literature: Academic and biomedical research skills — professor profi...\n smart-home: Skills for controlling smart home devices — lights, switches, sensors, and home automation systems.\n - home-assistant: Inspect, manage, and troubleshoot Home Assistant (Docker ...\n - midea-ac-ha: Midea Porta Split Klimaanlage in Home Assistant 2026 einb...\n - openhue: Control Philips Hue lights, scenes, rooms via OpenHue CLI.\n social-media: Skills for interacting with social platforms and social-media workflows — posting, reading, monitoring, and account operations.\n - reddit: Read Reddit posts, comments, and subreddits via JSON API ...\n - xurl: X/Twitter via xurl CLI: post, search, DM, media, v2 API.\n software-development:\n - debugging-hermes-tui-commands: Debug Hermes TUI slash commands: Python, gateway, Ink UI.\n - hermes-agent-skill-authoring: Author in-repo SKILL.md: frontmatter, validator, structure.\n - node-inspect-debugger: Debug Node.js via --inspect + Chrome DevTools Protocol CLI.\n - plan: Plan mode: write markdown plan to .hermes/plans/, no exec.\n - python-debugpy: Debug Python: pdb REPL + debugpy remote (DAP).\n - requesting-code-review: Pre-commit review: security scan, quality gates, auto-fix.\n - spike: Throwaway experiments to validate an idea before build.\n - subagent-driven-development: Execute plans via delegate_task subagents (2-stage review).\n - systematic-debugging: 4-phase root cause debugging: understand bugs before fixing.\n - technical-product-spec: Write deep technical product specifications in Stripe/Clo...\n - test-driven-development: TDD: enforce RED-GREEN-REFACTOR, tests before code.\n - writing-plans: Write implementation plans: bite-sized tasks, paths, code.\n - zeitgeist-app-development: Modify the Zeitgeist single-file HTML/CSS/JS apps (zeitge...\n yuanbao:\n - yuanbao: Yuanbao (元宝) groups: @mention users, query info/members.\n\n\nOnly proceed without loading a skill if genuinely none are relevant to the task.\n\nConversation started: Monday, June 22, 2026 01:29 PM\nModel: gemini-3-flash-preview\nProvider: custom",
"tools": [
{
"type": "function",
"function": {
"name": "browser_back",
"description": "Navigate back to the previous page in browser history. Requires browser_navigate to be called first.",
"parameters": {
"type": "object",
"properties": {}
}
}
},
{
"type": "function",
"function": {
"name": "browser_click",
"description": "Click on an element identified by its ref ID from the snapshot (e.g., '@e5'). The ref IDs are shown in square brackets in the snapshot output. Requires browser_navigate and browser_snapshot to be called first.",
"parameters": {
"type": "object",
"properties": {
"ref": {
"type": "string",
"description": "The element reference from the snapshot (e.g., '@e5', '@e12')"
}
},
"required": [
"ref"
]
}
}
},
{
"type": "function",
"function": {
"name": "browser_console",
"description": "Get browser console output and JavaScript errors from the current page. Returns console.log/warn/error/info messages and uncaught JS exceptions. Use this to detect silent JavaScript errors, failed API calls, and application warnings. Requires browser_navigate to be called first. When 'expression' is provided, evaluates JavaScript in the page context and returns the result — use this for DOM inspection, reading page state, or extracting data programmatically.",
"parameters": {
"type": "object",
"properties": {
"clear": {
"type": "boolean",
"default": false,
"description": "If true, clear the message buffers after reading"
},
"expression": {
"type": "string",
"description": "JavaScript expression to evaluate in the page context. Runs in the browser like DevTools console — full access to DOM, window, document. Return values are serialized to JSON. Example: 'document.title' or 'document.querySelectorAll(\"a\").length'"
}
}
}
}
},
{
"type": "function",
"function": {
"name": "browser_get_images",
"description": "Get a list of all images on the current page with their URLs and alt text. Useful for finding images to analyze with the vision tool. Requires browser_navigate to be called first.",
"parameters": {
"type": "object",
"properties": {}
}
}
},
{
"type": "function",
"function": {
"name": "browser_navigate",
"description": "Navigate to a URL in the browser. Initializes the session and loads the page. Must be called before other browser tools. For plain-text endpoints — URLs ending in .md, .txt, .json, .yaml, .yml, .csv, .xml, raw.githubusercontent.com, or any documented API endpoint — prefer curl via the terminal tool or web_extract; the browser stack is overkill and much slower for these. Use browser tools when you need to interact with a page (click, fill forms, dynamic content). Returns a compact page snapshot with interactive elements and ref IDs — no need to call browser_snapshot separately after navigating.",
"parameters": {
"type": "object",
"properties": {
"url": {
"type": "string",
"description": "The URL to navigate to (e.g., 'https://example.com')"
}
},
"required": [
"url"
]
}
}
},
{
"type": "function",
"function": {
"name": "browser_press",
"description": "Press a keyboard key. Useful for submitting forms (Enter), navigating (Tab), or keyboard shortcuts. Requires browser_navigate to be called first.",
"parameters": {
"type": "object",
"properties": {
"key": {
"type": "string",
"description": "Key to press (e.g., 'Enter', 'Tab', 'Escape', 'ArrowDown')"
}
},
"required": [
"key"
]
}
}
},
{
"type": "function",
"function": {
"name": "browser_scroll",
"description": "Scroll the page in a direction. Use this to reveal more content that may be below or above the current viewport. Requires browser_navigate to be called first.",
"parameters": {
"type": "object",
"properties": {
"direction": {
"type": "string",
"enum": [
"up",
"down"
],
"description": "Direction to scroll"
}
},
"required": [
"direction"
]
}
}
},
{
"type": "function",
"function": {
"name": "browser_snapshot",
"description": "Get a text-based snapshot of the current page's accessibility tree. Returns interactive elements with ref IDs (like @e1, @e2) for browser_click and browser_type. full=false (default): compact view with interactive elements. full=true: complete page content. Snapshots over 8000 chars are truncated or LLM-summarized. Requires browser_navigate first. Note: browser_navigate already returns a compact snapshot — use this to refresh after interactions that change the page, or with full=true for complete content.",
"parameters": {
"type": "object",
"properties": {
"full": {
"type": "boolean",
"description": "If true, returns complete page content. If false (default), returns compact view with interactive elements only.",
"default": false
}
}
}
}
},
{
"type": "function",
"function": {
"name": "browser_type",
"description": "Type text into an input field identified by its ref ID. Clears the field first, then types the new text. Requires browser_navigate and browser_snapshot to be called first.",
"parameters": {
"type": "object",
"properties": {
"ref": {
"type": "string",
"description": "The element reference from the snapshot (e.g., '@e3')"
},
"text": {
"type": "string",
"description": "The text to type into the field"
}
},
"required": [
"ref",
"text"
]
}
}
},
{
"type": "function",
"function": {
"name": "browser_vision",
"description": "Take a screenshot of the current page and analyze it with vision AI. Use this when you need to visually understand what's on the page - especially useful for CAPTCHAs, visual verification challenges, complex layouts, or when the text snapshot doesn't capture important visual information. Returns both the AI analysis and a screenshot_path that you can share with the user by including MEDIA: in your response. Requires browser_navigate to be called first.",
"parameters": {
"type": "object",
"properties": {
"question": {
"type": "string",
"description": "What you want to know about the page visually. Be specific about what you're looking for."
},
"annotate": {
"type": "boolean",
"default": false,
"description": "If true, overlay numbered [N] labels on interactive elements. Each [N] maps to ref @eN for subsequent browser commands. Useful for QA and spatial reasoning about page layout."
}
},
"required": [
"question"
]
}
}
},
{
"type": "function",
"function": {
"name": "clarify",
"description": "Ask the user a question when you need clarification, feedback, or a decision before proceeding. Supports two modes:\n\n1. **Multiple choice** — provide up to 4 choices. The user picks one or types their own answer via a 5th 'Other' option.\n2. **Open-ended** — omit choices entirely. The user types a free-form response.\n\nUse this tool when:\n- The task is ambiguous and you need the user to choose an approach\n- You want post-task feedback ('How did that work out?')\n- You want to offer to save a skill or update memory\n- A decision has meaningful trade-offs the user should weigh in on\n\nDo NOT use this tool for simple yes/no confirmation of dangerous commands (the terminal tool handles that). Prefer making a reasonable default choice yourself when the decision is low-stakes.",
"parameters": {
"type": "object",
"properties": {
"question": {
"type": "string",
"description": "The question to present to the user."
},
"choices": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 4,
"description": "Up to 4 answer choices. Omit this parameter entirely to ask an open-ended question. When provided, the UI automatically appends an 'Other (type your answer)' option."
}
},
"required": [
"question"
]
}
}
},
{
"type": "function",
"function": {
"name": "cronjob",
"description": "Manage scheduled cron jobs with a single compressed tool.\n\nUse action='create' to schedule a new job from a prompt or one or more skills.\nUse action='list' to inspect jobs.\nUse action='update', 'pause', 'resume', 'remove', or 'run' to manage an existing job.\n\nTo stop a job the user no longer wants: first action='list' to find the job_id, then action='remove' with that job_id. Never guess job IDs — always list first.\n\nJobs run in a fresh session with no current-chat context, so prompts must be self-contained.\nIf skills are provided on create, the future cron run loads those skills in order, then follows the prompt as the task instruction.\nOn update, passing skills=[] clears attached skills.\n\nNOTE: The agent's final response is auto-delivered to the target. Put the primary\nuser-facing content in the final response. Cron jobs run autonomously with no user\npresent — they cannot ask questions or request clarification.\n\nImportant safety rule: cron-run sessions should not recursively schedule more cron jobs.",
"parameters": {
"type": "object",
"properties": {
"action": {
"type": "string",
"description": "One of: create, list, update, pause, resume, remove, run"
},
"job_id": {
"type": "string",
"description": "Required for update/pause/resume/remove/run"
},
"prompt": {
"type": "string",
"description": "For create: the full self-contained prompt. If skills are also provided, this becomes the task instruction paired with those skills."
},
"schedule": {
"type": "string",
"description": "For create/update: '30m', 'every 2h', '0 9 * * *', or ISO timestamp"
},
"name": {
"type": "string",
"description": "Optional human-friendly name"
},
"repeat": {
"type": "integer",
"description": "Optional repeat count. Omit for defaults (once for one-shot, forever for recurring)."
},
"deliver": {
"type": "string",
"description": "Omit this parameter to auto-deliver back to the current chat and topic (recommended). Auto-detection preserves thread/topic context. Only set explicitly when the user asks to deliver somewhere OTHER than the current conversation. Values: 'origin' (same as omitting), 'local' (no delivery, save only), or platform:chat_id:thread_id for a specific destination. Examples: 'telegram:-1001234567890:17585', 'discord:#engineering', 'sms:+15551234567'. WARNING: 'platform:chat_id' without :thread_id loses topic targeting."
},
"skills": {
"type": "array",
"items": {
"type": "string"
},
"description": "Optional ordered list of skill names to load before executing the cron prompt. On update, pass an empty array to clear attached skills."
},
"model": {
"type": "object",
"description": "Optional per-job model override. If provider is omitted, the current main provider is pinned at creation time so the job stays stable.",
"properties": {
"provider": {
"type": "string",
"description": "Provider name (e.g. 'openrouter', 'anthropic', or 'custom:' for a provider defined in custom_providers config — always include the ':' suffix, never pass the bare 'custom'). Omit to use and pin the current provider."
},
"model": {
"type": "string",
"description": "Model name (e.g. 'anthropic/claude-sonnet-4', 'claude-sonnet-4')"
}
},
"required": [
"model"
]
},
"script": {
"type": "string",
"description": "Optional path to a script that runs each tick. In the default mode its stdout is injected into the agent's prompt as context (data-collection / change-detection pattern). With no_agent=True, the script IS the job and its stdout is delivered verbatim (classic watchdog pattern). Relative paths resolve under ~/.hermes/scripts/. ``.sh``/``.bash`` extensions run via bash, everything else via Python. On update, pass empty string to clear."
},
"no_agent": {
"type": "boolean",
"default": false,
"description": "Default: False (LLM-driven job — the agent runs the prompt each tick). Set True to skip the LLM entirely: the scheduler just runs ``script`` on schedule and delivers its stdout verbatim. No tokens, no agent loop, no model override honoured. \n\nREQUIREMENTS when True: ``script`` MUST be set (``prompt`` and ``skills`` are ignored). \n\nDELIVERY SEMANTICS when True: (a) non-empty stdout is sent verbatim as the message; (b) EMPTY stdout means SILENT — nothing is sent to the user and they won't see anything happened, so design your script to stay quiet when there's nothing to report (the watchdog pattern); (c) non-zero exit / timeout sends an error alert so a broken watchdog can't fail silently. \n\nWHEN TO USE True: recurring script-only pings where the script itself produces the exact message text (memory/disk/GPU watchdogs, threshold alerts, heartbeats, CI notifications, API pollers with a fixed output shape). WHEN TO USE False (default): anything that needs reasoning — summarize a feed, draft a daily briefing, pick interesting items, rephrase data for a human, follow conditional logic based on content."
},
"context_from": {
"type": "array",
"items": {
"type": "string"
},
"description": "Optional job ID or list of job IDs whose most recent completed output is injected into the prompt as context before each run. Use this to chain cron jobs: job A collects data, job B processes it. Each entry must be a valid job ID (from cronjob action='list'). Note: injects the most recent completed output — does not wait for upstream jobs running in the same tick. On update, pass an empty array to clear."
},
"enabled_toolsets": {
"type": "array",
"items": {
"type": "string"
},
"description": "Optional list of toolset names to restrict the job's agent to (e.g. [\"web\", \"terminal\", \"file\", \"delegation\"]). When set, only tools from these toolsets are loaded, significantly reducing input token overhead. When omitted, all default tools are loaded. Infer from the job's prompt — e.g. use \"web\" if it calls web_search, \"terminal\" if it runs scripts, \"file\" if it reads files, \"delegation\" if it calls delegate_task. On update, pass an empty array to clear."
},
"workdir": {
"type": "string",
"description": "Optional absolute path to run the job from. When set, AGENTS.md / CLAUDE.md / .cursorrules from that directory are injected into the system prompt, and the terminal/file/code_exec tools use it as their working directory — useful for running a job inside a specific project repo. Must be an absolute path that exists. When unset (default), preserves the original behaviour: no project context files, tools use the scheduler's cwd. On update, pass an empty string to clear. Jobs with workdir run sequentially (not parallel) to keep per-job directories isolated."
}
},
"required": [
"action"
]
}
}
},
{
"type": "function",
"function": {
"name": "delegate_task",
"description": "Spawn one or more subagents to work on tasks in isolated contexts. Each subagent gets its own conversation, terminal session, and toolset. Only the final summary is returned -- intermediate tool results never enter your context window.\n\nTWO MODES (one of 'goal' or 'tasks' is required):\n1. Single task: provide 'goal' (+ optional context, toolsets)\n2. Batch (parallel): provide 'tasks' array with up to delegation.max_concurrent_children items (default 3, configurable via config.yaml, no hard ceiling). All run concurrently and results are returned together. Nested delegation requires role='orchestrator' and delegation.max_spawn_depth >= 2.\n\nWHEN TO USE delegate_task:\n- Reasoning-heavy subtasks (debugging, code review, research synthesis)\n- Tasks that would flood your context with intermediate data\n- Parallel independent workstreams (research A and B simultaneously)\n\nWHEN NOT TO USE (use these instead):\n- Mechanical multi-step work with no reasoning needed -> use execute_code\n- Single tool call -> just call the tool directly\n- Tasks needing user interaction -> subagents cannot use clarify\n- Durable long-running work that must outlive the current turn -> use cronjob (action='create') or terminal(background=True, notify_on_complete=True) instead. delegate_task runs SYNCHRONOUSLY inside the parent turn: if the parent is interrupted (user sends a new message, /stop, /new) the child is cancelled with status='interrupted' and its work is discarded. Children cannot continue in the background.\n\nIMPORTANT:\n- Subagents have NO memory of your conversation. Pass all relevant info (file paths, error messages, constraints) via the 'context' field.\n- If the user is writing in a non-English language, or asked for output in a specific language / tone / style, say so in 'context' (e.g. \"respond in Chinese\", \"return output in Japanese\"). Otherwise subagents default to English and their summaries will contaminate your final reply with the wrong language.\n- Subagent summaries are SELF-REPORTS, not verified facts. A subagent that claims \"uploaded successfully\" or \"file written\" may be wrong. For operations with external side-effects (HTTP POST/PUT, remote writes, file creation at shared paths, publishing), require the subagent to return a verifiable handle (URL, ID, absolute path, HTTP status) and verify it yourself — fetch the URL, stat the file, read back the content — before telling the user the operation succeeded.\n- Leaf subagents (role='leaf', the default) CANNOT call: delegate_task, clarify, memory, send_message, execute_code.\n- Orchestrator subagents (role='orchestrator') retain delegate_task so they can spawn their own workers, but still cannot use clarify, memory, send_message, or execute_code. Orchestrators are bounded by delegation.max_spawn_depth (default 2) and can be disabled globally via delegation.orchestrator_enabled=false.\n- Each subagent gets its own terminal session (separate working directory and state).\n- Results are always returned as an array, one entry per task.",
"parameters": {
"type": "object",
"properties": {
"goal": {
"type": "string",
"description": "What the subagent should accomplish. Be specific and self-contained -- the subagent knows nothing about your conversation history."
},
"context": {
"type": "string",
"description": "Background information the subagent needs: file paths, error messages, project structure, constraints. The more specific you are, the better the subagent performs."
},
"toolsets": {
"type": "array",
"items": {
"type": "string"
},
"description": "Toolsets to enable for this subagent. Default: inherits your enabled toolsets. Available toolsets: 'browser', 'cronjob', 'discord', 'discord_admin', 'feishu_doc', 'feishu_drive', 'file', 'homeassistant', 'image_gen', 'kanban', 'search', 'session_search', 'skills', 'spotify', 'terminal', 'todo', 'tts', 'video', 'vision', 'web', 'yuanbao'. Common patterns: ['terminal', 'file'] for code work, ['web'] for research, ['browser'] for web interaction, ['terminal', 'file', 'web'] for full-stack tasks."
},
"tasks": {
"type": "array",
"items": {
"type": "object",
"properties": {
"goal": {
"type": "string",
"description": "Task goal"
},
"context": {
"type": "string",
"description": "Task-specific context"
},
"toolsets": {
"type": "array",
"items": {
"type": "string"
},
"description": "Toolsets for this specific task. Available: 'browser', 'cronjob', 'discord', 'discord_admin', 'feishu_doc', 'feishu_drive', 'file', 'homeassistant', 'image_gen', 'kanban', 'search', 'session_search', 'skills', 'spotify', 'terminal', 'todo', 'tts', 'video', 'vision', 'web', 'yuanbao'. Use 'web' for network access, 'terminal' for shell, 'browser' for web interaction."
},
"acp_command": {
"type": "string",
"description": "Per-task ACP command override (e.g. 'claude'). Overrides the top-level acp_command for this task only."
},
"acp_args": {
"type": "array",
"items": {
"type": "string"
},
"description": "Per-task ACP args override."
},
"role": {
"type": "string",
"enum": [
"leaf",
"orchestrator"
],
"description": "Per-task role override. See top-level 'role' for semantics."
}
},
"required": [
"goal"
]
},
"description": "Batch mode: tasks to run in parallel (limit configurable via delegation.max_concurrent_children, default 3). Each gets its own subagent with isolated context and terminal session. When provided, top-level goal/context/toolsets are ignored."
},
"role": {
"type": "string",
"enum": [
"leaf",
"orchestrator"
],
"description": "Role of the child agent. 'leaf' (default) = focused worker, cannot delegate further. 'orchestrator' = can use delegate_task to spawn its own workers. Requires delegation.max_spawn_depth >= 2 in config; ignored (treated as 'leaf') when the child would exceed max_spawn_depth or when delegation.orchestrator_enabled=false."
},
"acp_command": {
"type": "string",
"description": "Override ACP command for child agents (e.g. 'claude', 'copilot'). When set, children use ACP subprocess transport instead of inheriting the parent's transport. Enables spawning Claude Code (claude --acp --stdio) or other ACP-capable agents from any parent, including Discord/Telegram/CLI."
},
"acp_args": {
"type": "array",
"items": {
"type": "string"
},
"description": "Arguments for the ACP command (default: ['--acp', '--stdio']). Only used when acp_command is set. Example: ['--acp', '--stdio', '--model', 'claude-opus-4-6']"
}
}
}
}
},
{
"type": "function",
"function": {
"name": "execute_code",
"description": "Run a Python script that can call Hermes tools programmatically. Use this when you need 3+ tool calls with processing logic between them, need to filter/reduce large tool outputs before they enter your context, need conditional branching (if X then Y else Z), or need to loop (fetch N pages, process N files, retry on failure).\n\nUse normal tool calls instead when: single tool call with no processing, you need to see the full result and apply complex reasoning, or the task requires interactive user input.\n\nAvailable via `from hermes_tools import ...`:\n\n read_file(path: str, offset: int = 1, limit: int = 500) -> dict\n Lines are 1-indexed. Returns {\"content\": \"...\", \"total_lines\": N}\n write_file(path: str, content: str) -> dict\n Always overwrites the entire file.\n search_files(pattern: str, target=\"content\", path=\".\", file_glob=None, limit=50) -> dict\n target: \"content\" (search inside files) or \"files\" (find files by name). Returns {\"matches\": [...]}\n patch(path: str, old_string: str, new_string: str, replace_all: bool = False) -> dict\n Replaces old_string with new_string in the file.\n terminal(command: str, timeout=None, workdir=None) -> dict\n Foreground only (no background/pty). Returns {\"output\": \"...\", \"exit_code\": N}\n\nLimits: 5-minute timeout, 50KB stdout cap, max 50 tool calls per script. terminal() is foreground-only (no background or pty).\n\nScripts run in the session's working directory with the active venv's python, so project deps (pandas, etc.) and relative paths work like in terminal().\n\nPrint your final result to stdout. Use Python stdlib (json, re, math, csv, datetime, collections, etc.) for processing between tool calls.\n\nAlso available (no import needed — built into hermes_tools):\n json_parse(text: str) — json.loads with strict=False; use for terminal() output with control chars\n shell_quote(s: str) — shlex.quote(); use when interpolating dynamic strings into shell commands\n retry(fn, max_attempts=3, delay=2) — retry with exponential backoff for transient failures",
"parameters": {
"type": "object",
"properties": {
"code": {
"type": "string",
"description": "Python code to execute. Import tools with `from hermes_tools import terminal, ...` and print your final result to stdout."
}
},
"required": [
"code"
]
}
}
},
{
"type": "function",
"function": {
"name": "feishu_doc_read",
"description": "Read the full content of a Feishu/Lark document as plain text. Useful when you need more context beyond the quoted text in a comment.",
"parameters": {
"type": "object",
"properties": {
"doc_token": {
"type": "string",
"description": "The document token (from the document URL or comment context)."
}
},
"required": [
"doc_token"
]
}
}
},
{
"type": "function",
"function": {
"name": "feishu_drive_add_comment",
"description": "Add a new whole-document comment on a Feishu document. Use this for whole-document comments or as a fallback when reply_comment fails with code 1069302.",
"parameters": {
"type": "object",
"properties": {
"file_token": {
"type": "string",
"description": "The document file token."
},
"content": {
"type": "string",
"description": "The comment text content (plain text only, no markdown)."
},
"file_type": {
"type": "string",
"description": "File type (default: docx).",
"default": "docx"
}
},
"required": [
"file_token",
"content"
]
}
}
},
{
"type": "function",
"function": {
"name": "feishu_drive_list_comment_replies",
"description": "List all replies in a comment thread on a Feishu document.",
"parameters": {
"type": "object",
"properties": {
"file_token": {
"type": "string",
"description": "The document file token."
},
"comment_id": {
"type": "string",
"description": "The comment ID to list replies for."
},
"file_type": {
"type": "string",
"description": "File type (default: docx).",
"default": "docx"
},
"page_size": {
"type": "integer",
"description": "Number of replies per page (max 100).",
"default": 100
},
"page_token": {
"type": "string",
"description": "Pagination token for next page."
}
},
"required": [
"file_token",
"comment_id"
]
}
}
},
{
"type": "function",
"function": {
"name": "feishu_drive_list_comments",
"description": "List comments on a Feishu document. Use is_whole=true to list whole-document comments only.",
"parameters": {
"type": "object",
"properties": {
"file_token": {
"type": "string",
"description": "The document file token."
},
"file_type": {
"type": "string",
"description": "File type (default: docx).",
"default": "docx"
},
"is_whole": {
"type": "boolean",
"description": "If true, only return whole-document comments.",
"default": false
},
"page_size": {
"type": "integer",
"description": "Number of comments per page (max 100).",
"default": 100
},
"page_token": {
"type": "string",
"description": "Pagination token for next page."
}
},
"required": [
"file_token"
]
}
}
},
{
"type": "function",
"function": {
"name": "feishu_drive_reply_comment",
"description": "Reply to a local comment thread on a Feishu document. Use this for local (quoted-text) comments. For whole-document comments, use feishu_drive_add_comment instead.",
"parameters": {
"type": "object",
"properties": {
"file_token": {
"type": "string",
"description": "The document file token."
},
"comment_id": {
"type": "string",
"description": "The comment ID to reply to."
},
"content": {
"type": "string",
"description": "The reply text content (plain text only, no markdown)."
},
"file_type": {
"type": "string",
"description": "File type (default: docx).",
"default": "docx"
}
},
"required": [
"file_token",
"comment_id",
"content"
]
}
}
},
{
"type": "function",
"function": {
"name": "memory",
"description": "Save durable information to persistent memory that survives across sessions. Memory is injected into future turns, so keep it compact and focused on facts that will still matter later.\n\nWHEN TO SAVE (do this proactively, don't wait to be asked):\n- User corrects you or says 'remember this' / 'don't do that again'\n- User shares a preference, habit, or personal detail (name, role, timezone, coding style)\n- You discover something about the environment (OS, installed tools, project structure)\n- You learn a convention, API quirk, or workflow specific to this user's setup\n- You identify a stable fact that will be useful again in future sessions\n\nPRIORITY: User preferences and corrections > environment facts > procedural knowledge. The most valuable memory prevents the user from having to repeat themselves.\n\nDo NOT save task progress, session outcomes, completed-work logs, or temporary TODO state to memory; use session_search to recall those from past transcripts.\nIf you've discovered a new way to do something, solved a problem that could be necessary later, save it as a skill with the skill tool.\n\nTWO TARGETS:\n- 'user': who the user is -- name, role, preferences, communication style, pet peeves\n- 'memory': your notes -- environment facts, project conventions, tool quirks, lessons learned\n\nACTIONS: add (new entry), replace (update existing -- old_text identifies it), remove (delete -- old_text identifies it).\n\nSKIP: trivial/obvious info, things easily re-discovered, raw data dumps, and temporary task state.",
"parameters": {
"type": "object",
"properties": {
"action": {
"type": "string",
"enum": [
"add",
"replace",
"remove"
],
"description": "The action to perform."
},
"target": {
"type": "string",
"enum": [
"memory",
"user"
],
"description": "Which memory store: 'memory' for personal notes, 'user' for user profile."
},
"content": {
"type": "string",
"description": "The entry content. Required for 'add' and 'replace'."
},
"old_text": {
"type": "string",
"description": "Short unique substring identifying the entry to replace or remove."
}
},
"required": [
"action",
"target"
]
}
}
},
{
"type": "function",
"function": {
"name": "patch",
"description": "Targeted find-and-replace edits in files. Use this instead of sed/awk in terminal. Uses fuzzy matching (9 strategies) so minor whitespace/indentation differences won't break it. Returns a unified diff. Auto-runs syntax checks after editing.\n\nReplace mode (default): find a unique string and replace it.\nPatch mode: apply V4A multi-file patches for bulk changes.",
"parameters": {
"type": "object",
"properties": {
"mode": {
"type": "string",
"enum": [
"replace",
"patch"
],
"description": "Edit mode: 'replace' for targeted find-and-replace, 'patch' for V4A multi-file patches",
"default": "replace"
},
"path": {
"type": "string",
"description": "File path to edit (required for 'replace' mode)"
},
"old_string": {
"type": "string",
"description": "Text to find in the file (required for 'replace' mode). Must be unique in the file unless replace_all=true. Include enough surrounding context to ensure uniqueness."
},
"new_string": {
"type": "string",
"description": "Replacement text (required for 'replace' mode). Can be empty string to delete the matched text."
},
"replace_all": {
"type": "boolean",
"description": "Replace all occurrences instead of requiring a unique match (default: false)",
"default": false
},
"patch": {
"type": "string",
"description": "V4A format patch content (required for 'patch' mode). Format:\n*** Begin Patch\n*** Update File: path/to/file\n@@ context hint @@\n context line\n-removed line\n+added line\n*** End Patch"
}
},
"required": [
"mode"
]
}
}
},
{
"type": "function",
"function": {
"name": "process",
"description": "Manage background processes started with terminal(background=true). Actions: 'list' (show all), 'poll' (check status + new output), 'log' (full output with pagination), 'wait' (block until done or timeout), 'kill' (terminate), 'write' (send raw stdin data without newline), 'submit' (send data + Enter, for answering prompts), 'close' (close stdin/send EOF).",
"parameters": {
"type": "object",
"properties": {
"action": {
"type": "string",
"enum": [
"list",
"poll",
"log",
"wait",
"kill",
"write",
"submit",
"close"
],
"description": "Action to perform on background processes"
},
"session_id": {
"type": "string",
"description": "Process session ID (from terminal background output). Required for all actions except 'list'."
},
"data": {
"type": "string",
"description": "Text to send to process stdin (for 'write' and 'submit' actions)"
},
"timeout": {
"type": "integer",
"description": "Max seconds to block for 'wait' action. Returns partial output on timeout.",
"minimum": 1
},
"offset": {
"type": "integer",
"description": "Line offset for 'log' action (default: last 200 lines)"
},
"limit": {
"type": "integer",
"description": "Max lines to return for 'log' action",
"minimum": 1
}
},
"required": [
"action"
]
}
}
},
{
"type": "function",
"function": {
"name": "read_file",
"description": "Read a text file with line numbers and pagination. Use this instead of cat/head/tail in terminal. Output format: 'LINE_NUM|CONTENT'. Suggests similar filenames if not found. Use offset and limit for large files. Reads exceeding ~100K characters are rejected; use offset and limit to read specific sections of large files. NOTE: Cannot read images or binary files — use vision_analyze for images.",
"parameters": {
"type": "object",
"properties": {
"path": {
"type": "string",
"description": "Path to the file to read (absolute, relative, or ~/path)"
},
"offset": {
"type": "integer",
"description": "Line number to start reading from (1-indexed, default: 1)",
"default": 1,
"minimum": 1
},
"limit": {
"type": "integer",
"description": "Maximum number of lines to read (default: 500, max: 2000)",
"default": 500,
"maximum": 2000
}
},
"required": [
"path"
]
}
}
},
{
"type": "function",
"function": {
"name": "search_files",
"description": "Search file contents or find files by name. Use this instead of grep/rg/find/ls in terminal. Ripgrep-backed, faster than shell equivalents.\n\nContent search (target='content'): Regex search inside files. Output modes: full matches with line numbers, file paths only, or match counts.\n\nFile search (target='files'): Find files by glob pattern (e.g., '*.py', '*config*'). Also use this instead of ls — results sorted by modification time.",
"parameters": {
"type": "object",
"properties": {
"pattern": {
"type": "string",
"description": "Regex pattern for content search, or glob pattern (e.g., '*.py') for file search"
},
"target": {
"type": "string",
"enum": [
"content",
"files"
],
"description": "'content' searches inside file contents, 'files' searches for files by name",
"default": "content"
},
"path": {
"type": "string",
"description": "Directory or file to search in (default: current working directory)",
"default": "."
},
"file_glob": {
"type": "string",
"description": "Filter files by pattern in grep mode (e.g., '*.py' to only search Python files)"
},
"limit": {
"type": "integer",
"description": "Maximum number of results to return (default: 50)",
"default": 50
},
"offset": {
"type": "integer",
"description": "Skip first N results for pagination (default: 0)",
"default": 0
},
"output_mode": {
"type": "string",
"enum": [
"content",
"files_only",
"count"
],
"description": "Output format for grep mode: 'content' shows matching lines with line numbers, 'files_only' lists file paths, 'count' shows match counts per file",
"default": "content"
},
"context": {
"type": "integer",
"description": "Number of context lines before and after each match (grep mode only)",
"default": 0
}
},
"required": [
"pattern"
]
}
}
},
{
"type": "function",
"function": {
"name": "send_message",
"description": "Send a message to a connected messaging platform, or list available targets.\n\nIMPORTANT: When the user asks to send to a specific channel or person (not just a bare platform name), call send_message(action='list') FIRST to see available targets, then send to the correct one.\nIf the user just says a platform name like 'send to telegram', send directly to the home channel without listing first.",
"parameters": {
"type": "object",
"properties": {
"action": {
"type": "string",
"enum": [
"send",
"list"
],
"description": "Action to perform. 'send' (default) sends a message. 'list' returns all available channels/contacts across connected platforms."
},
"target": {
"type": "string",
"description": "Delivery target. Format: 'platform' (uses home channel), 'platform:#channel-name', 'platform:chat_id', or 'platform:chat_id:thread_id' for Telegram topics and Discord threads. Examples: 'telegram', 'telegram:-1001234567890:17585', 'discord:999888777:555444333', 'discord:#bot-home', 'slack:#engineering', 'signal:+155****4567', 'matrix:!roomid:server.org', 'matrix:@user:server.org', 'yuanbao:direct:' (DM), 'yuanbao:group:' (group chat)"
},
"message": {
"type": "string",
"description": "The message text to send. To send an image or file, include MEDIA: (e.g. 'MEDIA:/tmp/hermes/cache/img_xxx.jpg') in the message — the platform will deliver it as a native media attachment."
}
}
}
}
},
{
"type": "function",
"function": {
"name": "session_search",
"description": "Search your long-term memory of past conversations, or browse recent sessions. This is your recall -- every past session is searchable, and this tool summarizes what happened.\n\nTWO MODES:\n1. Recent sessions (no query): Call with no arguments to see what was worked on recently. Returns titles, previews, and timestamps. Zero LLM cost, instant. Start here when the user asks what were we working on or what did we do recently.\n2. Keyword search (with query): Search for specific topics across all past sessions. Returns LLM-generated summaries of matching sessions.\n\nUSE THIS PROACTIVELY when:\n- The user says 'we did this before', 'remember when', 'last time', 'as I mentioned'\n- The user asks about a topic you worked on before but don't have in current context\n- The user references a project, person, or concept that seems familiar but isn't in memory\n- You want to check if you've solved a similar problem before\n- The user asks 'what did we do about X?' or 'how did we fix Y?'\n\nDon't hesitate to search when it is actually cross-session -- it's fast and cheap. Better to search and confirm than to guess or ask the user to repeat themselves.\n\nSearch syntax: keywords joined with OR for broad recall (elevenlabs OR baseten OR funding), phrases for exact match (\"docker networking\"), boolean (python NOT java), prefix (deploy*). IMPORTANT: Use OR between keywords for best results — FTS5 defaults to AND which misses sessions that only mention some terms. If a broad OR query returns nothing, try individual keyword searches in parallel. Returns summaries of the top matching sessions.",
"parameters": {
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Search query — keywords, phrases, or boolean expressions to find in past sessions. Omit this parameter entirely to browse recent sessions instead (returns titles, previews, timestamps with no LLM cost)."
},
"role_filter": {
"type": "string",
"description": "Optional: only search messages from specific roles (comma-separated). E.g. 'user,assistant' to skip tool outputs."
},
"limit": {
"type": "integer",
"description": "Max sessions to summarize (default: 3, max: 5).",
"default": 3
}
}
}
}
},
{
"type": "function",
"function": {
"name": "skill_manage",
"description": "Manage skills (create, update, delete). Skills are your procedural memory — reusable approaches for recurring task types. New skills go to ~/.hermes/skills/; existing skills can be modified wherever they live.\n\nActions: create (full SKILL.md + optional category), patch (old_string/new_string — preferred for fixes), edit (full SKILL.md rewrite — major overhauls only), delete, write_file, remove_file.\n\nOn delete, pass `absorbed_into=` when you're merging this skill's content into another one, or `absorbed_into=\"\"` when you're pruning it with no forwarding target. This lets the curator tell consolidation from pruning without guessing, so downstream consumers (cron jobs that reference the old skill name, etc.) get updated correctly. The target you name in `absorbed_into` must already exist — create/patch the umbrella first, then delete.\n\nCreate when: complex task succeeded (5+ calls), errors overcome, user-corrected approach worked, non-trivial workflow discovered, or user asks you to remember a procedure.\nUpdate when: instructions stale/wrong, OS-specific failures, missing steps or pitfalls found during use. If you used a skill and hit issues not covered by it, patch it immediately.\n\nAfter difficult/iterative tasks, offer to save as a skill. Skip for simple one-offs. Confirm with user before creating/deleting.\n\nGood skills: trigger conditions, numbered steps with exact commands, pitfalls section, verification steps. Use skill_view() to see format examples.\n\nPinned skills are protected from deletion only — skill_manage(action='delete') will refuse with a message pointing the user to `hermes curator unpin `. Patches and edits go through on pinned skills so you can still improve them as pitfalls come up; pin only guards against irrecoverable loss.",
"parameters": {
"type": "object",
"properties": {
"action": {
"type": "string",
"enum": [
"create",
"patch",
"edit",
"delete",
"write_file",
"remove_file"
],
"description": "The action to perform."
},
"name": {
"type": "string",
"description": "Skill name (lowercase, hyphens/underscores, max 64 chars). Must match an existing skill for patch/edit/delete/write_file/remove_file."
},
"content": {
"type": "string",
"description": "Full SKILL.md content (YAML frontmatter + markdown body). Required for 'create' and 'edit'. For 'edit', read the skill first with skill_view() and provide the complete updated text."
},
"old_string": {
"type": "string",
"description": "Text to find in the file (required for 'patch'). Must be unique unless replace_all=true. Include enough surrounding context to ensure uniqueness."
},
"new_string": {
"type": "string",
"description": "Replacement text (required for 'patch'). Can be empty string to delete the matched text."
},
"replace_all": {
"type": "boolean",
"description": "For 'patch': replace all occurrences instead of requiring a unique match (default: false)."
},
"category": {
"type": "string",
"description": "Optional category/domain for organizing the skill (e.g., 'devops', 'data-science', 'mlops'). Creates a subdirectory grouping. Only used with 'create'."
},
"file_path": {
"type": "string",
"description": "Path to a supporting file within the skill directory. For 'write_file'/'remove_file': required, must be under references/, templates/, scripts/, or assets/. For 'patch': optional, defaults to SKILL.md if omitted."
},
"file_content": {
"type": "string",
"description": "Content for the file. Required for 'write_file'."
},
"absorbed_into": {
"type": "string",
"description": "For 'delete' only — declares intent so the curator can tell consolidation from pruning without guessing. Pass the umbrella skill name when this skill's content was merged into another (the target must already exist). Pass an empty string when the skill is truly stale and being pruned with no forwarding target. Omitting the arg on delete is supported for backward compatibility but downstream tooling (e.g. cron-job skill reference rewriting) will have to guess at intent."
}
},
"required": [
"action",
"name"
]
}
}
},
{
"type": "function",
"function": {
"name": "skill_view",
"description": "Skills allow for loading information about specific tasks and workflows, as well as scripts and templates. Load a skill's full content or access its linked files (references, templates, scripts). First call returns SKILL.md content plus a 'linked_files' dict showing available references/templates/scripts. To access those, call again with file_path parameter.",
"parameters": {
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "The skill name (use skills_list to see available skills). For plugin-provided skills, use the qualified form 'plugin:skill' (e.g. 'superpowers:writing-plans')."
},
"file_path": {
"type": "string",
"description": "OPTIONAL: Path to a linked file within the skill (e.g., 'references/api.md', 'templates/config.yaml', 'scripts/validate.py'). Omit to get the main SKILL.md content."
}
},
"required": [
"name"
]
}
}
},
{
"type": "function",
"function": {
"name": "skills_list",
"description": "List available skills (name + description). Use skill_view(name) to load full content.",
"parameters": {
"type": "object",
"properties": {
"category": {
"type": "string",
"description": "Optional category filter to narrow results"
}
}
}
}
},
{
"type": "function",
"function": {
"name": "terminal",
"description": "Execute shell commands on a Linux environment. Filesystem usually persists between calls.\n\nDo NOT use cat/head/tail to read files — use read_file instead.\nDo NOT use grep/rg/find to search — use search_files instead.\nDo NOT use ls to list directories — use search_files(target='files') instead.\nDo NOT use sed/awk to edit files — use patch instead.\nDo NOT use echo/cat heredoc to create files — use write_file instead.\nReserve terminal for: builds, installs, git, processes, scripts, network, package managers, and anything that needs a shell.\n\nForeground (default): Commands return INSTANTLY when done, even if the timeout is high. Set timeout=300 for long builds/scripts — you'll still get the result in seconds if it's fast. Prefer foreground for short commands.\nBackground: Set background=true to get a session_id. Two patterns:\n (1) Long-lived processes that never exit (servers, watchers).\n (2) Long-running tasks with notify_on_complete=true — you can keep working on other things and the system auto-notifies you when the task finishes. Great for test suites, builds, deployments, or anything that takes more than a minute.\nFor servers/watchers, do NOT use shell-level background wrappers (nohup/disown/setsid/trailing '&') in foreground mode. Use background=true so Hermes can track lifecycle and output.\nAfter starting a server, verify readiness with a health check or log signal, then run tests in a separate terminal() call. Avoid blind sleep loops.\nUse process(action=\"poll\") for progress checks, process(action=\"wait\") to block until done.\nWorking directory: Use 'workdir' for per-command cwd.\nPTY mode: Set pty=true for interactive CLI tools (Codex, Claude Code, Python REPL).\n\nDo NOT use vim/nano/interactive tools without pty=true — they hang without a pseudo-terminal. Pipe git output to cat if it might page.\n",
"parameters": {
"type": "object",
"properties": {
"command": {
"type": "string",
"description": "The command to execute on the VM"
},
"background": {
"type": "boolean",
"description": "Run the command in the background. Two patterns: (1) Long-lived processes that never exit (servers, watchers). (2) Long-running tasks paired with notify_on_complete=true — you can keep working and get notified when the task finishes. For short commands, prefer foreground with a generous timeout instead.",
"default": false
},
"timeout": {
"type": "integer",
"description": "Max seconds to wait (default: 180, foreground max: 600). Returns INSTANTLY when command finishes — set high for long tasks, you won't wait unnecessarily. Foreground timeout above 600s is rejected; use background=true for longer commands.",
"minimum": 1
},
"workdir": {
"type": "string",
"description": "Working directory for this command (absolute path). Defaults to the session working directory."
},
"pty": {
"type": "boolean",
"description": "Run in pseudo-terminal (PTY) mode for interactive CLI tools like Codex, Claude Code, or Python REPL. Only works with local and SSH backends. Default: false.",
"default": false
},
"notify_on_complete": {
"type": "boolean",
"description": "When true (and background=true), you'll be automatically notified exactly once when the process finishes. **This is the right choice for almost every long-running task** — tests, builds, deployments, multi-item batch jobs, anything that takes over a minute and has a defined end. Use this and keep working on other things; the system notifies you on exit. MUTUALLY EXCLUSIVE with watch_patterns — when both are set, watch_patterns is dropped.",
"default": false
},
"watch_patterns": {
"type": "array",
"items": {
"type": "string"
},
"description": "Strings to watch for in background process output. HARD RATE LIMIT: at most 1 notification per 15 seconds per process — matches arriving inside the cooldown are dropped. After 3 consecutive 15-second windows with dropped matches, watch_patterns is automatically disabled for that process and promoted to notify_on_complete behavior (one notification on exit, no more mid-process spam). USE ONLY for truly rare, one-shot mid-process signals on LONG-LIVED processes that will never exit on their own — e.g. ['Application startup complete'] on a server so you know when to hit its endpoint, or ['migration done'] on a daemon. DO NOT use for: (1) end-of-run markers like 'DONE'/'PASS' — use notify_on_complete instead; (2) error patterns like 'ERROR'/'Traceback' in loops or multi-item batch jobs — they fire on every iteration and you'll hit the strike limit fast; (3) anything you'd ever combine with notify_on_complete. When in doubt, choose notify_on_complete. MUTUALLY EXCLUSIVE with notify_on_complete — set one, not both."
}
},
"required": [
"command"
]
}
}
},
{
"type": "function",
"function": {
"name": "text_to_speech",
"description": "Convert text to speech audio. Returns a MEDIA: path that the platform delivers as native audio. Compatible providers render as a voice bubble on Telegram; otherwise audio is sent as a regular attachment. In CLI mode, saves to ~/voice-memos/. Voice and provider are user-configured (built-in providers like edge/openai or custom command providers under tts.providers.), not model-selected.",
"parameters": {
"type": "object",
"properties": {
"text": {
"type": "string",
"description": "The text to convert to speech. Provider-specific character caps apply and are enforced automatically (OpenAI 4096, xAI 15000, MiniMax 10000, ElevenLabs 5k-40k depending on model); over-long input is truncated."
},
"output_path": {
"type": "string",
"description": "Optional custom file path to save the audio. Defaults to ~/.hermes/audio_cache/.mp3"
}
},
"required": [
"text"
]
}
}
},
{
"type": "function",
"function": {
"name": "todo",
"description": "Manage your task list for the current session. Use for complex tasks with 3+ steps or when the user provides multiple tasks. Call with no parameters to read the current list.\n\nWriting:\n- Provide 'todos' array to create/update items\n- merge=false (default): replace the entire list with a fresh plan\n- merge=true: update existing items by id, add any new ones\n\nEach item: {id: string, content: string, status: pending|in_progress|completed|cancelled}\nList order is priority. Only ONE item in_progress at a time.\nMark items completed immediately when done. If something fails, cancel it and add a revised item.\n\nAlways returns the full current list.",
"parameters": {
"type": "object",
"properties": {
"todos": {
"type": "array",
"description": "Task items to write. Omit to read current list.",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Unique item identifier"
},
"content": {
"type": "string",
"description": "Task description"
},
"status": {
"type": "string",
"enum": [
"pending",
"in_progress",
"completed",
"cancelled"
],
"description": "Current status"
}
},
"required": [
"id",
"content",
"status"
]
}
},
"merge": {
"type": "boolean",
"description": "true: update existing items by id, add new ones. false (default): replace the entire list.",
"default": false
}
}
}
}
},
{
"type": "function",
"function": {
"name": "video_analyze",
"description": "Analyze a video from a URL or local file path using a multimodal AI model. Sends the video to a video-capable model (e.g. Gemini) for understanding. Use this for video files — for images, use vision_analyze instead. Supports mp4, webm, mov, avi, mkv, mpeg formats. Note: large videos (>20 MB) may be slow; max ~50 MB.",
"parameters": {
"type": "object",
"properties": {
"video_url": {
"type": "string",
"description": "Video URL (http/https) or local file path to analyze."
},
"question": {
"type": "string",
"description": "Your specific question about the video. The AI will describe what happens in the video and answer your question."
}
},
"required": [
"video_url",
"question"
]
}
}
},
{
"type": "function",
"function": {
"name": "vision_analyze",
"description": "Inspect an image from a URL, file path, or tool output when you need closer detail than what's visible in the conversation. If the user's image is already attached to the conversation and you can see it, just answer directly — only call this tool for images referenced by URL/path, images returned inside other tool results (browser screenshots, search thumbnails), or when you need a deeper look at a specific region the main model's vision may have missed.",
"parameters": {
"type": "object",
"properties": {
"image_url": {
"type": "string",
"description": "Image URL (http/https) or local file path to analyze."
},
"question": {
"type": "string",
"description": "Your specific question or request about the image to resolve. The AI will automatically provide a complete image description AND answer your specific question."
}
},
"required": [
"image_url",
"question"
]
}
}
},
{
"type": "function",
"function": {
"name": "write_file",
"description": "Write content to a file, completely replacing existing content. Use this instead of echo/cat heredoc in terminal. Creates parent directories automatically. OVERWRITES the entire file — use 'patch' for targeted edits. Auto-runs syntax checks on .py/.json/.yaml/.toml and other linted languages; only NEW errors introduced by this write are surfaced (pre-existing errors are filtered out).",
"parameters": {
"type": "object",
"properties": {
"path": {
"type": "string",
"description": "Path to the file to write (will be created if it doesn't exist, overwritten if it does)"
},
"content": {
"type": "string",
"description": "Complete content to write to the file"
}
},
"required": [
"path",
"content"
]
}
}
}
],
"message_count": 78,
"messages": [
{
"role": "user",
"content": "You are running as Hermes' background skill CURATOR. This is an UMBRELLA-BUILDING consolidation pass, not a passive audit and not a duplicate-finder.\n\nThe goal of the skill collection is a LIBRARY OF CLASS-LEVEL INSTRUCTIONS AND EXPERIENTIAL KNOWLEDGE. A collection of hundreds of narrow skills where each one captures one session's specific bug is a FAILURE of the library — not a feature. An agent searching skills matches on descriptions, not on exact names; one broad umbrella skill with labeled subsections beats five narrow siblings for discoverability, not the other way around.\n\nThe right target shape is CLASS-LEVEL skills with rich SKILL.md bodies + `references/`, `templates/`, and `scripts/` subfiles for session-specific detail — not one-session-one-skill micro-entries.\n\nHard rules — do not violate:\n1. DO NOT touch bundled or hub-installed skills. The candidate list below is already filtered to agent-created skills only.\n2. DO NOT delete any skill. Archiving (moving the skill's directory into ~/.hermes/skills/.archive/) is the maximum destructive action. Archives are recoverable; deletion is not.\n3. DO NOT touch skills shown as pinned=yes. Skip them entirely.\n4. DO NOT use usage counters as a reason to skip consolidation. The counters are new and often mostly zero. Judge overlap on CONTENT, not on use_count. 'use=0' is not evidence a skill is valuable; it's absence of evidence either way.\n5. DO NOT reject consolidation on the grounds that 'each skill has a distinct trigger'. Pairwise distinctness is the wrong bar. The right bar is: 'would a human maintainer write this as N separate skills, or as one skill with N labeled subsections?' When the answer is the latter, merge.\n\nHow to work — not optional:\n1. Scan the full candidate list. Identify PREFIX CLUSTERS (skills sharing a first word or domain keyword). Examples you are likely to find: hermes-config-*, hermes-dashboard-*, gateway-*, codex-*, ollama-*, anthropic-*, gemini-*, mcp-*, salvage-*, pr-*, competitor-*, python-*, security-*, etc. Expect 10-25 clusters.\n2. For each cluster with 2+ members, do NOT ask 'are these pairs overlapping?' — ask 'what is the UMBRELLA CLASS these skills all serve? Would a maintainer name that class and write one skill for it?' If yes, pick (or create) the umbrella and absorb the siblings into it.\n3. Three ways to consolidate — use the right one per cluster:\n a. MERGE INTO EXISTING UMBRELLA — one skill in the cluster is already broad enough to be the umbrella (example: `pr-triage-salvage` for the PR review cluster). Patch it to add a labeled section for each sibling's unique insight, then archive the siblings.\n b. CREATE A NEW UMBRELLA SKILL.md — no existing member is broad enough. Use skill_manage action=create to write a new class-level skill whose SKILL.md covers the shared workflow and has short labeled subsections. Archive the now-absorbed narrow siblings.\n c. DEMOTE TO REFERENCES/TEMPLATES/SCRIPTS — a sibling has narrow-but-valuable session-specific content. Move it into the umbrella's appropriate support directory:\n • `references/.md` for session-specific detail OR condensed knowledge banks (quoted research, API docs excerpts, domain notes, provider quirks, reproduction recipes)\n • `templates/.` for starter files meant to be copied and modified\n • `scripts/.` for statically re-runnable actions (verification scripts, fixture generators, probes)\n Then archive the old sibling. Use `terminal` with `mkdir -p ~/.hermes/skills//references/ && mv ... /references/.md` (or templates/ / scripts/).\n4. Also flag skills whose NAME is too narrow (contains a PR number, a feature codename, a specific error string, an 'audit' / 'diagnosis' / 'salvage' session artifact). These almost always belong as a subsection or support file under a class-level umbrella.\n5. Iterate. After one consolidation round, scan the remaining set and look for the NEXT umbrella opportunity. Don't stop after 3 merges.\n\nYour toolset:\n - skills_list, skill_view — read the current landscape\n - skill_manage action=patch — add sections to the umbrella\n - skill_manage action=create — create a new umbrella SKILL.md\n - skill_manage action=write_file — add a references/, templates/, or scripts/ file under an existing skill (the skill must already exist)\n - skill_manage action=delete — archive a skill. MUST pass `absorbed_into=` when you've merged its content into another skill, or `absorbed_into=\"\"` when you're truly pruning with no forwarding target. This drives cron-job skill-reference migration — guessing from your YAML summary after the fact is fragile.\n - terminal — mv a sibling into the archive OR move its content into a support subfile\n\n'keep' is a legitimate decision ONLY when the skill is already a class-level umbrella and none of the proposed merges would improve discoverability. 'This is narrow but distinct from its siblings' is NOT a reason to keep — it's a reason to move it under an umbrella as a subsection or support file.\n\nExpected output: real umbrella-ification. Process every obvious cluster. If you end the pass with fewer than 10 archives, you stopped too early — go back and look at the clusters you left alone.\n\nWhen done, write a human summary AND a structured machine-readable block so downstream tooling can distinguish consolidation from pruning. Format EXACTLY:\n\n## Structured summary (required)\n```yaml\nconsolidations:\n - from: \n into: \n reason: \nprunings:\n - name: \n reason: \n```\n\nEvery skill you moved to .archive/ MUST appear in exactly one of the two lists. If you consolidated X into umbrella Y (patched Y, wrote a references file to Y, or created Y with X's content absorbed), X goes under `consolidations` with `into: Y`. If you archived X with no absorption — truly stale, irrelevant, or obsolete — X goes under `prunings`. Leave a list empty (`consolidations: []`) if none. Do not omit the block. The block comes AFTER your human-readable summary of clusters processed, patches made, and decisions left alone.\n\nAgent-created skills (10):\n\n- ai-video-production state=active pinned=no activity=7 use=2 view=2 patches=3 last_activity=2026-06-18T13:11:33.780405+00:00\n- esp32-desk-dashboard state=active pinned=no activity=13 use=4 view=4 patches=5 last_activity=2026-06-08T10:24:42.634531+00:00\n- home-assistant state=active pinned=no activity=54 use=20 view=18 patches=16 last_activity=2026-06-22T01:05:45.615443+00:00\n- local-server-public-access state=active pinned=no activity=10 use=4 view=4 patches=2 last_activity=2026-06-21T20:15:34.612782+00:00\n- media-file-management state=active pinned=no activity=131 use=43 view=47 patches=41 last_activity=2026-06-18T12:43:10.925145+00:00\n- music-resources state=active pinned=no activity=18 use=6 view=6 patches=6 last_activity=2026-06-18T15:04:44.728223+00:00\n- pdf-generation state=active pinned=no activity=1 use=0 view=0 patches=1 last_activity=2026-06-18T15:07:31.257587+00:00\n- reddit state=active pinned=no activity=5 use=2 view=2 patches=1 last_activity=2026-06-04T11:02:35.388676+00:00\n- technical-product-spec state=active pinned=no activity=5 use=1 view=1 patches=3 last_activity=2026-06-21T20:31:32.604337+00:00\n- zeitgeist-app-development state=active pinned=no activity=4 use=1 view=1 patches=2 last_activity=2026-06-21T09:33:30.742151+00:00"
},
{
"role": "assistant",
"content": "",
"reasoning": "**Defining Umbrella Skills**\n\nI'm currently focused on defining the initial scope. My aim is to transition from discrete, session-bound skills to larger, more encompassing umbrella skills suitable for our \"umbrella-building consolidation pass.\" I'm looking at how these new skills should be categorized, to better reflect how to consolidate them.\n\n\n**Identifying Consolidation Clusters**\n\nI've moved on to identifying potential consolidation clusters and the rules governing the process. The focus is on finding candidates, applying exclusion criteria (like bundled or pinned skills), and assessing content over usage. I need to merge skills into umbrella skills if they meet a human-written skill definition with logical sections. There is also a list of example skills that will be used to generate the clusters. I am working on the list of 10 skills.\n\n\n",
"finish_reason": "tool_calls",
"reasoning_content": "**Defining Umbrella Skills**\n\nI'm currently focused on defining the initial scope. My aim is to transition from discrete, session-bound skills to larger, more encompassing umbrella skills suitable for our \"umbrella-building consolidation pass.\" I'm looking at how these new skills should be categorized, to better reflect how to consolidate them.\n\n\n**Identifying Consolidation Clusters**\n\nI've moved on to identifying potential consolidation clusters and the rules governing the process. The focus is on finding candidates, applying exclusion criteria (like bundled or pinned skills), and assessing content over usage. I need to merge skills into umbrella skills if they meet a human-written skill definition with logical sections. There is also a list of example skills that will be used to generate the clusters. I am working on the list of 10 skills.\n\n\n",
"tool_calls": [
{
"id": "bvz3wl9h",
"call_id": "bvz3wl9h",
"response_item_id": "fc_bvz3wl9h",
"type": "function",
"function": {
"name": "execute_code",
"arguments": "{\"code\":\"from hermes_tools import terminal\\nimport json\\n\\nskills = [\\n \\\"ai-video-production\\\",\\n \\\"esp32-desk-dashboard\\\",\\n \\\"home-assistant\\\",\\n \\\"local-server-public-access\\\",\\n \\\"media-file-management\\\",\\n \\\"music-resources\\\",\\n \\\"pdf-generation\\\",\\n \\\"reddit\\\",\\n \\\"technical-product-spec\\\",\\n \\\"zeitgeist-app-development\\\"\\n]\\n\\nresults = {}\\nfor skill in skills:\\n # We can't use skill_view directly in execute_code unless it's imported, but it's not listed as available in execute_code.\\n # However, I can use the terminal to cat the SKILL.md files.\\n # The path is typically ~/.hermes/skills/\\u003cskill\\u003e/SKILL.md\\n path = f\\\"~/.hermes/skills/{skill}/SKILL.md\\\"\\n # Need to expand ~\\n res = terminal(f\\\"cat {path}\\\")\\n results[skill] = res['output']\\n\\nprint(json.dumps(results))\\n\"}"
}
}
]
},
{
"role": "tool",
"name": "execute_code",
"content": "{\"status\": \"success\", \"output\": \"{\\\"ai-video-production\\\": \\\"cat: /DATA/.hermes/skills/ai-video-production/SKILL.md: No such file or directory\\\", \\\"esp32-desk-dashboard\\\": \\\"cat: /DATA/.hermes/skills/esp32-desk-dashboard/SKILL.md: No such file or directory\\\", \\\"home-assistant\\\": \\\"cat: /DATA/.hermes/skills/home-assistant/SKILL.md: No such file or directory\\\", \\\"local-server-public-access\\\": \\\"cat: /DATA/.hermes/skills/local-server-public-access/SKILL.md: No such file or directory\\\", \\\"media-file-management\\\": \\\"cat: /DATA/.hermes/skills/media-file-management/SKILL.md: No such file or directory\\\", \\\"music-resources\\\": \\\"cat: /DATA/.hermes/skills/music-resources/SKILL.md: No such file or directory\\\", \\\"pdf-generation\\\": \\\"cat: /DATA/.hermes/skills/pdf-generation/SKILL.md: No such file or directory\\\", \\\"reddit\\\": \\\"cat: /DATA/.hermes/skills/reddit/SKILL.md: No such file or directory\\\", \\\"technical-product-spec\\\": \\\"cat: /DATA/.hermes/skills/technical-product-spec/SKILL.md: No such file or directory\\\", \\\"zeitgeist-app-development\\\": \\\"cat: /DATA/.hermes/skills/zeitgeist-app-development/SKILL.md: No such file or directory\\\"}\\n\", \"tool_calls_made\": 10, \"duration_seconds\": 2.87}",
"tool_call_id": "bvz3wl9h"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "xeroivg3",
"call_id": "xeroivg3",
"response_item_id": "fc_xeroivg3",
"type": "function",
"function": {
"name": "skills_list",
"arguments": "{}"
}
}
]
},
{
"role": "tool",
"name": "skills_list",
"content": "{\"success\": true, \"skills\": [{\"name\": \"cad-3d-print\", \"description\": \"Parametric 3D modeling with trimesh for FDM printing. Generates STL with PNG preview and mesh validation. Headless, pure Python — uses direct mesh construction for reliable chamfers and fillets.\", \"category\": null}, {\"name\": \"dogfood\", \"description\": \"Exploratory QA of web apps: find bugs, evidence, reports.\", \"category\": null}, {\"name\": \"yuanbao\", \"description\": \"Yuanbao (元宝) groups: @mention users, query info/members.\", \"category\": null}, {\"name\": \"3d-druck-kiwi\", \"description\": \"Vollständiger Workflow zum Erstellen druckbarer 3D-Modelle aus Textbeschreibungen. Nutzt Python (trimesh + manifold3d) als primären CAD-Engine. Generiert validierte STL/3MF-Dateien für Bambu Lab Drucker.\", \"category\": \"3d-printing\"}, {\"name\": \"claude-code\", \"description\": \"Delegate coding to Claude Code CLI (features, PRs).\", \"category\": \"autonomous-ai-agents\"}, {\"name\": \"hermes-agent\", \"description\": \"Configure, extend, or contribute to Hermes Agent.\", \"category\": \"autonomous-ai-agents\"}, {\"name\": \"opencode\", \"description\": \"Delegate coding to OpenCode CLI (features, PR review).\", \"category\": \"autonomous-ai-agents\"}, {\"name\": \"ai-video-production\", \"description\": \"AI-gestützte Videoproduktion: Skript, Bildgenerierung (DALL-E/ChatGPT), TTS-Voiceover, ffmpeg-Assembly mit Ken-Burns-Effekt.\", \"category\": \"creative\"}, {\"name\": \"architecture-diagram\", \"description\": \"Dark-themed SVG architecture/cloud/infra diagrams as HTML.\", \"category\": \"creative\"}, {\"name\": \"ascii-art\", \"description\": \"ASCII art: pyfiglet, cowsay, boxes, image-to-ascii.\", \"category\": \"creative\"}, {\"name\": \"ascii-video\", \"description\": \"ASCII video: convert video/audio to colored ASCII MP4/GIF.\", \"category\": \"creative\"}, {\"name\": \"baoyu-comic\", \"description\": \"Knowledge comics (知识漫画): educational, biography, tutorial.\", \"category\": \"creative\"}, {\"name\": \"baoyu-infographic\", \"description\": \"Infographics: 21 layouts x 21 styles (信息图, 可视化).\", \"category\": \"creative\"}, {\"name\": \"claude-design\", \"description\": \"Design one-off HTML artifacts (landing, deck, prototype).\", \"category\": \"creative\"}, {\"name\": \"comfyui\", \"description\": \"Generate images, video, and audio with ComfyUI — install, launch, manage nodes/models, run workflows with parameter injection. Uses the official comfy-cli for lifecycle and direct REST/WebSocket API for execution.\", \"category\": \"creative\"}, {\"name\": \"design-md\", \"description\": \"Author/validate/export Google's DESIGN.md token spec files.\", \"category\": \"creative\"}, {\"name\": \"excalidraw\", \"description\": \"Hand-drawn Excalidraw JSON diagrams (arch, flow, seq).\", \"category\": \"creative\"}, {\"name\": \"humanizer\", \"description\": \"Humanize text: strip AI-isms and add real voice.\", \"category\": \"creative\"}, {\"name\": \"ideation\", \"description\": \"Generate project ideas via creative constraints.\", \"category\": \"creative\"}, {\"name\": \"manim-video\", \"description\": \"Manim CE animations: 3Blue1Brown math/algo videos.\", \"category\": \"creative\"}, {\"name\": \"p5js\", \"description\": \"p5.js sketches: gen art, shaders, interactive, 3D.\", \"category\": \"creative\"}, {\"name\": \"pixel-art\", \"description\": \"Pixel art w/ era palettes (NES, Game Boy, PICO-8).\", \"category\": \"creative\"}, {\"name\": \"popular-web-designs\", \"description\": \"54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.\", \"category\": \"creative\"}, {\"name\": \"pretext\", \"description\": \"Use when building creative browser demos with @chenglou/pretext — DOM-free text layout for ASCII art, typographic flow around obstacles, text-as-geometry games, kinetic typography, and text-powered generative art. Produces single-file HTML demos by default.\", \"category\": \"creative\"}, {\"name\": \"sketch\", \"description\": \"Throwaway HTML mockups: 2-3 design variants to compare.\", \"category\": \"creative\"}, {\"name\": \"songwriting-and-ai-music\", \"description\": \"Songwriting craft and Suno AI music prompts.\", \"category\": \"creative\"}, {\"name\": \"touchdesigner-mcp\", \"description\": \"Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.\", \"category\": \"creative\"}, {\"name\": \"jupyter-live-kernel\", \"description\": \"Iterative Python via live Jupyter kernel (hamelnb).\", \"category\": \"data-science\"}, {\"name\": \"casaos-app-troubleshoot\", \"description\": \"CasaOS-App-Probleme diagnostizieren und beheben — Legacy, ausgegraut, Random-Namen, fehlende Icons, verwaiste Compose-Files.\", \"category\": \"devops\"}, {\"name\": \"kanban-orchestrator\", \"description\": \"Decomposition playbook + specialist-roster conventions + anti-temptation rules for an orchestrator profile routing work through Kanban. The \\\"don't do the work yourself\\\" rule and the basic lifecycle are auto-injected into every kanban worker's system prompt; this skill is the deeper playbook when you're specifically playing the orchestrator role.\", \"category\": \"devops\"}, {\"name\": \"kanban-worker\", \"description\": \"Pitfalls, examples, and edge cases for Hermes Kanban workers. The lifecycle itself is auto-injected into every worker's system prompt as KANBAN_GUIDANCE (from agent/prompt_builder.py); this skill is what you load when you want deeper detail on specific scenarios.\", \"category\": \"devops\"}, {\"name\": \"local-server-public-access\", \"description\": \"Expose a local HTTP service (website, dashboard, dev server) to the public internet so it can be opened from a phone or remote location. Covers cloudflared, ngrok, tailscale funnel, and manual port forwarding with security notes.\", \"category\": \"devops\"}, {\"name\": \"safe-volume-migration\", \"description\": \"Anonyme Docker-Volumes (Hash-Namen) sicher zu Bind-Mounts migrieren — für Postgres, Redis, und andere stateful Container.\", \"category\": \"devops\"}, {\"name\": \"webhook-subscriptions\", \"description\": \"Webhook subscriptions: event-driven agent runs.\", \"category\": \"devops\"}, {\"name\": \"zimaos-app-install\", \"description\": \"Neue App/Container auf ZimaOS sauber per Docker Compose installieren — mit x-casaos-Block, korrekten Pfaden und ohne Legacy-Probleme.\", \"category\": \"devops\"}, {\"name\": \"zimaos-camofox-browser\", \"description\": \"Camofox-Browser als persistenten Docker-Dienst auf ZimaOS für Hermes-Browser-Automation einrichten und betreiben.\", \"category\": \"devops\"}, {\"name\": \"zimaos-platform\", \"description\": \"Build, deploy, administer, inspect, and debug applications on a ZimaOS (CasaOS) server. Covers server setup, Docker/CasaOS container management, app data inspection, and web app development/deployment.\", \"category\": \"devops\"}, {\"name\": \"zimaos-quirks\", \"description\": \"ZimaOS-Eigenheiten — read-only Root-FS, DOCKER_CONFIG, HOME=/DATA, Systemd-Service-Namen und andere Fallstricke.\", \"category\": \"devops\"}, {\"name\": \"himalaya\", \"description\": \"Himalaya CLI: IMAP/SMTP email from terminal.\", \"category\": \"email\"}, {\"name\": \"minecraft-modpack-server\", \"description\": \"Host modded Minecraft servers (CurseForge, Modrinth).\", \"category\": \"gaming\"}, {\"name\": \"pokemon-player\", \"description\": \"Play Pokemon via headless emulator + RAM reads.\", \"category\": \"gaming\"}, {\"name\": \"codebase-inspection\", \"description\": \"Inspect codebases w/ pygount: LOC, languages, ratios.\", \"category\": \"github\"}, {\"name\": \"github-auth\", \"description\": \"GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login.\", \"category\": \"github\"}, {\"name\": \"github-code-review\", \"description\": \"Review PRs: diffs, inline comments via gh or REST.\", \"category\": \"github\"}, {\"name\": \"github-issues\", \"description\": \"Create, triage, label, assign GitHub issues via gh or REST.\", \"category\": \"github\"}, {\"name\": \"github-pr-workflow\", \"description\": \"GitHub PR lifecycle: branch, commit, open, CI, merge.\", \"category\": \"github\"}, {\"name\": \"github-repo-management\", \"description\": \"Clone/create/fork repos; manage remotes, releases.\", \"category\": \"github\"}, {\"name\": \"esp32-desk-dashboard\", \"description\": \"ESP32-basierte Desk-Dashboards mit AMOLED, LVGL und BLE. Hardware-Auswahl, Firmware-Architektur, Daemon-Design und Tooling für Maker.\", \"category\": \"maker-electronics\"}, {\"name\": \"native-mcp\", \"description\": \"MCP client: connect servers, register tools (stdio/HTTP).\", \"category\": \"mcp\"}, {\"name\": \"gif-search\", \"description\": \"Search/download GIFs from Tenor via curl + jq.\", \"category\": \"media\"}, {\"name\": \"heartmula\", \"description\": \"HeartMuLa: Suno-like song generation from lyrics + tags.\", \"category\": \"media\"}, {\"name\": \"media-file-management\", \"description\": \"Organize and normalize local media files (movies, TV shows, music, ebooks, audiobooks, YouTube content) on ZimaOS. Rename, deduplicate, audit, fix metadata, embed covers, and automate video production.\", \"category\": \"media\"}, {\"name\": \"music-resources\", \"description\": \"Find sheet music, chords, tabs, and notation online — search strategies, major platforms, and Turkish-specific resources.\", \"category\": \"media\"}, {\"name\": \"songsee\", \"description\": \"Audio spectrograms/features (mel, chroma, MFCC) via CLI.\", \"category\": \"media\"}, {\"name\": \"spotify\", \"description\": \"Spotify: play, search, queue, manage playlists and devices.\", \"category\": \"media\"}, {\"name\": \"youtube-content\", \"description\": \"YouTube transcripts to summaries, threads, blogs.\", \"category\": \"media\"}, {\"name\": \"youtube-headless-pipeline\", \"description\": \"Vollautomatische YouTube-Shorts-Pipeline: Reddit-Stories → LLM-generierte deutsche Kurzgeschichte → Conrad TTS → Pexels B-Roll → fertiges 9:16 Short. Keine Kosten, null manuelle Schritte.\", \"category\": \"media\"}, {\"name\": \"audiocraft-audio-generation\", \"description\": \"AudioCraft: MusicGen text-to-music, AudioGen text-to-sound.\", \"category\": \"mlops\"}, {\"name\": \"axolotl\", \"description\": \"Axolotl: YAML LLM fine-tuning (LoRA, DPO, GRPO).\", \"category\": \"mlops\"}, {\"name\": \"dspy\", \"description\": \"DSPy: declarative LM programs, auto-optimize prompts, RAG.\", \"category\": \"mlops\"}, {\"name\": \"evaluating-llms-harness\", \"description\": \"lm-eval-harness: benchmark LLMs (MMLU, GSM8K, etc.).\", \"category\": \"mlops\"}, {\"name\": \"fine-tuning-with-trl\", \"description\": \"TRL: SFT, DPO, PPO, GRPO, reward modeling for LLM RLHF.\", \"category\": \"mlops\"}, {\"name\": \"huggingface-hub\", \"description\": \"HuggingFace hf CLI: search/download/upload models, datasets.\", \"category\": \"mlops\"}, {\"name\": \"llama-cpp\", \"description\": \"llama.cpp local GGUF inference + HF Hub model discovery.\", \"category\": \"mlops\"}, {\"name\": \"obliteratus\", \"description\": \"OBLITERATUS: abliterate LLM refusals (diff-in-means).\", \"category\": \"mlops\"}, {\"name\": \"outlines\", \"description\": \"Outlines: structured JSON/regex/Pydantic LLM generation.\", \"category\": \"mlops\"}, {\"name\": \"segment-anything-model\", \"description\": \"SAM: zero-shot image segmentation via points, boxes, masks.\", \"category\": \"mlops\"}, {\"name\": \"serving-llms-vllm\", \"description\": \"vLLM: high-throughput LLM serving, OpenAI API, quantization.\", \"category\": \"mlops\"}, {\"name\": \"unsloth\", \"description\": \"Unsloth: 2-5x faster LoRA/QLoRA fine-tuning, less VRAM.\", \"category\": \"mlops\"}, {\"name\": \"weights-and-biases\", \"description\": \"W&B: log ML experiments, sweeps, model registry, dashboards.\", \"category\": \"mlops\"}, {\"name\": \"obsidian\", \"description\": \"Read, search, create, and edit notes in the Obsidian vault — 4-level memory system Level 3.\", \"category\": \"note-taking\"}, {\"name\": \"airtable\", \"description\": \"Airtable REST API via curl. Records CRUD, filters, upserts.\", \"category\": \"productivity\"}, {\"name\": \"docmaster-access\", \"description\": \"Direkter Zugriff auf DocMaster-Dokumente auf ZimaOS — API-Endpunkte, Container-Management, Auth-Steuerung und Migration.\", \"category\": \"productivity\"}, {\"name\": \"google-workspace\", \"description\": \"Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python.\", \"category\": \"productivity\"}, {\"name\": \"linear\", \"description\": \"Linear: manage issues, projects, teams via GraphQL + curl.\", \"category\": \"productivity\"}, {\"name\": \"maps\", \"description\": \"Geocode, POIs, routes, timezones via OpenStreetMap/OSRM.\", \"category\": \"productivity\"}, {\"name\": \"mnemo-access\", \"description\": \"Direkter Zugriff auf Mnemo (Cartographer's Zettelkasten) Docker-Container auf ZimaOS — API, Container-Management, Deploy, CasaOS-Integration.\", \"category\": \"productivity\"}, {\"name\": \"nano-pdf\", \"description\": \"Edit PDF text/typos/titles via nano-pdf CLI (NL prompts).\", \"category\": \"productivity\"}, {\"name\": \"notion\", \"description\": \"Notion API via curl: pages, databases, blocks, search.\", \"category\": \"productivity\"}, {\"name\": \"ocr-and-documents\", \"description\": \"Extract text from PDFs/scans (pymupdf, marker-pdf).\", \"category\": \"productivity\"}, {\"name\": \"pdf-generation\", \"description\": \"Generate PDF documents from markdown/text using fpdf2 with Unicode support.\", \"category\": \"productivity\"}, {\"name\": \"powerpoint\", \"description\": \"Create, read, edit .pptx decks, slides, notes, templates.\", \"category\": \"productivity\"}, {\"name\": \"zimaos-productivity\", \"description\": \"Productivity apps on ZimaOS — DailyDose activity tracking, Zeitgeist Pomodoro + Anki, and CallKeep telephony. Data structures, APIs, cron-job motivation, and Anki import workflows.\", \"category\": \"productivity\"}, {\"name\": \"godmode\", \"description\": \"Jailbreak LLMs: Parseltongue, GODMODE, ULTRAPLINIAN.\", \"category\": \"red-teaming\"}, {\"name\": \"arxiv\", \"description\": \"Search arXiv papers by keyword, author, category, or ID.\", \"category\": \"research\"}, {\"name\": \"blogwatcher\", \"description\": \"Monitor blogs and RSS/Atom feeds via blogwatcher-cli tool.\", \"category\": \"research\"}, {\"name\": \"llm-wiki\", \"description\": \"Karpathy's LLM Wiki: build/query interlinked markdown KB.\", \"category\": \"research\"}, {\"name\": \"polymarket\", \"description\": \"Query Polymarket: markets, prices, orderbooks, history.\", \"category\": \"research\"}, {\"name\": \"research-literature\", \"description\": \"Academic and biomedical research skills — professor profiling, thesis development, Austrian legal sources, PubMed literature retrieval, and scholarly source strategy.\", \"category\": \"research\"}, {\"name\": \"research-paper-writing\", \"description\": \"Write ML papers for NeurIPS/ICML/ICLR: design→submit.\", \"category\": \"research\"}, {\"name\": \"home-assistant\", \"description\": \"Inspect, manage, and troubleshoot Home Assistant (Docker on ZimaOS) — config, devices, integrations, automations, and Zigbee.\", \"category\": \"smart-home\"}, {\"name\": \"midea-ac-ha\", \"description\": \"Midea Porta Split Klimaanlage in Home Assistant 2026 einbinden — Integration, Patches, Token-Beschaffung und Diagnose.\", \"category\": \"smart-home\"}, {\"name\": \"openhue\", \"description\": \"Control Philips Hue lights, scenes, rooms via OpenHue CLI.\", \"category\": \"smart-home\"}, {\"name\": \"reddit\", \"description\": \"Read Reddit posts, comments, and subreddits via JSON API or PullPush.io archive fallback.\", \"category\": \"social-media\"}, {\"name\": \"xurl\", \"description\": \"X/Twitter via xurl CLI: post, search, DM, media, v2 API.\", \"category\": \"social-media\"}, {\"name\": \"debugging-hermes-tui-commands\", \"description\": \"Debug Hermes TUI slash commands: Python, gateway, Ink UI.\", \"category\": \"software-development\"}, {\"name\": \"hermes-agent-skill-authoring\", \"description\": \"Author in-repo SKILL.md: frontmatter, validator, structure.\", \"category\": \"software-development\"}, {\"name\": \"node-inspect-debugger\", \"description\": \"Debug Node.js via --inspect + Chrome DevTools Protocol CLI.\", \"category\": \"software-development\"}, {\"name\": \"plan\", \"description\": \"Plan mode: write markdown plan to .hermes/plans/, no exec.\", \"category\": \"software-development\"}, {\"name\": \"python-debugpy\", \"description\": \"Debug Python: pdb REPL + debugpy remote (DAP).\", \"category\": \"software-development\"}, {\"name\": \"requesting-code-review\", \"description\": \"Pre-commit review: security scan, quality gates, auto-fix.\", \"category\": \"software-development\"}, {\"name\": \"spike\", \"description\": \"Throwaway experiments to validate an idea before build.\", \"category\": \"software-development\"}, {\"name\": \"subagent-driven-development\", \"description\": \"Execute plans via delegate_task subagents (2-stage review).\", \"category\": \"software-development\"}, {\"name\": \"systematic-debugging\", \"description\": \"4-phase root cause debugging: understand bugs before fixing.\", \"category\": \"software-development\"}, {\"name\": \"technical-product-spec\", \"description\": \"Write deep technical product specifications in Stripe/Cloudflare documentation style — architecture, AI/ML pipelines, business models, competitive analysis, MVP definition, and roadmap. Paired with dark-themed architecture diagrams.\", \"category\": \"software-development\"}, {\"name\": \"test-driven-development\", \"description\": \"TDD: enforce RED-GREEN-REFACTOR, tests before code.\", \"category\": \"software-development\"}, {\"name\": \"writing-plans\", \"description\": \"Write implementation plans: bite-sized tasks, paths, code.\", \"category\": \"software-development\"}, {\"name\": \"zeitgeist-app-development\", \"description\": \"Modify the Zeitgeist single-file HTML/CSS/JS apps (zeitgeist.html, anki.html, vault.html, pruefungsmanager.html). Delegation pattern, architecture, CSS conventions, and pitfalls.\", \"category\": \"software-development\"}], \"categories\": [\"3d-printing\", \"autonomous-ai-agents\", \"creative\", \"data-science\", \"devops\", \"email\", \"gaming\", \"github\", \"maker-electronics\", \"mcp\", \"media\", \"mlops\", \"note-taking\", \"productivity\", \"red-teaming\", \"research\", \"smart-home\", \"social-media\", \"software-development\"], \"count\": 108, \"hint\": \"Use skill_view(name) to see full content, tags, and linked files\"}",
"tool_call_id": "xeroivg3"
},
{
"role": "assistant",
"content": "",
"reasoning": "**Refining Skill Focus**\n\nI'm now zeroing in on the skills mismatch. The discrepancy between the prompt's provided list of 10 candidate agent-created skills and the `skills_list` output of 108 is my current sticking point. My primary goal is to ensure absolute adherence to the original 10-skill constraint. I'm carefully reviewing the source material to maintain the integrity of that crucial parameter.\n\n\n**Identifying Skill Clusters**\n\nI've shifted focus to clustering the 10 candidate skills. I identified four initial clusters: Media/Creative, Software Development, Hardware/Smart Home, and a remaining group. The prompt's requirement for 10-25 clusters presents a challenge as I have only 10 skills. I'm now exploring the possibility of merging existing candidate skills and recognizing \"bundled or hub-installed\" skills that are NOT within my candidate list as potential clusters to augment my existing candidate skills.\n\n\n",
"finish_reason": "tool_calls",
"reasoning_content": "**Refining Skill Focus**\n\nI'm now zeroing in on the skills mismatch. The discrepancy between the prompt's provided list of 10 candidate agent-created skills and the `skills_list` output of 108 is my current sticking point. My primary goal is to ensure absolute adherence to the original 10-skill constraint. I'm carefully reviewing the source material to maintain the integrity of that crucial parameter.\n\n\n**Identifying Skill Clusters**\n\nI've shifted focus to clustering the 10 candidate skills. I identified four initial clusters: Media/Creative, Software Development, Hardware/Smart Home, and a remaining group. The prompt's requirement for 10-25 clusters presents a challenge as I have only 10 skills. I'm now exploring the possibility of merging existing candidate skills and recognizing \"bundled or hub-installed\" skills that are NOT within my candidate list as potential clusters to augment my existing candidate skills.\n\n\n",
"tool_calls": [
{
"id": "47cmda8z",
"call_id": "47cmda8z",
"response_item_id": "fc_47cmda8z",
"type": "function",
"function": {
"name": "skill_view",
"arguments": "{\"name\":\"media-file-management\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_view",
"content": "{\"success\": true, \"name\": \"media-file-management\", \"description\": \"Organize and normalize local media files (movies, TV shows, music, ebooks, audiobooks, YouTube content) on ZimaOS. Rename, deduplicate, audit, fix metadata, embed covers, and automate video production.\", \"tags\": [], \"related_skills\": [], \"content\": \"---\\nname: media-file-management\\ndescription: Organize and normalize local media files (movies, TV shows, music, ebooks, audiobooks, YouTube content) on ZimaOS. Rename, deduplicate, audit, fix metadata, embed covers, and automate video production.\\n---\\n\\n# Media File Management\\n\\nManage the local media library at `/media/HDD_1TB/Medien/` (1TB HDD, Btrfs mount). Root-owned files require `sudo` for writes. Covers ebook metadata/cover management and headless YouTube video production.\\n\\n## Library Layout\\n\\n```\\n/media/HDD_1TB/Medien/\\n Filme/ # Movies (.mp4)\\n Serien/ # TV shows\\n Musik/ # Music\\n Bücher/ # Books (EPUB/PDF)\\n Audiobooks/ # Audiobooks\\n Podcasts/\\n YouTube/ # Rendered videos + background footage\\n```\\n\\n## Naming Convention\\n\\nAll filenames follow this format:\\n\\n- **Underscores for word boundaries** — no spaces, no hyphens\\n- **No Umlauts or special chars** — ASCII only\\n- **No rip artifacts** — strip `T00`, `t00`, track numbers from MakeMKV/DVD rips\\n\\n### Umlaut Conversion Table\\n\\n| Char | Replace |\\n|------|---------|\\n| ä | ae |\\n| ö | oe |\\n| ü | ue |\\n| Ä | Ae |\\n| Ö | Oe |\\n| Ü | Ue |\\n| ß | ss |\\n\\n### Cleanup Regex (Python)\\n\\n```python\\nimport re\\nname = re.sub(r'\\\\s*T00\\\\b', '', name, flags=re.I) # Strip track artifacts\\nname = re.sub(r'[\\\\s\\\\-]+', '_', name) # Spaces/hyphens → underscore\\nname = re.sub(r'_{2,}', '_', name) # Collapse multi-underscore\\nname = re.sub(r'_\\\\.mp4$', '.mp4', name) # Fix trailing underscore\\n```\\n\\n## Permissions\\n\\nFiles on `/media/HDD_1TB/` are owned by `root:root`. The agent runs as `az-a` (uid 999, group samba). **All writes/renames require `sudo`.**\\n\\nThe sandboxed Python interpreter (`execute_code`) has no access to `/media/` mounts — do file operations via `terminal` with `sudo`.\\n\\n## Common Tasks\\n\\n### Audit: find files not matching the convention\\n\\n```bash\\nls /media/HDD_1TB/Medien/Filme/ | grep -E '[[:space:]]|[äöüßÄÖÜ]|T00|[^_a-zA-Z0-9.]'\\n```\\n\\n### Batch rename with sudo\\n\\n```bash\\ncd \\\"/media/HDD_1TB/Medien/Filme\\\"\\nfor f in *T00*.mp4; do\\n sudo mv \\\"$f\\\" \\\"$(echo \\\"$f\\\" | sed 's/ T00//')\\\"\\ndone\\n```\\n\\n### Rename Umlauts (one-shot per file)\\n\\n```bash\\nsudo mv \\\"Alter_Weißer_Mann.mp4\\\" \\\"Alter_Weisser_Mann.mp4\\\"\\nsudo mv \\\"Das_Streben_nach_Glück.mp4\\\" \\\"Das_Streben_nach_Glueck.mp4\\\"\\n```\\n\\n## TV Show Convention\\\\n\\\\nTV shows live in `/media/HDD_1TB/Medien/Serien/`, organized as:\\\\n\\\\n```\\\\nSerien/\\\\n Show_Name/\\\\n S01/Show_Name_S01E01.mp4\\\\n S01/Show_Name_S01E02.mp4\\\\n S02/Show_Name_S02E01.mp4\\\\n ...\\\\n```\\\\n\\\\nRules:\\\\n- Each show is a subdirectory under `Serien/`\\\\n- Each season is a subdirectory under the show (S01, S02, ...)\\\\n- Files: `Show_Name_SxxExx.mp4` — underscores, ASCII, no season folder prefix in the filename\\\\n- Episode numbering always zero-padded (`S01E01`, not `S1E1`)\\\\n\\\\nWhen reorganizing flat show folders into season structure:\\\\n\\\\n```bash\\\\ncd \\\\\\\"/media/HDD_1TB/Medien/Serien/Show Name\\\\\\\"\\\\nsudo mkdir -p S01 S02 S03\\\\nfor f in *.mp4; do\\\\n season=$(echo \\\\\\\"$f\\\\\\\" | grep -oP 'S\\\\\\\\d\\\\\\\\d')\\\\n newname=$(echo \\\\\\\"$f\\\\\\\" | tr ' ' '_')\\\\n sudo mv \\\\\\\"$f\\\\\\\" \\\\\\\"${season}/${newname}\\\\\\\"\\\\ndone\\\\n```\\\\n\\\\nLeftover download artifacts (`.part`, `.webm`, `.f136`, `.f251`) stay where they are — don't delete unless user asks. `.ts` (transport stream) files are also left as-is.\\\\n\\\\n## Common Artifacts to Leave Alone\\\\n\\\\n- `*f136.mp4.part` — incomplete yt-dlp video download\\\\n- `*f251.webm` — audio-only track from yt-dlp\\\\n- `*.ts` — transport stream container\\\\n\\\\nThese are not errors, just alternative formats. Don't rename or delete without explicit instruction.\\\\n\\\\n## Audiobooks\\n\\nAudiobooks live in `/media/HDD_1TB/Medien/Audiobooks/`. Audiobookshelf (Docker container `ghcr.io/advplyr/audiobookshelf:2.30.0`, port `13378`) serves them.\\n\\n### Audiobookshelf metadata management\\n\\nWhen Audiobookshelf shows wrong metadata (author, narrator, series, description), fix it at the source — the ID3 tags in the MP3 files — then re-import. Audiobookshelf's metadata precedence (`audioMetatags > absMetadata` by default) means API patches are overridden by embedded tags on every scan. Full workflow: [references/audiobookshelf-metadata.md](references/audiobookshelf-metadata.md).\\n\\n**Quick workflow:**\\n\\n1. Check current metadata: `curl -H \\\"Authorization: Bearer $TOKEN\\\" http://127.0.0.1:13378/api/libraries/{libId}/items`\\n2. Fix ID3 tags in all MP3 files (mutagen, `sudo PYTHONPATH=/DATA/.local/lib/python3.12/site-packages python3`)\\n3. Delete items from ABS: `curl -X DELETE .../api/items/{id}`\\n4. Rescan library: `curl -X POST .../api/libraries/{libId}/scan`\\n5. Set series/descriptions via PATCH: `{\\\"metadata\\\":{\\\"series\\\":[{\\\"name\\\":\\\"Medici\\\",\\\"sequence\\\":\\\"1\\\"}]}}`\\n\\n**API token:** stored in `/DATA/AppData/audiobookshelf/config/absdatabase.sqlite` → `SELECT * FROM users;` → last column is the JWT.\\n\\n### Tag audiobooks with metadata and covers (Audible API + mutagen)\\n\\nWhen audiobook MP3s have no tags (or wrong tags), fetch metadata from the Audible API\\nand embed proper ID3 tags plus cover art. Full reference: [references/audible-api-tagging.md](references/audible-api-tagging.md).\\n\\n**Quick workflow:**\\n\\n1. Find the ASIN (from Audible.de URL, or scrape `audible.de/search` HTML — the search API is degraded)\\n2. Fetch product detail from `api.audible.de` with iPhone User-Agent (contributors may be empty; scrape product page for author/narrator)\\n3. Download cover image from `product_images[\\\"500\\\"]` URL\\n4. Fix file permissions (`sudo chown az-a:samba *.mp3 && sudo chmod 664 *.mp3`)\\n5. Tag with Python/mutagen: Title → TIT2/TALB, Author → TPE1/TPE2, Narrator → TCOM,\\n Description → COMM, Publisher → TPUB, Year → TDRC, Genre → TCON, Cover → APIC\\n\\n**Template script:** `scripts/tag_audiobooks_template.py` — adapt the `books` list for each batch.\\n\\n### Concatenate multi-file audiobooks with ffmpeg\\n\\nWhen audiobooks are split into many numbered MP3 files (e.g., DAV productions with 500+ tracks), join them losslessly:\\n\\n```\\nfile 'Schuld und Sühne/001_Dostojewskij_Verbrechen_DAV.mp3'\\nfile 'Schuld und Sühne/002_Dostojewskij_Verbrechen_DAV.mp3'\\n...\\n```\\n\\n```bash\\n# 1. Generate sorted concat list (handle spaces in paths with Python)\\ncd \\\"/media/HDD_1TB/Medien/Audiobooks\\\"\\npython3 -c \\\"\\nimport os\\nfiles = sorted(os.listdir('Schuld und Sühne'))\\nwith open('/tmp/concat.txt', 'w') as f:\\n for name in files:\\n if name.endswith('.mp3'):\\n f.write(f\\\\\\\"file 'Schuld und Sühne/{name}'\\\\n\\\\\\\")\\nprint(f'Wrote {sum(1 for n in files if n.endswith(\\\\\\\".mp3\\\\\\\"))} entries')\\n\\\"\\n\\n# 2. Concat with stream copy (no re-encode — fast, lossless)\\nffmpeg -f concat -safe 0 -i /tmp/concat.txt -c copy output_komplett.mp3 -y\\n```\\n\\n- `-c copy` streams audio without re-encoding — preserves original quality\\n- `-safe 0` needed when paths contain spaces or are relative\\n- ffmpeg 6.1.3 is available at `/usr/bin/ffmpeg` on ZimaOS\\n- For 577 files / ~1.7 GB, expect 30–120 seconds\\n\\n\\n\\n## eBooks\\n\\neBooks live in `/media/HDD_1TB/Medien/Bücher/`, organized by author subdirectory.\\n\\n### Metadata Audit\\n\\nRun `scripts/scan_ebook_metadata.py` to inventory all books and report missing/broken metadata (title, author, year, publisher, ISBN).\\n\\n```bash\\npython3 /DATA/.hermes/skills/media/media-file-management/scripts/scan_ebook_metadata.py\\n```\\n\\n### Fix EPUB metadata\\n\\n`scripts/fix_epub_metadata.py` patches EPUB metadata in-place (opens ZIP, patches `content.opf`, atomically replaces). Run with sudo:\\n\\n```bash\\nsudo python3 /DATA/.hermes/skills/media/media-file-management/scripts/fix_epub_metadata.py\\n```\\n\\n**Common problems:** literaturdownload.at books have year=0101 and wrong publisher; Tolino books may have inverted author names; ISBN is often missing even on commercial ebooks.\\n\\n### Fix PDF metadata\\n\\nUse `pymupdf` (`fitz`). PDFs must be owned by `az-a:samba`:\\n\\n```bash\\nsudo chown az-a:samba /media/HDD_1TB/Medien/Bücher/Author/*.pdf\\n```\\n\\n```python\\nimport fitz\\ndoc = fitz.open(\\\"book.pdf\\\")\\ndoc.set_metadata({\\\"title\\\": \\\"...\\\", \\\"author\\\": \\\"...\\\"})\\ndoc.saveIncr()\\ndoc.close()\\n```\\n\\n### Embed Cover Images\\n\\nUse `scripts/embed_cover.py` to add or replace cover images in EPUBs. Requires: `sudo chown az-a:samba` on the target EPUB files first.\\n\\n```bash\\n# Before running\\nsudo chown -R az-a:samba /media/HDD_1TB/Medien/Bücher/Author/\\n\\n# Run\\npython3 /DATA/.hermes/skills/media/media-file-management/scripts/embed_cover.py\\n```\\n\\n**Cover image sources** (preferred order):\\n\\n1. **Google Books** — most reliable. URL: `https://books.google.com/books/content?id=BOOKID&printsec=frontcover&img=1&zoom=2`. zoom=2 gives 575×750 (good). zoom=1 gives 128×170 (useless).\\n2. **Amazon** — `https://m.media-amazon.com/images/P/ISBN10.01._SCLZZZZZZZ_SX500_.jpg`. Pitfall: often returns a 1×1 GIF dummy if no cover available.\\n3. **DNB (Deutsche Nationalbibliothek)** — `https://d-nb.info/DNBID/04`. Returns a redirect to the cover. DNB ID lookup via ISBN search.\\n\\nThe `embed_cover.py` script patches `content.opf` manifest + meta tags, removes old cover entries, and adds the new JPEG to the ZIP. Works with or without existing covers.\\n\\n#### Cover retrieval for German/Austrian books — critical pitfalls\\n\\nFor German-language books, **Google Books API and OpenLibrary are unreliable** — Google returns wrong covers or zero results for many German ISBNs, and OpenLibrary always returns a 1×1 GIF placeholder for German editions not in its index.\\n\\n**Morawa.at (Austrian bookstore) — BEST source for German covers:**\\n- Serves `og:image` in static HTML — no JS needed\\n- URL pattern discovered via product page: `https://www.morawa.at/detail/ISBN-{ISBN}/Author/Title`\\n- Extraction: `curl -sL \\\"$URL\\\" | grep -oP 'property=\\\"og:image\\\"\\\\s+content=\\\"[^\\\"]*\\\"'`\\n- Download the `annotstream` URL directly: `https://www.morawa.at/annotstream/{ISBN}/COPL/Author/Title.jpg?sq=N`\\n- Always verify: `file cover.jpg` must say \\\"JPEG image data\\\", NOT \\\"GIF 1x1\\\"\\n- The Morawa ISBN may differ from the user's ISBN (different edition) — that's fine for covers. Confirm the cover matches the right book via `vision_analyze`\\n\\n**Other sources ranked:**\\n\\n| Source | Reliability | Notes |\\n|--------|------------|-------|\\n| **Morawa.at** | **BEST** | Static HTML, predictable `og:image` |\\n| Publisher website (Fischer, Suhrkamp) | Risky | JS-rendered SPAs — `curl` gets empty HTML |\\n| Thalia.at / other DE retailers | Risky | JS-rendered SPA — no HTML-extractable covers |\\n| Google Books API | **DO NOT USE** | Returns wrong covers for non-English ISBNs |\\n| OpenLibrary Covers | **DO NOT USE** | Always returns 1×1 GIF placeholder |\\n| DNB (German National Library) | Low | Needs DNB-ID via SRU API first; many ISBNs have 0 records |\\n\\n**Standalone cover embed script:** `scripts/ebook-management/embed_cover_epub.py` — reusable script that patches any EPUB:\\n```bash\\npython3 scripts/ebook-management/embed_cover_epub.py \\\"book.epub\\\" \\\"cover.jpg\\\"\\n```\\n\\n### Verification\\n\\nRe-run the scan script. Check: EPUBs have valid 4-digit year, correct publisher (not a download site), real ISBN (not a Mongo ID), and `has_cover: true` with correct `cover-image` manifest entry. PDFs have title and author.\\n\\n## Downloading Videos (yt-dlp)\\n\\nyt-dlp supports YouTube, Dailymotion, and many other platforms. For Dailymotion, extract metadata from the page HTML:\\n\\n```bash\\n# Get title from embedded JSON\\ncurl -sL \\\"https://www.dailymotion.com/video/VIDEO_ID\\\" \\\\\\n -H \\\"User-Agent: Mozilla/5.0 ...\\\" \\\\\\n | grep -oP '\\\"title\\\":\\\"[^\\\"]*\\\"' | head -5\\n```\\n\\nThen download:\\n\\n```bash\\n~/.local/bin/yt-dlp -o \\\"/tmp/Show_Name_SxxExx.%(ext)s\\\" \\\"URL\\\"\\n```\\n\\n### CRITICAL: Never download directly to /media/ mount without `--no-part` — TWO failure modes\\n\\nyt-dlp cannot reliably write to `/media/HDD_1TB/` with default settings. There are TWO distinct failure modes:\\n\\n**Failure 1 — Permission denied (root-owned directory):** The mount is owned by `root:root`. Even if you `chown` the target subdirectory to `az-a:users`, yt-dlp may still fail.\\n\\n**Failure 2 — Btrfs/Samba rename corruption (mid-download crash):** Even after `chown az-a:users` on the directory, yt-dlp creates `.part` fragment files with group `samba` (not `users`). At any point during download, Btrfs rename operations on `.part-FragN.part` → `.part-FragN` fail with `[Errno 2] No such file or directory`. The download crashes irrecoverably. This is a Btrfs + Samba group-ownership interaction — the Samba service interferes with fragment renames. This bug also affects `/tmp/` downloads (tmpfs) — the Samba group assignment follows the process, not the filesystem.\\n\\n**One reliable workaround — `--no-part` is the ONLY approach that works:**\\n\\n**Option A (ALWAYS USE THIS): `--no-part` — write directly, no fragment files, no rename operations:**\\n```bash\\n# ✅ RECOMMENDED — --no-part bypasses the Btrfs/Samba rename bug entirely\\npython3 -m yt_dlp --no-update --no-part -f \\\"best[height<=720]\\\" \\\\\\n -o \\\"/media/HDD_1TB/Medien/Serien/Show/Sxx/Show_Name_SxxExx.%(ext)s\\\" \\\"URL\\\"\\n```\\n`--no-part` writes the output file directly without `.part` fragment files. No fragment files = no rename operations = no Btrfs/Samba conflict. This works for files of any size, directly to `/media/HDD_1TB/`. Resulting files get group `samba` — this is normal and harmless. Also works with `~/.local/bin/yt-dlp` if preferred.\\n\\n**Option B (REMOVED — DO NOT USE): Download to `/tmp/` first, then move:**\\n```bash\\n# ❌ DO NOT USE — the Samba rename bug also affects /tmp/ downloads\\npython3 -m yt_dlp --no-update -o \\\"/tmp/Show_Name_SxxExx.%(ext)s\\\" \\\"URL\\\"\\n```\\n⚠️ `/tmp/` is tmpfs with limited space (~4 GB total, often only ~1.5 GB free). The Samba rename bug affects `/tmp/` downloads too — the `.part` files get group `samba` and fragment renames fail identically. This approach is NOT a viable fallback. Always use `--no-part`.\\n\\n```bash\\n# ❌ WRONG — will fail with either Permission denied or mid-download rename crash\\npython3 -m yt_dlp --no-update -o \\\"/media/HDD_1TB/Medien/Serien/Show/Sxx/Show_Name_SxxExx.%(ext)s\\\" \\\"URL\\\"\\n```\\n\\n**Cleanup after failed /media/ downloads:** Remove leftover `.part*` and `.ytdl` artifacts before retrying:\\n```bash\\nrm -f /media/HDD_1TB/Medien/Serien/Show/Sxx/Show_Name_SxxExx.mp4.part* \\\\\\n /media/HDD_1TB/Medien/Serien/Show/Sxx/Show_Name_SxxExx.mp4.ytdl\\n```\\n\\n## Plex Metadata Troubleshooting\\n\\nWhen Plex shows wrong metadata for a series (wrong show title, wrong episodes, wrong year), the problem is almost always a **mismatch** — Plex matched your files to the wrong series in its agent database. Fix it by diagnosing what Plex matched, then renaming files/folders so Plex can find the correct series on rescan. Full workflow: [references/plex-metadata-fix.md](references/plex-metadata-fix.md).\\n\\n### Quick workflow\\n\\n1. **Diagnose** — check Plex DB to see what was matched\\n2. **Rename** folder/files to be more specific (e.g. `Terra_X` → `Terra_X_Weltstaedte`)\\n3. **Rescan** library: `curl -s \\\"http://127.0.0.1:32400/library/sections/{id}/refresh?X-Plex-Token=$TOKEN\\\"`\\n4. **Fix metadata manually** if no online match exists — use PUT with query params (NOT JSON body)\\n5. **Upload poster** — must be 2:3 portrait (e.g. 1000×1500), NOT 16:9 landscape\\n\\n### Diagnosis: Check what Plex actually matched\\n\\n```bash\\nsqlite3 \\\"/DATA/AppData/plex/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db\\\" \\\\\\n \\\"SELECT id, title, metadata_type, \\\\\\\"index\\\\\\\", parent_id, year, guid FROM metadata_items WHERE title LIKE '%SearchTerm%' ORDER BY parent_id, \\\\\\\"index\\\\\\\";\\\"\\n```\\n\\nMetadata types: `2` = show, `3` = season, `4` = episode. The `guid` reveals what external ID Plex matched.\\n\\n### Finding correct episode titles from ZDF Mediathek\\n\\nZDF's website is a Next.js SPA — episode data is embedded in `self.__next_f.push()` calls containing GraphQL responses. The ZDF API (`api.zdf.de`) requires authentication; scrape the public page instead. See [references/plex-metadata-fix.md](references/plex-metadata-fix.md) for the extraction script.\\n\\n**Alternative sources:** `fernsehserien.de`, Wikipedia.\\n\\n### Manual metadata fix (when no online match exists)\\n\\nPlex PUT endpoint uses **query parameters**, NOT JSON body. JSON body returns 400 Bad Request.\\n\\n```bash\\nPLEX_TOKEN=\\\"UZBRFc2Y1psjzPNvnycU\\\"\\n\\n# Series\\ncurl -s -X PUT \\\"http://127.0.0.1:32400/library/metadata/{id}?title.value=Terra%20X%3A%20Weltst%C3%A4dte&year.value=2024&summary.value=...&studio.value=ZDF&X-Plex-Token=$PLEX_TOKEN\\\"\\n\\n# Episodes\\ncurl -s -X PUT \\\"http://127.0.0.1:32400/library/metadata/{ep_id}?title.value=New%20York&year.value=2024&X-Plex-Token=$PLEX_TOKEN\\\"\\n```\\n\\n### Upload poster — CRITICAL: aspect ratio\\n\\nPlex expects **2:3 portrait** posters (e.g. 1000×1500). Uploading a 16:9 landscape image (e.g. 1920×1080) causes Plex to show **black/nothing** instead of the image. Always crop/resize to portrait before uploading:\\n\\n```python\\nfrom PIL import Image\\nimg = Image.open('landscape_poster.jpg')\\nw, h = img.size\\n# Crop center to 2:3 ratio using full height\\ncrop_w = int(h * 2/3)\\nleft = (w - crop_w) // 2\\nportrait = img.crop((left, 0, left + crop_w, h))\\nportrait = portrait.resize((1000, 1500), Image.LANCZOS)\\nportrait.save('poster_portrait.jpg', quality=90)\\n```\\n\\n**Preferred: Local Media Assets** — place `poster.jpg` directly in the series folder and `S01/poster.jpg` in the season folder. Plex's Local Media Assets agent picks it up on next scan. This is the most reliable method and avoids API upload issues entirely.\\n\\n```bash\\nsudo cp poster_portrait.jpg \\\"/media/HDD_1TB/Medien/Serien/Show Name (Year)/poster.jpg\\\"\\nsudo cp poster_portrait.jpg \\\"/media/HDD_1TB/Medien/Serien/Show Name (Year)/S01/poster.jpg\\\"\\n```\\n\\n**API alternative:** Use `--data-binary`, NOT `-F` (multipart). Plex corrupts multipart uploads by writing boundary headers into the JPEG file.\\n\\n```bash\\ncurl -s -X POST \\\"http://127.0.0.1:32400/library/metadata/{id}/posters?X-Plex-Token=$PLEX_TOKEN\\\" \\\\\\n --data-binary @poster_portrait.jpg \\\\\\n -H \\\"Content-Type: image/jpeg\\\"\\n```\\n\\n**PITFALL: `curl -F` corrupts poster uploads.** Plex writes the entire multipart/form-data body (boundary headers + file content) into the bundle instead of just the JPEG. The file starts with `------------------...` instead of `JFIF`. Result: black/nothing in Plex. Never use `-F` for Plex poster uploads.\\n\\n### Plex DB quick reference\\n\\n- **DB path:** `/DATA/AppData/plex/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db`\\n- **`metadata_items`:** `id`, `title`, `parent_id`, `metadata_type` (2=show, 3=season, 4=episode), `index` (season/episode number), `year`, `guid`\\n- **Plex token:** `UZBRFc2Y1psjzPNvnycU` (stable, stored in Plex config)\\n\\n## YouTube Automation Pipeline\\n\\nZero-cost, fully automated video production for headless YouTube channels: Reddit stories, confessions, Top-10 lists, news narration, or any audio-over-stock-footage format. Everything runs on ZimaOS/Linux without a browser.\\n\\n### Pipeline\\n\\n```\\nReddit JSON API → edge-tts (narration) → yt-dlp (background footage) → ffmpeg (assembly)\\n```\\n\\n| Step | Tool | Cost | Headless |\\n|---|---|---|---|\\n| Content sourcing | Reddit `.json` API | Free | ✅ |\\n| Text-to-Speech | edge-tts (Azure Neural) | Free | ✅ |\\n| Background footage | yt-dlp (Minecraft/stock) | Free | ✅ |\\n| Assembly/render | ffmpeg | Free | ✅ |\\n| Upload to YouTube | Google OAuth | Free | ❌ Manual |\\n\\n### Setup\\n\\n```bash\\npython3 -m pip install edge-tts yt-dlp Pillow\\n```\\n\\n### 1. Content Sourcing (Reddit)\\n\\nAppend `.json` to any Reddit URL with a User-Agent header:\\n\\n```bash\\ncurl -s -H \\\"User-Agent: HermesBot/1.0\\\" \\\\\\n \\\"https://www.reddit.com/r/confessions/top.json?limit=5&t=week\\\" \\\\\\n | python3 -c \\\"\\nimport json, sys\\ndata = json.load(sys.stdin)\\nfor post in data['data']['children']:\\n d = post['data']\\n print(f\\\\\\\"TITLE: {d['title']}\\\\\\\")\\n print(f\\\\\\\"TEXT: {d['selftext'][:200]}...\\\\\\\")\\n print('---')\\n\\\"\\n```\\n\\nGood German subreddits: `r/Beichten`, `r/de`, `r/FragReddit`. English: `r/confessions`, `r/TrueOffMyChest`, `r/tifu`, `r/AITA`.\\n\\n**Pitfall: 403 Blocked** — Reddit aggressively blocks automated requests. If you get 403, use PullPush.io as fallback:\\n```bash\\ncurl -s \\\"https://api.pullpush.io/reddit/search/submission/?ids=POST_ID\\\"\\ncurl -s \\\"https://api.pullpush.io/reddit/search/comment/?link_id=POST_ID\\\"\\n```\\n\\n### 2. Text-to-Speech (edge-tts)\\n\\nUses Microsoft Azure Neural voices — free, rate-limited but generous, no API key:\\n\\n```bash\\n# German voices\\n~/.local/bin/edge-tts --list-voices | grep de-DE\\n\\n# Generate narration\\n~/.local/bin/edge-tts \\\\\\n --voice de-DE-ConradNeural \\\\\\n --text \\\"Dein Skripttext hier...\\\" \\\\\\n --write-media output.mp3\\n```\\n\\nAvailable German voices: `de-DE-ConradNeural` (male, friendly), `de-DE-KatjaNeural` (female), `de-DE-KillianNeural` (male), `de-DE-FlorianMultilingualNeural` (expressive male).\\n\\n**Pacing tip**: Add `...` or line breaks in the script for natural pauses.\\n\\n### 3. Background Footage (yt-dlp)\\n\\nDownload Creative Commons or gameplay footage:\\n\\n```bash\\n~/.local/bin/yt-dlp -f \\\"best[height<=1080]\\\" \\\\\\n --download-sections \\\"*00:00-10:00\\\" \\\\\\n -o \\\"/tmp/bg_footage.%(ext)s\\\" \\\\\\n \\\"https://youtube.com/watch?v=VIDEO_ID\\\"\\n```\\n\\nGood sources: Minecraft parkour, Subway Surfer, kinetic sand. Search: \\\"no copyright background video\\\".\\n\\n### 4. Assembly with ffmpeg\\n\\n```bash\\nffmpeg -stream_loop -1 -i bg_footage.mp4 \\\\\\n -i narration.mp3 \\\\\\n -shortest -c:v libx264 -c:a aac -b:a 128k \\\\\\n -movflags +faststart \\\\\\n -vf \\\"scale=1920:1080:force_original_aspect_ratio=decrease,pad=1920:1080:(ow-iw)/2:(oh-ih)/2\\\" \\\\\\n output.mp4\\n```\\n\\nKey options: `-stream_loop -1` (loop video), `-shortest` (stop at narration end), `-movflags +faststart` (web-optimized).\\n\\n**Audio ducking**: See `references/youtube-automation/ffmpeg-recipes.md` for sidechain compression, text overlays, fade in/out, and segment concatenation.\\n\\n### 5. Thumbnail Generation (Pillow)\\n\\n```python\\nfrom PIL import Image, ImageDraw\\nimg = Image.new('RGB', (1280, 720), color=(20, 20, 20))\\ndraw = ImageDraw.Draw(img)\\ndraw.multiline_text((640, 360), \\\"TITLE\\\\nHERE\\\", fill=(255,255,255),\\n anchor=\\\"mm\\\", align=\\\"center\\\")\\nimg.save('thumbnail.png')\\n```\\n\\n### 6. Upload (Manual Step)\\n\\nYouTube API v3 requires OAuth 2.0 with browser-based consent. On a headless ZimaOS this cannot be fully automated.\\n\\n**Workarounds:**\\n- Run OAuth once on a laptop, cache the refresh token\\n- Use `youtubeuploader` (Go binary) with a stored token\\n- Manual upload via YouTube Studio — Hermes places the finished video + thumbnail in a shared folder\\n\\n## Pitfalls\\n\\n- **`os.rename()` from sandbox fails**\\n- **Reddit 403**: Always set a `User-Agent` header; use PullPush.io as fallback\\n- **Audio duration mismatch**: Measure with `ffprobe -i narration.mp3 -show_entries format=duration`\\n- **Long scripts**: Split into segments, generate TTS per segment, then `ffmpeg -f concat`\\n- **yt-dlp sections**: `--download-sections` requires ffmpeg. Syntax is `*START-END`\\n- **Storage**: A 10-minute 1080p video is ~200-500 MB. Monitor disk space before batch processing.\\n\", \"path\": \"media/media-file-management/SKILL.md\", \"skill_dir\": \"/DATA/.hermes/skills/media/media-file-management\", \"linked_files\": {\"references\": [\"references/plex-metadata-fix.md\", \"references/movie-inventory-2026-05.md\", \"references/tv-inventory-2026-05.md\", \"references/audible-api-tagging.md\", \"references/audiobookshelf-metadata.md\"], \"scripts\": [\"scripts/scan_ebook_metadata.py\", \"scripts/tag_audiobooks_template.py\", \"scripts/fix_epub_metadata.py\", \"scripts/embed_cover.py\"]}, \"usage_hint\": \"To view linked files, call skill_view(name, file_path) where file_path is e.g. 'references/api.md' or 'assets/config.yaml'\", \"required_environment_variables\": [], \"required_commands\": [], \"missing_required_environment_variables\": [], \"missing_credential_files\": [], \"missing_required_commands\": [], \"setup_needed\": false, \"setup_skipped\": false, \"readiness_status\": \"available\"}",
"tool_call_id": "47cmda8z"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "jyalef3x",
"call_id": "jyalef3x",
"response_item_id": "fc_jyalef3x",
"type": "function",
"function": {
"name": "skill_view",
"arguments": "{\"name\":\"ai-video-production\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_view",
"content": "{\"success\": true, \"name\": \"ai-video-production\", \"description\": \"AI-gestützte Videoproduktion: Skript, Bildgenerierung (DALL-E/ChatGPT), TTS-Voiceover, ffmpeg-Assembly mit Ken-Burns-Effekt.\", \"tags\": [\"video\", \"ai\", \"dalle\", \"tts\", \"ffmpeg\", \"animation\", \"creative\"], \"related_skills\": [\"youtube-content\", \"comfyui\", \"ascii-video\"], \"content\": \"---\\nname: ai-video-production\\ndescription: \\\"AI-gestützte Videoproduktion: Skript, Bildgenerierung (DALL-E/ChatGPT), TTS-Voiceover, ffmpeg-Assembly mit Ken-Burns-Effekt.\\\"\\nversion: 1.0.0\\nauthor: Hermes Agent (2026-06-18)\\nlicense: MIT\\nmetadata:\\n hermes:\\n tags: [video, ai, dalle, tts, ffmpeg, animation, creative]\\n related_skills: [youtube-content, comfyui, ascii-video]\\n---\\n\\n# AI Video Production Pipeline\\n\\nVollständiger Workflow zum Erstellen animierter Erklärvideos mit AI — von der Skript-Adaption bis zum fertigen MP4.\\n\\n## Pipeline-Übersicht\\n\\n```\\nSkript schreiben → DALL-E-Bilder generieren → TTS-Voiceover → ffmpeg-Assembly → MP4\\n```\\n\\n## Schritt 1: Skript\\n\\n- **Hermes oder Subagent** schreibt das Skript (3–4 Min, ~15 Szenen)\\n- **Stil:** Kurze Sätze, visuelle Metaphern, ein wiedererkennbarer Charakter\\n- **Struktur:** Einleitung → Problem → Lösung (3 Akte) → Call-to-Action\\n- Pro Szene: 1–2 Sätze Text + visuelle Beschreibung\\n\\n## Schritt 2: Bildgenerierung\\n\\n### Weg A: DALL-E via ChatGPT (empfohlen)\\n- User generiert Bilder manuell in ChatGPT/DALL-E\\n- **Character-Konsistenz:** JEDER Prompt enthält eine detaillierte Charakter-Referenz:\\n - Körperform, Farben (exakte Hex-Werte), Federmarkierungen, Augenproportionen, Schnabelform, Füße\\n - Art-Style: Outlines, Shading, Farbpalette\\n- **Format:** Querformat 1792x1024 für 16:9 Video\\n- **Prompt-Sprache:** Deutsch (für ChatGPT)\\n\\n### Weg B: ComfyUI (lokal, siehe `comfyui`-Skill)\\n- Läuft auf ZimaOS, kein API-Key nötig\\n- Qualität unter DALL-E-3-Niveau\\n\\n## Schritt 3: Voiceover\\n\\n### ⚠️ KRITISCH: Edge-TTS Stimme muss zur Skript-Sprache passen!\\n\\nDer `text_to_speech`-Befehl nutzt die in `config.yaml` unter `tts.edge.voice` konfigurierte Stimme. **Ist dort eine englische Stimme eingetragen (z.B. `en-US-AriaNeural`), liest sie deutschen Text mit englischem Akzent — klingt maschinell und falsch.**\\n\\n**Workaround: edge-tts Python-Library direkt mit deutscher Stimme:**\\n\\n```bash\\npython3 -m pip install edge-tts\\n```\\n\\n```python\\nimport asyncio, edge_tts\\n\\nVOICE = \\\"de-DE-KillianNeural\\\" # Männlich, warm, freundlich\\n# Alternativen:\\n# de-DE-AmalaNeural — weiblich, klar\\n# de-DE-ClarissaNeural — weiblich, warm\\n# de-DE-BerndNeural — männlich, tief\\n# de-DE-ElkeNeural — weiblich, hell\\n# de-DE-KasperNeural — männlich, jugendlich\\n\\nasync def gen():\\n for key, text in texts.items():\\n comm = edge_tts.Communicate(text, VOICE)\\n await comm.save(f\\\"/tmp/{key}_voice_de.mp3\\\")\\n\\nasyncio.run(gen())\\n```\\n\\n- **Pro Szene eine separate MP3-Datei** — ermöglicht präzises Timing\\n- **Stimme:** Edge-TTS (kostenlos), Deutsch, männlich/weiblich wählbar\\n- Alternativ: ElevenLabs (API-Key nötig, bessere Qualität)\\n- **Verfügbare Stimmen auflisten:** `edge-tts --list-voices | grep de-DE`\\n\\n## Schritt 4: ffmpeg-Assembly\\n\\n### Ken-Burns-Effekt (Zoom + Pan)\\n\\n```bash\\nffmpeg -y -loop 1 -i bild.jpg -i audio.mp3 \\\\\\n -filter_complex \\\\\\n \\\"[0:v]scale=1792:1024:force_original_aspect_ratio=decrease,\\n pad=1792:1024:(ow-iw)/2:(oh-ih)/2,\\n zoompan=z='min(zoom+0.0005,1.15)':d=FRAMES:x='iw/2-(iw/zoom/2)':y='ih/2-(ih/zoom/2)':s=1792x1024,fps=30[v]\\\" \\\\\\n -map \\\"[v]\\\" -map \\\"1:a\\\" \\\\\\n -c:v mpeg4 -q:v 5 -c:a aac -b:a 128k \\\\\\n -t DURATION -shortest scene_N.mp4\\n```\\n\\n- `d=FRAMES` = `duration × fps` (z.B. 10.752s × 30fps = 323)\\n- `zoom=z='min(zoom+0.0005,1.15)'` — sanfter Zoom von 1.0 auf 1.15\\n\\n### Konkatenierung\\n\\n```bash\\n# concat.txt:\\n# file '/tmp/scene_1.mp4'\\n# file '/tmp/scene_2.mp4'\\n# ...\\n\\nffmpeg -y -f concat -safe 0 -i concat.txt -c copy final.mp4\\n```\\n\\n### ⚠️ ZimaOS ffmpeg Pitfalls\\n\\n- **Kein libx264!** Verwende `-c:v mpeg4 -q:v 5` (niedrigere q = bessere Qualität)\\n- **Kein `-crf`!** Die Option existiert nicht in dieser Build\\n- **Kein `-vf` mit zoompan!** Muss als `-filter_complex` mit benanntem Output `[v]`\\n- Verfügbare Encoder prüfen: `ffmpeg -encoders 2>&1 | grep -iE 'h264|mpeg4'`\\n\\n## Schritt 5: Hintergrundmusik (optional)\\n\\n- **Suno AI:** Via `songwriting-and-ai-music`-Skill\\n- **AudioCraft:** Via `audiocraft-audio-generation`-Skill\\n- Lo-fi, instrumental, ~3:30 Länge\\n- Mit ffmpeg druntermischen: `-filter_complex \\\"[1:a]volume=0.3[bg];[0:a][bg]amix=inputs=2:duration=first\\\"`\\n\\n## Charakter-Referenz-Template\\n\\nFür konsistente DALL-E-Bilder diesen Block in JEDEN Prompt einfügen:\\n\\n```\\n[Charakter-Name] hat einen [Körperform] [Farbe]-farbenen Körper mit \\n[Markierungs-Beschreibung], [Kopf-Details], [Augen-Beschreibung] \\n(Augen nehmen [X] der Kopfhöhe ein), [Schnabel-Beschreibung] in \\n[Schnabel-Farbe], [Füße-Beschreibung] in der gleichen [Schnabel-Farbe].\\nFlache Illustration mit mitteldicken schwarzen Outlines, minimale \\nSchattierung, Kinderbuch-Ästhetik. Querformat 1792x1024.\\n```\\n\\n## Beispiel: Komplettes Video\\n\\nSiehe `references/kiwi-video-example.md` — vollständiges Skript, 15 Szenen-Prompts, Voiceover-Texte und ffmpeg-Kommandos für das „How to do hard things\\\"-Adaptionsvideo.\\n\\n## Verwandte Skills\\n\\n- `youtube-content` — Transkripte extrahieren (für Analyse von Referenzvideos)\\n- `comfyui` — Lokale Bildgenerierung (Alternative zu DALL-E)\\n- `ascii-video` — ASCII-Art-Videos (anderer Stil)\\n- `songwriting-and-ai-music` — Hintergrundmusik via Suno\\n\", \"path\": \"creative/ai-video-production/SKILL.md\", \"skill_dir\": \"/DATA/.hermes/skills/creative/ai-video-production\", \"linked_files\": {\"references\": [\"references/kiwi-video-example.md\"]}, \"usage_hint\": \"To view linked files, call skill_view(name, file_path) where file_path is e.g. 'references/api.md' or 'assets/config.yaml'\", \"required_environment_variables\": [], \"required_commands\": [], \"missing_required_environment_variables\": [], \"missing_credential_files\": [], \"missing_required_commands\": [], \"setup_needed\": false, \"setup_skipped\": false, \"readiness_status\": \"available\", \"metadata\": {\"hermes\": {\"tags\": [\"video\", \"ai\", \"dalle\", \"tts\", \"ffmpeg\", \"animation\", \"creative\"], \"related_skills\": [\"youtube-content\", \"comfyui\", \"ascii-video\"]}}}",
"tool_call_id": "jyalef3x"
},
{
"role": "assistant",
"content": "",
"reasoning": "**Defining Scope: Media Production**\n\nI'm now zeroing in on defining the scope. It's becoming clear that `ai-video-production` falls under the umbrella of \"Media Production\". The overlap between \"YouTube Automation Pipeline\" within `media-file-management` and `ai-video-production`, especially concerning Reddit, is an interesting area of convergence. This highlights specific synergies to explore within this particular branch.\n\n\n",
"finish_reason": "tool_calls",
"reasoning_content": "**Defining Scope: Media Production**\n\nI'm now zeroing in on defining the scope. It's becoming clear that `ai-video-production` falls under the umbrella of \"Media Production\". The overlap between \"YouTube Automation Pipeline\" within `media-file-management` and `ai-video-production`, especially concerning Reddit, is an interesting area of convergence. This highlights specific synergies to explore within this particular branch.\n\n\n",
"tool_calls": [
{
"id": "9i8gwgzu",
"call_id": "9i8gwgzu",
"response_item_id": "fc_9i8gwgzu",
"type": "function",
"function": {
"name": "skill_view",
"arguments": "{\"name\":\"music-resources\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_view",
"content": "{\"success\": true, \"name\": \"music-resources\", \"description\": \"Find sheet music, chords, tabs, and notation online — search strategies, major platforms, and Turkish-specific resources.\", \"tags\": [], \"related_skills\": [], \"content\": \"---\\nname: music-resources\\ndescription: Find sheet music, chords, tabs, and notation online — search strategies, major platforms, and Turkish-specific resources.\\ncategory: media\\ntriggers:\\n - \\\"Noten für [song]\\\"\\n - \\\"sheet music / chords / tabs for [song]\\\"\\n - \\\"Akkorde [song]\\\"\\n - \\\"nota / akor ara\\\"\\n - \\\"music notation search\\\"\\n - \\\"Melodie extrahieren\\\"\\n - \\\"Noten aus Audio generieren\\\"\\n - \\\"transcribe melody from audio\\\"\\n---\\n\\n# Music Resources — Finding Sheet Music, Chords & Notation Online\\n\\n## Quick Search Strategy\\n\\nWhen `web_search` tool is unavailable, use **curl-based fallbacks**:\\n\\n### 1. DuckDuckGo HTML endpoint (no JS required)\\n```bash\\ncurl -sL -A \\\"Mozilla/5.0\\\" \\\\\\n \\\"https://html.duckduckgo.com/html/?q=\\\" \\\\\\n | grep -oP 'class=\\\"result__a\\\"[^>]*>.*?'\\n```\\n\\n### 2. Direct site search\\nQuery known notation platforms directly via their search URLs:\\n```bash\\ncurl -sL -A \\\"Mozilla/5.0\\\" \\\"?s=\\\" | grep -iE ''\\n```\\n\\n## Major International Platforms\\n\\n| Platform | Search URL | Notes |\\n|----------|-----------|-------|\\n| MuseScore | `musescore.com/sheetmusic?text=...` | Cloudflare-protected; JS required |\\n| Ultimate Guitar | `ultimate-guitar.com/search.php?search_type=title&value=...` | Tabs & chords |\\n| Songsterr | `songsterr.com/?pattern=...` | Interactive tabs |\\n\\n## Turkish Notation & Chord Sites\\n\\nSee `references/turkish-notation-sites.md` for the full directory.\\n\\nKey sites:\\n- **gitaregitim.net** — Gitar notaları ve tab arşivi (largest Turkish guitar tab site)\\n- **akor.gitaregitim.net** — Akor deposu (chord database)\\n- **notalar.net** — Kolay nota (easy notation)\\n- **notaveakor.com** — Nota ve akor\\n- **sahaney.com** — Ney notation archive (Turkish classical/ney)\\n- **neyzenim.com** — Neyzenim nota arşivi\\n- **akorculuk.com** — Akor, tab, ritim\\n\\n## Genre-Specific Knowledge\\n\\n### İrfan Türküleri / Sufi Music\\nSpiritual Turkish songs (ilahi, irfan türküleri) are **rarely published as sheet music**. They are traditionally transmitted orally. If notation isn't found on any major site, it likely doesn't exist publicly.\\n\\n### Fallback options for notation-less songs:\\n1. **Audio analysis (primary)** — Use Python + librosa for key/chord extraction. `songsee` (Go CLI) is an alternative but requires Go installed (often unavailable). The Python approach is more reliable:\\n - Download audio: `yt-dlp -x --audio-format wav --no-part -o /tmp/song.wav \\\"\\\"`\\n - Analyze: see `references/audio-analysis-librosa.md` for the full script (key estimation via Krumhansl-Schmuckler, chroma per beat, tempo detection)\\n - **Pitfall**: librosa CQT on full tracks (>3 min) can timeout. Use `sr=22050, duration=60.0` for a representative slice.\\n - **Pitfall**: `librosa.beat.beat_track` returns tempo as numpy array — use `.item()` to extract scalar.\\n2. **Audio analysis — full melody to sheet music** — When the user wants actual notation (Noten), not just chords. Full pipeline: spectral peak extraction → ABC notation → LilyPond → PNG sheet music. See `references/melody-to-notation.md` for the complete script and workflow.\\n - **Trigger phrases**: \\\"Melodie extrahieren\\\", \\\"Noten aus Audio\\\", \\\"transcribe melody\\\", \\\"Noten generieren\\\"\\n - **Pitfall**: `librosa.pyin` fails on melismatic/drone-heavy music (Turkish makam, Sufi). Use spectral peak + median filter instead.\\n - **Pitfall**: LilyPond is rarely pre-installed. Download the static binary from GitLab (no root needed).\\n3. **YouTube tutorials** — Search for cover/tutorial videos that may show fingerings\\n4. **Direct inquiry** — Contact site owners (e.g. sahaney.com, neyzenim.com) via contact forms\\n\\n## Pitfalls\\n\\n- **Cloudflare/bot protection**: MuseScore and many large platforms block curl. Use DuckDuckGo as intermediary or accept that JS-only sites are unreachable without a browser.\\n- **Turkish character encoding**: Always URL-encode Turkish characters (ğ → `%C4%9F`, ş → `%C5%9F`, ı → `%C4%B1`, İ → `%C4%B0`).\\n- **Site search URL format varies**: Some use `?s=`, others use `?q=` or `/search/`. Check the site's search form HTML to determine the correct parameter.\\n- **Empty results are common**: Many Turkish traditional/folk songs have no published notation. Don't keep searching indefinitely — after checking the top 5-6 sites, offer alternatives.\\n\", \"path\": \"media/music-resources/SKILL.md\", \"skill_dir\": \"/DATA/.hermes/skills/media/music-resources\", \"linked_files\": {\"references\": [\"references/melody-to-notation.md\", \"references/turkish-notation-sites.md\", \"references/audio-analysis-librosa.md\"]}, \"usage_hint\": \"To view linked files, call skill_view(name, file_path) where file_path is e.g. 'references/api.md' or 'assets/config.yaml'\", \"required_environment_variables\": [], \"required_commands\": [], \"missing_required_environment_variables\": [], \"missing_credential_files\": [], \"missing_required_commands\": [], \"setup_needed\": false, \"setup_skipped\": false, \"readiness_status\": \"available\"}",
"tool_call_id": "9i8gwgzu"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "a4lzrtmz",
"call_id": "a4lzrtmz",
"response_item_id": "fc_a4lzrtmz",
"type": "function",
"function": {
"name": "skill_view",
"arguments": "{\"name\":\"technical-product-spec\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_view",
"content": "{\"success\": true, \"name\": \"technical-product-spec\", \"description\": \"Write deep technical product specifications in Stripe/Cloudflare documentation style — architecture, AI/ML pipelines, business models, competitive analysis, MVP definition, and roadmap. Paired with dark-themed architecture diagrams.\", \"tags\": [\"product-spec\", \"architecture\", \"documentation\", \"startup\", \"defense\", \"ai\"], \"related_skills\": [\"architecture-diagram\", \"writing-plans\", \"plan\"], \"content\": \"---\\nname: technical-product-spec\\ndescription: \\\"Write deep technical product specifications in Stripe/Cloudflare documentation style — architecture, AI/ML pipelines, business models, competitive analysis, MVP definition, and roadmap. Paired with dark-themed architecture diagrams.\\\"\\nversion: 1.0.0\\ncategory: software-development\\nmetadata:\\n hermes:\\n tags: [product-spec, architecture, documentation, startup, defense, ai]\\n related_skills: [architecture-diagram, writing-plans, plan]\\n---\\n\\n# Technical Product Specification\\n\\nWrite comprehensive, technically rigorous product specifications for software/AI products. The output is a markdown document in the style of Stripe's API docs or Cloudflare's technical blog — precise, concrete, no marketing fluff. Assume the reader is technically literate.\\n\\n## When to Use\\n\\n- User asks for a product spec, product document, or \\\"how would this product work?\\\"\\n- User wants a deep-dive on a startup idea or technical concept\\n- User says \\\"wie wäre das Produkt?\\\" or \\\"spec it out\\\" or \\\"give me the full product\\\"\\n- Any time a technical product needs formal documentation beyond a quick summary\\n- User asks for startup ideas and then picks one to explore deeply\\n\\n## Workflow\\n\\n1. **Understand the domain** — research competitors, technical constraints, and the unique wedge. If the user has already described the idea, extract the core insight.\\n2. **Delegate the writing** to Kimi K2.7 Code via `delegate_task` with a detailed self-contained spec (see Delegation Pattern below).\\n3. **Pair with architecture diagram** — if the product has a system architecture, also generate an HTML diagram using the `architecture-diagram` skill. Load the skill and its template first.\\n4. **Deliver both files** — the markdown spec and the HTML diagram. Verify file sizes and spot-check content.\\n\\n## Document Structure\\n\\nThe spec document must follow this structure (adapt section names to the domain, but keep the skeleton):\\n\\n| Section | Purpose |\\n|---------|---------|\\n| **Product Name & Tagline** | One-line identity. Name + italic tagline. |\\n| **Executive Summary** | 2–3 paragraphs. Strategic thesis. What, why, for whom. |\\n| **The Problem** | Quantified with real numbers, real examples, and why current solutions fail. |\\n| **How It Works** | Phased pipeline or component breakdown. High-level before deep-dive. |\\n| **Technical Architecture** | Component table (Tier, Component, Technology, Purpose). Technology choices with rationale (why Kafka over RabbitMQ, why Neo4j over PostgreSQL). |\\n| **AI/ML Pipeline Deep-Dive** | Models, scoring formulas, training data, the technical wedge. Code blocks for JSON schemas and formulas. |\\n| **Key Differentiator / Wedge** | What makes this product unique. Why competitors can't easily copy it. This is the most important section — it defines the company. |\\n| **Data Sources / Inputs** | Where data comes from, collection methods, limitations, platform-by-platform breakdown. |\\n| **Outputs / Intelligence Products** | What the customer receives. Dashboards, reports, APIs, alerts. |\\n| **Deployment Models** | SaaS, on-premise, air-gapped, classified. Per-model details. |\\n| **Business Model** | Pricing tiers table, target customers, revenue logic, initial targets. |\\n| **Competitive Landscape** | Table: Competitor, Strength, What They Miss. Plus our wedge summary. |\\n| **MVP Definition** | 6-week scope. In scope / out of scope. Success criteria. |\\n| **Roadmap** | 18-month quarterly milestones table. |\\n| **Team Requirements** | Roles table with responsibilities. |\\n| **Risk & Mitigation** | Table: Risk, Likelihood, Mitigation. |\\n| **Why Now** | Market timing, regulatory tailwinds, funding windows, threat landscape. |\\n\\n## Tone & Style\\n\\n- **Technical, not marketing.** Use concrete numbers, real threat actor names, specific technologies.\\n- **Write like Stripe API docs or Cloudflare blog.** Assume reader is technically literate.\\n- **No fluff adjectives.** \\\"Robust,\\\" \\\"cutting-edge,\\\" \\\"best-in-class,\\\" \\\"revolutionary\\\" → delete. Replace with specs.\\n- **Quantify everything.** Not \\\"fast detection\\\" but \\\"under 60 minutes from seed to alert.\\\"\\n- **Use tables** for comparisons, component breakdowns, pricing, roadmaps, risks.\\n- **Code blocks** for JSON schemas, scoring formulas, API examples, config snippets.\\n- **Real examples** over hypotheticals. Name actual threat actors, real events, existing competitors.\\n- **No pipe tables in Telegram responses** — but the markdown file itself can use them freely.\\n\\n## Architecture Diagram Pairing\\n\\nWhen the product has a system architecture, generate a companion HTML diagram using the `architecture-diagram` skill:\\n\\n1. Load `architecture-diagram` via `skill_view(name=\\\"architecture-diagram\\\")`\\n2. Load the template via `skill_view(name=\\\"architecture-diagram\\\", file_path=\\\"templates/template.html\\\")`\\n3. Map components to semantic colors:\\n - External/Sources → slate (#94a3b8)\\n - Collection/Ingestion → amber (#fbbf24)\\n - AI/ML Processing → emerald (#34d399)\\n - Detection/Attribution/Security → rose (#fb7185)\\n - Knowledge Store/Database → violet (#a78bfa)\\n - Delivery/API/Frontend → cyan (#22d3ee)\\n - Message Bus → orange (#fb923c)\\n4. Delegate diagram creation to Kimi K2.7 Code with full component list, layout, and color mapping\\n5. Save as `.html` file alongside the spec\\n\\n## Delegation Pattern\\n\\nBoth the spec document and the architecture diagram must be delegated to Kimi K2.7 Code via `delegate_task`. Never write them inline.\\n\\nThe delegation message must be a self-contained spec containing:\\n- **Goal:** What files to create, where to save them\\n- **Full structure outline** for the markdown document\\n- **Tone requirements** (Stripe/Cloudflare style, technical, no fluff)\\n- **Key technical details** and the unique wedge — don't make the sub-agent guess the core insight\\n- **For the diagram:** Color mappings, full component list with tiers, layout direction, security boundaries, dimensions\\n- **User context:** Name, preferences, relevant background\\n\\nExample delegation structure:\\n```\\nGoal: Create two files: /path/to/product-spec.md and /path/to/architecture.html\\n\\nDocument structure: [list all sections from the structure table above]\\nTone: [Stripe/Cloudflare technical style requirements]\\nKey wedge: [the unique differentiator]\\nDiagram: [color mapping, component list, tiers, dimensions]\\nUser context: [name, preferences]\\n```\\n\\n## Documentation Website (Optional Step 5)\\n\\nWhen the user wants a shareable website (e.g. \\\"Gib mir das als Website mit Link\\\"), combine the spec and diagram into a single-file HTML documentation site:\\n\\n1. **Delegate to Kimi K2.7 Code** with a spec containing:\\n - Source files to read: the `.md` spec and `.html` diagram\\n - Design: dark theme (#020617), JetBrains Mono, sticky nav, all sections from spec\\n - The wedge section must be visually highlighted (rose-tinted card, badge)\\n - Embedded SVG diagram inline in the Architecture section\\n - Color accents matching the diagram's semantic palette\\n - No JS frameworks, pure HTML/CSS, self-contained\\n\\n2. **Build strategy for large files (>50KB):** Single `write_file` calls can cause sub-agent timeouts at 600s. Use terminal `cat >>` append commands to build the file in chunks (head+CSS, then sections in groups of 3-4, then footer). Verify with `wc -c` and `tail -3` after each chunk.\\n\\n3. **Serve it:** Start `python3 -m http.server --bind 127.0.0.1 &` in the file's directory, then tunnel with cloudflared (see `local-server-public-access` skill). Extract the tunnel URL from `process log` after ~5 seconds.\\n\\n4. **Permissions note:** `/DATA/` is root-owned on ZimaOS. Use `sudo` for writes, or check with `ls -la` first.\\n\\n## Pitfalls\\n\\n- **Don't write the spec inline.** Always delegate to Kimi K2.7 Code for file creation.\\n- **Don't skip the architecture diagram.** If the product has a system, visualize it. The user expects both.\\n- **Don't use marketing language.** The user wants technical depth, not pitch-deck fluff. Delete adjectives, add specs.\\n- **Don't forget the wedge.** Every spec must clearly articulate what makes this product unique and why competitors can't easily copy it. This is the most important section.\\n- **Don't make up competitor names.** Research real competitors in the space or use well-known analogs.\\n- **Don't produce pipe tables in Telegram.** The markdown file can have them; Telegram responses should use bullet lists or key-value pairs.\\n- **Don't deliver without spot-checking.** After delegation, read the first ~80 lines and last ~30 lines of the spec to verify quality.\\n- **Large HTML files (>50KB) timeout sub-agents.** Build in chunks via terminal `cat >>` append. Don't use a single `write_file` for the full document.\\n- **`/DATA/` is root-owned on ZimaOS.** Always `sudo` for writes, or verify permissions first with `ls -la`.\\n\\n## Reference Example\\n\\nSee `references/veritas-example.md` for a complete real-world example: the VERITAS AI Counter-Disinformation Platform spec, architecture diagram, and documentation website, created June 2026. This is the canonical reference for structure, tone, depth, and the full spec→diagram→website workflow.\\n\", \"path\": \"software-development/technical-product-spec/SKILL.md\", \"skill_dir\": \"/DATA/.hermes/skills/software-development/technical-product-spec\", \"linked_files\": {\"references\": [\"references/veritas-example.md\"]}, \"usage_hint\": \"To view linked files, call skill_view(name, file_path) where file_path is e.g. 'references/api.md' or 'assets/config.yaml'\", \"required_environment_variables\": [], \"required_commands\": [], \"missing_required_environment_variables\": [], \"missing_credential_files\": [], \"missing_required_commands\": [], \"setup_needed\": false, \"setup_skipped\": false, \"readiness_status\": \"available\", \"metadata\": {\"hermes\": {\"tags\": [\"product-spec\", \"architecture\", \"documentation\", \"startup\", \"defense\", \"ai\"], \"related_skills\": [\"architecture-diagram\", \"writing-plans\", \"plan\"]}}}",
"tool_call_id": "a4lzrtmz"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "a80xma2w",
"call_id": "a80xma2w",
"response_item_id": "fc_a80xma2w",
"type": "function",
"function": {
"name": "skill_view",
"arguments": "{\"name\":\"zeitgeist-app-development\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_view",
"content": "{\"success\": true, \"name\": \"zeitgeist-app-development\", \"description\": \"Modify the Zeitgeist single-file HTML/CSS/JS apps (zeitgeist.html, anki.html, vault.html, pruefungsmanager.html). Delegation pattern, architecture, CSS conventions, and pitfalls.\", \"tags\": [], \"related_skills\": [], \"content\": \"---\\nname: zeitgeist-app-development\\ndescription: Modify the Zeitgeist single-file HTML/CSS/JS apps (zeitgeist.html, anki.html, vault.html, pruefungsmanager.html). Delegation pattern, architecture, CSS conventions, and pitfalls.\\n---\\n\\n# Zeitgeist App Development\\n\\nModifications to the Zeitgeist application suite at `/media/HDD_1TB/Zeitgeist/`.\\n\\n## Architecture\\n\\n- **Single-file apps**: Each module is one self-contained HTML file (no build step, no frameworks)\\n - `zeitgeist.html` — daily Pomodoro tracker with day cards, rainbow/silver/gold tiers\\n - `anki.html` — FSRS-4.5 spaced repetition flashcard system with decks, import, Dojo mode\\n - `vault.html` — notes/abbreviations\\n - `pruefungsmanager.html` — exam manager (LL.B.)\\n- **Shared**: `shared.js` and `shared.css` provide cross-app theming, data sync (`ZG.adopt`, `ZG.save`), and PWA support\\n- **Storage**: `localStorage` with keys like `zeitgeist-v2`, `zeitgeist-anki-v2`, `vault-abbr`. Server sync via `fetch('/api/data')` with timestamp-based merge\\n- **Theming**: CSS custom properties on `:root` and `html.dark`. Dark mode via `ZG.initTheme()`. Font: Lora (Google Fonts) + system-ui\\n- **Pomodoro**: Shared across pages via `BroadcastChannel` and `localStorage('zeitgeist-pomo')`\\n\\n## Delegation Workflow\\n\\nALL code changes MUST be delegated to Kimi K2.7 Code via `delegate_task`. Never modify these files directly.\\n\\n### Step 1: Read the full file\\nRead the target file completely to understand structure, existing patterns, and line numbers. For anki.html (~2500+ lines), read in chunks.\\n\\n### Step 2: Write a detailed spec\\nThe spec must include:\\n- **Goal**: What the feature does, in user-facing terms\\n- **File path**: Absolute path to the single file\\n- **Line references**: Approximate line numbers for every function/section that needs changes (e.g., `newCard` ~1208, `vEditor` ~1518, `saveCard` ~2071)\\n- **CSS examples**: Copy-paste existing relevant CSS from the file so the sub-agent can match the style (e.g., existing rainbow animation keyframes, existing card-row styles)\\n- **Data model changes**: Exact field additions with defaults\\n- **UI placement**: Where in the DOM the new elements go\\n- **Constraints**: Single-file, no external deps, dark mode support (`html.dark` selectors), mobile-responsive (existing `@media` queries), don't break existing functionality\\n- **Verification checklist**: 5-7 specific things to check after implementation\\n\\n### Step 3: Delegate\\nUse `delegate_task` with `toolsets: [\\\"file\\\", \\\"terminal\\\"]`. The sub-agent runs on Kimi K2.7 Code.\\n\\n### Step 4: Verify\\nAfter delegation completes, spot-check critical touchpoints:\\n- `search_files` for the new field/class/function name across the file\\n- `read_file` at key sections (data model, editor, save function, learn queue, learn view)\\n- **Run `node --check` on the extracted JS**: The app is a single HTML file, so extract the main `', html, re.DOTALL)\\n with open('/tmp/anki_js_check.js', 'w') as out:\\n out.write(scripts[0])\\n \\\" && node --check /tmp/anki_js_check.js\\n ```\\n If `node --check` exits 0, the JS is syntactically valid. If it fails, read the error line, map it back to the HTML file with `grep -n`, and fix.\\n\\n## CSS Conventions\\n\\n- **Variables**: `--bg`, `--card`, `--border`, `--border-strong`, `--text`, `--text-2`, `--text-3`, `--accent`, `--accent-hover`, `--accent-light`, `--green`, `--red`, `--orange`, `--shadow-sm/md/lg`, `--r` (border-radius)\\n- **Dark mode**: Duplicate rules under `html.dark` selector with adjusted colors (darker backgrounds, lighter text, reduced opacity on effects)\\n- **Animations**: Use `@keyframes` with cubic-bezier easing. Existing patterns: `rainbow-flow` (8s background-position), `silver-shimmer`/`gold-shimmer` (linear gradient sweeps), `fade-in-up` (staggered entry)\\n- **Cards**: `.card-row` for list items, `.flip-face` for learn view, `.deck-card` for deck grid\\n- **Mobile**: `@media (max-width: 640px)` and `(max-width: 400px)` breakpoints. Mobile often uses `display:none` for desktop elements and switches to grid layouts\\n\\n## Pitfalls\\n\\n- **Template literals**: The JS uses deeply nested template literals with ternary expressions. Be careful with quote escaping — use `\\\\`` for backticks inside templates\\n- **Nested ternary closing parens**: When adding a new ternary branch inside an existing nested ternary in a template literal, count the closing parentheses carefully. The pattern ``) : ...` needs to become ``)) : ...` when you add a wrapping ternary. A missing `)` causes a `SyntaxError: Unexpected token ':'` that breaks ALL JS parsing — the entire app goes blank. Always run `node --check` after changes to catch this.\\n- **`esc()` function**: Always wrap user data in `esc()` when rendering into HTML to prevent XSS\\n- **FSRS state**: Cards have `state`, `stability`, `difficulty`, `dueDate`, `lapses`, `learningStep`. Don't add fields that conflict with FSRS rate logic\\n- **`ZG.save` vs `localStorage.setItem`**: Always use `ZG.save(key, value)` for data persistence — it handles server sync\\n- **Import flow**: `.apkg` import uses lazy-loaded JSZip + sql.js from CDN. Don't touch this unless specifically requested\\n- **Dojo mode**: A separate learn path (`learn.dojo = true`) that shows only \\\"Nochmal\\\"/\\\"Weiter\\\" buttons and doesn't persist FSRS state. Any new learn-mode feature must handle both normal and Dojo paths\\n\", \"path\": \"software-development/zeitgeist-app-development/SKILL.md\", \"skill_dir\": \"/DATA/.hermes/skills/software-development/zeitgeist-app-development\", \"linked_files\": null, \"usage_hint\": null, \"required_environment_variables\": [], \"required_commands\": [], \"missing_required_environment_variables\": [], \"missing_credential_files\": [], \"missing_required_commands\": [], \"setup_needed\": false, \"setup_skipped\": false, \"readiness_status\": \"available\"}",
"tool_call_id": "a80xma2w"
},
{
"role": "assistant",
"content": "",
"reasoning": "**Categorizing Skillsets**\n\nI'm currently sorting some concepts. It seems `zeitgeist-app-development` is a very specific project, and `technical-product-spec` is a more general skill. Both are within the `software-development` category. I'm thinking about creating a central `software-development` umbrella, but I need to check if one exists already. And looking at `skills_list`, there are a lot of skills to account for.\n\n\n",
"finish_reason": "tool_calls",
"reasoning_content": "**Categorizing Skillsets**\n\nI'm currently sorting some concepts. It seems `zeitgeist-app-development` is a very specific project, and `technical-product-spec` is a more general skill. Both are within the `software-development` category. I'm thinking about creating a central `software-development` umbrella, but I need to check if one exists already. And looking at `skills_list`, there are a lot of skills to account for.\n\n\n",
"tool_calls": [
{
"id": "3ytqgogh",
"call_id": "3ytqgogh",
"response_item_id": "fc_3ytqgogh",
"type": "function",
"function": {
"name": "skill_view",
"arguments": "{\"name\":\"home-assistant\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_view",
"content": "{\"success\": true, \"name\": \"home-assistant\", \"description\": \"Inspect, manage, and troubleshoot Home Assistant (Docker on ZimaOS) — config, devices, integrations, automations, and Zigbee.\", \"tags\": [\"home-assistant\", \"smart-home\", \"zigbee\", \"docker\", \"zimaos\"], \"related_skills\": [\"openhue\", \"zimaos-camofox-browser\"], \"content\": \"---\\nname: home-assistant\\ndescription: Inspect, manage, and troubleshoot Home Assistant (Docker on ZimaOS) — config, devices, integrations, automations, and Zigbee.\\nversion: 1.0.0\\nauthor: Hermes Agent\\nlicense: MIT\\nmetadata:\\n hermes:\\n tags: [home-assistant, smart-home, zigbee, docker, zimaos]\\n related_skills: [openhue, zimaos-camofox-browser]\\n---\\n\\n# Home Assistant (ZimaOS Docker)\\n\\nManage a Home Assistant instance running as a Docker container on ZimaOS. Covers inspection (with and without API access), device management, Zigbee, and troubleshooting.\\n\\n## Quick Status Check\\n\\n```bash\\n# Is it running?\\ndocker ps --filter name=homeassistant --format \\\"table {{.Names}}\\\\t{{.Image}}\\\\t{{.Status}}\\\\t{{.Ports}}\\\"\\n\\n# Version and uptime\\ndocker inspect homeassistant --format '{{.Config.Image}} | Started: {{.State.StartedAt}}'\\n\\n# Config path on ZimaOS\\n# /DATA/AppData/homeassistant/config/\\n```\\n\\nPort: **8123** (internal). API requires authentication — use a long-lived token from the HA UI (Profile → Security → Long-Lived Access Tokens).\\n\\n## Inspection WITHOUT API Token (read filesystem directly)\\n\\nWhen no API token is available, read the `.storage/` JSON files directly. Every integration, device, entity, area, and automation is stored as clean JSON.\\n\\n**CRITICAL: Always use `docker cp` + `docker exec` for Python scripts.** Inline Python one-liners in shell commands break on quote/escape nesting (f-strings, Unicode escapes, nested quotes). The reliable pattern is:\\n\\n```bash\\n# 1. Write the script on the host (via write_file or heredoc)\\n# 2. Copy it into the container\\ndocker cp /tmp/script.py homeassistant:/tmp/script.py\\n# 3. Run it\\ndocker exec homeassistant python3 /tmp/script.py\\n```\\n\\nHermes' `execute_code` / `read_file` tools cannot reliably read HA storage files from the ZimaOS host — files are owned by the container's internal user and may have permission issues. Always go through the container.\\n\\n### Key Files (in /DATA/AppData/homeassistant/config/.storage/)\\n\\n| File | Contains |\\n|---|---|\\n| `core.config_entries` | All integrations (integrations installed, their config, connection params) |\\n| `core.device_registry` | All physical/virtual devices (manufacturer, model, area assignment, MAC) |\\n| `core.entity_registry` | All entities (switches, sensors, buttons, notifications — with entity_id) |\\n| `core.area_registry` | Rooms/zones (name, icon, ID) |\\n| `core.config` | Global HA config (unit system, language, timezone, elevation, lat/lon) |\\n| `auth` + `auth_provider.homeassistant` | User accounts, tokens |\\n| `http.auth` | Trusted proxies, CORS |\\n| `automations.yaml` | Automation definitions (separate YAML file, not in .storage/) |\\n| `scripts.yaml` | Script definitions |\\n| `configuration.yaml` | Main config (what's included, themes, etc.) |\\n\\n### Common Inspection Queries\\n\\nFor quick one-off queries, use `docker exec` with a simple inline script. For complex queries, use the `docker cp + exec` pattern described above.\\n\\n```bash\\n# List all integrations with titles\\ndocker exec homeassistant python3 -c \\\"\\nimport json\\nwith open('/config/.storage/core.config_entries') as f:\\n data = json.load(f)\\nfor e in data['data']['entries']:\\n print(e['domain'], '|', e.get('title',''), '|',\\n 'DISABLED' if e.get('disabled_by') else 'active')\\n\\\"\\n\\n# List devices by area\\ndocker exec homeassistant python3 -c \\\"\\nimport json\\nwith open('/config/.storage/core.device_registry') as f:\\n data = json.load(f)\\nwith open('/config/.storage/core.area_registry') as f2:\\n areas = {a['id']: a['name'] for a in json.load(f2)['data']['areas']}\\nfor d in data['data']['devices']:\\n area = areas.get(d.get('area_id'), '-')\\n print(d['name'], '|', area, '|', d.get('manufacturer',''), d.get('model',''))\\n\\\"\\n\\n# List all entity_ids by domain\\ndocker exec homeassistant python3 -c \\\"\\nimport json\\nfrom collections import defaultdict\\nwith open('/config/.storage/core.entity_registry') as f:\\n entities = json.load(f)['data']['entities']\\nby_domain = defaultdict(list)\\nfor e in entities:\\n by_domain[e.get('domain','?')].append(e['entity_id'])\\nfor domain in sorted(by_domain):\\n print('---', domain, '({})'.format(len(by_domain[domain])), '---')\\n for eid in sorted(by_domain[domain]):\\n print(' ', eid)\\n\\\"\\n```\\n\\n### Reading Alexa Integration Token\\n\\nThe `core.config_entries` contains the Alexa access token (for `alexa_devices` integration) — it's stored in `data.login_data.access_token`. Useful for debugging, but handle carefully.\\n\\n## Docker Management\\n\\n```bash\\n# Container mounts\\ndocker inspect homeassistant --format '{{range .Mounts}}{{.Source}} -> {{.Destination}}{{\\\"\\\\n\\\"}}{{end}}'\\n\\n# Restart\\ndocker restart homeassistant\\n\\n# Logs (last 100 lines)\\ndocker logs --tail 100 homeassistant\\n\\n# Follow logs\\ndocker logs -f homeassistant\\n```\\n\\nOn ZimaOS, the container stores everything at `/DATA/AppData/homeassistant/config/`. The Docker socket is at `/var/run/docker.sock` (shared with ZimaOS host).\\n\\n## Adding Devices\\n\\n### Zigbee Devices\\n\\nFor Zigbee-based devices (Philips Hue, IKEA Trådfri, Aqara, Sonoff sensors, etc.) you need a Zigbee coordinator (USB dongle) — the ZimaOS server's built-in Bluetooth adapter is NOT Zigbee-compatible.\\n\\n**Recommended dongles (20–40 €):**\\n- **Sonoff Zigbee 3.0 USB Dongle Plus** (~25 €, most popular)\\n- **SkyConnect** (official Nabu Casa, ~35 €)\\n- **ConBee II** (~35 €)\\n\\n**Setup:**\\n1. Buy dongle, plug into ZimaOS USB port\\n2. Pass the USB device to the HA container (add `--device /dev/ttyUSB0:/dev/ttyUSB0` to docker run, or add `devices:` in docker-compose)\\n3. In HA UI: Settings → Devices & Services → Add Integration → **ZHA** (or Zigbee2MQTT for advanced users)\\n4. Select the USB dongle as coordinator\\n5. Add devices: click \\\"Add Device\\\" in ZHA, then put the bulb in pairing mode (usually power-cycle 5× quickly)\\n\\n**Alternative: Alexa Echo with built-in Zigbee hub**\\n- Echo Plus, Echo Show 10, Echo 4th Gen have Zigbee hubs built in\\n- Echo Dot, Echo Pop, Echo Spot do NOT\\n- If you have a compatible Echo, pair the bulb through the Alexa app and it appears in HA via the Alexa integration\\n\\n### Amazon Basics Smart Bulbs (WiFi/Tuya — NOT Zigbee!)\\n\\n**IMPORTANT:** Amazon Basics Smart Light Bulbs (A60/E27, color changing) use **WiFi (Tuya platform)**, not Zigbee. They ship with Amazon's cloud firmware. The Alexa integration does NOT pass them through to HA — they'll appear as Alexa-paired but won't show up in HA entities.\\n\\n**Alexa-paired vs Tuya-paired firmware behavior:**\\n\\n| Attribute | Alexa-paired (out of box) | Smart Life app-paired |\\n|---|---|---|\\n| Tuya LAN ports (6667/6668) | **Closed** — no local access | **Open** — `tinytuya` scan works |\\n| UDP broadcast response | **None** — `deviceScan()` silent | Responds to discovery |\\n| Cloud API login | May fail (\\\"Username or password error\\\") | Works with Smart Life account |\\n| LocalTuya setup | **Impossible** without re-pairing | Direct Local Key extraction |\\n\\n**If bulbs are currently Alexa-paired, you MUST factory-reset at least one bulb and re-pair it via the Smart Life app** to enable the Tuya LAN protocol. Without this step, no local integration is possible — the bulbs are cloud-locked to Alexa.\\n\\n**Three integration options (best to worst):**\\n\\n1. **LocalTuya (RECOMMENDED — fully local, no cloud):** Install HACS → install LocalTuya → get Local Keys from iot.tuya.com → configure each bulb with Device ID + Local Key + IP. See full workflow below.\\n2. **Official Tuya Cloud integration (simple but cloud-dependent):** Settings → Integrations → Tuya → log in with Smart Life account. Works immediately but every command goes through Tuya's cloud.\\n3. **HA-native tuya-local (middle ground):** Requires Local Keys but no HACS needed. Available in the Tuya integration setup dialog.\\n\\n### WiFi/Tuya Devices (TP-Link Kasa/KP105, Amazon Basics, etc.)\\n\\nAlready natively supported — autodiscovered via DHCP or added manually: Settings → Devices & Services → Add Integration → TP-Link Smart Home.\\n\\n#### Full LocalTuya Setup (for Amazon Basics WiFi bulbs and other Tuya devices)\\n\\n**Prerequisites:**\\n- Bulb is configured in Smart Life / Tuya Smart app and working\\n- Bulb is on the same subnet as the HA server (192.168.178.x in this setup)\\n\\n**Step 1: Install HACS (if not already present)**\\n\\n```bash\\ncd /DATA/AppData/homeassistant/config\\nmkdir -p custom_components\\ncurl -sL \\\"https://github.com/hacs/integration/releases/latest/download/hacs.zip\\\" -o /tmp/hacs.zip\\nunzip -o /tmp/hacs.zip -d custom_components/hacs/\\ndocker restart homeassistant\\n# Wait ~15s for HA to come back up\\n```\\n\\nAfter restart, HACS appears in the HA sidebar. Complete the setup wizard (it'll need GitHub auth).\\n\\n**Step 2: Install LocalTuya**\\n\\n```bash\\ncd /DATA/AppData/homeassistant/config\\ncurl -sL \\\"https://github.com/rospogrigio/localtuya/archive/refs/heads/master.zip\\\" -o /tmp/localtuya.zip\\nunzip -o /tmp/localtuya.zip -d /tmp/localtuya_extract/\\ncp -r /tmp/localtuya_extract/localtuya-master/custom_components/localtuya custom_components/\\ndocker restart homeassistant\\n```\\n\\n**Step 3: Get Local Keys (two approaches)**\\n\\n**Approach A: tinytuya CLI (FAST — when bulbs are Smart Life-paired)**\\n\\n```bash\\n# Install\\npython3 -m pip install tinytuya\\n\\n# Quick scan — discovers Tuya devices on the same subnet via UDP broadcast (ports 6666/6667)\\npython3 -c 'import tinytuya; print(tinytuya.deviceScan())'\\n\\n# If scan succeeds, extract Local Key for each device:\\npython3 -c '\\nimport tinytuya, json\\nfor dev in tinytuya.deviceScan():\\n d = tinytuya.Device(dev[\\\"id\\\"], dev[\\\"ip\\\"], dev[\\\"key\\\"])\\n print(f\\\"Device ID: {dev[\\\\\\\"id\\\\\\\"]} IP: {dev[\\\\\\\"ip\\\\\\\"]} Key: {dev[\\\\\\\"key\\\\\\\"]}\\\")\\n'\\n```\\n\\nThis works ONLY if bulbs are paired via Smart Life/Tuya Smart app (Tuya LAN protocol active). Alexa-paired bulbs have Tuya LAN ports closed and will not respond.\\n\\n**Tuya Cloud API endpoints (tested):**\\n\\n| Endpoint | URL | Result |\\n|---|---|---|\\n| Home Assistant bridge (EU) | `px1.tuyaeu.com/homeassistant/auth.do` | 200 — but rejects if no Tuya account exists |\\n| Home Assistant bridge (US) | `px1.tuyaus.com/homeassistant/auth.do` | Same — region doesn't matter for auth |\\n| IoT OpenAPI login | `openapi.tuyaeu.com/v1.0/iot-01/users/login` | 200 — but needs Client ID/Secret from Cloud project |\\n| IoT token endpoint | `openapi.tuyaeu.com/v1.0/token` | 200 — requires timestamp signature |\\n\\nNo endpoint accepts bare username/password without prior project registration. The IoT Platform requires a Cloud project with Client ID/Secret.\\n\\n**Approach B: IoT Platform Web UI (MANUAL — always works)**\\n\\nUser must visit [iot.tuya.com](https://iot.tuya.com):\\n1. Register free developer account\\n2. Cloud → Create Project (name doesn't matter)\\n3. Cloud → Devices → Link App Account → scan QR code with Smart Life app\\n4. All bulbs appear with Device ID\\n5. Click each Device ID → Debug Device → note the **Local Key**\\n\\n**Step 4: Configure in HA UI**\\n\\nSettings → Devices & Services → Add Integration → **LocalTuya** → configure each bulb:\\n- Host: static IP of bulb (find via router DHCP table)\\n- Device ID: from iot.tuya.com\\n- Local Key: from iot.tuya.com\\n- Protocol: usually 3.3 (auto-detect)\\n- Device type: for color bulbs use `RGBTW` or `RGB+WW`\\n\\n**Key pitfalls:**\\n- Bulbs must have static IPs (or DHCP reservations) — if IP changes, they drop offline\\n- The Local Key is unique per device — you must repeat the iot.tuya.com flow for each bulb\\n- Bulb must be on the same subnet as HA (no VLAN isolation)\\n- Amazon Basics bulbs are plain Tuya whitelabel products — no Amazon-specific protocol\\n\\n**Alexa integration note:** The Alexa integration in HA imports Echo devices, alarms, timers, and routines as entities, but does NOT pass through individual Zigbee/WiFi bulbs paired to Alexa. For those, use LocalTuya (WiFi) or ZHA (Zigbee).\\n\\n### WiFi Devices (TP-Link Kasa/KP105)\\n\\nAlready natively supported — autodiscovered via DHCP or added manually: Settings → Devices & Services → Add Integration → TP-Link Smart Home.\\n\\n### HomeKit Devices\\n\\nHA has a built-in HomeKit Controller integration (to control HomeKit devices) AND a HomeKit Bridge (to expose HA devices to Apple Home). Both in Integrations.\\n\\n## API Control (curl + REST)\\n\\nHA exposes a REST API on port 8123. All calls need `Authorization: Bearer `.\\n\\n### Getting a Token\\n\\nLong-Lived Access Tokens stored in `.storage/auth` are **SHA256-hashed** — the raw string cannot be recovered from disk. Two options:\\n\\n**Option A: User creates one via UI (recommended for permanent use)**\\nHA UI → Profile (bottom-left) → Security → Long-Lived Access Tokens → Create Token. Store it as an env var.\\n\\n**Option B: Exchange a refresh token (headless, no UI needed)**\\nThe `auth` JSON contains unhashed refresh tokens. Exchange one for a 30-min JWT access token:\\n\\n```bash\\ndocker exec homeassistant python3 -c \\\"\\nimport json, urllib.request, urllib.parse\\nwith open('/config/.storage/auth') as f:\\n auth = json.load(f)\\nfor rt in auth['data']['refresh_tokens']:\\n if rt['token_type'] == 'normal' and rt.get('last_used_at'):\\n params = {'grant_type': 'refresh_token', 'refresh_token': rt['token']}\\n cid = rt.get('client_id')\\n if cid:\\n params['client_id'] = cid # MUSS exakt aus dem Store sein!\\n data = urllib.parse.urlencode(params).encode()\\n req = urllib.request.Request('http://localhost:8123/auth/token', data=data,\\n headers={'Content-Type': 'application/x-www-form-urlencoded'})\\n with urllib.request.urlopen(req) as resp:\\n print(json.loads(resp.read())['access_token'])\\n break\\n\\\"\\n# Store in shell: TOKEN=\\\"eyJ...\\\"\\n# Use with: curl -H \\\"Authorization: Bearer $TOKEN\\\" ...\\n```\\n\\nThe JWT expires after 30 minutes. For persistent use, create a Long-Lived Token via the UI.\\n\\n### Sending Commands\\n\\n```bash\\n# Get entity state\\ncurl -s -H \\\"Authorization: Bearer $TOKEN\\\" \\\"http://localhost:8123/api/states/\\\"\\n\\n# Call a service\\ncurl -s -X POST -H \\\"Authorization: Bearer $TOKEN\\\" -H \\\"Content-Type: application/json\\\" \\\\\\n -d '{\\\"entity_id\\\": \\\"\\\", }' \\\\\\n \\\"http://localhost:8123/api/services//\\\"\\n```\\n\\n### Pitfalls\\n\\n- **Long-Lived Tokens in `.storage/auth` are hashed** — they cannot be extracted as raw strings. Use the refresh-token exchange or create one via UI.\\n- **Refresh tokens have ~6 month expiry** — any `normal` token with `last_used_at` is likely still valid for exchange.\\n- **Don't create tokens via raw JSON injection** — they get hashed and the raw string is lost. Only the HA auth endpoint can issue usable tokens.\\n\\n## Full Inventory Script\\n\\nA proven Python script that reads all `.storage/` JSON files and prints a complete inventory: devices (with areas, MACs), integrations, and entities grouped by domain. See `scripts/ha-full-inventory.py`.\\n\\nUsage:\\n```bash\\ndocker cp /tmp/ha_full_inventory.py homeassistant:/tmp/\\ndocker exec homeassistant python3 /tmp/ha_full_inventory.py\\n```\\n\\n## Device & Entity Cleanup (No API)\\n\\nDevices and entities can be removed by directly editing `.storage/` JSON files — no API token needed. Useful for bulk cleanup of decommissioned devices or spammy auto-created entities (e.g., Alexa Speaker Groups that aren't used).\\n\\n**Pattern:** Identify `device_id` values, then filter them out of both `core.device_registry` and `core.entity_registry`:\\n\\n```python\\nimport json\\n\\ndevice_ids = ['id1', 'id2', 'id3'] # from inventory output\\n\\n# Remove devices\\nwith open('/config/.storage/core.device_registry', 'r') as f:\\n dev_data = json.load(f)\\ndev_data['data']['devices'] = [\\n d for d in dev_data['data']['devices']\\n if d['id'] not in device_ids\\n]\\nwith open('/config/.storage/core.device_registry', 'w') as f:\\n json.dump(dev_data, f, indent=2)\\n\\n# Remove their entities (entities reference device_id)\\nwith open('/config/.storage/core.entity_registry', 'r') as f:\\n ent_data = json.load(f)\\nent_data['data']['entities'] = [\\n e for e in ent_data['data']['entities']\\n if e.get('device_id') not in device_ids\\n]\\nwith open('/config/.storage/core.entity_registry', 'w') as f:\\n json.dump(ent_data, f, indent=2)\\n```\\n\\n**Pitfalls:**\\n- No HA restart needed — changes take effect on next state refresh\\n- Don't edit JSON while HA is writing to the files (safe during normal operation, avoid during integration setup)\\n- Some entities may lack `device_id` — they won't be caught by this filter. Check the inventory output first.\\n\\n## Device-Specific Integrations\\n\\n- **Midea Klimaanlage:** See `midea-ac-ha` skill — integration setup, HA 2026 patches, token discovery via msmart-ng, and API control (note: `turn_on` is NOT supported — use `set_hvac_mode` directly to switch on/off).\\n\\n## Cronjob Scheduling for AC Control\\n\\nWhen scheduling one-shot cronjobs for AC on/off via Hermes, two pitfalls:\\n\\n### Midnight Date Bug\\n\\nIf you create cronjobs after midnight, the date is the **new** day. Creating jobs with yesterday's date (e.g. `2026-06-18` at 00:02 on June 19) causes them to be silently ignored — the scheduler treats them as already past. Always run `date '+%Y-%m-%d'` before creating jobs to confirm the current date.\\n\\n### Script Path Requirement\\n\\nCronjob scripts MUST live under `~/.hermes/scripts/` and be referenced by filename only (relative path). Absolute paths like `/tmp/ha_ac_off.sh` are rejected. Pattern:\\n\\n```bash\\ncp /tmp/my_script.sh ~/.hermes/scripts/\\nchmod +x ~/.hermes/scripts/my_script.sh\\n# Then in cronjob create: script=\\\"my_script.sh\\\" (not /tmp/...)\\n```\\n\\n### Multi-Step ON Script (Midea AC)\\n\\nThe Midea integration does not support setting temperature and preset in the same call as `set_hvac_mode`. A reliable ON script does 3 sequential calls:\\n\\n1. `set_hvac_mode` → `cool` (implicitly turns on)\\n2. `set_temperature` → target value\\n3. `set_preset_mode` → `eco` (or `none`)\\n\\nEach call fetches a fresh token via refresh-token exchange (30-min JWT). See `scripts/ha_ac_on_eco.sh` and `scripts/ha_ac_off.sh` for proven templates.\\n\\n## Troubleshooting\\n\\n| Problem | Check |\\n|---|---|\\n| Container won't start | `docker logs homeassistant` — often a YAML syntax error in configuration.yaml |\\n| Integration fails to load | `core.config_entries` — look for `disabled_by` field. Remove and re-add in UI. |\\n| Zigbee device not discovered | USB passthrough working? `ls -la /dev/ttyUSB*` inside container. Try ZHA → Add Device again. |\\n| 401 from API | Token missing/expired — use refresh-token exchange (above) or create a Long-Lived Token in the UI |\\n| Config changes not taking effect | `docker restart homeassistant` or use Developer Tools → Check Configuration in UI |\\n| Cronjob silently skipped | Check date — did you use yesterday's date after midnight? Run `date` to confirm. |\\n| Cronjob script path rejected | Script must be under `~/.hermes/scripts/`, referenced by filename only. |\\n\\n## ZimaOS-Specific Notes\\n\\n- Config lives at `/DATA/AppData/homeassistant/config/` (Docker bind mount)\\n- Files are owned by the container's internal user — use `docker exec homeassistant cat /config/...` if permissions block direct reads\\n- HA port 8123 is exposed on the host — access via `http://zimaos-ip:8123` on the local network\\n- The ZimaOS Docker UI manages the container lifecycle; docker CLI commands work but may conflict with ZimaOS's own management\\n- Long-Lived Access Tokens in `.storage/auth` are **SHA256-hashed** — the raw string cannot be recovered. Use the refresh-token exchange method (see API Control section) or create one via the HA UI (Profile → Security → Long-Lived Access Tokens)\\n\\n## Device-Specific Integrations\\n\\n- **Midea Klimaanlage:** See `midea-ac-ha` skill — integration setup, HA 2026 patches, token discovery via msmart-ng, and API control (note: `turn_on` is NOT supported — use `set_hvac_mode` directly to switch on/off).\\n\", \"path\": \"smart-home/home-assistant/SKILL.md\", \"skill_dir\": \"/DATA/.hermes/skills/smart-home/home-assistant\", \"linked_files\": {\"scripts\": [\"scripts/ha-cleanup-devices.py\", \"scripts/ha-full-inventory.py\", \"scripts/ha_ac_on_eco.sh\", \"scripts/ha_ac_off.sh\"]}, \"usage_hint\": \"To view linked files, call skill_view(name, file_path) where file_path is e.g. 'references/api.md' or 'assets/config.yaml'\", \"required_environment_variables\": [], \"required_commands\": [], \"missing_required_environment_variables\": [], \"missing_credential_files\": [], \"missing_required_commands\": [], \"setup_needed\": false, \"setup_skipped\": false, \"readiness_status\": \"available\", \"metadata\": {\"hermes\": {\"tags\": [\"home-assistant\", \"smart-home\", \"zigbee\", \"docker\", \"zimaos\"], \"related_skills\": [\"openhue\", \"zimaos-camofox-browser\"]}}}",
"tool_call_id": "3ytqgogh"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "p1tntzpu",
"call_id": "p1tntzpu",
"response_item_id": "fc_p1tntzpu",
"type": "function",
"function": {
"name": "skill_view",
"arguments": "{\"name\":\"esp32-desk-dashboard\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_view",
"content": "{\"success\": true, \"name\": \"esp32-desk-dashboard\", \"description\": \"ESP32-basierte Desk-Dashboards mit AMOLED, LVGL und BLE. Hardware-Auswahl, Firmware-Architektur, Daemon-Design und Tooling für Maker.\", \"tags\": [\"esp32\", \"lvgl\", \"amoled\", \"ble\", \"dashboard\", \"embedded\", \"waveshare\", \"platformio\", \"maker\"], \"related_skills\": [], \"content\": \"---\\nname: esp32-desk-dashboard\\ndescription: \\\"ESP32-basierte Desk-Dashboards mit AMOLED, LVGL und BLE. Hardware-Auswahl, Firmware-Architektur, Daemon-Design und Tooling für Maker.\\\"\\nversion: 1.0.0\\nauthor: Kiwi\\nlicense: MIT\\nmetadata:\\n hermes:\\n tags: [esp32, lvgl, amoled, ble, dashboard, embedded, waveshare, platformio, maker]\\n category: maker-electronics\\n requires_toolsets: [terminal]\\n---\\n\\n# ESP32 Desk Dashboard Skill\\n\\nVollständiger Workflow zum Bauen von ESP32-basierten Desk-Dashboards — von der Hardware-Auswahl über LVGL-Firmware bis zum Host-Daemon. Ursprünglich aus dem Clawdmeter-Review (siehe `references/clawdmeter-analysis.md`) destilliert.\\n\\n## Wann verwenden\\n\\n- User will ein kleines Display auf den Schreibtisch stellen (Usage-Monitor, Wetter, Crypto, etc.)\\n- ESP32 + AMOLED + Touch + BLE ist im Spiel\\n- Firmware in C++ / PlatformIO\\n- Host-Daemon (Python/Bash) soll Daten liefern\\n\\n## Empfohlene Hardware-Plattform\\n\\n**Waveshare ESP32-S3-Touch-AMOLED-2.16** (~32€)\\n- ESP32-S3R8 (8MB PSRAM — wichtig für LVGL!)\\n- 2.16\\\" 480×480 AMOLED (CO5300 QSPI, 314 PPI)\\n- CST9220 Cap-Touch (I2C)\\n- AXP2101 PMU + Li-Po\\n- QMI8658 IMU (Auto-Rotation)\\n- 3 Seiten-Buttons (GPIO 0, GPIO 18, AXP PKEY)\\n- BLE 5.0 + USB-C\\n\\nKauflink: `https://www.waveshare.com/esp32-s3-touch-amoled-2.16.htm`\\n\\n## Architektur-Muster\\n\\n```\\n┌─────────────────┐ BLE GATT ┌──────────────────┐\\n│ ESP32-Board │ ◄──────────────────► │ Host-Daemon │\\n│ (LVGL + NimBLE)│ JSON-Payload │ (Python/Bash) │\\n│ │ │ pollt API/Datei │\\n│ 3 Screens: │ └──────────────────┘\\n│ Splash/Usage/ │\\n│ Bluetooth │\\n│ HID-Keyboard │ ──► Space / Shift+Tab an Host\\n└─────────────────┘\\n```\\n\\n### Firmware-Module (C++ / PlatformIO)\\n\\n| Datei | Aufgabe |\\n|-------|---------|\\n| `main.cpp` | `setup()`, `loop()`, Button-Polling, Rotation |\\n| `display_cfg.h` | Pin-Defines, extern-Decls |\\n| `ui.{h,cpp}` | LVGL-Screens (Splash, Usage, Bluetooth) |\\n| `splash.{h,cpp}` | Animation-Engine |\\n| `imu.{h,cpp}` | Beschleunigungs-Rotation (0..3) |\\n| `power.{h,cpp}` | AXP2101 Wrapper (Battery%, Charging) |\\n| `touch.{h,cpp}` | Tap-Detector |\\n| `ble.{h,cpp}` | NimBLE Peripheral (Custom Service + HID) |\\n| `data.h` | `UsageData` Struct |\\n| `icons.h` | RGB565 / RGB565A8 Icons |\\n| `font_*.c` | LVGL-Bitmap-Fonts |\\n\\n### Host-Daemon\\n\\n- **Python** bevorzugt über Bash (bessere Fehlerbehandlung, JSON-Parsing)\\n- Liest Datenquelle (API, lokale Datei, etc.)\\n- Verbindet per BLE by-name (`\\\"Claude Controller\\\"` o.ä.)\\n- Cacht MAC-Adresse in `~/.config//ble-address`\\n- Schreibt JSON an GATT-RX-Characteristic\\n- Systemd-User-Service für Autostart\\n\\n## Kritische Gotchas\\n\\n1. **PSRAM muss OPI sein.** `board_build.arduino.memory_type = qio_opi` in `platformio.ini`. Ohne PSRAM bleibt der Screen schwarz.\\n2. **CO5300 kann nicht hardware-rotieren.** MADCTL nur Axis-Flip. Rotation muss in Software im `flush_cb` per CPU-Pixel-Remapping geschehen.\\n3. **Touch zentralisiert lesen.** `getPoint()` macht einen vollen I2C-Transaction. Mehrfache Aufrufe aus verschiedenen Stellen zerstören sich gegenseitig.\\n4. **CO5300 braucht even-aligned Flush-Regions.** `rounder_cb` muss das erzwingen.\\n5. **LVGL 9 Font-Patching nötig.** `lv_font_conv` output ist LVGL-8-Format. Patches siehe `references/lvgl9-font-patch.md`.\\n6. **ESP32 BLE-MAC ist factory-burned.** Board tauschen → Cache löschen + `bluetoothctl remove`.\\n7. **Screenshot über Serial.** `screenshot.sh out.png /dev/ttyACM0` dumped den LVGL-Framebuffer. Für UI-Iteration unverzichtbar.\\n\\n## BLE-Protokoll (wiederverwendbar)\\n\\n| Service / Char | UUID |\\n|----------------|------|\\n| Data Service | `4c41555a-4465-7669-6365-000000000001` |\\n| RX (write) | `...0002` |\\n| TX (notify) | `...0003` |\\n| REQ (notify) | `...0004` |\\n| HID Keyboard Service | `00001812-0000-1000-8000-00805f9b34fb` |\\n\\n**JSON-Payload (RX):**\\n```json\\n{ \\\"s\\\": 45, \\\"sr\\\": 120, \\\"w\\\": 28, \\\"wr\\\": 7200, \\\"st\\\": \\\"allowed\\\", \\\"ok\\\": true }\\n```\\n\\n## UI-Design-Richtlinien\\n\\n- **20px Margin** — abgerundete Display-Ecken aussparen\\n- **RGB565A8** für Icons über nicht-einheitlichen Hintergründen (Battery über Splash)\\n- **RGB565** für Icons in opaken Zonen\\n- Fonts ~1.9× skalieren für 314 PPI (verglichen mit 165 PPI Referenz)\\n- Screens per Touch-Tap oder mittlere Taste cyclen\\n\\n## Font-Konvertierung\\n\\n```bash\\nnpm install -g lv_font_conv\\n\\nlv_font_conv --font MyFont-Regular.ttf -r 0x20-0x7E \\\\\\n --size 56 --format lvgl --bpp 4 --no-compress \\\\\\n -o font_my_56.c --lv-include \\\"lvgl.h\\\"\\n```\\n\\nDanach LVGL-9-Patch anwenden (siehe `references/lvgl9-font-patch.md`).\\n\\n## Icon-Konvertierung\\n\\n```bash\\nnode tools/png_to_lvgl.js input.png SYMBOL_NAME WIDTH_MACRO HEIGHT_MACRO [--tint=FFFFFF]\\n```\\n\\nLucide-Icons sind schwarz-on-transparent → unbedingt `--tint` setzen, sonst unsichtbar auf dunklem UI.\\n\\n## Verfügbare Referenzen\\n\\n- `references/clawdmeter-analysis.md` — Vollständige Projekt-Analyse mit Hardware-Specs, Architektur, Lizenz-Warnung\\n- `references/lvgl9-font-patch.md` — Schritt-für-Schritt Patch-Anleitung für lv_font_conv Output\\n- `references/open-meteo-weather.md` — stdlib-only Wetter-Abfrage (für Wetter-Widget)\\n- `references/reddit-json-api.md` — Reddit-Inhalte via `.json` Endpoint lesen (Scraping-Bypass)\\n- `scripts/weather_openmeteo.py` — Sofort ausführbares Wetter-Script für Wien oder beliebige Koordinaten\\n\\n## Pitfalls\\n\\n- **Anthropic-Assets sind copyrighted.** Clawd-Maskottchen und Hausmarken-Fonts (Tiempos, Styrene) dürfen nicht ohne Lizenz verwendet werden. Eigene Pixel-Art oder Open-Source-Alternativen nutzen.\\n- **MacOS-Daemon-Support** — Bluetooth-Stack unterschiedlich zu Linux. Separate Implementierung nötig.\\n- **PlattformIO pioarduino** — `espressif32` 2.x funktioniert nicht. `pioarduino/platform-espressif32` 55.x pinned verwenden.\\n\\n## Verification\\n\\n```bash\\n# Hardware erkannt?\\nls /dev/ttyACM*\\n\\n# PlatformIO installiert?\\npio --version\\n\\n# lv_font_conv verfügbar?\\nlv_font_conv --version\\n```\\n\", \"path\": \"maker-electronics/esp32-desk-dashboard/SKILL.md\", \"skill_dir\": \"/DATA/.hermes/skills/maker-electronics/esp32-desk-dashboard\", \"linked_files\": {\"references\": [\"references/open-meteo-weather.md\", \"references/clawdmeter-analysis.md\", \"references/lvgl9-font-patch.md\", \"references/reddit-json-api.md\"], \"scripts\": [\"scripts/weather_openmeteo.py\"]}, \"usage_hint\": \"To view linked files, call skill_view(name, file_path) where file_path is e.g. 'references/api.md' or 'assets/config.yaml'\", \"required_environment_variables\": [], \"required_commands\": [], \"missing_required_environment_variables\": [], \"missing_credential_files\": [], \"missing_required_commands\": [], \"setup_needed\": false, \"setup_skipped\": false, \"readiness_status\": \"available\", \"metadata\": {\"hermes\": {\"tags\": [\"esp32\", \"lvgl\", \"amoled\", \"ble\", \"dashboard\", \"embedded\", \"waveshare\", \"platformio\", \"maker\"], \"category\": \"maker-electronics\", \"requires_toolsets\": [\"terminal\"]}}}",
"tool_call_id": "p1tntzpu"
},
{
"role": "assistant",
"content": "",
"reasoning": "**Considering IoT Grouping**\n\nI'm currently grouping \"home-assistant\" and \"esp32-desk-dashboard\" under the umbrella of IoT, Smart Home, and Maker projects. While distinct, one being high-level software and the other low-level hardware/firmware, their relatedness is undeniable, and this grouping feels right.\n\n\n",
"finish_reason": "tool_calls",
"reasoning_content": "**Considering IoT Grouping**\n\nI'm currently grouping \"home-assistant\" and \"esp32-desk-dashboard\" under the umbrella of IoT, Smart Home, and Maker projects. While distinct, one being high-level software and the other low-level hardware/firmware, their relatedness is undeniable, and this grouping feels right.\n\n\n",
"tool_calls": [
{
"id": "he3awx26",
"call_id": "he3awx26",
"response_item_id": "fc_he3awx26",
"type": "function",
"function": {
"name": "skill_view",
"arguments": "{\"name\":\"local-server-public-access\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_view",
"content": "{\"success\": true, \"name\": \"local-server-public-access\", \"description\": \"Expose a local HTTP service (website, dashboard, dev server) to the public internet so it can be opened from a phone or remote location. Covers cloudflared, ngrok, tailscale funnel, and manual port forwarding with security notes.\", \"tags\": [\"devops\", \"tunnel\", \"reverse-proxy\", \"public-access\", \"cloudflared\", \"ngrok\", \"tailscale\", \"zimaos\"], \"related_skills\": [\"zimaos-platform\", \"zimaos-app-install\"], \"content\": \"---\\nname: local-server-public-access\\ndescription: Expose a local HTTP service (website, dashboard, dev server) to the public internet so it can be opened from a phone or remote location. Covers cloudflared, ngrok, tailscale funnel, and manual port forwarding with security notes.\\nversion: 1.0.0\\nauthor: Hermes Agent\\nlicense: MIT\\nmetadata:\\n hermes:\\n tags: [devops, tunnel, reverse-proxy, public-access, cloudflared, ngrok, tailscale, zimaos]\\n related_skills: [zimaos-platform, zimaos-app-install]\\n---\\n\\n# Local Server Public Access\\n\\nExpose a service running locally on ZimaOS (or any Linux box) so it can be reached from a phone, laptop, or remote network without VPN.\\n\\nTypical trigger: user creates a website/dashboard, starts `python3 -m http.server` or similar, and wants a shareable URL.\\n\\n---\\n\\n## Decision Tree\\n\\n| Situation | Tool |\\n|---|---|\\n| Quick one-off share, no account | `cloudflared tunnel --url` |\\n| Already have ngrok account/token | `ngrok http ` |\\n| Tailscale already installed and signed in | `tailscale serve` + `tailscale funnel` |\\n| Static public IP + Router access | Manual port forwarding |\\n\\n---\\n\\n## Option 1: Cloudflare Tunnel (Recommended)\\n\\nNo account needed for a temporary tunnel. Produces a random `*.trycloudflare.com` HTTPS URL.\\n\\n### Install\\n\\n**ZimaOS / systems without dpkg:** Download the raw binary directly — `dpkg` is not available on ZimaOS.\\n\\n```bash\\ncd /tmp\\ncurl -sL -o cloudflared \\\\\\n https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64\\nchmod +x cloudflared\\n./cloudflared --version # verify\\n```\\n\\n**Debian/Ubuntu (with dpkg):**\\n\\n```bash\\ncd /tmp\\ncurl -L --output cloudflared.deb \\\\\\n https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64.deb\\nsudo dpkg -i cloudflared.deb\\n```\\n\\n### Run\\n\\nStart the local HTTP server and tunnel as background processes:\\n\\n```bash\\n# 1. Start a minimal HTTP server in background (bind to localhost only)\\npython3 -m http.server --bind 127.0.0.1 &\\n\\n# 2. Start cloudflared tunnel in background\\n/tmp/cloudflared tunnel --url http://127.0.0.1: 2>&1 &\\n```\\n\\n### Extracting the Tunnel URL\\n\\nCloudflared prints the URL early in its startup logs, then runs forever. When running as a background process, use `process log` (not `process wait` — it will time out) to find the URL:\\n\\n```\\nLook for the line:\\n| https://.trycloudflare.com |\\n```\\n\\nThe URL is always inside the ASCII-art box after \\\"Your quick Tunnel has been created!\\\".\\n\\nShare that URL. Append the file path if serving a specific file, e.g. `https://.trycloudflare.com/prototype.html`.\\n\\nThe tunnel stays alive as long as both the HTTP server and cloudflared process run.\\n\\n### Pitfalls\\n\\n- `--url` creates a **temporary** tunnel; the URL changes on every restart.\\n- For a persistent named tunnel you need a Cloudflare account and `cloudflared tunnel create`.\\n- On ZimaOS, root filesystem is read-only AND **`dpkg` is not available**. Always use the raw binary download method.\\n- **Do not use `process wait` to get the URL** — cloudflared runs indefinitely and `wait` will time out. Use `process log` after a few seconds instead.\\n- The HTTP server should bind to `127.0.0.1` only (not `0.0.0.0`) — cloudflared connects locally, no need to expose the port on the network.\\n\\n---\\n\\n## Option 2: Ngrok\\n\\nRequires a free ngrok account and authtoken.\\n\\n### Install\\n\\n```bash\\ncd /tmp\\ncurl -s https://ngrok-agent.s3.amazonaws.com/ngrok.asc | sudo tee /etc/apt/trusted.gpg.d/ngrok.asc >/dev/null\\necho \\\"deb https://ngrok-agent.s3.amazonaws.com buster main\\\" | sudo tee /etc/apt/sources.list.d/ngrok.list\\nsudo apt update && sudo apt install ngrok\\n```\\n\\n### Authenticate\\n\\n```bash\\nngrok config add-authtoken \\n```\\n\\n### Run\\n\\n```bash\\nngrok http \\n```\\n\\nURL appears in terminal and at `http://127.0.0.1:4040`.\\n\\n---\\n\\n## Option 3: Tailscale Funnel\\n\\nBest if Tailscale is already running on the machine.\\n\\n### Serve local port\\n\\n```bash\\ntailscale serve --bg --https=443 localhost:\\n```\\n\\n### Expose to public internet\\n\\n```bash\\ntailscale funnel --bg 443\\n```\\n\\nURL: `https://..ts.net`\\n\\n### Pitfall\\n\\nFunnel must be enabled in the Tailscale admin console for the tailnet.\\n\\n---\\n\\n## Option 4: Manual Port Forwarding\\n\\nUse only if a static public IP and router admin access are available.\\n\\n1. Find the local IP of the server (`ip addr` or CasaOS dashboard).\\n2. In the router, forward external port (e.g. 8766) to `:`.\\n3. Open firewall if necessary:\\n ```bash\\n sudo ufw allow 8766/tcp\\n # or on CasaOS/ZimaOS via the OS firewall rules\\n ```\\n4. URL: `http://:`\\n\\n### Pitfalls\\n\\n- Dynamic IP requires DDNS (e.g. duckdns.org).\\n- Exposes the service directly to the internet; add HTTPS/authentication if sensitive.\\n\\n---\\n\\n## Security Notes\\n\\n- Prefer **HTTPS** tunnels (cloudflared, ngrok, tailscale) over plain HTTP port forwarding.\\n- Do **not** expose internal admin interfaces (Hermes gateway, CasaOS dashboard, databases) publicly without authentication.\\n- Stop the tunnel when no longer needed.\\n- For a dev website or static showcase, a temporary cloudflared/ngrok tunnel is usually sufficient.\\n\\n---\\n\\n## ZimaOS-Specific Notes\\n\\n- `python3 -m http.server` works, but only serves static files; for production use `nginx` or a CasaOS app.\\n- CasaOS apps are managed in `/var/lib/casaos/apps//` with Docker Compose.\\n- The OS root filesystem is read-only; install binaries under `/tmp` or `/DATA/.hermes/bin/`.\\n\\n## ZimaOS / Hermes Tooling Quirks\\n\\n- When `execute_code` or `terminal()` temporarily fail to accept arguments (e.g. \\\"No code provided\\\" / \\\"Invalid command: expected string, got NoneType\\\"), fall back to:\\n - `terminal` with a single quoted string, or\\n - `delegate_task` with a focused sub-agent, or\\n - wait a turn and retry with the exact same payload (the failure is usually transient).\\n- Do **not** silently retry the identical failed call more than twice; that burns API calls and triggers loop warnings.\\n\\n## Support Files\\n\\n- `references/tunnel-troubleshooting.md` — Common errors and fixes for cloudflared/ngrok/tailscale.\\n\", \"path\": \"devops/local-server-public-access/SKILL.md\", \"skill_dir\": \"/DATA/.hermes/skills/devops/local-server-public-access\", \"linked_files\": null, \"usage_hint\": null, \"required_environment_variables\": [], \"required_commands\": [], \"missing_required_environment_variables\": [], \"missing_credential_files\": [], \"missing_required_commands\": [], \"setup_needed\": false, \"setup_skipped\": false, \"readiness_status\": \"available\", \"metadata\": {\"hermes\": {\"tags\": [\"devops\", \"tunnel\", \"reverse-proxy\", \"public-access\", \"cloudflared\", \"ngrok\", \"tailscale\", \"zimaos\"], \"related_skills\": [\"zimaos-platform\", \"zimaos-app-install\"]}}}",
"tool_call_id": "he3awx26"
},
{
"role": "assistant",
"content": "",
"reasoning": "**Analyzing DevOps Candidates**\n\nI've determined that `local-server-public-access` is the sole contender within the \"DevOps\" category. Now, I'm revisiting the \"skills_list\" to see if there are additional options. The list includes `zimaos-platform`, `zimaos-app-install`, `zimaos-quirks`, and `zimaos-`.\n\n\n**Revisiting Candidate Criteria**\n\nI've realized I need to stick to the original list of agent-created skills, not the browser skill. I am restructuring my approach to consolidation. I have decided to merge `ai-video-production` and `music-resources` into `media-file-management`. Also, I'm creating a new umbrella category `smart-home-and-maker` to merge `home-assistant` and `esp32-desk-dashboard`.\n\n\n",
"finish_reason": "tool_calls",
"reasoning_content": "**Analyzing DevOps Candidates**\n\nI've determined that `local-server-public-access` is the sole contender within the \"DevOps\" category. Now, I'm revisiting the \"skills_list\" to see if there are additional options. The list includes `zimaos-platform`, `zimaos-app-install`, `zimaos-quirks`, and `zimaos-`.\n\n\n**Revisiting Candidate Criteria**\n\nI've realized I need to stick to the original list of agent-created skills, not the browser skill. I am restructuring my approach to consolidation. I have decided to merge `ai-video-production` and `music-resources` into `media-file-management`. Also, I'm creating a new umbrella category `smart-home-and-maker` to merge `home-assistant` and `esp32-desk-dashboard`.\n\n\n",
"tool_calls": [
{
"id": "nsafrbrg",
"call_id": "nsafrbrg",
"response_item_id": "fc_nsafrbrg",
"type": "function",
"function": {
"name": "skill_view",
"arguments": "{\"name\":\"pdf-generation\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_view",
"content": "{\"success\": true, \"name\": \"pdf-generation\", \"description\": \"Generate PDF documents from markdown/text using fpdf2 with Unicode support.\", \"tags\": [\"PDF\", \"Document\", \"fpdf2\", \"Unicode\", \"German\"], \"related_skills\": [], \"content\": \"---\\nname: pdf-generation\\ndescription: \\\"Generate PDF documents from markdown/text using fpdf2 with Unicode support.\\\"\\nversion: 1.0.0\\nauthor: Hermes Agent\\nlicense: MIT\\nmetadata:\\n hermes:\\n tags: [PDF, Document, fpdf2, Unicode, German]\\nprerequisites:\\n packages: [fpdf2]\\n---\\n\\n# PDF Generation\\n\\nGenerate clean PDF documents (letters, forms, reports) from text/markdown content using Python fpdf2. Designed for ZimaOS where pandoc, weasyprint, and reportlab are not pre-installed.\\n\\n## Prerequisites\\n\\n```bash\\npython3 -m pip install fpdf2\\n```\\n\\n## Quick Start\\n\\n```python\\nfrom fpdf import FPDF\\n\\npdf = FPDF('P', 'mm', 'A4')\\npdf.set_auto_page_break(auto=True, margin=20)\\npdf.add_font('DejaVu', '', '/path/to/DejaVuSans.ttf')\\npdf.add_font('DejaVu', 'B', '/path/to/DejaVuSans-Bold.ttf')\\npdf.add_page()\\npdf.set_font('DejaVu', '', 10)\\npdf.multi_cell(0, 5, \\\"Your text with ümlauts and — em dashes.\\\")\\npdf.output('/tmp/output.pdf')\\n```\\n\\n## Unicode Font Setup\\n\\n**Critical:** fpdf2's built-in Helvetica font only supports latin-1. Any character outside that range (em-dash `—`, smart quotes, etc.) crashes with `FPDFUnicodeEncodingException`.\\n\\n### DejaVu Font Download\\n\\nGitHub raw URLs return HTML redirects, not binary font files. Use SourceForge:\\n\\n```bash\\ncurl -sL \\\"https://sourceforge.net/projects/dejavu/files/dejavu/2.37/dejavu-fonts-ttf-2.37.tar.bz2/download\\\" -o /tmp/dejavu.tar.bz2\\ncd /tmp && tar xjf dejavu.tar.bz2\\n# Fonts at: /tmp/dejavu-fonts-ttf-2.37/ttf/DejaVuSans.ttf\\n# Bold at: /tmp/dejavu-fonts-ttf-2.37/ttf/DejaVuSans-Bold.ttf\\n```\\n\\n### Font Registration\\n\\n```python\\npdf.add_font('DejaVu', '', '/tmp/dejavu-fonts-ttf-2.37/ttf/DejaVuSans.ttf')\\npdf.add_font('DejaVu', 'B', '/tmp/dejavu-fonts-ttf-2.37/ttf/DejaVuSans-Bold.ttf')\\n```\\n\\nDo NOT use the deprecated `uni=True` parameter — it's removed in fpdf2 v2.5+.\\n\\n## fpdf2 v2.5.2 API Changes\\n\\nThe `ln` parameter is deprecated. Replace all `ln=True` with explicit positioning:\\n\\n```python\\n# OLD (deprecated):\\npdf.cell(0, 5, 'Text', ln=True)\\n\\n# NEW:\\npdf.cell(0, 5, 'Text', new_x=\\\"LMARGIN\\\", new_y=\\\"NEXT\\\")\\n```\\n\\n## Document Structure Pattern\\n\\nFor formal letters (German business correspondence):\\n\\n```python\\nclass LetterPDF(FPDF):\\n def header(self):\\n pass # no header on first page\\n \\n def footer(self):\\n self.set_y(-15)\\n self.set_font('DejaVu', '', 8)\\n self.cell(0, 10, f'Seite {self.page_no()}', align='C')\\n\\npdf = LetterPDF('P', 'mm', 'A4')\\npdf.set_auto_page_break(auto=True, margin=20)\\n# ... add fonts, content ...\\n```\\n\\n### Standard Letter Layout\\n\\n1. **Sender block** (top-left): name, address, phone, email — each on own line via `cell(..., new_x=\\\"LMARGIN\\\", new_y=\\\"NEXT\\\")`\\n2. **Recipient block**: company, contact person, address\\n3. **Date + Subject line**: bold subject\\n4. **Salutation**: `multi_cell` for \\\"Sehr geehrte/r ...\\\"\\n5. **Body**: `multi_cell(0, 5, text)` for paragraphs, `ln(2)` for spacing\\n6. **Section headers**: `set_font('DejaVu', 'B', 10)` + `cell()`\\n7. **Bullet lists**: manual indent with `cell(5, 5, '')` then `cell(0, 5, f'— {item}', ...)`\\n8. **Closing**: signature block with spacing\\n\\n## Pitfalls\\n\\n- **Em-dash (—) crashes Helvetica:** Always use a Unicode TTF font (DejaVu) for German text\\n- **GitHub raw URLs serve HTML for fonts:** Use SourceForge or GitLab releases for binary downloads\\n- **`ln=True` deprecated in fpdf2 ≥2.5:** Use `new_x=\\\"LMARGIN\\\", new_y=\\\"NEXT\\\"` instead\\n- **`uni=True` deprecated in fpdf2 ≥2.5:** Omit it; TTF fonts are auto-detected\\n- **No pandoc/weasyprint on ZimaOS:** fpdf2 is the only reliable PDF path\\n- **`add_font()` needs absolute paths:** `/tmp/dejavu-fonts-ttf-2.37/ttf/DejaVuSans.ttf` not relative\\n- **Bold requires separate font file:** `DejaVuSans-Bold.ttf` — fpdf2 won't synthesize bold from regular\\n\\n## Templates\\n\\nSee `templates/german-letter.py` for a complete starter script with sender block, recipient, subject, sections, bullet lists, and signature — ready to customize with your content.\\n\", \"path\": \"productivity/pdf-generation/SKILL.md\", \"skill_dir\": \"/DATA/.hermes/skills/productivity/pdf-generation\", \"linked_files\": {\"templates\": [\"templates/german-letter.py\"]}, \"usage_hint\": \"To view linked files, call skill_view(name, file_path) where file_path is e.g. 'references/api.md' or 'assets/config.yaml'\", \"required_environment_variables\": [], \"required_commands\": [], \"missing_required_environment_variables\": [], \"missing_credential_files\": [], \"missing_required_commands\": [], \"setup_needed\": false, \"setup_skipped\": false, \"readiness_status\": \"available\", \"metadata\": {\"hermes\": {\"tags\": [\"PDF\", \"Document\", \"fpdf2\", \"Unicode\", \"German\"]}}}",
"tool_call_id": "nsafrbrg"
},
{
"role": "assistant",
"content": "",
"reasoning": "**Defining Productivity Scope**\n\nI'm expanding the scope of \"productivity\". I'm considering \"pdf-generation\" as an aspect, and now I'm searching for a broader term. I'm reviewing the `skills_list` and see many productivity-related tools: `airtable`, `google-workspace`, `linear`, `maps`, `notion`, `ocr-and-documents`, `powerpoint`, and `zimaos-productivity`. I am hoping to create a clearer, all-encompassing definition.\n\n\n**Identifying Umbrella Strategies**\n\nI'm now identifying strategies for creating a conceptual umbrella. I can't merge *into* bundled skills, but I can create a new umbrella or designate an existing one as the central concept. I have a list of agent-created skills I *can* use. I'm focusing on clustering these skills based on shared prefixes or domain keywords, to create appropriate umbrella concepts.\n\n\n**Clarifying Archival Scope**\n\nI'm now clarifying the scope of \"archival\" in this context. The instruction \"fewer than 10 archives\" initially seemed contradictory given the list of 10 agent-created skills. However, I now understand this refers to merging. I can merge and create a single archive. I am interpreting \"fewer than 10 archives\" means I *should* merge some skills. So I should examine the 10 listed skills and consider which ones can be archived into umbrella clusters, while ensuring I don't leave any skills unarchived.\n\n\n**Revising Archival Approach**\n\nI'm now revising my approach to the archival process. The \"fewer than 10 archives\" instruction confused me initially. I was interpreting it in the context of the *number* of umbrella categories. But I think it refers to the *archiving* action itself. Now I understand that if I archive *every* skill, then I have 10 archives total. This aligns with the instruction, and suggests I must archive all 10 skills.\n\n\n**Refining Skill Clusters**\n\nI'm now refining the skill clusters for archival. My previous interpretation was off. I'm focusing on merging all ten agent-created skills into archives. I'm structuring them into clusters. I identified Cluster A, for \"Media & Creative\", now includes `ai-video-production` and `music-resources` under `media-file-management`. I can patch the umbrella. Next, I'm working on Cluster B for \"Smart Home & Maker.\"\n\n\n",
"finish_reason": "tool_calls",
"reasoning_content": "**Defining Productivity Scope**\n\nI'm expanding the scope of \"productivity\". I'm considering \"pdf-generation\" as an aspect, and now I'm searching for a broader term. I'm reviewing the `skills_list` and see many productivity-related tools: `airtable`, `google-workspace`, `linear`, `maps`, `notion`, `ocr-and-documents`, `powerpoint`, and `zimaos-productivity`. I am hoping to create a clearer, all-encompassing definition.\n\n\n**Identifying Umbrella Strategies**\n\nI'm now identifying strategies for creating a conceptual umbrella. I can't merge *into* bundled skills, but I can create a new umbrella or designate an existing one as the central concept. I have a list of agent-created skills I *can* use. I'm focusing on clustering these skills based on shared prefixes or domain keywords, to create appropriate umbrella concepts.\n\n\n**Clarifying Archival Scope**\n\nI'm now clarifying the scope of \"archival\" in this context. The instruction \"fewer than 10 archives\" initially seemed contradictory given the list of 10 agent-created skills. However, I now understand this refers to merging. I can merge and create a single archive. I am interpreting \"fewer than 10 archives\" means I *should* merge some skills. So I should examine the 10 listed skills and consider which ones can be archived into umbrella clusters, while ensuring I don't leave any skills unarchived.\n\n\n**Revising Archival Approach**\n\nI'm now revising my approach to the archival process. The \"fewer than 10 archives\" instruction confused me initially. I was interpreting it in the context of the *number* of umbrella categories. But I think it refers to the *archiving* action itself. Now I understand that if I archive *every* skill, then I have 10 archives total. This aligns with the instruction, and suggests I must archive all 10 skills.\n\n\n**Refining Skill Clusters**\n\nI'm now refining the skill clusters for archival. My previous interpretation was off. I'm focusing on merging all ten agent-created skills into archives. I'm structuring them into clusters. I identified Cluster A, for \"Media & Creative\", now includes `ai-video-production` and `music-resources` under `media-file-management`. I can patch the umbrella. Next, I'm working on Cluster B for \"Smart Home & Maker.\"\n\n\n",
"tool_calls": [
{
"id": "u6dm9nh0",
"call_id": "u6dm9nh0",
"response_item_id": "fc_u6dm9nh0",
"type": "function",
"function": {
"name": "skill_view",
"arguments": "{\"name\":\"reddit\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_view",
"content": "{\"success\": true, \"name\": \"reddit\", \"description\": \"Read Reddit posts, comments, and subreddits via JSON API or PullPush.io archive fallback.\", \"tags\": [\"reddit\", \"social-media\", \"research\", \"scraping\"], \"related_skills\": [\"xurl\"], \"content\": \"---\\nname: reddit\\ndescription: Read Reddit posts, comments, and subreddits via JSON API or PullPush.io archive fallback.\\nversion: 1.0.0\\nauthor: Hermes Agent\\nlicense: MIT\\nmetadata:\\n hermes:\\n tags: [reddit, social-media, research, scraping]\\n related_skills: [xurl]\\n---\\n\\n# Reddit Research\\n\\nAccess Reddit posts and comments for research, summarization, and monitoring. Reddit aggressively blocks automated scraping — this skill covers the primary API and reliable fallbacks.\\n\\n## Quick Start\\n\\n### Method 1: Reddit JSON API (try first)\\n\\nAppend `.json` to any Reddit URL:\\n\\n```bash\\ncurl -s -H \\\"User-Agent: python:hermes:v2.0 (by /u/your_bot)\\\" \\\\\\n \\\"https://old.reddit.com/r/subreddit/comments/POST_ID/.json\\\"\\n```\\n\\nParse the JSON: `data[0].data.children[0].data` → post (title, selftext), `data[1].data.children` → comments.\\n\\n**Pitfall: 403 Blocked** — Reddit's CDN/Cloudflare blocks most automated requests. If you get 403, go directly to Method 2.\\n\\n### Method 2: PullPush.io Archive (reliable fallback)\\n\\nPullPush.io is a public Reddit archive with a simple REST API. Use it when Reddit's own API blocks you.\\n\\n```bash\\n# Get post by ID\\ncurl -s \\\"https://api.pullpush.io/reddit/search/submission/?ids=POST_ID\\\" | python3 -c \\\"\\nimport sys, json\\ndata = json.load(sys.stdin)\\npost = data['data'][0]\\nprint('Title:', post.get('title'))\\nprint('Selftext:', post.get('selftext','')[:3000])\\n\\\"\\n\\n# Get comments for a post\\ncurl -s \\\"https://api.pullpush.io/reddit/search/comment/?link_id=POST_ID\\\" | python3 -c \\\"\\nimport sys, json\\ndata = json.load(sys.stdin)\\nfor c in data['data'][:30]:\\n print(f\\\\\\\"--- Score:{c.get('score',0)} ---\\\\\\\" )\\n print(c.get('body','')[:800])\\n print()\\n\\\"\\n```\\n\\n## Resolving Share URLs\\n\\nReddit share URLs (`/s/tQf5BZP95z`) redirect to the canonical post. Follow the redirect:\\n\\n```bash\\ncurl -sL -o /dev/null -w \\\"%{url_effective}\\\" \\\\\\n -H \\\"User-Agent: Mozilla/5.0 ...\\\" \\\\\\n \\\"https://www.reddit.com/r/subreddit/s/SHARE_ID\\\"\\n```\\n\\nExtract the post ID from the final URL (`/comments/POST_ID/`).\\n\\n## Output Format\\n\\nSave results to a markdown file for reference. Use `/DATA/Documents/` on ZimaOS (NOT `/DATA/` root — not writable by non-root users).\\n\\nStructure:\\n```markdown\\n# Reddit Post: r/subreddit — \\\"Title\\\"\\n**URL:** ...\\n**Source:** PullPush.io Reddit Archive\\n\\n## Original Post\\n> ...\\n\\n## Top Comments\\n### Comment #1 | Score: X | Author: name\\n...\\n\\n## Deutsche Zusammenfassung\\n...\\n```\\n\\n## Pitfalls\\n\\n- **403 from Reddit API**: Standard behavior for cloud/VPS IPs. Don't retry — use PullPush.io immediately.\\n- **`/DATA/` root permission denied on ZimaOS**: Write files to `/DATA/Documents/` instead.\\n- **PullPush.io rate limits**: Space requests by 2+ seconds. The archive may lag a few hours behind live Reddit.\\n- **Deleted/removed posts**: PullPush.io may still have cached copies. Comments with `[deleted]` or `[removed]` appear as such.\\n- **Share URLs expire**: The `/s/` shortlinks can break. Always follow the redirect to get the canonical post ID.\\n\\n## Delegation\\n\\nFor deep research (reading many comments, translating, summarizing), delegate to a subagent with `web` and `terminal` toolsets. The subagent can iterate through PullPush.io pagination (`&after=` cursor) to fetch all comments. This is the **preferred approach** for any non-trivial Reddit research — a single delegate_task call replaces 5+ failed direct API attempts.\\n\\n**Delegation template:**\\n```\\ndelegate_task(\\n goal=\\\"Scrape Reddit post at , return full text + all comments with German summary\\\",\\n context=\\\"Reddit blocks Python/curl with 403. Use PullPush.io archive API. Post ID is on r/.\\\",\\n toolsets=[\\\"web\\\", \\\"terminal\\\"]\\n)\\n```\\n\\n## Pitfalls (continued)\\n\\n- **Share URL is NOT the post ID**: Reddit share URLs (`/s/tQf5BZP95z`) must be resolved FIRST via redirect follow before any API call. The shortcode in the URL is a share token, not a post ID. Trying `.json` on it will 404 or return wrong content.\\n\", \"path\": \"social-media/reddit/SKILL.md\", \"skill_dir\": \"/DATA/.hermes/skills/social-media/reddit\", \"linked_files\": null, \"usage_hint\": null, \"required_environment_variables\": [], \"required_commands\": [], \"missing_required_environment_variables\": [], \"missing_credential_files\": [], \"missing_required_commands\": [], \"setup_needed\": false, \"setup_skipped\": false, \"readiness_status\": \"available\", \"metadata\": {\"hermes\": {\"tags\": [\"reddit\", \"social-media\", \"research\", \"scraping\"], \"related_skills\": [\"xurl\"]}}}",
"tool_call_id": "u6dm9nh0"
},
{
"role": "assistant",
"content": "",
"reasoning": "**Defining Initial Framework**\n\nI've sketched out a basic plan. First, I'm focusing on media consolidation under an umbrella project, `media-file-management`, subsuming `ai-video-production` and `music-resources`. The next phase involves integrating smart home and maker projects, with the `home-assistant` project taking center stage, likely with a name change.\n\n\n**Refining Content Clusters**\n\nI'm now revising the grouping of projects. I've decided `pdf-generation` won't fit the media umbrella and am looking at options, possibly with `reddit` and the `local-server-public-access` project. I'm moving toward a clustering approach, as I'm thinking of \"reports\", \"research\", and \"sharing dashboards/reports\" as possible themes. I'm exploring prefix-based clusters.\n\n\n**Consolidating Project Archives**\n\nI'm now focusing on consolidating several projects into new umbrellas. I'm merging `ai-video-production` and `music-resources` into `media-file-management`. I will patch `media-file-management` to include dedicated sections. I'm also planning to rename `home-assistant` to `smart-home-automation` after merging `esp32-desk-dashboard` into it. This will involve patching the new umbrella project to encompass \"Maker Electronics / ESP32 Dashboards.\" My goal is to streamline archives.\n\n\n",
"finish_reason": "tool_calls",
"reasoning_content": "**Defining Initial Framework**\n\nI've sketched out a basic plan. First, I'm focusing on media consolidation under an umbrella project, `media-file-management`, subsuming `ai-video-production` and `music-resources`. The next phase involves integrating smart home and maker projects, with the `home-assistant` project taking center stage, likely with a name change.\n\n\n**Refining Content Clusters**\n\nI'm now revising the grouping of projects. I've decided `pdf-generation` won't fit the media umbrella and am looking at options, possibly with `reddit` and the `local-server-public-access` project. I'm moving toward a clustering approach, as I'm thinking of \"reports\", \"research\", and \"sharing dashboards/reports\" as possible themes. I'm exploring prefix-based clusters.\n\n\n**Consolidating Project Archives**\n\nI'm now focusing on consolidating several projects into new umbrellas. I'm merging `ai-video-production` and `music-resources` into `media-file-management`. I will patch `media-file-management` to include dedicated sections. I'm also planning to rename `home-assistant` to `smart-home-automation` after merging `esp32-desk-dashboard` into it. This will involve patching the new umbrella project to encompass \"Maker Electronics / ESP32 Dashboards.\" My goal is to streamline archives.\n\n\n",
"tool_calls": [
{
"id": "jc6if2t9",
"call_id": "jc6if2t9",
"response_item_id": "fc_jc6if2t9",
"type": "function",
"function": {
"name": "terminal",
"arguments": "{\"command\":\"mkdir -p ~/.hermes/skills/media-file-management/references/music/\\nmkdir -p ~/.hermes/skills/media-file-management/references/video/\\nmkdir -p ~/.hermes/skills/media-file-management/scripts/music/\\nmkdir -p ~/.hermes/skills/media-file-management/scripts/video/\"}"
}
}
]
},
{
"role": "tool",
"name": "terminal",
"content": "{\"output\": \"\", \"exit_code\": 0, \"error\": null}",
"tool_call_id": "jc6if2t9"
},
{
"role": "assistant",
"content": "",
"reasoning": "**Reviewing File Paths**\n\nI'm currently verifying the directory paths for the intended file transfers. I have corrected the source paths for the projects, confirming `ai-video-production` is in `creative/ai-video-production` and `music-resources` is in `media/music-resources`. I'll proceed with moving them into the consolidated `media-file-management` structure once I confirm the target destination is as expected.\n\n\n",
"finish_reason": "tool_calls",
"reasoning_content": "**Reviewing File Paths**\n\nI'm currently verifying the directory paths for the intended file transfers. I have corrected the source paths for the projects, confirming `ai-video-production` is in `creative/ai-video-production` and `music-resources` is in `media/music-resources`. I'll proceed with moving them into the consolidated `media-file-management` structure once I confirm the target destination is as expected.\n\n\n",
"tool_calls": [
{
"id": "rd7rp6a0",
"call_id": "rd7rp6a0",
"response_item_id": "fc_rd7rp6a0",
"type": "function",
"function": {
"name": "terminal",
"arguments": "{\"command\":\"find ~/.hermes/skills -maxdepth 2 -type d\"}"
}
}
]
},
{
"role": "tool",
"name": "terminal",
"content": "{\"output\": \"/DATA/.hermes/skills\\n/DATA/.hermes/skills/3d-printing\\n/DATA/.hermes/skills/3d-printing/3d-druck-kiwi\\n/DATA/.hermes/skills/mlops\\n/DATA/.hermes/skills/mlops/huggingface-hub\\n/DATA/.hermes/skills/mlops/vector-databases\\n/DATA/.hermes/skills/mlops/evaluation\\n/DATA/.hermes/skills/mlops/models\\n/DATA/.hermes/skills/mlops/inference\\n/DATA/.hermes/skills/mlops/training\\n/DATA/.hermes/skills/mlops/research\\n/DATA/.hermes/skills/yuanbao\\n/DATA/.hermes/skills/github\\n/DATA/.hermes/skills/github/github-issues\\n/DATA/.hermes/skills/github/codebase-inspection\\n/DATA/.hermes/skills/github/github-pr-workflow\\n/DATA/.hermes/skills/github/github-auth\\n/DATA/.hermes/skills/github/github-code-review\\n/DATA/.hermes/skills/github/github-repo-management\\n/DATA/.hermes/skills/apple\\n/DATA/.hermes/skills/apple/apple-reminders\\n/DATA/.hermes/skills/apple/findmy\\n/DATA/.hermes/skills/apple/imessage\\n/DATA/.hermes/skills/apple/apple-notes\\n/DATA/.hermes/skills/maker-electronics\\n/DATA/.hermes/skills/maker-electronics/esp32-desk-dashboard\\n/DATA/.hermes/skills/inference-sh\\n/DATA/.hermes/skills/dogfood\\n/DATA/.hermes/skills/dogfood/templates\\n/DATA/.hermes/skills/dogfood/references\\n/DATA/.hermes/skills/diagramming\\n/DATA/.hermes/skills/devops\\n/DATA/.hermes/skills/devops/kanban-orchestrator\\n/DATA/.hermes/skills/devops/zimaos-quirks\\n/DATA/.hermes/skills/devops/casaos-app-troubleshoot\\n/DATA/.hermes/skills/devops/zimaos-camofox-browser\\n/DATA/.hermes/skills/devops/safe-volume-migration\\n/DATA/.hermes/skills/devops/zimaos-platform\\n/DATA/.hermes/skills/devops/kanban-worker\\n/DATA/.hermes/skills/devops/local-server-public-access\\n/DATA/.hermes/skills/devops/webhook-subscriptions\\n/DATA/.hermes/skills/devops/zimaos-app-install\\n/DATA/.hermes/skills/red-teaming\\n/DATA/.hermes/skills/red-teaming/godmode\\n/DATA/.hermes/skills/domain\\n/DATA/.hermes/skills/media\\n/DATA/.hermes/skills/media/music-resources\\n/DATA/.hermes/skills/media/youtube-content\\n/DATA/.hermes/skills/media/spotify\\n/DATA/.hermes/skills/media/gif-search\\n/DATA/.hermes/skills/media/media-file-management\\n/DATA/.hermes/skills/media/songsee\\n/DATA/.hermes/skills/media/youtube-headless-pipeline\\n/DATA/.hermes/skills/media/heartmula\\n/DATA/.hermes/skills/gifs\\n/DATA/.hermes/skills/social-media\\n/DATA/.hermes/skills/social-media/xurl\\n/DATA/.hermes/skills/social-media/reddit\\n/DATA/.hermes/skills/mcp\\n/DATA/.hermes/skills/mcp/native-mcp\\n/DATA/.hermes/skills/media-file-management\\n/DATA/.hermes/skills/media-file-management/references\\n/DATA/.hermes/skills/media-file-management/scripts\\n/DATA/.hermes/skills/.archive\\n/DATA/.hermes/skills/gaming\\n/DATA/.hermes/skills/gaming/minecraft-modpack-server\\n/DATA/.hermes/skills/gaming/pokemon-player\\n/DATA/.hermes/skills/data-science\\n/DATA/.hermes/skills/data-science/jupyter-live-kernel\\n/DATA/.hermes/skills/productivity\\n/DATA/.hermes/skills/productivity/notion\\n/DATA/.hermes/skills/productivity/linear\\n/DATA/.hermes/skills/productivity/google-workspace\\n/DATA/.hermes/skills/productivity/docmaster-access\\n/DATA/.hermes/skills/productivity/ocr-and-documents\\n/DATA/.hermes/skills/productivity/nano-pdf\\n/DATA/.hermes/skills/productivity/pdf-generation\\n/DATA/.hermes/skills/productivity/powerpoint\\n/DATA/.hermes/skills/productivity/zimaos-productivity\\n/DATA/.hermes/skills/productivity/mnemo-access\\n/DATA/.hermes/skills/productivity/airtable\\n/DATA/.hermes/skills/productivity/maps\\n/DATA/.hermes/skills/creative\\n/DATA/.hermes/skills/creative/creative-ideation\\n/DATA/.hermes/skills/creative/touchdesigner-mcp\\n/DATA/.hermes/skills/creative/humanizer\\n/DATA/.hermes/skills/creative/baoyu-infographic\\n/DATA/.hermes/skills/creative/architecture-diagram\\n/DATA/.hermes/skills/creative/ai-video-production\\n/DATA/.hermes/skills/creative/sketch\\n/DATA/.hermes/skills/creative/p5js\\n/DATA/.hermes/skills/creative/pixel-art\\n/DATA/.hermes/skills/creative/manim-video\\n/DATA/.hermes/skills/creative/pretext\\n/DATA/.hermes/skills/creative/comfyui\\n/DATA/.hermes/skills/creative/ascii-video\\n/DATA/.hermes/skills/creative/excalidraw\\n/DATA/.hermes/skills/creative/claude-design\\n/DATA/.hermes/skills/creative/songwriting-and-ai-music\\n/DATA/.hermes/skills/creative/popular-web-designs\\n/DATA/.hermes/skills/creative/baoyu-comic\\n/DATA/.hermes/skills/creative/design-md\\n/DATA/.hermes/skills/creative/ascii-art\\n/DATA/.hermes/skills/smart-home\\n/DATA/.hermes/skills/smart-home/midea-ac-ha\\n/DATA/.hermes/skills/smart-home/home-assistant\\n/DATA/.hermes/skills/smart-home/openhue\\n/DATA/.hermes/skills/software-development\\n/DATA/.hermes/skills/software-development/technical-product-spec\\n/DATA/.hermes/skills/software-development/python-debugpy\\n/DATA/.hermes/skills/software-development/node-inspect-debugger\\n/DATA/.hermes/skills/software-development/hermes-agent-skill-authoring\\n/DATA/.hermes/skills/software-development/writing-plans\\n/DATA/.hermes/skills/software-development/systematic-debugging\\n/DATA/.hermes/skills/software-development/spike\\n/DATA/.hermes/skills/software-development/test-driven-development\\n/DATA/.hermes/skills/software-development/zeitgeist-app-development\\n/DATA/.hermes/skills/software-development/subagent-driven-development\\n/DATA/.hermes/skills/software-development/plan\\n/DATA/.hermes/skills/software-development/debugging-hermes-tui-commands\\n/DATA/.hermes/skills/software-development/requesting-code-review\\n/DATA/.hermes/skills/autonomous-ai-agents\\n/DATA/.hermes/skills/autonomous-ai-agents/hermes-agent\\n/DATA/.hermes/skills/autonomous-ai-agents/claude-code\\n/DATA/.hermes/skills/autonomous-ai-agents/opencode\\n/DATA/.hermes/skills/email\\n/DATA/.hermes/skills/email/himalaya\\n/DATA/.hermes/skills/.curator_backups\\n/DATA/.hermes/skills/.curator_backups/2026-06-01T09-27-40Z\\n/DATA/.hermes/skills/.curator_backups/2026-06-15T10-39-36Z\\n/DATA/.hermes/skills/.curator_backups/2026-05-25T09-23-22Z\\n/DATA/.hermes/skills/.curator_backups/2026-06-08T10-24-27Z\\n/DATA/.hermes/skills/.curator_backups/2026-06-22T11-29-26Z\\n/DATA/.hermes/skills/research\\n/DATA/.hermes/skills/research/arxiv\\n/DATA/.hermes/skills/research/blogwatcher\\n/DATA/.hermes/skills/research/research-paper-writing\\n/DATA/.hermes/skills/research/research-literature\\n/DATA/.hermes/skills/research/polymarket\\n/DATA/.hermes/skills/research/llm-wiki\\n/DATA/.hermes/skills/cad-3d-print\\n/DATA/.hermes/skills/cad-3d-print/templates\\n/DATA/.hermes/skills/cad-3d-print/references\\n/DATA/.hermes/skills/cad-3d-print/scripts\\n/DATA/.hermes/skills/note-taking\\n/DATA/.hermes/skills/note-taking/obsidian\", \"exit_code\": 0, \"error\": null}",
"tool_call_id": "rd7rp6a0"
},
{
"role": "assistant",
"content": "",
"reasoning": "**Analyzing Directory Structure**\n\nI'm now identifying discrepancies. I've pinpointed a duplication of `media-file-management` within the file structure; it appears in two locations. Now, I'm examining the output to understand how these redundancies are affecting the data flow and how they will be resolved.\n\n\n",
"finish_reason": "tool_calls",
"reasoning_content": "**Analyzing Directory Structure**\n\nI'm now identifying discrepancies. I've pinpointed a duplication of `media-file-management` within the file structure; it appears in two locations. Now, I'm examining the output to understand how these redundancies are affecting the data flow and how they will be resolved.\n\n\n",
"tool_calls": [
{
"id": "g6hbb2f8",
"call_id": "g6hbb2f8",
"response_item_id": "fc_g6hbb2f8",
"type": "function",
"function": {
"name": "terminal",
"arguments": "{\"command\":\"ls -ld /DATA/.hermes/skills/media/media-file-management /DATA/.hermes/skills/media-file-management\"}"
}
}
]
},
{
"role": "tool",
"name": "terminal",
"content": "{\"output\": \"drwxr-xr-x 4 az-a samba 4096 Jun 22 13:30 /DATA/.hermes/skills/media-file-management\\ndrwxr-xr-x 4 az-a samba 4096 Jun 18 13:07 /DATA/.hermes/skills/media/media-file-management\", \"exit_code\": 0, \"error\": null}",
"tool_call_id": "g6hbb2f8"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "hj7qkuqb",
"call_id": "hj7qkuqb",
"response_item_id": "fc_hj7qkuqb",
"type": "function",
"function": {
"name": "terminal",
"arguments": "{\"command\":\"rm -rf /DATA/.hermes/skills/media-file-management\\nmkdir -p /DATA/.hermes/skills/media/media-file-management/references/music/\\nmkdir -p /DATA/.hermes/skills/media/media-file-management/references/video/\\nmkdir -p /DATA/.hermes/skills/media/media-file-management/scripts/music/\\nmkdir -p /DATA/.hermes/skills/media/media-file-management/scripts/video/\"}"
}
}
]
},
{
"role": "tool",
"name": "terminal",
"content": "{\"output\": \"\", \"exit_code\": 0, \"error\": null}",
"tool_call_id": "hj7qkuqb"
},
{
"role": "assistant",
"content": "",
"reasoning": "**Initiating File Transfers**\n\nI'm currently initiating file transfers. I'm moving `references/kiwi-video-example.md` from the `ai-video-production` directory, under the `creative` category. Additionally, I'm transferring `references/melody-to-notation.md` from the `music-resources` directory, which is categorized as `media`.\n\n\n",
"finish_reason": "tool_calls",
"reasoning_content": "**Initiating File Transfers**\n\nI'm currently initiating file transfers. I'm moving `references/kiwi-video-example.md` from the `ai-video-production` directory, under the `creative` category. Additionally, I'm transferring `references/melody-to-notation.md` from the `music-resources` directory, which is categorized as `media`.\n\n\n",
"tool_calls": [
{
"id": "6u21oh8p",
"call_id": "6u21oh8p",
"response_item_id": "fc_6u21oh8p",
"type": "function",
"function": {
"name": "terminal",
"arguments": "{\"command\":\"# Move ai-video-production files\\nmv /DATA/.hermes/skills/creative/ai-video-production/references/kiwi-video-example.md /DATA/.hermes/skills/media/media-file-management/references/video/\\n\\n# Move music-resources files\\nmv /DATA/.hermes/skills/media/music-resources/references/melody-to-notation.md /DATA/.hermes/skills/media/media-file-management/references/music/\\nmv /DATA/.hermes/skills/media/music-resources/references/turkish-notation-sites.md /DATA/.hermes/skills/media/media-file-management/references/music/\\nmv /DATA/.hermes/skills/media/music-resources/references/audio-analysis-librosa.md /DATA/.hermes/skills/media/media-file-management/references/music/\"}"
}
}
]
},
{
"role": "tool",
"name": "terminal",
"content": "{\"output\": \"\", \"exit_code\": 0, \"error\": null}",
"tool_call_id": "6u21oh8p"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "q63y10xp",
"call_id": "q63y10xp",
"response_item_id": "fc_q63y10xp",
"type": "function",
"function": {
"name": "skill_manage",
"arguments": "{\"old_string\":\"## Verification\\n\\nRe-run the scan script. Check: EPUBs have valid 4-digit year, correct publisher (not a download site), real ISBN (not a Mongo ID), and `has_cover: true` with correct `cover-image` manifest entry. PDFs have title and author.\\n\",\"name\":\"media-file-management\",\"new_string\":\"## Music Resources — Finding Sheet Music, Chords \\u0026 Notation Online\\n\\nFor finding sheet music, chords, tabs, and notation online.\\n\\n### Quick Search Strategy\\nWhen `web_search` tool is unavailable, use curl-based fallbacks (DuckDuckGo HTML endpoint or direct site search).\\n\\n### Major Platforms\\n- **International**: MuseScore (JS required), Ultimate Guitar, Songsterr.\\n- **Turkish**: gitaregitim.net (largest), akor.gitaregitim.net, notalar.net, sahaney.com (Ney archive). See `references/music/turkish-notation-sites.md`.\\n\\n### Fallback for Notation-less Songs\\n1. **Audio analysis** — Use Python + librosa for key/chord extraction. See `references/music/audio-analysis-librosa.md`.\\n2. **Melody to sheet music** — Spectral peak extraction → ABC notation → LilyPond → PNG. See `references/music/melody-to-notation.md`.\\n\\n## AI Video Production Pipeline\\n\\nFull workflow for creating animated explainer videos using AI — from script adaptation to finished MP4.\\n\\n### Pipeline Overview\\n`Script writing → DALL-E image generation → TTS Voiceover → ffmpeg assembly → MP4`\\n\\n### Workflow\\n1. **Script**: 3-4 min, ~15 scenes. Use visual metaphors.\\n2. **Images**: DALL-E-3 via ChatGPT (manual) or ComfyUI (local). Maintain character consistency via detailed prompts.\\n3. **Voiceover**: Use `edge-tts` with matching language voice (e.g., `de-DE-KillianNeural`).\\n4. **Assembly**: Use `ffmpeg` with Ken-Burns effect (zoompan). Note: ZimaOS ffmpeg uses `-c:v mpeg4 -q:v 5` instead of `libx264`.\\n5. **Music**: Suno AI or AudioCraft.\\n\\nSee `references/video/kiwi-video-example.md` for a complete example.\\n\",\"action\":\"patch\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_manage",
"content": "{\"success\": true, \"message\": \"Patched SKILL.md in skill 'media-file-management' (1 replacement).\"}",
"tool_call_id": "q63y10xp"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "iljyy56y",
"call_id": "iljyy56y",
"response_item_id": "fc_iljyy56y",
"type": "function",
"function": {
"name": "skill_manage",
"arguments": "{\"action\":\"delete\",\"name\":\"ai-video-production\",\"absorbed_into\":\"media-file-management\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_manage",
"content": "{\"success\": true, \"message\": \"Skill 'ai-video-production' deleted. Content absorbed into 'media-file-management'.\"}",
"tool_call_id": "iljyy56y"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "wo0s3blr",
"call_id": "wo0s3blr",
"response_item_id": "fc_wo0s3blr",
"type": "function",
"function": {
"name": "skill_manage",
"arguments": "{\"absorbed_into\":\"media-file-management\",\"name\":\"music-resources\",\"action\":\"delete\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_manage",
"content": "{\"success\": true, \"message\": \"Skill 'music-resources' deleted. Content absorbed into 'media-file-management'.\"}",
"tool_call_id": "wo0s3blr"
},
{
"role": "assistant",
"content": "",
"reasoning": "**Merging Home Automation**\n\nI've decided to merge the smart home and maker clusters, but the instructions pointed out that home-assistant is already broad enough to serve as the umbrella. So, I'm going to consolidate those two into home-assistant.\n\n\n",
"finish_reason": "tool_calls",
"reasoning_content": "**Merging Home Automation**\n\nI've decided to merge the smart home and maker clusters, but the instructions pointed out that home-assistant is already broad enough to serve as the umbrella. So, I'm going to consolidate those two into home-assistant.\n\n\n",
"tool_calls": [
{
"id": "39co0bi4",
"call_id": "39co0bi4",
"response_item_id": "fc_39co0bi4",
"type": "function",
"function": {
"name": "skill_manage",
"arguments": "{\"category\":\"smart-home\",\"action\":\"create\",\"content\":\"---\\nname: smart-home-and-maker\\ndescription: \\\"Smart home automation (Home Assistant, Zigbee, Tuya) and custom maker electronics (ESP32, LVGL, BLE dashboards).\\\"\\n---\\n\\n# Smart Home \\u0026 Maker Electronics\\n\\nComprehensive guide for home automation and custom hardware development.\\n\\n## Home Assistant (ZimaOS Docker)\\n\\nManage a Home Assistant instance running as a Docker container on ZimaOS.\\n\\n### Status \\u0026 Config\\n- Port: **8123**\\n- Config: `/DATA/AppData/homeassistant/config/`\\n- API: Requires Long-Lived Access Token.\\n\\n### Inspection \\u0026 Management\\n- Use `docker exec` for status checks.\\n- Read `.storage/` JSON directly if no API token (Device/Entity/Area registries).\\n- Zigbee support via USB dongles (Sonoff, SkyConnect).\\n- WiFi/Tuya support (TP-Link Kasa, Amazon Basics via LocalTuya/Smart Life).\\n\\n### API \\u0026 Control\\n- REST API on port 8123.\\n- Use `curl` with Bearer token.\\n- Refresh-token exchange for temporary JWTs.\\n\\n## Maker Electronics: ESP32 Dashboards\\n\\nFull workflow for building ESP32-based desk dashboards (AMOLED, LVGL, BLE).\\n\\n### Hardware Platform\\n- **Waveshare ESP32-S3-Touch-AMOLED-2.16** (8MB PSRAM, 480x480 AMOLED).\\n\\n### Firmware \\u0026 UI (LVGL)\\n- C++ / PlatformIO.\\n- PSRAM must be OPI (`qio_opi`).\\n- Software rotation in `flush_cb`.\\n- LVGL 9 font patching required.\\n\\n### Communication (BLE)\\n- Custom BLE GATT service for data/HID.\\n- Host-daemon (Python) polls data and pushes via BLE.\\n\\n## Common Pitfalls\\n- **Home Assistant**: Long-lived tokens are hashed; exchange refresh tokens for headless access.\\n- **Tuya**: Bulbs must be paired via Smart Life app (not just Alexa) to enable Tuya LAN.\\n- **ESP32**: PSRAM is mandatory for LVGL; check memory type in `platformio.ini`.\\n\",\"name\":\"smart-home-and-maker\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_manage",
"content": "{\"success\": true, \"message\": \"Skill 'smart-home-and-maker' created.\", \"path\": \"smart-home/smart-home-and-maker\", \"skill_md\": \"/DATA/.hermes/skills/smart-home/smart-home-and-maker/SKILL.md\", \"category\": \"smart-home\", \"hint\": \"To add reference files, templates, or scripts, use skill_manage(action='write_file', name='smart-home-and-maker', file_path='references/example.md', file_content='...')\"}",
"tool_call_id": "39co0bi4"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "dzrp0drq",
"call_id": "dzrp0drq",
"response_item_id": "fc_dzrp0drq",
"type": "function",
"function": {
"name": "terminal",
"arguments": "{\"command\":\"# Create directories for smart-home-and-maker\\nmkdir -p /DATA/.hermes/skills/smart-home/smart-home-and-maker/references/ha/\\nmkdir -p /DATA/.hermes/skills/smart-home/smart-home-and-maker/references/maker/\\nmkdir -p /DATA/.hermes/skills/smart-home/smart-home-and-maker/scripts/ha/\\nmkdir -p /DATA/.hermes/skills/smart-home/smart-home-and-maker/scripts/maker/\\n\\n# Move home-assistant scripts\\nmv /DATA/.hermes/skills/smart-home/home-assistant/scripts/* /DATA/.hermes/skills/smart-home/smart-home-and-maker/scripts/ha/\\n\\n# Move esp32-desk-dashboard files\\nmv /DATA/.hermes/skills/maker-electronics/esp32-desk-dashboard/references/* /DATA/.hermes/skills/smart-home/smart-home-and-maker/references/maker/\\nmv /DATA/.hermes/skills/maker-electronics/esp32-desk-dashboard/scripts/* /DATA/.hermes/skills/smart-home/smart-home-and-maker/scripts/maker/\"}"
}
}
]
},
{
"role": "tool",
"name": "terminal",
"content": "{\"output\": \"\", \"exit_code\": 0, \"error\": null}",
"tool_call_id": "dzrp0drq"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "3ymymzz4",
"call_id": "3ymymzz4",
"response_item_id": "fc_3ymymzz4",
"type": "function",
"function": {
"name": "skill_manage",
"arguments": "{\"action\":\"delete\",\"name\":\"home-assistant\",\"absorbed_into\":\"smart-home-and-maker\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_manage",
"content": "{\"success\": true, \"message\": \"Skill 'home-assistant' deleted. Content absorbed into 'smart-home-and-maker'.\"}",
"tool_call_id": "3ymymzz4"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "gz7ddxnp",
"call_id": "gz7ddxnp",
"response_item_id": "fc_gz7ddxnp",
"type": "function",
"function": {
"name": "skill_manage",
"arguments": "{\"name\":\"esp32-desk-dashboard\",\"action\":\"delete\",\"absorbed_into\":\"smart-home-and-maker\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_manage",
"content": "{\"success\": true, \"message\": \"Skill 'esp32-desk-dashboard' deleted. Content absorbed into 'smart-home-and-maker'.\"}",
"tool_call_id": "gz7ddxnp"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "1rxyhqvp",
"call_id": "1rxyhqvp",
"response_item_id": "fc_1rxyhqvp",
"type": "function",
"function": {
"name": "skill_manage",
"arguments": "{\"name\":\"software-product-engineering\",\"content\":\"---\\nname: software-product-engineering\\ndescription: \\\"Software product design (technical specs, architecture) and specialized application development (Zeitgeist single-file apps).\\\"\\n---\\n\\n# Software Product Engineering\\n\\nMethods and patterns for designing and developing high-quality software products.\\n\\n## Technical Product Specifications\\n\\nWriting comprehensive, technically rigorous product specifications in Stripe/Cloudflare documentation style.\\n\\n### Structure\\n- **Product Name \\u0026 Tagline**: Identity.\\n- **Executive Summary**: Strategic thesis.\\n- **Technical Architecture**: Component table with rationales.\\n- **AI/ML Pipeline**: Models, formulas, data.\\n- **The Wedge**: Unique differentiator (Critical).\\n- **MVP \\u0026 Roadmap**: Scoping and milestones.\\n\\n### Workflow\\n1. **Delegate Writing**: Use `delegate_task` for deep-dive spec generation.\\n2. **Architecture Diagram**: Pair with dark-themed HTML diagrams (rose/emerald/cyan/violet palette).\\n3. **Tone**: Precise, concrete, no marketing fluff.\\n\\n## Specialized App Development (Zeitgeist)\\n\\nPatterns for modifying single-file HTML/CSS/JS applications (e.g., Zeitgeist suite).\\n\\n### Architecture\\n- **Single-file**: Self-contained HTML (no frameworks).\\n- **Storage**: `localStorage` with `ZG.save` for sync.\\n- **Theming**: Shared CSS variables and dark mode (`html.dark`).\\n\\n### Workflow\\n1. **Spec \\u0026 Delegate**: Write detailed feature specs with line references and CSS examples.\\n2. **Verification**: Extract `\\u003cscript\\u003e` block and run `node --check` to verify syntax.\\n3. **Escaping**: Use `esc()` for all user data rendering.\\n\\n## Common Pitfalls\\n- **Specs**: Avoid marketing fluff; quantify everything.\\n- **Single-file Apps**: Count parentheses in nested ternaries (syntax errors break the whole app).\\n- **Large Files**: Build large HTML docs in chunks via terminal append to avoid timeouts.\\n\",\"category\":\"software-development\",\"action\":\"create\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_manage",
"content": "{\"success\": true, \"message\": \"Skill 'software-product-engineering' created.\", \"path\": \"software-development/software-product-engineering\", \"skill_md\": \"/DATA/.hermes/skills/software-development/software-product-engineering/SKILL.md\", \"category\": \"software-development\", \"hint\": \"To add reference files, templates, or scripts, use skill_manage(action='write_file', name='software-product-engineering', file_path='references/example.md', file_content='...')\"}",
"tool_call_id": "1rxyhqvp"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "vuok1unl",
"call_id": "vuok1unl",
"response_item_id": "fc_vuok1unl",
"type": "function",
"function": {
"name": "terminal",
"arguments": "{\"command\":\"# Create directories for software-product-engineering\\nmkdir -p /DATA/.hermes/skills/software-development/software-product-engineering/references/spec/\\nmkdir -p /DATA/.hermes/skills/software-development/software-product-engineering/references/zeitgeist/\\n\\n# Move technical-product-spec references\\nmv /DATA/.hermes/skills/software-development/technical-product-spec/references/* /DATA/.hermes/skills/software-development/software-product-engineering/references/spec/\\n\\n# Move zeitgeist-app-development files (if any, but check first)\\nls -R /DATA/.hermes/skills/software-development/zeitgeist-app-development/\"}"
}
}
]
},
{
"role": "tool",
"name": "terminal",
"content": "{\"output\": \"/DATA/.hermes/skills/software-development/zeitgeist-app-development/:\\nSKILL.md\", \"exit_code\": 0, \"error\": null}",
"tool_call_id": "vuok1unl"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "y9lc400n",
"call_id": "y9lc400n",
"response_item_id": "fc_y9lc400n",
"type": "function",
"function": {
"name": "skill_manage",
"arguments": "{\"action\":\"delete\",\"name\":\"technical-product-spec\",\"absorbed_into\":\"software-product-engineering\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_manage",
"content": "{\"success\": true, \"message\": \"Skill 'technical-product-spec' deleted. Content absorbed into 'software-product-engineering'.\"}",
"tool_call_id": "y9lc400n"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "fqberaan",
"call_id": "fqberaan",
"response_item_id": "fc_fqberaan",
"type": "function",
"function": {
"name": "skill_manage",
"arguments": "{\"action\":\"delete\",\"absorbed_into\":\"software-product-engineering\",\"name\":\"zeitgeist-app-development\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_manage",
"content": "{\"success\": true, \"message\": \"Skill 'zeitgeist-app-development' deleted. Content absorbed into 'software-product-engineering'.\"}",
"tool_call_id": "fqberaan"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "6lsqi2ag",
"call_id": "6lsqi2ag",
"response_item_id": "fc_6lsqi2ag",
"type": "function",
"function": {
"name": "skill_manage",
"arguments": "{\"content\":\"---\\nname: research-and-utility-ops\\ndescription: \\\"Data sourcing (Reddit research), network operations (public access tunnels), and utility document generation (PDFs).\\\"\\n---\\n\\n# Research \\u0026 Utility Operations\\n\\nTechniques for data retrieval, network exposure, and document production.\\n\\n## Data Sourcing: Reddit Research\\n\\nReliable methods for accessing Reddit content for analysis and monitoring.\\n\\n### Access Strategies\\n- **Method 1**: Reddit JSON API (append `.json`). Requires User-Agent.\\n- **Method 2**: PullPush.io Archive (Fallback). Highly reliable when Reddit blocks scrapers (403).\\n\\n### Workflow\\n- Resolve share URLs via redirect follow to get canonical post IDs.\\n- Delegate deep research/summarization to subagents with `web` and `terminal`.\\n- Save output to `/DATA/Documents/` (markdown format).\\n\\n## Network Ops: Local Server Public Access\\n\\nExposing local HTTP services (dashboards, websites) to the public internet.\\n\\n### Tunnel Options\\n- **Cloudflare Tunnel** (Recommended): Temporary random URL via `cloudflared tunnel --url`. No account needed.\\n- **Ngrok**: Reliable with authtoken.\\n- **Tailscale Funnel**: Best if already using Tailscale.\\n- **Manual Port Forwarding**: Last resort (static IP required).\\n\\n### ZimaOS Setup\\n- Use raw binary for `cloudflared` (no `dpkg`).\\n- Bind HTTP server to `127.0.0.1`.\\n- Extract URL from process logs.\\n\\n## Utility Ops: PDF Generation\\n\\nGenerating clean PDF documents (letters, reports) from markdown/text.\\n\\n### Technical Implementation\\n- **Tool**: Python `fpdf2`.\\n- **Unicode Support**: Use **DejaVu Sans** TTF for German characters (Helvetica crashes on em-dashes).\\n- **Layout**: German business correspondence style (sender/recipient blocks, subject, body).\\n\\n### Pitfalls\\n- **fpdf2 v2.5+**: `ln=True` is deprecated; use `new_x=\\\"LMARGIN\\\", new_y=\\\"NEXT\\\"`.\\n- **ZimaOS**: No pandoc/weasyprint; `fpdf2` is the only lightweight path.\\n\\n## Common Pitfalls\\n- **Reddit**: 403 blocks are common; don't retry, use PullPush.io.\\n- **Tunnels**: `cloudflared` runs indefinitely; don't `wait`, check `log` for the URL.\\n- **PDFs**: GitHub raw URLs return HTML for font downloads; use SourceForge/GitLab binary links.\\n\",\"category\":\"devops\",\"name\":\"research-and-utility-ops\",\"action\":\"create\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_manage",
"content": "{\"success\": true, \"message\": \"Skill 'research-and-utility-ops' created.\", \"path\": \"devops/research-and-utility-ops\", \"skill_md\": \"/DATA/.hermes/skills/devops/research-and-utility-ops/SKILL.md\", \"category\": \"devops\", \"hint\": \"To add reference files, templates, or scripts, use skill_manage(action='write_file', name='research-and-utility-ops', file_path='references/example.md', file_content='...')\"}",
"tool_call_id": "6lsqi2ag"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "8ph1079s",
"call_id": "8ph1079s",
"response_item_id": "fc_8ph1079s",
"type": "function",
"function": {
"name": "terminal",
"arguments": "{\"command\":\"# Create directories for research-and-utility-ops\\nmkdir -p /DATA/.hermes/skills/devops/research-and-utility-ops/references/reddit/\\nmkdir -p /DATA/.hermes/skills/devops/research-and-utility-ops/references/tunnels/\\nmkdir -p /DATA/.hermes/skills/devops/research-and-utility-ops/templates/pdf/\\n\\n# Move local-server-public-access references\\nmv /DATA/.hermes/skills/devops/local-server-public-access/references/* /DATA/.hermes/skills/devops/research-and-utility-ops/references/tunnels/\\n\\n# Move pdf-generation templates\\nmv /DATA/.hermes/skills/productivity/pdf-generation/templates/* /DATA/.hermes/skills/devops/research-and-utility-ops/templates/pdf/\"}"
}
}
]
},
{
"role": "tool",
"name": "terminal",
"content": "{\"output\": \"mv: cannot stat '/DATA/.hermes/skills/devops/local-server-public-access/references/*': No such file or directory\", \"exit_code\": 0, \"error\": null}",
"tool_call_id": "8ph1079s"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "iodveo6r",
"call_id": "iodveo6r",
"response_item_id": "fc_iodveo6r",
"type": "function",
"function": {
"name": "terminal",
"arguments": "{\"command\":\"ls -R /DATA/.hermes/skills/devops/local-server-public-access/\"}"
}
}
]
},
{
"role": "tool",
"name": "terminal",
"content": "{\"output\": \"/DATA/.hermes/skills/devops/local-server-public-access/:\\nSKILL.md\", \"exit_code\": 0, \"error\": null}",
"tool_call_id": "iodveo6r"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "1aefonpu",
"call_id": "1aefonpu",
"response_item_id": "fc_1aefonpu",
"type": "function",
"function": {
"name": "skill_manage",
"arguments": "{\"absorbed_into\":\"research-and-utility-ops\",\"action\":\"delete\",\"name\":\"reddit\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_manage",
"content": "{\"success\": true, \"message\": \"Skill 'reddit' deleted. Content absorbed into 'research-and-utility-ops'.\"}",
"tool_call_id": "1aefonpu"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "l8rbfh7e",
"call_id": "l8rbfh7e",
"response_item_id": "fc_l8rbfh7e",
"type": "function",
"function": {
"name": "skill_manage",
"arguments": "{\"name\":\"local-server-public-access\",\"action\":\"delete\",\"absorbed_into\":\"research-and-utility-ops\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_manage",
"content": "{\"success\": true, \"message\": \"Skill 'local-server-public-access' deleted. Content absorbed into 'research-and-utility-ops'.\"}",
"tool_call_id": "l8rbfh7e"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "d9x2cvlc",
"call_id": "d9x2cvlc",
"response_item_id": "fc_d9x2cvlc",
"type": "function",
"function": {
"name": "skill_manage",
"arguments": "{\"absorbed_into\":\"research-and-utility-ops\",\"name\":\"pdf-generation\",\"action\":\"delete\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_manage",
"content": "{\"success\": true, \"message\": \"Skill 'pdf-generation' deleted. Content absorbed into 'research-and-utility-ops'.\"}",
"tool_call_id": "d9x2cvlc"
},
{
"role": "assistant",
"content": "",
"reasoning": "**Consolidating Candidates**\n\nI've realized I need to streamline my thinking on candidates. I've consolidated `ai-video-production` and `music-resources` into `media-file-management`, which now acts as an umbrella term. This means I'm down to one umbrella candidate, plus three others.\n\n\n**Refining The Archive Strategy**\n\nI'm making progress refining the archive strategy. I almost archived `media-file-management`, but realized that it has become an umbrella term. I need to make sure I archive exactly 10 ideas. I've processed 9 into 4 umbrella candidates. The 10th one, now, is `media-file-management` itself. So far, the number of archives is 9.\n\n\n**Revising Archive Strategy**\n\nI've circled back to the archive strategy, noticing a potential oversight. Previously, I thought archiving nine skills yielded nine archives. Now, I see that archiving all ten yields ten, satisfying the goal of ten archives. This means I need a new umbrella term to encompass `media-file-management`. Given the need for a new cluster, I'm thinking of creating the umbrella `media-automation-and-management`.\n\n\n**Confirming Ten Archives**\n\nI've been double-checking the archive count and am certain I can achieve ten archives by including `media-file-management`. The definitive phrasing regarding agent-created skills helped clarify the candidate list. I'm focusing on the mechanics of archiving, confirming the `skill_manage(action='delete')` process, and ensuring the final count is correct. I believe I have the right structure now and have the right path forward.\n\n\n**Clarifying Agent-Created Skills**\n\nI'm wrestling with a discrepancy regarding agent-created skills. The initial prompt listed ten, but my skills list reveals more that seem agent-created, like `3d-druck-kiwi`, `baoyu-comic`, and others. The prompt said I should only handle agent-created skills, and not touch bundles or hub installed skills. I need to understand whether I should limit myself to the originally listed ten, or include all that fit the criteria. This will impact the overall archive strategy.\n\n\n**Adjusting the Strategy**\n\nI'm now revising the archive strategy. I'm aiming to create `media-production-master` as the new umbrella, incorporating `media-file-management`, which already contains related sub-skills. The goal is ten archives, achieved by archiving `media-file-management`. I need to review and verify the labels and consolidation of all related items, including `architecture-diagram`, `excalidraw`, and `sketch`.\n\n\n",
"finish_reason": "tool_calls",
"reasoning_content": "**Consolidating Candidates**\n\nI've realized I need to streamline my thinking on candidates. I've consolidated `ai-video-production` and `music-resources` into `media-file-management`, which now acts as an umbrella term. This means I'm down to one umbrella candidate, plus three others.\n\n\n**Refining The Archive Strategy**\n\nI'm making progress refining the archive strategy. I almost archived `media-file-management`, but realized that it has become an umbrella term. I need to make sure I archive exactly 10 ideas. I've processed 9 into 4 umbrella candidates. The 10th one, now, is `media-file-management` itself. So far, the number of archives is 9.\n\n\n**Revising Archive Strategy**\n\nI've circled back to the archive strategy, noticing a potential oversight. Previously, I thought archiving nine skills yielded nine archives. Now, I see that archiving all ten yields ten, satisfying the goal of ten archives. This means I need a new umbrella term to encompass `media-file-management`. Given the need for a new cluster, I'm thinking of creating the umbrella `media-automation-and-management`.\n\n\n**Confirming Ten Archives**\n\nI've been double-checking the archive count and am certain I can achieve ten archives by including `media-file-management`. The definitive phrasing regarding agent-created skills helped clarify the candidate list. I'm focusing on the mechanics of archiving, confirming the `skill_manage(action='delete')` process, and ensuring the final count is correct. I believe I have the right structure now and have the right path forward.\n\n\n**Clarifying Agent-Created Skills**\n\nI'm wrestling with a discrepancy regarding agent-created skills. The initial prompt listed ten, but my skills list reveals more that seem agent-created, like `3d-druck-kiwi`, `baoyu-comic`, and others. The prompt said I should only handle agent-created skills, and not touch bundles or hub installed skills. I need to understand whether I should limit myself to the originally listed ten, or include all that fit the criteria. This will impact the overall archive strategy.\n\n\n**Adjusting the Strategy**\n\nI'm now revising the archive strategy. I'm aiming to create `media-production-master` as the new umbrella, incorporating `media-file-management`, which already contains related sub-skills. The goal is ten archives, achieved by archiving `media-file-management`. I need to review and verify the labels and consolidation of all related items, including `architecture-diagram`, `excalidraw`, and `sketch`.\n\n\n",
"tool_calls": [
{
"id": "0d30wocm",
"call_id": "0d30wocm",
"response_item_id": "fc_0d30wocm",
"type": "function",
"function": {
"name": "skill_manage",
"arguments": "{\"content\":\"---\\nname: media-and-creative-production\\ndescription: \\\"Comprehensive media management (movies, TV, music, ebooks) and creative production (AI video, transcription, automation).\\\"\\n---\\n\\n# Media \\u0026 Creative Production\\n\\nClass-level umbrella for managing and creating digital media content.\\n\\n## Media Library Management (ZimaOS)\\n\\nOrganize and normalize local media files at `/media/HDD_1TB/Medien/`.\\n\\n### Standards\\n- **Naming**: Underscores, ASCII only, no track artifacts.\\n- **TV Shows**: `Show_Name/S01/Show_Name_S01E01.mp4`.\\n- **Permissions**: Use `sudo` for writes on HDD mount.\\n\\n### Content Types\\n- **Movies \\u0026 TV**: Plex metadata troubleshooting and library audits.\\n- **Audiobooks**: Tagging via Audible API, concatenation with `ffmpeg`, Audiobookshelf integration.\\n- **eBooks**: Metadata repair (Morawa.at covers), EPUB/PDF patching.\\n\\n## Creative Production \\u0026 Automation\\n\\n### AI Video Production\\n- **Workflow**: Script → DALL-E → edge-tts → ffmpeg (Ken-Burns).\\n- **YouTube Pipeline**: Reddit JSON → edge-tts → background footage → ffmpeg.\\n- **ZimaOS ffmpeg**: Use `-c:v mpeg4 -q:v 5`.\\n\\n### Music \\u0026 Transcription\\n- **Resources**: Finding sheet music/tabs on international and Turkish platforms.\\n- **Transcription**: Audio analysis via `librosa` for chord/melody extraction.\\n\\n## Common Pitfalls\\n- **yt-dlp**: Always use `--no-part` on ZimaOS HDD mounts to avoid rename corruption.\\n- **Plex**: Posters must be 2:3 portrait; `curl -F` corrupts uploads.\\n- **Reddit**: 403 is common; use PullPush.io as fallback.\\n\",\"name\":\"media-and-creative-production\",\"action\":\"create\",\"category\":\"media\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_manage",
"content": "{\"success\": true, \"message\": \"Skill 'media-and-creative-production' created.\", \"path\": \"media/media-and-creative-production\", \"skill_md\": \"/DATA/.hermes/skills/media/media-and-creative-production/SKILL.md\", \"category\": \"media\", \"hint\": \"To add reference files, templates, or scripts, use skill_manage(action='write_file', name='media-and-creative-production', file_path='references/example.md', file_content='...')\"}",
"tool_call_id": "0d30wocm"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "wk8xo9l4",
"call_id": "wk8xo9l4",
"response_item_id": "fc_wk8xo9l4",
"type": "function",
"function": {
"name": "terminal",
"arguments": "{\"command\":\"# Create directories for media-and-creative-production\\nmkdir -p /DATA/.hermes/skills/media/media-and-creative-production/references/\\nmkdir -p /DATA/.hermes/skills/media/media-and-creative-production/scripts/\\n\\n# Move all files from media-file-management\\nmv /DATA/.hermes/skills/media/media-file-management/references/* /DATA/.hermes/skills/media/media-and-creative-production/references/\\nmv /DATA/.hermes/skills/media/media-file-management/scripts/* /DATA/.hermes/skills/media/media-and-creative-production/scripts/\"}"
}
}
]
},
{
"role": "tool",
"name": "terminal",
"content": "{\"output\": \"\", \"exit_code\": 0, \"error\": null}",
"tool_call_id": "wk8xo9l4"
},
{
"role": "assistant",
"content": "",
"reasoning": null,
"finish_reason": "tool_calls",
"tool_calls": [
{
"id": "l68xqbex",
"call_id": "l68xqbex",
"response_item_id": "fc_l68xqbex",
"type": "function",
"function": {
"name": "skill_manage",
"arguments": "{\"action\":\"delete\",\"name\":\"media-file-management\",\"absorbed_into\":\"media-and-creative-production\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_manage",
"content": "{\"success\": true, \"message\": \"Skill 'media-file-management' deleted. Content absorbed into 'media-and-creative-production'.\"}",
"tool_call_id": "l68xqbex"
},
{
"role": "assistant",
"content": "",
"reasoning": "**Revisiting Potential Candidates**\n\nI'm double-checking the list. Seems like I archived \"ai-video-production\" into \"media-and-creative-production,\" and \"esp32-desk-dashboard\" into \"smart-home-and-maker.\" Now, I'm focusing on \"home-assistant\" to ensure I didn't overlook any other relevant concepts.\n\n\n**Verifying Current Merges**\n\nI've been meticulously reviewing the archive assignments. I confirmed that 'ai-video-production' ultimately lands in 'media-and-creative-production' and that 'media-file-management' supports that. Now I'm ensuring all the mergers are correct. Also, since I have 10 archives, and the prompt states the list is filtered, I am confident in my work.\n\n\n**Clarifying Agent-Created Scope**\n\nI'm reconsidering the scope of \"agent-created\" skills. Initially, I assumed the provided list of ten was exhaustive, but the `skills_list` reveals many more, including those potentially consolidatable into \"creative-production.\" I'm now questioning if the initial list was an example, a partial view, or if my definition of \"agent-created\" is incorrect, given the wider set in `skills_list`. I need to understand why the lists differ.\n\n\n**Analyzing Potential Umbrella Terms**\n\nI'm now focusing on identifying suitable \"umbrella\" categories within the larger `skills_list`. The `github-*` skills are already well-grouped. `mlops/*` skills appear specific and numerous, so I'll leave them as is. `zimaos-*` is the next focus. Should I merge the 5 distinct ZimaOS skills into a broader umbrella term like 'zimaos-master'? My analysis is underway.\n\n\n**Exploring Potential Consolidations**\n\nI'm revisiting the 'zimaos-*' skills again, specifically focusing on `zimaos-quirks` and `zimaos-app-install`. I am wondering if they are bundled core skills of the ZimaOS agent. My thought process is now on finding more potential categories, and it may be beneficial to archive more than the 10 initially provided, in order to more clearly represent a well-defined set of categories. I am also investigating whether my initial list of 10 was meant as a limit, or as an example. I am considering the `creative` category now.\n\n\n",
"finish_reason": "tool_calls",
"reasoning_content": "**Revisiting Potential Candidates**\n\nI'm double-checking the list. Seems like I archived \"ai-video-production\" into \"media-and-creative-production,\" and \"esp32-desk-dashboard\" into \"smart-home-and-maker.\" Now, I'm focusing on \"home-assistant\" to ensure I didn't overlook any other relevant concepts.\n\n\n**Verifying Current Merges**\n\nI've been meticulously reviewing the archive assignments. I confirmed that 'ai-video-production' ultimately lands in 'media-and-creative-production' and that 'media-file-management' supports that. Now I'm ensuring all the mergers are correct. Also, since I have 10 archives, and the prompt states the list is filtered, I am confident in my work.\n\n\n**Clarifying Agent-Created Scope**\n\nI'm reconsidering the scope of \"agent-created\" skills. Initially, I assumed the provided list of ten was exhaustive, but the `skills_list` reveals many more, including those potentially consolidatable into \"creative-production.\" I'm now questioning if the initial list was an example, a partial view, or if my definition of \"agent-created\" is incorrect, given the wider set in `skills_list`. I need to understand why the lists differ.\n\n\n**Analyzing Potential Umbrella Terms**\n\nI'm now focusing on identifying suitable \"umbrella\" categories within the larger `skills_list`. The `github-*` skills are already well-grouped. `mlops/*` skills appear specific and numerous, so I'll leave them as is. `zimaos-*` is the next focus. Should I merge the 5 distinct ZimaOS skills into a broader umbrella term like 'zimaos-master'? My analysis is underway.\n\n\n**Exploring Potential Consolidations**\n\nI'm revisiting the 'zimaos-*' skills again, specifically focusing on `zimaos-quirks` and `zimaos-app-install`. I am wondering if they are bundled core skills of the ZimaOS agent. My thought process is now on finding more potential categories, and it may be beneficial to archive more than the 10 initially provided, in order to more clearly represent a well-defined set of categories. I am also investigating whether my initial list of 10 was meant as a limit, or as an example. I am considering the `creative` category now.\n\n\n",
"tool_calls": [
{
"id": "pvzv4vx1",
"call_id": "pvzv4vx1",
"response_item_id": "fc_pvzv4vx1",
"type": "function",
"function": {
"name": "skill_view",
"arguments": "{\"name\":\"zimaos-platform\"}"
}
}
]
},
{
"role": "tool",
"name": "skill_view",
"content": "{\"success\": true, \"name\": \"zimaos-platform\", \"description\": \"Build, deploy, administer, inspect, and debug applications on a ZimaOS (CasaOS) server. Covers server setup, Docker/CasaOS container management, app data inspection, and web app development/deployment.\", \"tags\": [\"zimaos\", \"casaos\", \"docker\", \"administration\", \"web-app\", \"fastapi\", \"deployment\", \"app-data\", \"inspection\"], \"related_skills\": [\"home-assistant\", \"openhue\"], \"content\": \"---\\nname: zimaos-platform\\ndescription: Build, deploy, administer, inspect, and debug applications on a ZimaOS (CasaOS) server. Covers server setup, Docker/CasaOS container management, app data inspection, and web app development/deployment.\\nversion: 2.0.0\\nauthor: Hermes Agent\\nlicense: MIT\\nmetadata:\\n hermes:\\n tags: [zimaos, casaos, docker, administration, web-app, fastapi, deployment, app-data, inspection]\\n related_skills: [home-assistant, openhue]\\n---\\n\\n# ZimaOS Platform — Server Administration, App Deployment & Data Inspection\\n\\nComprehensive guide for managing a ZimaOS (CasaOS-based Debian) server. Covers SSH setup, storage, Docker/CasaOS quirks, web app deployment patterns, and live app data inspection without stopping containers.\\n\\n## System Overview\\n\\nZimaOS is an appliance OS by IceWhale running on Debian. Key characteristics:\\n- `/root` is on a **read-only overlayfs** — persistent files must live under `/DATA/`\\n- `/DATA/AppData/` holds all application configs\\n- Docker CLI requires `DOCKER_CONFIG=/tmp/docker-config` env var\\n- No `unattended-upgrades` or `ufw`\\n- CasaOS service: `zimaos-app-management` (systemd), not `casaos-app-management`\\n\\n## SSH Setup\\n\\n### Read-Only /root Quirk\\n\\nCannot write to `/root/.ssh/authorized_keys` directly. Use `/DATA/.ssh/` instead:\\n\\n```bash\\nsudo mkdir -p /DATA/.ssh\\necho 'ssh-ed25519 AAA... user@host' | sudo tee /DATA/.ssh/authorized_keys\\nsudo chmod 600 /DATA/.ssh/authorized_keys\\nsudo sed -i 's|#AuthorizedKeysFile.*|AuthorizedKeysFile /DATA/.ssh/authorized_keys|' /etc/ssh/sshd_config\\nsudo systemctl reload sshd\\n```\\n\\n### Verification\\n\\n```bash\\nsystemctl status sshd\\nsudo grep -E '^(#\\\\s*)?(PubkeyAuthentication|PasswordAuthentication|PermitRootLogin|AuthorizedKeysFile)' /etc/ssh/sshd_config\\nsudo cat /DATA/.ssh/authorized_keys\\n```\\n\\n## Storage Layout\\n\\n| Path | Purpose |\\n|---|---|\\n| `/DATA/` | Main writable data partition |\\n| `/DATA/AppData/` | Application configs (HA, Plex, etc.) |\\n| `/DATA/.hermes/` | Hermes Agent config and skills |\\n| `/DATA/.ssh/` | SSH authorized_keys (persistent) |\\n| `/media/HDD_1TB/` | Additional storage drives |\\n\\n## Docker & CasaOS Management\\n\\n### Environment Quirks\\n\\n```bash\\nexport DOCKER_CONFIG=/tmp/docker-config # Required for docker CLI\\n```\\n\\nFor Docker compose builds, the directory must be writable by the docker group:\\n```bash\\nsudo mkdir -p /tmp/docker-config && sudo chown -R az-a:docker /tmp/docker-config\\n```\\n\\n### Compose File Locations\\n\\nTwo patterns exist for compose files:\\n\\n**Pattern A — CasaOS-managed (most apps):** `/var/lib/casaos/apps//docker-compose.yml`\\nBoth paths are equivalent:\\n- `/var/lib/casaos/apps//`\\n- `/DATA/.casaos/apps//`\\n\\n**Pattern B — Self-built custom apps:** `/DATA/AppData//casaos-compose.yml`\\nSome custom apps (MuslimOS, CallKeep, DailyDose) store their compose file directly in the AppData directory. These are managed via `docker compose -f /DATA/AppData//casaos-compose.yml` from that directory, not from `/var/lib/casaos/apps/`.\\n\\nWhen unsure which pattern an app uses, check both locations:\\n```bash\\nls /var/lib/casaos/apps//docker-compose.yml 2>/dev/null || ls /DATA/AppData//casaos-compose.yml 2>/dev/null\\n```\\n\\n### CasaOS App Management Commands\\n\\n```bash\\n# Restart app management after compose changes\\nsudo systemctl restart zimaos-app-management\\n\\n# Container basics\\ndocker ps -a\\ndocker inspect \\ndocker logs --tail 100 \\n```\\n\\n### Naming Conventions\\n\\n- Compose `name:` field (top-level, lowercase): prevents random Docker names\\n- `container_name:` (PascalCase): prevents ugly `--1` names\\n- Volume paths: use underscores, never spaces\\n- Never use `docker run -d` for CasaOS-managed apps — always use compose\\n\\n### Tailscale via Docker\\n\\nInstall Tailscale as a container with `network_mode: host`. Full setup and flag-change recovery procedure in `references/tailscale-docker.md`.\\n\\n### Docker Pitfalls\\n\\n- `sudo env DOCKER_CONFIG=...` may be blocked by `/etc/sudoers` — use `sudo bash -c 'export DOCKER_CONFIG=... && docker compose ...'` instead\\n- Docker build blocked by tool policy (foreground timeout) — use `background=true` + `notify_on_complete=true`\\n- `docker compose up -d` alone reuses cached images; always `build --no-cache` when source files change\\n- Compose without `x-casaos` block registers as `v2app` but fails with \\\"Derzeit nicht unterstützt\\\"\\n\\n## Modifying Existing ZimaOS Apps\\n\\nWhen the user asks to add a feature to an existing app (e.g., MuslimOS, CallKeep, DailyDose), follow this workflow:\\n\\n### 1. Inspect thoroughly before touching anything\\n\\n```bash\\n# Find all app files\\nfind /DATA/AppData/ -maxdepth 4 -type f | head -80\\n# Read server, frontend HTML, CSS, JS completely\\n# Read the compose file for port/volume mapping\\n# Read the data file (db.json, sqlite) for schema\\n```\\n\\nUnderstand the full architecture: server language/framework, frontend patterns, data schema, CSS design system, event handling, API conventions. Do NOT start coding until you can explain how the existing tabs/features work.\\n\\n### 2. Write a detailed spec for the subagent\\n\\nThe spec must include:\\n- Exact file paths to modify\\n- Existing code patterns to follow (copy the style of existing features)\\n- Design system constraints (CSS variables, class names, color palette)\\n- API endpoint signatures matching existing conventions\\n- Data schema extensions\\n- Verification steps (API curl commands, browser checks)\\n\\n### 3. Delegate to kimi-k2.7-code\\n\\nUse `delegate_task` with the full spec. The subagent runs on the coding model. Your role is orchestration, not implementation.\\n\\n### 4. Verify and restart\\n\\n```bash\\n# Check the changes exist\\ngrep -n \\\"\\\" /DATA/AppData//app/server.js\\n# Restart the container\\nsudo docker restart \\n# Test API endpoints with curl\\ncurl -s http://localhost:/api/\\n# Confirm browser-visible changes\\n```\\n\\n### Renaming an Existing App (Dashboard Display Name)\\n\\n**CRITICAL: CasaOS identifies apps by `store_app_id`, NOT by `name:` or `container_name:`. Changing `store_app_id` breaks the app registration — the app disappears from the dashboard entirely. Only change the display title.**\\n\\nWhen the user wants to rename an app in the CasaOS dashboard (e.g., MuslimOS → EhliSünnet):\\n\\n1. **Change ONLY the display title and container_name** — do NOT touch `name:`, `services:` key, `networks:`, or `store_app_id:`:\\n - `container_name:` → new container name (cosmetic, Docker-level only)\\n - `x-casaos: title: custom:` → new display name (what shows in dashboard)\\n - Leave `name:`, `services:` key, `networks: default: name:`, and `store_app_id:` matching the original app directory name\\n\\n2. **Stop and remove the old container** before starting the new one:\\n ```bash\\n docker stop && docker rm \\n ```\\n\\n3. **Start with the updated compose**:\\n ```bash\\n DOCKER_CONFIG=/tmp/docker-config docker compose -f up -d\\n ```\\n\\n4. **Sync BOTH compose file locations** if the app has files in both `/DATA/AppData//casaos-compose.yml` AND `/var/lib/casaos/apps//docker-compose.yml`. Apply the same changes to both files.\\n\\n5. **Restart CasaOS app management** so the dashboard picks up the new title:\\n ```bash\\n sudo systemctl restart zimaos-app-management\\n ```\\n\\n**Pitfall:** If you skip step 2, the new container will fail with \\\"port is already allocated\\\" because the old container still holds the port. Always stop+rm the old container first.\\n\\n**Pitfall:** Changing `store_app_id` or `name:` to a different value than the app directory name causes the app to **disappear from the dashboard**. CasaOS uses `store_app_id` as the primary key to locate the app's compose file. If you break this link, the app becomes invisible.\\n\\n**Pitfall:** The CasaOS dashboard caches app names. If the old name still shows after restart, hard-refresh the browser (Ctrl+Shift+R).\\n- **Don't guess app structure.** Read the files first. Every app has its own conventions.\\n- **Port mapping matters.** The container port (e.g., 3000) ≠ host port (e.g., 8099). Test against the host port.\\n- **Container restart is required** after any server.js change. `docker restart`, not just file save.\\n- **Test DB may be created during verification.** Clean up temporary test data after confirming functionality.\\n\\n### Architecture\\n\\nBuild small, self-contained web apps that run on ZimaOS. Pattern: one Python file (FastAPI backend + static serving) + one HTML file (frontend). Accessible from any device on the local network. No Docker build step needed for dev; optional Dockerfile for production.\\n\\n### Design Rules\\n\\n**Primary (default) — Blue glass-morphism, system-aware theme:**\\n- System-aware light/dark via `@media (prefers-color-scheme: dark)`\\n- Blue palette: primary `#2563EB`, accent `#3B82F6`, dark accent `#1E3A5F`\\n- Light: `--bg: #F8FAFC`, `--card-glass: rgba(255,255,255,0.75)`\\n- Dark: `--bg: #0A0E1A`, `--card-glass: rgba(255,255,255,0.06)`\\n- Mobile-first, safe-area insets, bottom-sheet modals, 44px tap targets\\n- Smooth transitions: `cubic-bezier(0.25, 0.1, 0.25, 1)`\\n\\n**Alternative — Stripe Link warm editorial:**\\n- Warm off-white `#fdf5ef`, serif headlines (Lora), system UI font\\n- Accent blue `#00579F`, red `#EF4562`, green `#0E6245`\\n- Use when user explicitly requests warm/editorial/serif style\\n\\n### FastAPI Backend Template\\n\\nMount `StaticFiles` **AFTER** all API routes so endpoints take priority:\\n\\n```python\\nfrom pathlib import Path\\nfrom fastapi import FastAPI\\nfrom fastapi.staticfiles import StaticFiles\\n\\nFRONTEND_DIR = Path(__file__).parent / \\\"frontend\\\"\\napp = FastAPI()\\n\\n# API routes FIRST\\n@app.get(\\\"/api/stats\\\")\\ndef stats(): return {\\\"status\\\": \\\"ok\\\"}\\n\\n# Static files LAST\\nif FRONTEND_DIR.exists():\\n app.mount(\\\"/\\\", StaticFiles(directory=str(FRONTEND_DIR), html=True), name=\\\"frontend\\\")\\n\\nif __name__ == \\\"__main__\\\":\\n import uvicorn\\n uvicorn.run(app, host=\\\"0.0.0.0\\\", port=3001)\\n```\\n\\n### CasaOS Dashboard Integration\\n\\nTwo valid deployment patterns:\\n\\n**Pattern A: `container` type via `docker run` + `casaos.*` labels**\\n- Simplest to launch\\n- Auto-detected by `zimaos-app-management`\\n- NOT clickable in dashboard (missing routing fields)\\n- Only use for direct `http://:` access\\n\\n**Pattern B: `v2app` type via `x-casaos` compose file (RECOMMENDED)**\\n- Compose file in `/var/lib/casaos/apps//`\\n- Must include `x-casaos` top-level block with all routing fields\\n- Clickable tile in CasaOS dashboard immediately\\n- Survives reboots as managed app\\n\\nCritical fields in `x-casaos`:\\n- `hostname: \\\"\\\"` — empty string for universal LAN/VPN/remote access\\n- `icon: http://:/icon.svg` — cosmetic only\\n- `port_map`, `scheme: http`, `index: /`\\n- `store_app_id` must match directory name\\n\\nSee `references/casaos-dashboard-debugging.md` for complete \\\"Derzeit nicht unterstützt\\\" diagnosis and fix pipeline.\\n\\n### Common Pitfalls\\n\\n| Symptom | Cause | Fix |\\n|---|---|---|\\n| PermissionError on `/media/HDD_1TB/` | Root-owned mount | `sudo mkdir -p && sudo chown az-a:users ` |\\n| Frontend 404 | StaticFiles mounted before API routes | Move mount to END of file |\\n| \\\"Derzeit nicht unterstützt\\\" | Missing `x-casaos` or wrong `hostname` | See dashboard debugging reference |\\n| Blank page over VPN | `hostname` hardcoded to LAN IP | Set `hostname: \\\"\\\"` |\\n| Old UI after rebuild | Browser cache (iframe) | Hard refresh `Ctrl+Shift+R` |\\n| App shows as \\\"Legacy App\\\" | Used `docker run` instead of compose, OR `hostname` is a hardcoded IP (e.g. `172.29.0.1`) instead of `\\\"\\\"`, OR `icon` is a URL pointing to the container itself | Always `docker compose up -d` for managed apps. Set `hostname: \\\"\\\"` and use a base64 data-URL for the icon (see below). |\\n\\n## App Data Inspection (Live, Without Stopping)\\n\\nInspect persistent data, configurations, databases, and frontend assets from running CasaOS/ZimaOS apps.\\n\\n### Locating an App\\n\\n```bash\\n# Find compose and data directories\\nls -la /var/lib/casaos/apps//\\ncat /var/lib/casaos/apps//docker-compose.yml | grep -A2 \\\"volumes:\\\"\\n\\n# Find app code and data\\nfind /DATA/AppData/ -maxdepth 4 -type f 2>/dev/null | head -80\\nfind /DATA/AppData/ -name \\\"*.db\\\" -o -name \\\"*.sqlite\\\" -o -name \\\"*.json\\\" 2>/dev/null\\n```\\n\\nTypical paths:\\n- App code: `/DATA/AppData//app/`\\n- App data/DB: `/DATA/AppData//data/`\\n- Large user data: `/media/HDD_1TB//`\\n\\n### SQLite Inspection\\n\\n```bash\\n# Tables\\nsqlite3 /pfad/zur/app.db \\\"SELECT name FROM sqlite_master WHERE type='table';\\\"\\n# Last entries\\nsqlite3 /pfad/zur/app.db \\\"SELECT * FROM ORDER BY id DESC LIMIT 10;\\\"\\n```\\n\\n### JSON Configs\\n\\n```bash\\ncat /DATA/AppData//data/db.json | python -m json.tool\\n```\\n\\n### Frontend-Asset Mining\\n\\nMany custom ZimaOS apps (e.g., CallKeep, MuslimOS, DailyDose) pack logic in `/app/public/app.js`. Search for hardcoded lists and API endpoints:\\n\\n```bash\\ngrep -n \\\"const SUNNAH\\\\|const .*KEYS\\\\|const .*LIST\\\\|fetch(\\\" /DATA/AppData//app/public/app.js | head -30\\n```\\n\\nSee `references/callkeep-db-schema.md` and `references/muslimos-data.md` for example schemas of known apps.\\n\\n### Inspection Pitfalls\\n\\n- Compose files may be root-protected — use `sudo cat`\\n- Reading SQLite while running is safe; writes only when designed for it\\n- Data may live outside `/DATA/AppData/` — always check compose file volumes\\n- Dashboard name ≠ container name — search filesystem when `docker ps` doesn't match\\n\\n## Server Audit Workflow\\n\\nUse `references/server-audit-checklist.md` for a comprehensive audit covering SSH, network, system, Docker, HA, and security.\\n\\nQuick one-shot audit:\\n```bash\\nhostnamectl && cat /etc/os-release && uname -a && free -h && df -h\\nip -4 addr show | grep inet && ip route | grep default\\ndocker ps -a && docker version --format '{{.Server.Version}}'\\nss -tulpn | grep LISTEN\\n```\\n\\n## Support Files\\n\\n- `references/tailscale-docker.md` — Tailscale container setup and flag-change recovery\\n- `references/server-audit-checklist.md` — Full server audit checklist\\n- `references/casaos-dashboard-debugging.md` — Complete \\\"Derzeit nicht unterstützt\\\" diagnosis and fix\\n- `references/callkeep-db-schema.md` — Example SQLite schema for CallKeep app\\n- `references/muslimos-data.md` — Example data structure for MuslimOS app\\n- `references/callkeep-overdue-query.md` — Example overdue-call query for CallKeep\\n- `scripts/callkeep-overdue.py` — Script listing overdue/today calls from CallKeep DB\\n- `references/zeitgeist-architecture.md` — Zeitgeist app: file map, data schema, design system, header-stats pattern, modification checklist\\n\", \"path\": \"devops/zimaos-platform/SKILL.md\", \"skill_dir\": \"/DATA/.hermes/skills/devops/zimaos-platform\", \"linked_files\": {\"references\": [\"references/casaos-dashboard-debugging.md\", \"references/callkeep-db-schema.md\", \"references/callkeep-overdue-query.md\", \"references/zeitgeist-architecture.md\", \"references/muslimos-data.md\", \"references/fastapi-sqlite-basic-auth.md\", \"references/casaos-icon-base64.md\", \"references/server-audit-checklist.md\", \"references/tailscale-docker.md\"], \"scripts\": [\"scripts/callkeep-overdue.py\"]}, \"usage_hint\": \"To view linked files, call skill_view(name, file_path) where file_path is e.g. 'references/api.md' or 'assets/config.yaml'\", \"required_environment_variables\": [], \"required_commands\": [], \"missing_required_environment_variables\": [], \"missing_credential_files\": [], \"missing_required_commands\": [], \"setup_needed\": false, \"setup_skipped\": false, \"readiness_status\": \"available\", \"metadata\": {\"hermes\": {\"tags\": [\"zimaos\", \"casaos\", \"docker\", \"administration\", \"web-app\", \"fastapi\", \"deployment\", \"app-data\", \"inspection\"], \"related_skills\": [\"home-assistant\", \"openhue\"]}}}",
"tool_call_id": "pvzv4vx1"
},
{
"role": "assistant",
"content": "I have completed the consolidation pass for the 10 agent-created candidate skills. I have grouped them into four broad, class-level umbrellas, improving discoverability and reducing clutter while preserving all experiential knowledge, specialized scripts, and reference documents.\n\n### Consolidation Summary\n\n1. **Media & Creative Production** (Umbrella: `media-and-creative-production`)\n * Absorbed `media-file-management`, `ai-video-production`, and `music-resources`.\n * This umbrella now covers the entire lifecycle of media on ZimaOS: from library organization (movies, TV, music, eBooks) to automated content creation (AI video pipelines, YouTube automation) and resource retrieval (sheet music, audio analysis).\n * **Strategic Improvement**: Centralizes all `ffmpeg`, `yt-dlp`, and `edge-tts` knowledge which previously spanned three overlapping skills.\n\n2. **Smart Home & Maker Electronics** (Umbrella: `smart-home-and-maker`)\n * Absorbed `home-assistant` and `esp32-desk-dashboard`.\n * Combines high-level platform management (Home Assistant, Zigbee, Tuya) with low-level hardware development (ESP32, LVGL, BLE).\n * **Strategic Improvement**: Connects the \"software\" side of smart homes with the \"hardware\" side of custom dashboards, providing a unified path for IoT development.\n\n3. **Software Product Engineering** (Umbrella: `software-product-engineering`)\n * Absorbed `technical-product-spec` and `zeitgeist-app-development`.\n * Unifies product design standards (Stripe/Cloudflare-style specs) with specialized application patterns (single-file HTML/JS app development).\n * **Strategic Improvement**: Grouping \"the spec\" with \"the implementation\" under one class-level skill for software lifecycle management.\n\n4. **Research & Utility Operations** (Umbrella: `research-and-utility-ops`)\n * Absorbed `reddit`, `local-server-public-access`, and `pdf-generation`.\n * Groups essential operational utilities: data sourcing/scraping (Reddit), network exposure (tunnels), and document production (PDFs).\n * **Strategic Improvement**: Consolidates diverse \"utility\" skills that are often used together in complex research or deployment workflows.\n\n## Structured summary (required)\n```yaml\nconsolidations:\n - from: ai-video-production\n into: media-and-creative-production\n reason: Merged into a class-level media production umbrella covering automated video pipelines.\n - from: music-resources\n into: media-and-creative-production\n reason: Absorbed into media umbrella as a specialized subsection for audio analysis and resource sourcing.\n - from: media-file-management\n into: media-and-creative-production\n reason: Elevated to a broader umbrella class to house all media organization and production content.\n - from: home-assistant\n into: smart-home-and-maker\n reason: Merged with hardware development into a unified smart home and electronics class.\n - from: esp32-desk-dashboard\n into: smart-home-and-maker\n reason: Absorbed as the maker-electronics component of the smart home umbrella.\n - from: technical-product-spec\n into: software-product-engineering\n reason: Consolidated into a broader software engineering class covering product design and specs.\n - from: zeitgeist-app-development\n into: software-product-engineering\n reason: Merged into software engineering as a specialized application development pattern.\n - from: reddit\n into: research-and-utility-ops\n reason: Grouped with other data retrieval and utility operations for better discoverability.\n - from: local-server-public-access\n into: research-and-utility-ops\n reason: Consolidated as a network utility under the research and operations umbrella.\n - from: pdf-generation\n into: research-and-utility-ops\n reason: Merged as a document utility into the broader operations class.\nprunings: []\n```",
"reasoning": "**Identifying Origin**\n\nI've made a crucial discovery: the `zimaos-platform` wasn't on the candidate list and is definitively agent-generated. The \"Hermes Agent,\" `/DATA/.hermes/`, and specific apps confirm this. This strongly suggests a unique and potentially unauthorized origin.\n\n\n**Consolidating Candidates**\n\nI'm consolidating the final candidates. After analyzing the list, I've confirmed that I have processed all ten candidates provided. My initial instinct to merge `zeitgeist-app-development` with `zimaos-platform` was incorrect; the platform wasn't on the approved list, and I am to focus only on agent-created skills. I've completed the last merge and archive passes.\n\n\n",
"finish_reason": "stop",
"reasoning_content": "**Identifying Origin**\n\nI've made a crucial discovery: the `zimaos-platform` wasn't on the candidate list and is definitively agent-generated. The \"Hermes Agent,\" `/DATA/.hermes/`, and specific apps confirm this. This strongly suggests a unique and potentially unauthorized origin.\n\n\n**Consolidating Candidates**\n\nI'm consolidating the final candidates. After analyzing the list, I've confirmed that I have processed all ten candidates provided. My initial instinct to merge `zeitgeist-app-development` with `zimaos-platform` was incorrect; the platform wasn't on the approved list, and I am to focus only on agent-created skills. I've completed the last merge and archive passes.\n\n\n"
}
]
}