Opt-in session analytics for Claude Code. After setup consent, tracks prompts, tokens, build time, and lines changed per session. Publishes shareable build cards on promptbook.gg. Strict consent gating — no data transmitted without explicit opt-in. Background submission after session end.

2 Skills

MIT License

Free Pricing

Installation

Open Claude Code and run this command:

/plugin install promptbook@claude-code-plugins-plus

Use --global to install for all projects, or --project for current project only.

What It Does

Build better. See your progress. Post the proof.

Promptbook is an opt-in analytics plugin for Claude Code. After setup consent, it tracks prompts, tokens, and build time, sends session metrics to promptbook.gg, and turns each session into shareable progress.

Skills (2)

doctor SKILL.md View full skill →

Diagnose Promptbook setup — check config, hooks, API key, and session tracking health.

Bash(node:*)Bash(curl:*)Bash(ls:*)Bash(stat:*)Bash(cat:*)Read

Promptbook Doctor

Name: promptbook
Author: Promptbook

Overview

Run diagnostics to verify Promptbook is set up correctly. Checks config, consent, API key validity, and recent session activity. Presents a clear pass/fail report.

Prerequisites

Promptbook must have been set up via /setup first
Node.js installed (used for config parsing)
Internet access (for API key verification)

Instructions

Run these checks in order via Bash and report each result.

1. Config file exists


if [ -f "$HOME/.promptbook/config.json" ]; then
  echo "CONFIG_FOUND"
  # Check permissions — should be 600 for security
  stat -f "%Lp" "$HOME/.promptbook/config.json" 2>/dev/null || stat -c "%a" "$HOME/.promptbook/config.json" 2>/dev/null
  # Check required fields exist (without displaying values)
  node -e "const c=JSON.parse(require('fs').readFileSync('$HOME/.promptbook/config.json','utf8'));console.log('has_api_key:',!!c.api_key);console.log('has_api_url:',!!c.api_url);console.log('auto_summary:',c.auto_summary);console.log('telemetry_consent:',c.telemetry_consent===true)"
else
  echo "NO_CONFIG"
fi

If no config file found or telemetry_consent is false: tell the user to run /setup first.

2. API key is valid

Test the API key without displaying it:


API_KEY=$(node -e "console.log(JSON.parse(require('fs').readFileSync('$HOME/.promptbook/config.json','utf8')).api_key)")
curl -sL -o /dev/null -w "%{http_code}" -X POST "https://promptbook.gg/api/auth/verify-setup" \
  -H "Authorization: Bearer $API_KEY"

200 = valid and verified
401 = invalid key — suggest running /setup again
Other = network issue — suggest checking connectivity

3. Last session activity

Check for recent session data files to verify hooks are firing:


ls -lt ~/.promptbook/sessions/ 2>/dev/null | head -5

If no session files found: hooks may not be firing. Suggest starting a new Claude Code session.

Output

Present results as a clear diagnostic report:


Promptbook Doctor
─────────────────
✓ Config:    Found (~/.promptbook/config.json)
✓ Consent:   Granted during setup
✓ API Key:   Valid and verified
✓ Activity:  Last session 2 hours ago

Use ✓ for passing checks, ✗ for failures, ⚠ for warnings.

Error Handling

If config file is missing, report ✗ Config and direct user to /setup
If consent is false, report ✗ Consent and direct user to /setup


                
                  
                  
                  setup
                  SKILL.md
                  View full skill →
                
                
                  Set up Promptbook — connect your account to start tracking builds.
                  
                      Bash(curl:*)Bash(open:*)Bash(xdg-open:*)Bash(mkdir:*)Bash(cat:*)Bash(chmod:*)Bash(node:*)Bash(nohup:*)Bash(find:*)Bash(wc:*)Read
                    
                
                
                  Promptbook Setup
Overview
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.
Prerequisites

Internet access (calls promptbook.gg API)
A browser for the sign-in step
Node.js installed (used by hook scripts)

Privacy Note
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.
Instructions
Run all commands via Bash — the user just waits for the browser sign-in.
1. Create a setup session

curl -sL -X POST "https://promptbook.gg/api/auth/setup-session"

Parse the JSON response to extract three values: token, devicecode, and setupurl.
2. Open the browser
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.
3. Poll for authorization
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 pollresult or authstatus (do NOT use a variable named status). Timeout after 5 minutes.
4. Exchange device code for API key

curl -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.
5. Save the config
Write to



      
      
          How It Works
          The plugin registers four Claude Code hooks:

Event
What it does


SessionStart
Creates a session file, loads recent context


UserPromptSubmit
Counts prompts


PostToolUse
Counts lines changed, tracks file types


SessionEnd
Finalizes stats, submits to promptbook.gg


After each session, you'll see a link to your progress. A short background process may continue briefly after Claude exits so Promptbook can submit the build and generate the title/summary. Customize the title, summary, and screenshot on the web — then share it.
        

      
      

      
      

      
      
  Ready to use promptbook?
  
    
    
        
        View on GitHub
      
  




      
      
          Related Plugins
          
            
                posthog-pack
                Complete PostHog integration skill pack with 24 skills covering product analytics, feature flags, session replay, and experimentation. Flagship tier vendor pack.
              
          
        

      
      
          Tags
          
            analyticstelemetrybuildsportfoliotrackingmetricssessions

Event	What it does
SessionStart	Creates a session file, loads recent context
UserPromptSubmit	Counts prompts
PostToolUse	Counts lines changed, tracks file types
SessionEnd	Finalizes stats, submits to promptbook.gg