observability-harness

Configure structured logs and diagnostics scripts for local code observability.

3|Updated Jun 8, 2026

Search Tags:#debugging #logging #code execution #diagnostics #process observability

Ready to run

npx skills add https://github.com/pax-k/pax-fullstack-harness --skill observability-harness

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: observability-harness
Source: https://github.com/pax-k/pax-fullstack-harness/tree/main/skills/observability-harness
Command: npx skills add https://github.com/pax-k/pax-fullstack-harness --skill observability-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill adds local-first observability to coding agents, enabling them to monitor, debug, and validate code execution without relying on external tools.

Core Features & Use Cases

Local Logging and Diagnostics: Structured logs and request correlation IDs.
Agent-Friendly Debugging: Utilize scripts/logs and scripts/diagnose for debugging.
Documentation and Best Practices: Guide for creating and linking local runtime documentation and debugging paths.
Process Observability: Integrate sprint contracts and evaluator rubrics.

Quick Start

Set up local observability by configuring structured logs and diagnostics scripts in your project.

Frequently Asked Questions about observability-harness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I add local observability and diagnostics to trace code execution?▼

Local observability is added by configuring structured logs and request correlation IDs in your project. This provides traceable code execution and process safety without relying on external tools.

What is local-first observability for coding agents?▼

Local-first observability is the ability to monitor, debug, and validate code execution directly within your environment. It uses logging conventions and diagnostics scripts to ensure traceability without external dependencies.

How do I set up structured logs and debugging paths for my project?▼

You set up structured logs and debugging paths by utilizing built-in scripts like scripts/logs and scripts/diagnose. These scripts provide agent-friendly debugging and link local runtime documentation for execution tracing.

Can I monitor code execution safely without external observability tools?▼

Yes, you can monitor code execution without external observability tools by implementing local logging conventions and diagnostics scripts. This approach ensures safe and traceable execution entirely within your local environment.

Do I need external dependencies to integrate sprint contracts and evaluator rubrics?▼

No external dependencies are required to integrate sprint contracts and evaluator rubrics. Process observability is achieved locally by incorporating these contracts into your structured logging and diagnostics workflow.