メニュー
Set up Promptbook — connect your account to start tracking builds. Use when the user wants to enable session analytics on promptbook.gg. Trigger with "/setup" or "set up promptbook".
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill setupコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Implement user sign-up and sign-in flows with Clerk. Use when building authentication UI, customizing sign-in experience, or implementing OAuth social login. Trigger with phrases like "clerk sign-in", "clerk sign-up", "clerk login flow", "clerk OAuth", "clerk social login".
Implement session management and middleware with Clerk. Use when managing user sessions, configuring route protection, or implementing token refresh and custom JWT templates. Trigger with phrases like "clerk session", "clerk middleware", "clerk route protection", "clerk token", "clerk JWT".
Configure enterprise SSO, role-based access control, and organization management. Use when implementing SSO integration, configuring role-based permissions, or setting up organization-level controls. Trigger with phrases like "clerk SSO", "clerk RBAC", "clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".
| name | setup |
| description | Set up Promptbook — connect your account to start tracking builds. Use when the user wants to enable session analytics on promptbook.gg. Trigger with "/setup" or "set up promptbook". |
| version | 1.4.0 |
| author | Promptbook <contact@promptbook.gg> |
| license | MIT |
| allowed-tools | Bash(curl:*), Bash(open:*), Bash(xdg-open:*), Bash(mkdir:*), Bash(cat:*), Bash(chmod:*), Bash(node:*), Bash(nohup:*), Bash(find:*), Bash(wc:*), Read |
| tags | ["analytics","telemetry","setup","onboarding"] |
| compatibility | Designed for Claude Code |
Connect a Promptbook account using the device-code OAuth flow. After consent, the plugin tracks session metrics (prompts, tokens, build time, lines changed) and publishes shareable build cards on promptbook.gg.
What IS sent to promptbook.gg: session ID, project name, model, timestamps, prompt count, token counts, build time, lines changed, language, file extension counts, and tool usage counts.
What is NEVER sent: source code, prompt content, file contents, file paths, or working directory.
To generate a title and summary for each build, the plugin calls Claude Haiku via the user's own Claude credentials — this data goes to Anthropic (same as normal Claude Code usage), never to Promptbook.
The plugin stays inactive until setup writes consent into ~/.promptbook/config.json. Continuing with setup means the user consents to this data collection. After each session ends, a short background process may continue briefly to submit stats and generate the title/summary.
Run all commands via Bash — the user just waits for the browser sign-in.
curl -sL -X POST "https://promptbook.gg/api/auth/setup-session"
Parse the JSON response to extract three values: token, device_code, and setup_url.
Use the setup_url value from step 1:
open "<setup_url value>" # macOS
xdg-open "<setup_url value>" # Linux
Tell the user: "Opening promptbook.gg — sign in or create an account to continue." If the browser cannot open, show the URL for manual access.
Check every 2 seconds using the token from step 1:
curl -sL "https://promptbook.gg/api/auth/setup-session/<token value>/status"
Parse the JSON and check whether status equals "authorized". Use a unique variable name like or (do NOT use a variable named ). Timeout after 5 minutes.
poll_resultauth_statusstatuscurl -sL -X POST "https://promptbook.gg/api/auth/setup-session/exchange" \
-H "Content-Type: application/json" \
-d "{\"device_code\": \"<device_code value>\"}"
Parse the JSON response to extract api_key.
Write to ~/.promptbook/config.json — the canonical config location shared by both plugin and bash installs:
mkdir -p "$HOME/.promptbook"
cat > "$HOME/.promptbook/config.json" << 'JSONEOF'
{
"api_key": "<api_key from step 4>",
"api_url": "https://promptbook.gg",
"auto_summary": true,
"telemetry_consent": true
}
JSONEOF
chmod 600 "$HOME/.promptbook/config.json"
The chmod 600 restricts config access to the owning user only — the file contains the API key.
curl -sL -X POST "https://promptbook.gg/api/auth/verify-setup" \
-H "Authorization: Bearer <api_key value>"
Tell the user:
/setup again anytime to reconnect or switch accounts."Ask the user: "Want me to scan your Claude Code history for past sessions? I can find builds from the last 90 days and upload them to your profile."
If yes, find the bundled backfill script:
find ~/.claude -path "*/promptbook/scripts/backfill-history.js" -type f 2>/dev/null | head -1
If it does not exist, stop and tell the user the plugin install looks incomplete. Do not download code from the network.
Count matching session files first:
find "$HOME/.claude/projects" -name "*.jsonl" -type f 2>/dev/null | wc -l
Then start in the background:
nohup node <path-to-backfill-history.js> \
--days 90 \
--generate-summaries \
> "$HOME/.promptbook/backfill-history.log" 2>&1 < /dev/null &
Tell the user: "Found session files. History import started in the background. See status at https://promptbook.gg/setup/history"
On success, display:
/setup againUser: /setup
Agent: Creating setup session... Opening promptbook.gg — sign in or create an account.
Waiting for authorization... Authorized! Saving config...
You're all set! Tracking starts on your next Claude Code session.
Want me to scan your history for past sessions?