stub_ok

Echo input queries as deterministic Evidence objects with metadata.

40|6|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/0xmariowu/Autosearch --skill stub-ok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stub_ok
Source: https://github.com/0xmariowu/Autosearch/tree/main/tests/fixtures/skills/channels/stub_ok
Command: npx skills add https://github.com/0xmariowu/Autosearch --skill stub-ok

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires autosearch, and includes scripts (resource) components.

What problem does it solve?

The stub channel provides a simple, always-available echo method to simulate a real channel during development and testing.

Core Features & Use Cases

  • Deterministic echo responses for given queries to validate end-to-end wiring.
  • Lightweight, dependency-free behavior ideal for local testing and demos.
  • Use Case: verify channel integration by sending a query and inspecting the echoed result.

Quick Start

Provide an input query and observe the deterministic echo response.

Frequently Asked Questions about stub_ok

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

FAQPage Schema
How do I test channel wiring with a deterministic echo response?

A stub channel provides a lightweight, always-available echo method that simulates a real channel by returning deterministic in-context replicas of input queries, making it ideal for local testing and development demos.

How do I get deterministic search results for a development demo?

To get deterministic search results for a development demo, call the async search(query) function to receive a stable list of Evidence objects replicating your input, ensuring consistent behavior during teaching scenarios and integration validation.

Do I need any external dependencies to use this echo channel for testing?

The stub channel relies on the autosearch dependency to function within the broader environment, requiring you to configure an async search interface that accepts a query string and returns a list of Evidence objects for successful integration.

What fields are included in the Evidence objects returned by the echo channel?

The Evidence objects returned by the echo channel include url, title, snippet, source_channel, and a fetched_at timestamp, providing a complete deterministic replica of the input query for validating your channel integration.

Can I use this stub channel to simulate a real search channel during local testing?

Use this stub channel to simulate a real search channel during local testing by sending a query and inspecting the echoed result, which returns a deterministic in-context replica of the input for validating channel integration.

Why use a stub channel instead of a live search channel for integration testing?

You use a stub channel instead of a live search channel for integration testing to eliminate external network variability, providing a dependency-free, deterministic echo that ensures stable and predictable validation of your channel wiring.