Results for “tool-invocation”

Recommends the best skill, agent, or command for a given task by classifying intent and scanning available tools.

Invoke a registered skill from the current skill listing. BLOCKING REQUIREMENT: when a skill from the listing matches the user's request, you MUST call this tool (not free-form text). Do not re-invoke a skill to repeat work already done: if a `<skill-loaded>` block for it with the same `args` is already present in the conversation, follow those instructions directly instead of calling the tool again. Do call the tool again when you need the skill with different arguments — the loaded block was expanded with the earlier `args` and will not reflect new inputs.

Identify the right tool for a process step. Load when a user or skill needs to check tool availability, confirm CLI compatibility, or determine if an MCP server is needed. Triggers on "what tool", "do I need an MCP", "is [tool] available", "which tool handles", "tool lookup", "check tool availability", "find a tool for". Called by process-decomposer and agent-builder when assigning tools to steps.

Creates or modifies agent tools for OpenAI Agents SDK, covering search, analysis, API integration, and database query patterns with caching and metrics.

Derive a portable product-idea kickoff prompt from the invoking repository for use with $idea-scope-brief in a different repository. Use when a repo suggests an adjacent product, SaaS, devtool, library, workflow, or experiment worth briefing elsewhere, but the user wants an idea prompt rather than code extraction or repo creation.

Proposes exactly one personal side-project idea per invocation, sized to a 1-3 day MVP. Targets CLI, automation, LLM, DX, productivity, and data-viz angles; avoids clichés like TODO apps, weather apps, and pomodoro timers. Output is an 8-section brief including a ready-to-paste coding-agent prompt. Use for morning/daily idea rituals and weekend-hack ideation. Don't use for existing-product feature proposals (Spark), dialogue brainstorming (Riff), or prototype implementation (Forge).

Selects session runtime capabilities when tools or external evidence are required. Do not use for ordinary local repository work.

Design tool descriptions, schemas, and response formats that agents can reliably route on, including MCP server design, tool-set consolidation, and naming conventions.

Add plugin tools, connect MCP servers, or chain existing tools in one script within the LaRuche agent environment.

Route a task description to the right processkit skill, project-specific process override, and MCP tool in a single deterministic call — use this at the start of every processkit domain task.

Reviews a plan from a prior session by extracting the canonical reference prompt from seed/plan-reviewer-design.md and invoking the plan-reviewer agent with it, surfacing the verdict without auto-applying changes.

Turn an app idea into a precise build prompt for an AI app builder (Lovable, v0, Bolt, Replit, and others). Trigger on "build me an app", "prompt for Lovable", "v0 prompt", "vibecode this", "I want to build a tool that", "prompt to build a web app", or any request to spin up an app with an AI builder.

Integrate services or agent harnesses with the 33GOD Bloodbank event bus. Covers schemas in Bloodbank schemas/ and docs/event-naming.md, producing events (NATS preferred; Dapr, HTTP /publish, hookd_bridge alternatives), consuming events (NATS, Dapr, FastStream, event-toaster), and agent hook wiring through the canonical services/agent-hooks publisher. Use for event publish/consume, authoring schemas, integrating harnesses (Claude Code, Copilot CLI, OpenCode, Cursor, Aider, Codex CLI, Hermes), or debugging missing envelopes. Triggers: bloodbank, event bus, publish, subscribe, NATS subject, holyfields legacy, CloudEvents, event-toaster, ntfy.delo.sh/bloodbank, bloodbank.v1.agent.session.started, bloodbank.v1.agent.tool.completed, bloodbank.cmd.v1.agent.invocation.start. Skip for generic brokers, n8n, hindsight memory, or non-event-bus 33GOD.