Add Response Format header to explain skill

1f14551·

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

Sessions

bc9922db4c84View transcript

Changes

1

• plugins/entire/skills/explain

• MSKILL.md+11

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