Results for “handle”

Use when a val sends email, receives email, or is triggered by an incoming email. Covers email-type vals (the Email handler shape, attachment limits, the assigned val email address) and sending mail via std/email.

Use when a val sends email, receives email, or is triggered by an incoming email. Covers email-type vals (the Email handler shape, attachment limits, the assigned val email address) and sending mail via std/email.

Generates a clipboard-ready handoff prompt for another AI agent to investigate or continue a task, with structured context and review instructions.

Writes or updates a HANDOFF.md file in the project root to capture goal, progress, and next steps for a fresh agent to continue in-progress work.

Controls Philips Hue lights and scenes through a Hue Bridge using the OpenHue CLI, including discovery, setup, and light management commands.

Compact the current conversation into a handoff document for another agent to pick up, including suggested skills and references to existing artifacts.

Compacts the current conversation into a handoff document for another agent to pick up, referencing existing artifacts by path or URL instead of duplicating them.

Compacts the current conversation into a handoff document for another agent to continue the work, saving it to the OS temporary directory.

CEO/Dispatcher. Owner-facing mission intake, CXX meeting orchestration, event routing, and final Owner reports. Trigger with /goal, /submission, /hot-fix, /ceo.

Writes or updates a HANDOFF.md document to preserve context for the next agent, including goal, progress, what worked, what didn't, and next steps.

Manage Remember The Milk tasks — list, add, complete, delete, search, prioritize, tag, move, and annotate tasks.

Names content by three coordinates: millisecond timestamp, SHA-256 hash, and optional human petname. Verifies content integrity, timestamps events, and maintains a local content store searchable by time, hash, or human words.

Use when creating or editing a macOS LaunchAgent for a recurring or scheduled script. Covers plist structure, PATH resolution, multiple trigger times, the reload workflow, and which behaviors launchd already handles so they don't need to be rebuilt.

Moderate ClawHub platform resources including skills, users, org publishers, plugin packages, and staff email using the repo-local admin CLI tool.

Master the AI tools that handle administrative work and boost personal productivity. From meeting notes to email management, get more done with less effort. Use when "meeting notes, email management, calendar optimization, productivity, time management, productivity, meetings, email, calendar, personal" mentioned.

Write WeChat public account long-form articles in the distinctive style of Khazix, a known AI content creator. Handles various input formats (PDF, links, notes) and guides the user through a structured writing process from material understanding to final polish.

Work ZenTao bugs/tasks end to end, manage task lifecycle and hours, or read a linked story as development context: fetch details, handle the user's request, verify changes, and ask before committing or writing back to ZenTao. Supports single items and sequential batches. Use when the user references ZenTao (禅道) bugs, tasks, stories, requirements, task status, or task hours.

Score, evaluate, and iteratively improve any content or strategy using an auto-assembled panel of domain experts. Handles copy, sequences, landing pages, strategy docs, titles, charts, recruiting evaluations, or anything else that needs a quality gate. Recursively iterates until all scores hit 90+ (max 3 rounds). Use when asked to: "expert panel this", "score this", "rate these variants", "quality check this", "panel review", "which version is better", "expert score", "evaluate this copy/strategy/page", or when another skill needs a quality gate on its output. Also triggers on: "score this landing page", "expert panel these email variants", "rate this headline", "panel these charts".

Local CLI issue tracker for todos, follow-ups, structured records, and the canonical pattern for decomposing multi-step work into a parent + subissues with acceptance criteria, dependency edges, and priority. Use when the user mentions a task to remember, a bug to track, an open question, anything that needs to outlive the current turn, or when planning multi-heartbeat work that needs `chainlink issue ready`-driven pickup across sessions. Includes guidance on writing descriptions future-you can act on (handles, success path, failure path) and idempotency tactics for actions that might fire twice (boundary firing, overlapping heartbeats, retried subagent completion). Pairs with five-whys (chainlink is the storage backend for RCA trees). Storage is local — issues live under a `.chainlink/` directory in the operator's repo.