| name | new-workspace |
| description | Provision a new filesystem-organiser workspace on disk. Use when the user wants to start organising a new filesystem area (local directory or Google Drive). Accepts a workspace name and optional variant (local | gdrive). Scaffolds the workspace, personalises CLAUDE.md from the user's global memory, and (by default) creates a GitHub repo. |
| disable-model-invocation | true |
| allowed-tools | Bash(mkdir *), Bash(cp *), Bash(cat *), Bash(git init *), Bash(git add *), Bash(git commit *), Bash(gh repo create *), Bash(gh auth status), Bash(git push *), Read |
Provision Filesystem-Organiser Workspace
Creates a new workspace for organising filesystem content. This plugin's commands (/filesystem-organiser:fs-scan, /filesystem-organiser:gdrive-organize, etc.) are globally available once installed — this skill only provisions the data scaffold (CLAUDE.md, context/, logs/, etc.) that those commands read from and write to.
Arguments
$ARGUMENTS is parsed as:
- First positional: workspace name (kebab-case, used as directory and GitHub repo name). Required.
- Second positional (optional): target parent path. Defaults to
~/repos/github/my-repos.
--variant=<local|gdrive> (optional): which scaffold to copy. Default: local. Use gdrive for Google Drive organisation via rclone.--local-only (optional): skip GitHub repo creation and push. Default: create a public GitHub repo and push.--private (optional): create the GitHub repo as private. Default: public.
Examples
/filesystem-organiser:new-workspace downloads-cleanup
/filesystem-organiser:new-workspace my-gdrive --variant=gdrive
/filesystem-organiser:new-workspace scratch-area --local-only
Procedure
1. Parse arguments
Extract workspace name, target parent path, variant, and flags from $ARGUMENTS. If workspace name is missing, ask the user for it before proceeding.
2. Resolve the scaffold path
The bundled scaffold lives at ${CLAUDE_SKILL_DIR}/../../template/<variant>/. Confirm it exists. If the variant isn't local or gdrive, tell the user which variants are available.
3. Read ambient facts
Read ~/.claude/CLAUDE.md if it exists. Extract OS, locale, timezone, and user identity facts. These will personalise the workspace's CLAUDE.md at step 6.
4. Create the workspace directory
mkdir -p <target-parent>/<workspace-name>
cp -r ${CLAUDE_SKILL_DIR}/../../template/<variant>/. <target-parent>/<workspace-name>/
Do not copy any .claude/ tree. The plugin's primitives are global.
5. Personalise CLAUDE.md
Open the new workspace's CLAUDE.md and:
- Replace any placeholder identity with the facts from step 3.
- Add a short header noting the workspace name and variant.
- If ambient facts include OS/locale, embed them so downstream commands can skip re-asking.
6. Prompt for workspace-specific facts
Ask the user only for facts this plugin can't infer:
- Local variant: the target directory to organise (write into
CLAUDE.md as ORGANISER_TARGET).
- Gdrive variant: the rclone remote name (write into
CLAUDE.md as GDRIVE_REMOTE). Remind the user to run /filesystem-organiser:rclone-configure after provisioning if they haven't set up rclone yet.
7. Initialise git and (optionally) publish
cd <target-parent>/<workspace-name>
git init
git add .
git commit -m "Initial workspace from filesystem-organiser plugin"
Unless --local-only is set:
gh repo create <workspace-name> --<public|private> --source=. --push
Use --public by default, --private if flag was passed.
8. Print next steps
Tell the user:
- Workspace path.
- Variant chosen.
- Which plugin commands apply (
/filesystem-organiser:fs-scan for local; /filesystem-organiser:gdrive-status, /filesystem-organiser:gdrive-organize etc. for gdrive).
- If gdrive variant and rclone not configured: suggest
/filesystem-organiser:rclone-install then /filesystem-organiser:rclone-configure.
- Reminder that the workspace is data — they can delete/move it freely without losing the plugin's commands.
Notes
- The scaffold path must be resolved via
${CLAUDE_SKILL_DIR}/../../template/ (not ${CLAUDE_PLUGIN_ROOT} — that variable isn't exported in skill bash injection, only in hooks/MCP).
- Never copy
.claude/commands/, .claude/agents/, or .claude/skills/ into the new workspace. If the user wants workspace-local overrides, they can add them manually later.
- Don't hard-code any personal paths or identifiers here — everything comes from user memory or prompts.
