skill-runner

Execute skills and append structured execution metrics to a JSON log.

52|3|Updated Feb 14, 2026

Search Tags:#automation #workflow #logging #json #skill #execution-logging

Ready to run

npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill skill-runner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: skill-runner
Source: https://github.com/ZTE-AICloud/Co-OmniSpec/tree/main/skills/skill-runner
Command: npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill skill-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill Runner standardizes the execution of specified skills and records structured metrics into FEATURE_DIR/omni-execution-log.json, enabling traceability of command runs.

Core Features & Use Cases

Record start and end times with OS-aware timestamps
Capture the executed skill name, input arguments, and output
Append a JSON log entry to the omni-execution-log.json without overwriting history

Quick Start

Invoke the runner with the target skill name and optional parameters to start automatic logging of the execution.

Frequently Asked Questions about skill-runner

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

FAQPage Schema

How do I log execution metrics for automated command workflows?▼

To log execution metrics for automated command workflows, use a runner that records start and end times, input arguments, and output. It appends structured entries to a centralized JSON log, ensuring traceability of command runs.

Can I append execution logs to a JSON file without overwriting history?▼

Yes, you can append execution logs to a JSON file without overwriting history. The runner appends each new entry to the omni-execution-log.json file, preserving all previous records for full traceability.

How do I capture OS-aware timestamps for skill execution logging?▼

To capture OS-aware timestamps for skill execution logging, invoke the runner with the target skill name. The runner automatically records deterministic start and end times based on the operating system environment.

What is the best way to standardize cross-platform command execution and logging?▼

The best way to standardize cross-platform command execution and logging is to use a runner that identifies and executes a given skill while automatically capturing timing, input, and output metrics into a structured JSON log.

Does the execution logger support custom input arguments for different skills?▼

Yes, the execution logger supports custom input arguments. You invoke the runner with the target skill name and optional parameters, which are then captured alongside the executed skill name and output in the JSON log entry.