Senso Search for ClawMax

This skill wraps the upstream senso-search workflow with ClawMax result formatting so agents can turn retrieval into actions quickly.

Use This Skill For

• finding prior incidents before triage
• grounding a current bug or customer case in verified evidence
• discovering which content IDs are relevant
• producing a compact cited handoff for another agent

Prerequisites

• SENSO_API_KEY is set
• senso CLI is installed
• always use --output json --quiet

Search Mode Selection

Choose the mode intentionally.

Use full search when:

• the next step needs a direct grounded answer
• you want both an answer and source chunks

senso search "<query>" --output json --quiet

Use context search when:

• you want raw chunks for your own synthesis
• you are handing evidence to another agent

senso search context "<query>" --output json --quiet

Use content search when:

• you need to discover relevant documents first
• you want content IDs before deeper retrieval

senso search content "<query>" --output json --quiet

ClawMax Query Pattern

Queries should combine:

• template or workflow subject
• concrete symptom or evidence phrase
• optional entity or artifact type

Examples:

• checkout modal overlap mobile screenshot
• customer refund transcript duplicate charge
• retail shelf stockout beverage aisle

Preferred Result Shape

Always convert results into a compact workflow-ready structure:

1. Answer One short grounded conclusion if available.
2. Top Evidence 1-3 bullets with title, content ID, and why it matters.
3. Confidence high / medium / low based on evidence quality and consistency.
4. Recommended Next Step what the next agent or workflow should do.

Required Handoff Output

Format results like this:

Answer:
- The strongest evidence suggests the issue is a mobile layout overlap in the checkout modal.

Top Evidence:
- Checkout QA Notes (cnt_123): mentions CTA overlap on 390px width
- Mobile Regression Screenshot Set (cnt_456): visually confirms footer/button collision

Confidence:
- high

Recommended Next Step:
- route to fix-coordinator with content IDs cnt_123 and cnt_456

Scoping Rules

If you already know relevant content IDs, prefer scoped search:

senso search "<query>" --content-ids <id1> <id2> --require-scoped-ids --output json --quiet

Use this whenever:

• the current workflow already ingested the relevant evidence
• you want to avoid unrelated results
• you are revisiting a known case or folder

Follow-Up Retrieval

If a result looks relevant but you need the full item:

senso content get <content_id> --output json --quiet

Use that before making strong claims from a single chunk.

Anti-Patterns

• do not dump raw JSON at the next agent unless explicitly needed
• do not use broad unscoped search when current content IDs are already known
• do not present an answer without citing titles and content IDs
• do not claim high confidence if the top evidence conflicts