Skill

setup-index

Register or create the user's video index — the base directory that holds all their video projects. Use on first run, or when the user says "set up my video index", "register my video workspace", "change my video index path", or similar. Persists the path so other skills can find it.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin video-editing

Tool Access

This skill is limited to using the following tools:

Bash(mkdir *)Bash(ls *)Bash(test *)Bash(realpath *)Bash(date *)Bash(jq *)ReadWrite

Preview

The **video index** is the top-level directory under which every video project lives as a subfolder. This skill registers (or creates) that directory.

SKILL.md

Similar Skills

using-superpowers

180.9k

Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.

3 files

superpowers

Stats

Stars1

Forks0

Last CommitApr 30, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

setup-index

Set Up Video Index

The video index is the top-level directory under which every video project lives as a subfolder. This skill registers (or creates) that directory.

Procedure

1. Check for existing config

DATA_DIR="${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/video-editing" INDEX_FILE="$DATA_DIR/index.json" test -f "$INDEX_FILE" && cat "$INDEX_FILE"

If one exists, show the user the current path and ask if they want to keep or change it.

2. Ask the user

Existing or new? — do they already have an index, or should one be created?

Path?

Existing: ask for absolute path; verify with test -d.
New: propose ~/media-workspaces/video as the default. Don't auto-create until the user confirms the path.

3. Create + persist

mkdir -p "$DATA_DIR" mkdir -p "<chosen-path>" # only if new

Write index.json:

{ "path": "/absolute/path", "created": "<ISO-8601>", "type": "video" }

4. Offer follow-up

Suggest the user run profile-system next (so render commands know what GPU/encoders to use). Mention they can now say "open my video index" or "create a new video project".