anortham/recall
skills/recall/SKILL.md
Use when starting a new session, after context loss, searching for prior work, or when the user asks what happened previously and needs Goldfish memory restored
$ install --global
skillsauthnpx skillsauth add anortham/goldfish recallInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 4, 2026, 4:13 AM199.6s1 file scanned
SKILL.md
- name:
- recall
- description:
- Use when starting a new session, after context loss, searching for prior work, or when the user asks what happened previously and needs Goldfish memory restored
- allowed-tools:
- mcp__goldfish__recall, mcp__goldfish__brief
Recall
When To Use
Call recall at session start, after compaction, or when you need prior work, decisions, or cross-project context.
mcp__goldfish__recall({})
Common Cases
- New session:
recall() - Recent work only:
recall({ since: "2h" }) - Wider history:
recall({ days: 7, limit: 20 }) - Search:
recall({ search: "auth refactor", full: true }) - Past decisions:
recall({ type: "decision" }) - By tags (AND):
recall({ tags: ["db", "ops"] }) - Cross-project scan:
recall({ workspace: "all", days: 1 }) - Brief only:
recall({ limit: 0 })
type keeps one of checkpoint/decision/incident/learning (untyped counts as checkpoint); tags matches checkpoints carrying ALL listed tags, case-insensitive. Both combine with search and each other.
Read The Result Correctly
Recall can surface:
- Active brief, which is the current strategic direction
- Checkpoints, which are the evidence trail
- Workspace summaries for cross-project recall
Treat the active brief as direction, not as an execution checklist. If you need implementation detail, read docs/plans/.
After Recall
- Summarize the active brief or recent checkpoint thread when it exists.
- Continue from the recalled context instead of re-deriving it.
Related Skills
anortham/handoff
testing
VerifiedTrustedCommunity
Use when returning to a project after time away, switching harnesses, or handing work off to another agent, to produce a structured session-resumption summary from the active brief, recent checkpoints, and git delta.
1SKILL.mdUpdated Apr 18, 2026
anortham/brief
development
VerifiedTrustedCommunity
Use when starting multi-session work, capturing approved project direction, updating goals or constraints, or when the user asks for durable strategic context that should persist across sessions
1SKILL.mdUpdated Apr 18, 2026
anortham/brief-status
testing
VerifiedTrustedCommunity
Use when the user asks for progress against current project direction, wants a status check on the active brief, or needs evidence-backed assessment across briefs, checkpoints, and docs/plans
1SKILL.mdUpdated Apr 18, 2026
anortham/brief-status
testing
VerifiedTrustedCommunity
Use when the user asks for progress against current project direction, wants a status check on the active brief, or needs evidence-backed assessment across briefs, checkpoints, and docs/plans
1SKILL.mdUpdated Apr 17, 2026