script-kit-logging — community script-kit-logging, script-kit-next, community, ide skills, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

About this Skill

Perfect for Debugging Agents needing structured logging patterns for observability and error tracking. Script Kit rewritten in Rust using GPUI (Zed's UI framework)

johnlindquist johnlindquist
[0]
[0]
Updated: 3/5/2026

Agent Capability Analysis

The script-kit-logging skill by johnlindquist is an open-source community AI agent skill for Claude Code and other IDE workflows, helping agents execute tasks with better context, repeatability, and domain-specific guidance.

Ideal Agent Persona

Perfect for Debugging Agents needing structured logging patterns for observability and error tracking.

Core Value

Empowers agents to utilize compact stderr formats with AI Compact Log Mode, leveraging categories like position, app, UI, and error for enhanced debugging capabilities with GPUI and Zed's UI framework.

Capabilities Granted for script-kit-logging

Debugging Script Kit applications with structured logging
Tracking errors using compact stderr formats
Analyzing performance with categories like perf and window_mgr

! Prerequisites & Limits

  • Requires SCRIPT_KIT_AI_LOG environment variable set to 1
  • Specific to Script Kit rewritten in Rust
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

script-kit-logging

Install script-kit-logging, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md
Readonly

Script Kit Logging

Structured logging patterns for debugging and observability.

AI Compact Log Mode (SCRIPT_KIT_AI_LOG=1)

Compact stderr format: SS.mmm|L|C|message

  • L: i INFO, w WARN, e ERROR, d DEBUG, t TRACE
  • C categories:
    • P position, A app, U UI, S stdin, H hotkey
    • V visibility, E exec, K key, F focus, T theme
    • C cache, R perf, W window_mgr, X error
    • M mouse_hover, L scroll_state, Q scroll_perf
    • D design, B script, N config, Z resize

Example:

  • Standard: ... INFO ... Selected display origin=(0,0)
  • Compact: 13.150|i|P|Selected display origin=(0,0)

Enable:

bash
1SCRIPT_KIT_AI_LOG=1 ./target/debug/script-kit-gpui 2>&1

Log Modes

ModeCommandUse Case
Compact AI logsSCRIPT_KIT_AI_LOG=1Default for AI agents (saves ~70% tokens)
Full debug logsRUST_LOG=debugDeep debugging
Specific moduleRUST_LOG=script_kit::theme=debugTarget one module

JSONL Logging

Logs to: ~/.scriptkit/logs/script-kit-gpui.jsonl

Line example:

json
1{"timestamp":"...","level":"INFO","target":"script_kit::executor","message":"Script executed","fields":{"script_name":"hello.ts","duration_ms":142,"exit_code":0}}

Tracing Patterns

Use tracing + tracing-subscriber:

  • #[instrument] for spans
  • Record duration_ms; warn if slow (e.g. >100ms)

Correlation IDs:

  • Generate UUID per user action/run
  • Attach to spans so nested logs inherit it

Required fields when relevant: correlation_id, duration_ms, bead_id, agent_name, files_touched

Log Level Guide

  • error: failure
  • warn: unexpected but handled
  • info: key events
  • debug: development
  • trace: very verbose

Filter by targets (module paths): script_kit::ui, script_kit::executor, script_kit::theme

Error Handling

  • Application errors: anyhow::Result; add .context() at boundaries
  • Domain/library errors: thiserror when callers match variants
  • User-facing errors: NotifyResultExt → log first (tracing::error!) then toast

Best practices:

  • Don't unwrap()/expect()
  • Add context at each level ("which file?", "what operation?")
  • Use typed fields in logs (avoid interpolated strings)

Log Queries

bash
1grep '"correlation_id":"abc-123"' ~/.scriptkit/logs/script-kit-gpui.jsonl 2grep '"duration_ms":' ~/.scriptkit/logs/script-kit-gpui.jsonl | jq 'select(.fields.duration_ms > 100)' 3grep '"level":"ERROR"' ~/.scriptkit/logs/script-kit-gpui.jsonl | tail -50

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is script-kit-logging?

Perfect for Debugging Agents needing structured logging patterns for observability and error tracking. Script Kit rewritten in Rust using GPUI (Zed's UI framework)

How do I install script-kit-logging?

Run the command: npx killer-skills add johnlindquist/script-kit-next. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for script-kit-logging?

Key use cases include: Debugging Script Kit applications with structured logging, Tracking errors using compact stderr formats, Analyzing performance with categories like perf and window_mgr.

Which IDEs are compatible with script-kit-logging?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for script-kit-logging?

Requires SCRIPT_KIT_AI_LOG environment variable set to 1. Specific to Script Kit rewritten in Rust.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add johnlindquist/script-kit-next. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use script-kit-logging immediately in the current project.

Related Skills

Looking for an alternative to script-kit-logging or another community skill for your workflow? Explore these related open-source skills.

View All

widget-generator

Logo of f
f

f.k.a. Awesome ChatGPT Prompts. Share, discover, and collect prompts from the community. Free and open source — self-host for your organization with complete privacy.

149.6k
0
AI

flags

Logo of vercel
vercel

flags is a Next.js feature management skill that enables developers to efficiently add or modify framework feature flags, streamlining React application development.

138.4k
0
Browser

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
AI

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
AI