create-shortcut
Create local skills as shortcuts — makes real /commands in .claude/skills/. Use when user says "create shortcut", "create skill", "make a command for", "add shortcut", or wants a quick custom /slash-command. Also lists and deletes local skills. ALSO triggers on "Unknown skill", "skill not found", or any unrecognized /slash-command — auto-creates it on the fly.
Soul-Brews-Studio · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Soul-Brews-Studio/arra-oracle-skills-cli --skill create-shortcut技能说明
name: create-shortcut description: Create local skills as shortcuts — makes real /commands in .claude/skills/. Use when user says "create shortcut", "create skill", "make a command for", "add shortcut", or wants a quick custom /slash-command. Also lists and deletes local skills. ALSO triggers on "Unknown skill", "skill not found", or any unrecognized /slash-command — auto-creates it on the fly. argument-hint: "[list [--mine|--untagged] | create | delete | --cleanup [--auto]]"
/create-shortcut - Local Skill Factory
Create real local skills (.claude/skills/<name>/SKILL.md) that show up as /commands in autocomplete.
Usage
/create-shortcut # list local skills
/create-shortcut list # same, with numbers
/create-shortcut list --mine # only stamped skills (installer: create-shortcut)
/create-shortcut list --untagged # only skills with no installer: field
/create-shortcut create deploy "Run tests then deploy"
/create-shortcut delete deploy # delete by name
/create-shortcut delete 3 # delete by number
/create-shortcut --cleanup # interactive bulk-archive of --mine skills
/create-shortcut --cleanup --auto # auto-archive anything stamped + unused 30d+
How It Works
Creates a SKILL.md in .claude/skills/<name>/ (project-local) or ~/.claude/skills/<name>/ (global with --global).
The skill immediately appears in / autocomplete after creation.
Mode 1: List (default)
Scan both local and global skills directories:
LOCAL_DIR=".claude/skills"
GLOBAL_DIR="$HOME/.claude/skills"
For each directory, list skill folders and show:
⚡ Local Skills (.claude/skills/)
1. deploy Run tests then deploy to prod
2. lint-fix Fix all linting errors
3. db-migrate Run database migrations
⚡ Global Skills (~/.claude/skills/)
4. trace (v3.4.8) [core] Find projects, code...
5. recap (v3.4.8) [core] Session orientation...
...
Delete local: /create-shortcut delete <name or number>
Mark core (arra-oracle-skills-cli installed) skills with [core].
Mark stamped skills (with installer: create-shortcut in frontmatter) with [mine] plus a relative-age hint (e.g. 2d ago).
Local skills with no installer: field have no tag (origin unknown).
Filter flags
/create-shortcut list # default — all local + global, marks [core] / [mine]
/create-shortcut list --mine # only skills with `installer: create-shortcut`
/create-shortcut list --untagged # only skills with NO `installer:` field (origin unknown)
For --mine and --untagged, the listing additionally shows:
created_atage (e.g. "2 days ago", "3 weeks ago") — pulled from the frontmattercreated_at:field for--mine; absent for--untagged.- Approximate usage count — derived by greping the command name across
~/.claude/projects/*/*.jsonlsession files (read-only, no stored counter — counts stay computed, not persisted).
Example --mine output:
⚡ Your skills (installer: create-shortcut)
1. deploy [mine] 2d ago · used 7× Run tests then deploy
2. read-and-deep-... [mine] 1d ago · used 1× Read a target and deep-analyse...
3. resonance [mine] 3w ago · used 24× Capture a resonance moment...
Bulk-archive: /create-shortcut --cleanup
Implementation hint: parse each SKILL.md frontmatter (top YAML block between --- lines) and check for the installer: key. --mine keeps only installer: create-shortcut; --untagged keeps only entries with no installer: key at all. Core skills (installer: arra-oracle-skills-cli ...) are excluded from both filtered views.
Mode 2: Create
/create-shortcut create <name> [description]
If description not provided, ask:
What should /<name> do?
Then create the skill:
SKILL_DIR=".claude/skills/<name>"
mkdir -p "$SKILL_DIR"
Write SKILL.md with a provenance stamp in the frontmatter (so the skill can later be filtered via --mine and bulk-cleaned via --cleanup):
---
name: <name>
description: <description>
installer: create-shortcut
created_at: <ISO 8601 timestamp with timezone, e.g. 2026-05-14T04:15:00+07:00>
created_session: <first 8 chars of $CLAUDE_SESSION_ID, optional but nice>
---
# /<name>
<description>
## Step 0: Init
Chain date with the first real command — never call date alone (saves 1 tool call):
\```bash
date "+🕐 %H:%M %Z (%A %d %B %Y)" && <first-real-command-here>
\```
## Instructions
<Ask user what the skill should do, or generate from description>
---
ARGUMENTS: $ARGUMENTS
Generating the stamp values:
# created_at — ISO 8601 with local timezone offset
CREATED_AT="$(date -Iseconds 2>/dev/null || date +%Y-%m-%dT%H:%M:%S%z)"
# created_session — first 8 chars of session id (skip silently if unset)
CREATED_SESSION="${CLAUDE_SESSION_ID:0:8}"
These three fields (installer, created_at, created_session) are always written for new skills created via this mode. They are the audit trail — without them, a skill created here is indistinguishable from one created by hand.
After creating, confirm:
✅ Created /<name>
📁 .claude/skills/<name>/SKILL.md
📝 <description>
Try it: /<name>
With --global flag
/create-shortcut create deploy "Deploy to prod" --global
Creates in ~/.claude/skills/ instead of .claude/skills/.
Mode 3: Delete
/create-shortcut delete <name or number>
- Find the skill (by name or list number)
- Show its content
- Ask confirmation: "Delete /? (yes/no)"
- If yes:
- Move to trash (Nothing is Deleted):
mv .claude/skills/<name> .claude/skills/.trash/<name>_$(date +%Y%m%d_%H%M%S) - Create
.trash/if needed: `mkdir -p .claude/skills/.t
- Move to trash (Nothing is Deleted):