skills.rest
joshka0
joshka0COMMUNITY
Explore all skills by this author →
GitHub

foxctl Observability

Query and filter foxcular observability events with timestamp and status filters.

3|Updated Apr 14, 2026
Search Tags:#debugging#observability#local development#error triage#event filtering#log querying#performance stats
One-click install
npx skills add https://github.com/joshka0/foxctl --skill foxctl-observability
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: foxctl Observability
Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-condensed/foxctl-obs
Command: npx skills add https://github.com/joshka0/foxctl --skill foxctl-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of not being able to quickly find, filter, and understand foxcular observability events (including errors and performance stats) without manually navigating through observability directories.

Core Features & Use Cases

  • Targeted event queries: Find recent, time-bounded, or operation-specific foxcular events such as skill.run or hook.execute, and restrict results by component, command/skill name, and status.
  • Error-focused triage: Quickly isolate error-only events to speed up debugging and incident response.
  • Optional aggregate statistics: Produce stats summaries for filtered command/skill execution so you can spot patterns over time.
  • Use Case: When a workflow fails, filter by operation and status=error to identify which skill command triggered the issue and review the most recent related events.

Quick Start

Run: foxctl run obs/logs --input '{"errors_only": true, "limit": 50}' to see the latest foxcular error events.

Frequently Asked Questions about foxctl Observability

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

FAQPage Schema
How do I query local development logs to find recent errors?▼

Query local development logs to find recent errors by filtering observability events with an errors_only flag and a result limit to isolate failed executions for triage.

What is the best way to triage observability events for a specific skill command?▼

Triage observability events for a specific skill command by applying operation, component, and status filters to retrieve timestamp-sorted execution histories and identify the failure source.

Can I monitor hook and job activity using event filtering?▼

Yes, you can monitor hook and job activity by selecting specific operations like hook.execute within the event query to browse execution patterns and inspect command-level histories.

How do I get performance stats for filtered command execution?▼

Get performance stats for filtered command execution by enabling optional aggregate statistics during your log query to produce summaries that spot execution patterns over time.

Does foxctl Observability support time-bounded log querying?▼

Yes, foxctl Observability supports time-bounded log querying by applying since, duration, or timestamp filters to restrict observability event results to specific timeframes.

Related Skills

Explore More Data & Analytics Skills→
roderikroderik
2

logging-best-practices

Implement wide-event logging with canonical log lines in web services via middleware and JSON schema.

Community
Basic
Greenmamba29Greenmamba29

log-analyzer

Parse and analyze application logs to identify errors, anomalies, and bottlenecks.

Community
Intermediate
dismantldismantl

session-historian

Parse JSONL session logs from Codex and Claude for cross-session analytics.

Community
Intermediate
microsoftmicrosoft
242

azure-diagnostics

Diagnose Azure production issues through systematic flow and KQL log analysis.

Official
Basic