script-kit-logging — community script-kit-logging, script-kit-next, community, ide skills

v1.0.0

About this Skill

Perfect for AI Agents like Claude Code and AutoGPT needing structured logging patterns for enhanced debugging and observability. Script Kit rewritten in Rust using GPUI (Zed's UI framework)

johnlindquist johnlindquist
[21]
[3]
Updated: 3/15/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
36
Canonical Locale
en
Detected Body Locale
en

Perfect for AI Agents like Claude Code and AutoGPT needing structured logging patterns for enhanced debugging and observability. Script Kit rewritten in Rust using GPUI (Zed's UI framework)

Core Value

Empowers agents to utilize compact log modes, such as the AI Compact Log Mode with `SCRIPT_KIT_AI_LOG=1`, and JSONL logging to `~/.scriptkit/logs/script-kit-gpui.jsonl`, providing efficient log analysis and tracing capabilities with libraries like `tracing` and `tracing-subscriber`.

Ideal Agent Persona

Perfect for AI Agents like Claude Code and AutoGPT needing structured logging patterns for enhanced debugging and observability.

Capabilities Granted for script-kit-logging

Debugging AI workflows with structured logging patterns
Analyzing performance issues using tracing patterns and correlation IDs
Filtering logs by targets, such as `script_kit::ui` or `script_kit::executor`, for focused debugging

! Prerequisites & Limits

  • Requires environment variable configuration, such as `SCRIPT_KIT_AI_LOG=1` or `RUST_LOG=debug`
  • Limited to specific log modes, including Compact AI logs and Full debug logs
  • Dependent on `tracing` and `tracing-subscriber` libraries for tracing capabilities

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

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

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 AI Agents like Claude Code and AutoGPT needing structured logging patterns for enhanced debugging and observability. 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 AI workflows with structured logging patterns, Analyzing performance issues using tracing patterns and correlation IDs, Filtering logs by targets, such as `script_kit::ui` or `script_kit::executor`, for focused debugging.

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 environment variable configuration, such as `SCRIPT_KIT_AI_LOG=1` or `RUST_LOG=debug`. Limited to specific log modes, including Compact AI logs and Full debug logs. Dependent on `tracing` and `tracing-subscriber` libraries for tracing capabilities.

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.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

script-kit-logging

Install script-kit-logging, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

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

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

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer