First-run setup for userscript-development. Optionally records the user's userscript repos base directory so other skills can default new userscripts there. Skipping is fine — the plugin works without it.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin userscript-developmentThis skill uses the workspace's default tool permissions.
One-time setup. Captures (optionally) where the user keeps their userscript repos so `new-userscript`, `publish-userscript`, etc. can default to that location.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
One-time setup. Captures (optionally) where the user keeps their userscript repos so new-userscript, publish-userscript, etc. can default to that location.
${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/userscript-development/config.json
DATA_ROOT="${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/userscript-development"
mkdir -p "$DATA_ROOT"
~/repos/github/userscripts). Press enter to skip — the plugin works without it." Accept absolute or ~-prefixed paths; expand ~.config.json:
{
"userscripts_base_path": "/abs/path/to/userscripts",
"default_author": "<from git config user.name>",
"default_namespace": "<from git config user.email or domain>"
}
{} so downstream skills can detect no preference.The user can override per-shell by exporting USERSCRIPT_REPOS_BASE. Skills should prefer that env var over the saved config when both are present.