Skip to content
Agentmart
Submit a tool

recall

In an lstack learning vault (a folder containing lstack.yaml), run a free-recall test where the user writes everything they remember about one node before any…

Skill by sscw32

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/sscw32-recall

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

In an lstack learning vault (a folder containing lstack.yaml), run a free-recall test where the user writes everything they remember about one node before any comparison. Use for "/recall", "let me brain-dump kernel", "free recall on X", "I'll write what I remember". Skip when the folder has no lstack.yaml, when the user wants questions asked (/quiz), or when "recall" refers to memory in code or a product recall.

Use cases: testing, writing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/recall

What's inside

Skill name
recall
Description
In an lstack learning vault (a folder containing lstack.yaml), run a free-recall test where the user writes everything they remember about one node before any comparison. Use for "/recall", "let me brain-dump kernel", "free recall on X", "I'll write what I remember". Skip when the folder has no lstack.yaml, when the user wants questions asked (/quiz), or when "recall" refers to memory in code or a product recall.
License
MIT
Instructions
55 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • openai.yaml · agents/

SKILL.md (first lines)

# Recall

Free recall, uninterrupted, then a hit-and-miss comparison and a scored result.

## Preconditions

Confirm `lstack.yaml` exists in the working directory or a parent. If not, say this isn't a vault and suggest `/setup-vault`. Read `MISSION.md`, `kb/today.md`, and the newest file in `log/`. Open with one line on where the user is.

## Argument

The text after the skill name in the user's message is a node id. If there is none, ask.

## Steps

1. Say: "Write everything you remember about <title>. Don't look anything up. Say done when finished." Then say nothing until the user says done. Do not prompt, do not hint, do not react to partial text.
2. Ask "confidence 1-4?" and wait.
3. Read the node's Summary, Terms, and Cards. Compare. List, one line each:
   - **Hit**: key points they stated correctly.
   - **Missed**: key points in the node they did not mention.
   - **Wrong**: statements that contradict the node or its sources, with the correction. Never let a wrong statement pass, even under pushback.
4. Score (below). Preview the node edit. Wait for yes. Write.
5. Offer to add each missed item as a card, previewed as `+` lines under `## Cards`. Yes writes them.
6. Run `node .lstack/lstack.mjs build`, then `node .lstack/lstack.mjs lint`. Report one line. If `lstack.yaml` says `node_available: false`, rebuild `kb/index.md` and `kb/today.md` by hand and say so. Offer `/wrap-up`.

## Scoring (from `lstack.yaml` `scheduling` and `.lstack/node-schema.md`)

- Result: `hit / (hit + missed)` over the Summary's key points, written as `n/m`. Any Wrong item counts against a hit. Pass when `n/m >= pass_threshold`.
- Delayed: `today - max(last_studied, last_tested) >= delayed_min_days`. Only a delayed test moves `status`. If not delayed, write `last_tested`, `last_result`, and `sessions` only, and say: "Recorded, but this doesn't count toward status because you studied it today."
- Delayed PASS: `passes_in_a_row += 1`; `next_review = today + ladder_days[min(passes_in_a_row, len - 1)]`; `learning → reviewing`; `reviewing → mastered` once `passes_in_a_row >= mastered_after_passes`.
- Delayed FAIL: `passes_in_a_row = 0`; `next_review = today + ladder_days[0]`; `status` drops one step.
- Record the stated confidence. Always: `last_tested = today`, `last_result = n/m`, append today to `sessions`.

## Preview format

```
### Proposed write: kb/vector-spaces/basis.md
**Frontmatter**
- status: learning → reviewing
- confidence: 2 → 3
- last_tested: null → 2026-09-15
- last_result: null → 4/5
- passes_in_a_row: 0 → 1
- next_review: null → 2026-09-18   (delayed pass; ladder_days[1] = +3 days)
- sessions: [2026-09-08] → [2026-09-08, 2026-09-15]
```

Reply **yes** to write, **no** to skip, or name what to change.

## Rules

- Praise the work, not the person.
- Never write into `sources/`, `notes/`, or `problems/attempts/`. Never edit generated files.
- No hooks, no sub-agents, no argument substitution.

From sscw32/lstack, MIT.

More from sscw32/lstack

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Sep 15, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from sscw32

Cite this page

recall skill. Agent Mart. https://agentmart.dev/skills/sscw32-recall (last updated 2026-10-24)