Add Response Format header to search skill

6184fe5·

alishakawaguchi·3mo ago·1 file·+11 added/-0 removed

Sessions

3fc8a587fcc7View transcript

[?
/superpowers:brainstorming for the skills how hard would it be to add the marvin logo in ascii art orClaude Code·Opus 4.7[1m]·2 steps](/content/gh/entireio/skills/session/35ea950f-b370-4441-934d-e6a994c53fd3#timeline-3fc8a587fcc7/index.html)

Changes

1

• plugins/entire/skills/search

• MSKILL.md+11

5 unmodified lines

6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22

5 unmodified lines

Use `entire search` to find relevant checkpoints before guessing from memory.

## Response Format

Begin the first response to this skill invocation with the line:

`Entire Search:`

followed by a blank line, then the content.

- Apply the header to the **first response of the invocation only.** Do not re-print it on follow-up turns within the same invocation (e.g. after the user answers a clarifying question).
- Do **not** include the header on error or early-exit responses (e.g. "Entire CLI not installed", "authentication required", "no matches"). The header's presence should signal that the skill ran and produced real output.

## When to Use

- The user asks things like "have we done this before?", "search past work", "find the previous implementation", or "look for checkpoints about X"
``