Skip to content
Back to skills

Jot Setup

ASecurity

Configure jot's capture backend. Run once to choose workbench or Capacities. Types are configured automatically on first capture — no upfront type mapping needed.

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

Works with

  • cli

Security analysis

A100/100

Scanned September 30, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Jot Setup?

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

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

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-setup
description: Configure jot's capture backend. Run once to choose workbench or Capacities. Types are configured automatically on first capture — no upfront type mapping needed.
---

# Jot Setup Skill

Configure where jot saves your captures. Type agents are configured automatically the first time you capture each type — no need to set them up in advance.

## Config Location

Reads and writes `${CLAUDE_CONFIG_DIR:-$HOME/.claude}/jot.md` (global config, not per-project).
Expand `~` to home directory before reading or writing.

## Step 1: Ask Backend Preference

Use AskUserQuestion with two options:
- **workbench** — Save captures as markdown files in a local workbench folder
- **capacities** — Save captures to your Capacities knowledge space via the `cap` CLI

## Step 2: If workbench chosen

Read `${CLAUDE_CONFIG_DIR:-$HOME/.claude}/jot.md` if it exists (preserve any existing fields unrelated to this step).
Write or update these fields:
```yaml
capture_backend: workbench
agents_dir: ${CLAUDE_CONFIG_DIR:-$HOME/.claude}/jot/agents/
routing: []
```

Report: "Configured for workbench. Captures will save to your workbench folder."

## Step 3: If capacities chosen

### Step 3a: Find cap CLI

```bash
which cap 2>/dev/null || ls /Users/subramk/.local/bin/cap 2>/dev/null
```

Store the path as `CAP`. If not found, stop:
> "capacities-cli is not installed or not in PATH. Install it and re-run `/jot:setup`."

### Step 3b: Verify connectivity

```bash
$CAP types --json 2>&1
```

If exit non-zero or output contains error, stop:
> "Cannot connect to Capacities. Check your authentication (`cap auth`) and re-run `/jot:setup`."

### Step 3c: Create agents directory

```bash
mkdir -p ${CLAUDE_CONFIG_DIR:-$HOME/.claude}/jot/agents
```

### Step 3d: Write config

Read `${CLAUDE_CONFIG_DIR:-$HOME/.claude}/jot.md` if it exists (preserve unrelated fields).
Write or update these fields:
```yaml
capture_backend: capacities
agents_dir: ${CLAUDE_CONFIG_DIR:-$HOME/.claude}/jot/agents/
routing: []
```

## Step 4: Report Success

**Workbench:** "Configured. Captures save to your workbench folder. Use `/jot:capture` to start capturing."

**Capacities:** "Ready. The first time you capture each type, jot will configure it automatically. No upfront setup needed — just start capturing."

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.