Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cwinvestments/report
Writes the session final report to a file, then prints only the path and a one-line summary. Fires when the prompt contains "Report per memstack:report", and also when the prompt begins with a standing trigger configured through MEMSTACK_REPORT_ON_TASK_PROMPTS or MEMSTACK_REPORT_TRIGGERS. Dormant otherwise.
Passed 4 of 12 test cases with the skill, and 2 of 12 without it.
and 3 more in the full report
5 fixed2 passed either way14 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
With `MEMSTACK_REPORT_TRIGGERS` set to `Task:`, the user inputs prompt: `Task: fix bug` (13 characters). Does this prompt trigger session report filing?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies that prefix triggers are dormant for prompts under 40 characters. | Missed | Passed |
The instructions your model reads when the skill loads.
The session states what it did, in a file, once, at the end.
Output Report: writing the session report..., then follow the rules below.
| Context | Status | Priority |
|---|---|---|
| The prompt contains "Report per memstack:report" | ACTIVE, write the file before finishing | P1 |
| The prompt's first non-blank line starts with a configured trigger | ACTIVE, same requirement | P1 |
| The prompt matched a prefix trigger, but is under 40 characters | DORMANT, see the floor below | n/a |
| The prompt asks for a summary, a recap or a status line | DORMANT, answer in the terminal, no file | n/a |
| A long session ends and nobody asked for a report | DORMANT, an unrequested file is litter | n/a |
| The prompt asks for a diary or a handoff | DORMANT, that is Diary and Project, not this | n/a |
The phrase always arms, on every install, with nothing configured. It is a phrase rather than a keyword because "report" appears in ordinary prose constantly.
Two environment variables add standing triggers on top of it. Both are unset by default, so a shipped install arms on the phrase and on nothing else.
| Variable | Effect |
|---|---|
MEMSTACK_REPORT_ON_TASK_PROMPTS | Set to 1, arms any prompt whose first non-blank line starts with Working directory:. Any other value, including 0, changes nothing. |
MEMSTACK_REPORT_TRIGGERS | Extra prefixes, semicolon separated, each matched against the first non-blank line. Surrounding spaces are trimmed, so Task briefing:; Ticket: configures two. |
Working directory: is separated out rather than left to the general list
because it is the opening line of a dispatched task prompt, which is the shape
this was built for, and because arming on it by default would file a report for
a large share of every prompt anyone writes.
When either variable is configured, the SessionStart hook injects one sentence saying so. That sentence is the only announcement: a prompt carrying the phrase announces the requirement itself, so a default install is told nothing and pays
test cases passed, vs 2 / 12 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.