joyclaw-daily-inspection-orchestrator

Coordinate OKR, AI, Continuous Delivery, and repair workflows into a weekly HTML report.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gaojingqi12/inspection --skill joyclaw-daily-inspection-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: joyclaw-daily-inspection-orchestrator
Source: https://github.com/gaojingqi12/inspection/tree/main
Command: npx skills add https://github.com/gaojingqi12/inspection --skill joyclaw-daily-inspection-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Coordinates and runs the JoyClaw daily inspection workflow across OKR, AI, repair, and delivery to produce a unified weekly HTML report for stakeholders.

Core Features & Use Cases

  • End-to-end orchestration of four sub-skills: OKR, AI, Continuous Delivery, and repair triggers.
  • Generates a single HTML report and per-skill JSON data to support weekly summaries and audits.
  • Automatically triggers repair flows when delays are detected and integrates results into the final report.

Quick Start

Start the orchestrator in the repository root to generate the weekly inspection summary.

Frequently Asked Questions about joyclaw-daily-inspection-orchestrator

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

FAQPage Schema
How do I automate daily inspection workflows into a single HTML report?

Daily inspection workflows are automated by orchestrating per-skill scripts that collect daily JSON data and aggregate results into a unified weekly HTML report for stakeholders.

What is the best way to coordinate OKR, AI, and continuous delivery inspections?

The best way to coordinate these inspections is using a metadata-driven orchestration workflow that runs per-skill automation scripts and aggregates the JSON results into a consistent output format.

Can I automatically trigger repair scripts when continuous delivery delays are detected?

Yes, repair scripts are automatically triggered when delays are detected during the inspection workflow, and the repair results are integrated directly into the final weekly summary report.

How does error handling work in metadata-driven inspection orchestration?

Error handling in metadata-driven inspection orchestration ensures consistent output formats for auditing by managing configuration-based workflows and capturing errors across per-skill automation scripts.

Do I need specific configuration files to run weekly inspection summaries?

You need configuration files to define the metadata-driven workflows, which support the end-to-end orchestration of OKR, AI, continuous delivery, and repair triggers to generate the final report.