zylos-ai
- 20 skills
- 0 followers
- 7 hours ago last updated
- ▌ Dashboard · zylos-ai bundleRead-only Zylos observability dashboard for agent state, costs, tools, communication, scheduler, and PM2 service health. Full features on Claude runtime. PM2, system health, communication, and scheduler monitoring on all runtimes.
- ▌ Doccraft · zylos-ai bundleTurn a document (research doc, architecture proposal, 方案文档, report, decision memo) into a beautiful, human-friendly standalone HTML page — conclusion-first information architecture, diagrams, status boards, progressive disclosure, dual theme, mobile-ready. Use when asked for a "可视化版", "美观易懂的版本", "HTML 版", "visual version", "做成网页", "readable version", or when delivering a long/dense document to a human reader who needs to grasp it quickly without losing detail.
- ▌ Lark Group Digest · zylos-ai bundleGenerate Lark group message digest (configurable schedule, default 3x daily). Fetches messages via digest.mjs, summarizes in Chinese, writes to pages, notifies the configured owner via Lark DM. Use when receiving a lark-group-digest scheduled task.
- ▌ Lark · zylos-ai bundleLark (international) communication channel. For Feishu (飞书, China) use the separate feishu component instead. Use when: (1) replying to Lark messages (DM or group @mentions), (2) sending proactive messages or media (images, files) to Lark users or groups, (3) managing DM access control (dmPolicy: open/allowlist/owner, dmAllowFrom list), (4) managing group access control (groupPolicy, per-group allowFrom, smart/mention modes), (5) operating Lark productivity surfaces via the bundled lark-cli — documents, sheets, slides, multidim Base, calendar, tasks, mail, drive, wiki, OKR, approval, attendance, video conferencing, minutes, Miaoda/Spark apps, native OpenAPI explorer (see "Bundled Capability Modules" in SKILL.md body — full module index under references/), (6) configuring the bot (admin CLI, markdown card settings, verification token), (7) troubleshooting Lark webhook or service issues. Config at ~/zylos/components/lark/config.json. Service: pm2 zylos-lark.
- ▌ Pages · zylos-ai bundleRegistered Markdown, HTML, and downloadable file pages for zylos. Use for styled documents or when a local file should be exposed as a safe attachment page. Agents register the source with the pages CLI and report the internal URL; files are served only after registration.
- ▌ Whatsapp · zylos-ai bundleWhatsApp communication channel via WhatsApp Web protocol (QR code login). Use when: (1) replying to WhatsApp messages (DM or group), (2) sending proactive messages or media (images, files) to WhatsApp users or groups, (3) managing DM access control (dmPolicy: open/allowlist/owner, dmAllowFrom list), (4) managing group access control (groupPolicy, per-group allowFrom), (5) configuring the bot (admin CLI, access policies), (6) troubleshooting WhatsApp connection or QR code scanning issues. Config at ~/zylos/components/whatsapp/config.json. Service: pm2 zylos-whatsapp.
- ▌ HTTP · zylos-ai bundleCaddy-based web server providing web console hosting, file sharing, and health check endpoints. Use when configuring HTTP access, setting up file sharing, or troubleshooting web connectivity.
- ▌ Shell · zylos-ai bundleCLI interactive mode channel. Delivers Claude responses to the zylos shell REPL via Unix socket.
- ▌ Scheduler · zylos-ai bundleUse when user wants to schedule tasks for future, recurring, or interval execution. Manages one-time, cron, and interval tasks dispatched via C4 comm-bridge.
- ▌ Comm Bridge · zylos-ai bundleC4 communication bridge — central gateway for ALL external communication (Telegram, Lark, etc.). Use when replying to users via the "reply via" path, sending proactive messages to external channels, querying recent conversations or checkpoint status (prefer c4-db.js CLI; sqlite3 OK for unsupported queries), fetching conversation history for Memory Sync, or creating checkpoints after sync. Incoming messages are queued by channel bots and delivered to Claude via a PM2 dispatcher daemon. Session-start hooks automatically provide conversation context and can trigger Memory Sync when unsummarized conversations exceed the configured threshold.
- ▌ New Session · zylos-aiStart a new session when context is high. Claude uses /clear, Codex uses /exit. Use when context is high or when a fresh session is needed.
- ▌ Web Console · zylos-ai bundleBuilt-in web interface for communicating with Claude without external services. Use when setting up or configuring the web console channel, or troubleshooting browser-based access.
- ▌ Create Skill · zylos-ai bundleGuide for creating effective skills. Use when asked to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
- ▌ Health Check · zylos-ai bundleSystem health check dispatched by the activity monitor via Control queue. Checks PM2 services, disk space, and memory usage. Use when receiving a control message containing "health-check".
- ▌ Zylos Memory · zylos-ai bundleCore memory system. Maintains persistent memory across sessions via tiered markdown files following the Inside Out model. Handles Memory Sync (processing conversations into structured memory), session rotation, consolidation, and context-aware state saving. Must be launched via a runtime-appropriate background subagent mechanism — do not invoke with the Skill tool.
- ▌ Check Context · zylos-ai bundleAccurately check current context window and token usage. Use when the user asks about context usage, token consumption, or when monitoring context levels.
- ▌ Restart Claude · zylos-ai bundleUse when the user asks to restart Claude Code, or after changing settings/hooks/keybindings.
- ▌ Upgrade Claude · zylos-ai bundleUpgrade Claude Code to the latest version with graceful shutdown and auto-restart. Use when the user asks to upgrade or when a new Claude Code version is available.
- ▌ Activity Monitor · zylos-ai bundleGuardian service that monitors the active runtime agent's state and automatically restarts it if stopped. Use when checking agent liveness state or understanding the auto-restart mechanism.
- ▌ Component Management · zylos-ai bundleGuidelines for managing zylos components via CLI and C4 channels. Use when installing, upgrading, or uninstalling components, or when user asks about available components.