Add Entire header to skill responses (#1) · Entire

Add Entire header to skill responses (#1)

667da6d→main·

alishakawaguchi·3mo ago·3 files·+33 added/-0 removed

* Add Response Format header to search skill

* Add Response Format header to explain skill

* Add Response Format header to session-handoff skill

Sessions

aed3151dbcc5View transcript

bc9922db4c84View transcript

3fc8a587fcc7View transcript

Changes

3

10 unmodified lines

11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

10 unmodified lines

- **Files** — What's the purpose of this file? What requirements drove its creation?
- **Line changes** — Why was this specific line added or modified?

## Response Format

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

`Entire Explain:`

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 is required but not installed", "this file is not tracked by git", "no session transcript was found for this commit"). The header's presence should signal that the skill ran and produced real output.

## Process

1. Verify the `entire` CLI is installed by running `entire version`.

Mplugins/entire/skills/explain/SKILL.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"

Mplugins/entire/skills/search/SKILL.md+11


3 unmodified lines

4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

3 unmodified lines

# Hand-Off Session

## Response Format

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

`Entire Session Handoff:`

followed by a blank line, then the content. The header applies to the full compaction-summary flow, including the "Unanswered Question" branch (which is still a successful run — the skill summarized the transcript and surfaced the question).

- 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 the surfaced unanswered question).
- Do **not** include the header on error or early-exit responses (e.g. no `.git/entire-sessions/` directory, no sessions found after filtering, transcript file missing at the path the session JSON points to). The header's presence should signal that the skill ran and produced real output.