Skip to content
Back to skills

Study Recall

ASecurity

Run a Feynman recall session on a previously coached topic

  • 3 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 30, 2026
ai-agentsbash

Security analysis

A100/100

Scanned September 30, 2026

npx -y skills add jskswamy/skills --skill study-recall --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Study Recall?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Study Recall
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jskswamy-study-recall/badge)](https://www.skillsdirectory.com/skills/jskswamy-study-recall)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: study-recall
description: Run a Feynman recall session on a previously coached topic
---

# Study Recall Skill

Run a Feynman-style recall session on a topic you've previously coached or studied independently. Reads the existing coaching note to target known gaps, then appends a row to the Recall Log.

## Arguments

- `<topic|url>` - Topic name or original URL used during coaching (required)
- `--depth shallow|standard|deep` - How many Feynman iterations to run (default: standard)

## Workflow

### Step 1: Parse Arguments

Extract topic/url and depth (default: standard).

### Step 2: Read Config

```bash
cat "${CLAUDE_CONFIG_DIR:-$HOME/.claude}/study.md" 2>/dev/null
```

Extract `notes_path` and `content_vaults`. Expand `~`:
```bash
NOTES_PATH=$(eval echo "<notes_path>")
```

### Step 3: Find Coaching Note

Generate slug from input (lowercase, hyphens, strip special chars).

```bash
ls "${NOTES_PATH}/<slug>.md" 2>/dev/null
```

If not found, try fuzzy match:
```bash
ls "${NOTES_PATH}/" | grep -i "<keywords_from_topic>"
```

If still not found, search content vaults for a matching note:
```bash
grep -ril "<topic_keywords>" <vault_1> <vault_2> --include="*.md" 2>/dev/null | head -5
```
If vault matches found, show them and let the user pick one. Use the selected
file as the note path (treat as a vault note — recall agent handles it the
same way as a coaching note).

If nothing found anywhere:
- Inform user no note exists for this topic
- Ask: start a coaching session first with `/study:coach <topic>`, or run recall without prior note?
- If they choose to proceed without note: run recall as cold recall (no gap targeting)

### Step 4: Run Recall Session

Read `<package-root>/agents/study/recall-agent.md` for the full session
logic. Run it directly in this conversation — do not spawn an agent.

Context to carry in:
- Topic name
- Coaching note path (or null for cold recall)
- Notes path: `NOTES_PATH`
- Depth: from `--depth` argument
- `from_coach: false`

### Step 5: Done

Report: "Recall log updated in `<note_path>`"

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.