viewer

Launch a local web UI to render PDCA pipeline artifacts and session state.

37|7|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/unclejobs-ai/second-claude-code --skill viewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: viewer
Source: https://github.com/unclejobs-ai/second-claude-code/tree/main/skills/viewer
Command: npx skills add https://github.com/unclejobs-ai/second-claude-code --skill viewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you verify and review PDCA pipeline outputs visually, so you can trust the rendered artifacts instead of relying only on JSON correctness.

Core Features & Use Cases

  • Open the SCC Artifact Viewer: Launches a local web UI that displays research, draft, and analysis artifacts for the current session.
  • Real-time artifact rendering: Watches state.json and artifacts/*.json and updates the UI via WebSocket.
  • Artifact-type support: Renders markdown, charts, code, and flow diagrams from the session’s artifact JSON files.

Quick Start

Start the viewer for your current PDCA session using the start-server command for the session directory and then open the returned URL in your browser.

Frequently Asked Questions about viewer

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

FAQPage Schema
How do I view PDCA pipeline artifacts like markdown and charts in a browser?

To view PDCA pipeline artifacts in a browser, you can launch a local web UI that reads session state and renders markdown, charts, code, and flow diagrams. It watches state.json and artifacts JSON files to update the display in real time.

What files are required to inspect PDCA research outputs locally?

Inspecting PDCA research outputs requires a valid session directory containing state.json, artifacts/*.json, server-info, and server.pid. Without these files, the local web UI cannot render the session's research, draft, and analysis outputs correctly.

How does real-time artifact rendering work for PDCA session outputs?

Real-time artifact rendering for PDCA session outputs works by watching state.json and artifacts/*.json files for changes. When updates are detected, the local web UI synchronizes via WebSocket to immediately display the latest markdown, charts, and diagrams.

Can I render PDCA flow diagrams and code inspection outputs without a web server?

Rendering PDCA flow diagrams and code inspection outputs requires a local web server. You must use the start-server command to launch the UI and open the returned URL, as the WebSocket connection needs an active server to display artifacts.

Why are my markdown and chart artifacts not rendering after a PDCA run?

Markdown and chart artifacts may not render if the session directory lacks state.json, artifacts/*.json, server-info, or server.pid files. Ensure the PDCA run completed successfully and the correct session directory path is provided to the viewer.

What is the best way to visually verify analysis outputs from a PDCA pipeline?

The best way to visually verify analysis outputs from a PDCA pipeline is to open an interactive artifact viewer. This local web UI displays rendered markdown, charts, code, and flow diagrams, letting you visually trust outputs rather than checking JSON correctness.