Skip to content
Back to skills

Jot Capture

ASecurity

Capture anything — from your current conversation or by starting a guided session. Classifies, extracts, studies, drafts, reviews, and saves.

  • 3 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 30, 2026
ai-agentsbashgitbackend

Security analysis

A100/100

Scanned September 30, 2026

npx -y skills add jskswamy/skills --skill jot-capture --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jot Capture?

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

Security grade badge for Jot Capture
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jskswamy-jot-capture/badge)](https://www.skillsdirectory.com/skills/jskswamy-jot-capture)

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: jot-capture
description: Capture anything — from your current conversation or by starting a guided session. Classifies, extracts, studies, drafts, reviews, and saves.
---

# Jot Capture Skill

## Step 1: Parse Arguments

Extract from raw arguments:
- Any explicit type hint (e.g., "book", "meeting", "idea")
- URL if present (matches `https?://[^\s]+`)
- Freeform content, or nothing for conversation capture

Store as `raw_args`.

## Step 2: Read Config

Read `${CLAUDE_CONFIG_DIR:-$HOME/.claude}/jot.md`. If absent, treat as empty with all defaults.

Extract:
- `capture_backend`: `workbench` | `capacities` (default: `workbench`)
- `review`: `both` | `workbench` | `capacities` | `off` (default: `both`)
- `agents_dir`: path to generated type agents (default: `${CLAUDE_CONFIG_DIR:-$HOME/.claude}/jot/agents/`)
- `routing[]`: array of routing entries (may be empty on first run)

Read `${CLAUDE_CONFIG_DIR:-$HOME/.claude}/jot.local.md` if present. Extract `workbench_path` (default: `~/workbench`).

Expand all `~` to absolute paths. Store as `WORKBENCH_PATH`.

Check cap availability:
```bash
which cap 2>/dev/null || echo "$HOME/.local/bin/cap"
```
Store result as `CAP`. If neither path exists, set `capture_backend = workbench`.

Store `capture_backend` as `BACKEND`.
Expand `agents_dir` `~` to absolute path. Store as `AGENTS_DIR`.

Get current date:
```bash
date +%Y-%m-%d
```
Store as `CURRENT_DATE`.

Store `review` value as `REVIEW` (default: `both`).

## Step 3: Extract Content (URL or file path only)

If `raw_args` contains a URL (`https?://`) or a local file path:

Delegate to the `jot:content-extractor` subagent:
- Provide: input type (`url` or `file`), the URL or resolved file path
- Receive: `CONTENT { title, description, body, raw_source }` (map: Content Summary → description, Source URL → raw_source)

If extraction fails, report the error and stop — do not proceed to Step 4.

If no URL or file path in `raw_args`: leave `CONTENT` empty (Mode B or conversation capture).

## Step 4: Run Capture Session

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

All variables are already resolved — carry them in:
- `raw_args`, `CONTENT`, `BACKEND`, `WORKBENCH_PATH`
- `CAP`, `AGENTS_DIR`, `routing[]`, `CURRENT_DATE`, `REVIEW`

Phase 1 of the spec treats these as pre-loaded. Skip re-fetching config.

Complete all phases in order:
classify → extract → study → draft → review → save

## Examples

```
/jot:capture                              # captures from current conversation
/jot:capture https://github.com/astral-sh/uv
/jot:capture meeting with Alice about roadmap
/jot:capture book Atomic Habits by James Clear
/jot:capture idea what if we used event sourcing
```

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.