Skill

new-userscript

Scaffold a new Tampermonkey userscript with a complete `==UserScript==` metadata block, sensible defaults, and a starter IIFE body. Drops it in the user's userscripts base directory if configured, otherwise asks where to place it.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin userscript-development

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Create a new userscript file ready to load into Tampermonkey.

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

Stars0

Forks0

Last CommitMay 2, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

New Userscript

Create a new userscript file ready to load into Tampermonkey.

Resolve the base path

Order of precedence:

$USERSCRIPT_REPOS_BASE env var

userscripts_base_path from ${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/userscript-development/config.json

Ask the user

Inputs

Script name (kebab-case for filename, human-readable for @name)

Target site(s) — for @match / @include (use @match by preference; it's stricter)

What the script does — one sentence for @description

Run timing — document-start | document-end | document-idle (default document-idle)

Needed APIs — any GM_* / GM.* grants (default none)

Metadata block reference

Use the official Tampermonkey metadata keys. Common ones:

// ==UserScript== // @name <Human Name> // @namespace <stable URL or reverse-domain> // @version 0.1.0 // @description <one sentence> // @author <name> // @match https://example.com/* // @icon https://www.google.com/s2/favicons?sz=64&domain=example.com // @grant none // @run-at document-idle // @license MIT // ==/UserScript==

Body template

(function () { 'use strict'; // TODO: implement console.log('[<script-name>] loaded on', location.href); })();

Layout

Create <base>/<script-name>/:

<script-name>.user.js — the script (Tampermonkey requires the .user.js suffix for install URLs)

README.md — placeholder; tell the user to run generate-readme later

.git — git init it so it's ready to publish

If the user prefers single-file userscripts (no per-script directory), accept <base>/<script-name>.user.js instead. Ask once and remember the choice in the user's config if they want.

New Userscript

Create a new userscript file ready to load into Tampermonkey.

Resolve the base path

Order of precedence:

$USERSCRIPT_REPOS_BASE env var
userscripts_base_path from ${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/userscript-development/config.json
Ask the user

Inputs

Script name (kebab-case for filename, human-readable for @name)
Target site(s) — for @match / @include (use @match by preference; it's stricter)
What the script does — one sentence for @description
Run timing — document-start | document-end | document-idle (default document-idle)
Needed APIs — any GM_* / GM.* grants (default none)

Metadata block reference

Use the official Tampermonkey metadata keys. Common ones:

// ==UserScript==
// @name         <Human Name>
// @namespace    <stable URL or reverse-domain>
// @version      0.1.0
// @description  <one sentence>
// @author       <name>
// @match        https://example.com/*
// @icon         https://www.google.com/s2/favicons?sz=64&domain=example.com
// @grant        none
// @run-at       document-idle
// @license      MIT
// ==/UserScript==

Full key list: https://www.tampermonkey.net/documentation.php?locale=en#meta

Body template

(function () {
    'use strict';

    // TODO: implement
    console.log('[<script-name>] loaded on', location.href);
})();

Layout

Create <base>/<script-name>/:

<script-name>.user.js — the script (Tampermonkey requires the .user.js suffix for install URLs)
README.md — placeholder; tell the user to run generate-readme later
.git — git init it so it's ready to publish

If the user prefers single-file userscripts (no per-script directory), accept <base>/<script-name>.user.js instead. Ask once and remember the choice in the user's config if they want.