clawperator-skill-author-by-agent-discovery

Route unmatched host requests through bounded discovery to emit one JSON artifact.

2|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/clawperator/clawperator --skill clawperator-skill-author-by-agent-discovery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clawperator-skill-author-by-agent-discovery
Source: https://github.com/clawperator/clawperator/tree/main/apps/node/bundled-skills/clawperator-skill-author-by-agent-discovery
Command: npx skills add https://github.com/clawperator/clawperator --skill clawperator-skill-author-by-agent-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route no-match host requests through bounded discovery to determine a single, truthful next step, ensuring predictable and auditable outcomes.

Core Features & Use Cases

  • Bounded discovery: limits snapshots, screenshots, and wall time to keep latency predictable.
  • One-shot decision: outputs exactly one recommended next step and a structured discovery artifact.
  • Safe routing: checks for existing runtime skills first and defers to recording or escalation only when appropriate.

Quick Start

Invoke the bounded discovery flow to produce a single JSON discovery artifact.

Frequently Asked Questions about clawperator-skill-author-by-agent-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route no-match host requests when no installed runtime skill matches?▼

Bounded discovery routes no-match host requests by running a limited discovery pass to determine a single, truthful next step. It checks installed skills first and outputs exactly one recommended action.

What is bounded discovery and how does it handle unmatched requests?▼

Bounded discovery limits snapshots, screenshots, and wall time to keep latency predictable while evaluating unmatched requests. It produces a single structured discovery artifact with one recommended next step.

How do I generate a discovery artifact for a no-match request?▼

Invoke the bounded discovery flow to produce a single JSON discovery artifact. This artifact records the evaluated outcome and recommends whether to record, escalate, decline, or hand off the request.

Can bounded discovery enforce latency limits on no-match request routing?▼

Bounded discovery enforces discovery budget limits by constraining snapshots, screenshots, and wall time. This ensures predictable latency and a single auditable outcome for every no-match request.

When should I use bounded discovery instead of directly recording a no-match request?▼

Use bounded discovery when no installed runtime skill matches and you need a truthful next step. It only routes to recording when appropriate, first checking existing skills and enforcing a single discovery pass.

Why does bounded discovery output only one recommended next step?▼

Bounded discovery outputs exactly one recommended next step to ensure predictable and auditable outcomes. This one-shot decision prevents ambiguous routing and emits a single structured discovery artifact.