From filesystem-organiser
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.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin filesystem-organiserThis skill is limited to using the following tools:
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.
Conducts multi-round deep research on GitHub repos via API and web searches, generating markdown reports with executive summaries, timelines, metrics, and Mermaid diagrams.
Share bugs, ideas, or general feedback.
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 is parsed as:
~/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./filesystem-organiser:new-workspace downloads-cleanup
/filesystem-organiser:new-workspace my-gdrive --variant=gdrive
/filesystem-organiser:new-workspace scratch-area --local-only
Extract workspace name, target parent path, variant, and flags from $ARGUMENTS. If workspace name is missing, ask the user for it before proceeding.
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.
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.
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.
Open the new workspace's CLAUDE.md and:
Ask the user only for facts this plugin can't infer:
CLAUDE.md as ORGANISER_TARGET).CLAUDE.md as GDRIVE_REMOTE). Remind the user to run /filesystem-organiser:rclone-configure after provisioning if they haven't set up rclone yet.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.
Tell the user:
/filesystem-organiser:fs-scan for local; /filesystem-organiser:gdrive-status, /filesystem-organiser:gdrive-organize etc. for gdrive)./filesystem-organiser:rclone-install then /filesystem-organiser:rclone-configure.${CLAUDE_SKILL_DIR}/../../template/ (not ${CLAUDE_PLUGIN_ROOT} — that variable isn't exported in skill bash injection, only in hooks/MCP)..claude/commands/, .claude/agents/, or .claude/skills/ into the new workspace. If the user wants workspace-local overrides, they can add them manually later.