recall

Use when Kris asks to catch up, recall work on a topic, resume stale work, find where he left off, or reconstruct current state from prior sessions.

Skill by kristofferremback

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/kristofferremback-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.

About

Use when Kris asks to catch up, recall work on a topic, resume stale work, find where he left off, or reconstruct current state from prior sessions.

Reviews

Write a review

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: Use when Kris asks to catch up, recall work on a topic, resume stale work, find where he left off, or reconstruct current state from prior sessions.
License: MIT
Instructions: 20 lines in SKILL.md · view on GitHub

Files (3)

LICENSE
NOTICE.md
SKILL.md

SKILL.md (first lines)

# Recall

Rebuild missing or stale working context. `handover` preserves known state forward; `recall` reconstructs it later.

1. Fix the workspace, topic, and time window. Default to the active workspace and a recent bounded window. Never search another workspace without being asked.
2. Search relevant harness transcripts and Threa records. Fan out bulk reading when useful, but keep raw transcripts out of the main context.
3. For a named feature, bug, or subsystem, use `why` to search relevant shared history for prior attempts, user reports, incidents, and decisions.
4. Verify historical claims against live git branches, PRs, tickets, checks, and deployed state. A transcript is history, not truth.
5. Stop when the named topic has enough current state to act. Exclude adjacent work unless it blocks this thread.

Return:

- **Capsule:** at most five bullets
- **Threads:** one status-tagged line per active, merged, reverted, planned, or uncommitted thread
- **Problems:** at most five recurring failures or unresolved risks
- **Next move:** the single most useful concrete action

Use direct links and mark evidence, inference, and gaps.

From kristofferremback/slopestyle, MIT.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Aug 19, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/kristofferremback/slopestyle
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from kristofferremback

Cite this page

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