Output Cards

Generate Research-Claw dashboard cards as JSON in fenced code blocks.

850|114|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/wentorai/Research-Claw --skill output-cards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Output Cards
Source: https://github.com/wentorai/Research-Claw/tree/main/skills/output-cards
Command: npx skills add https://github.com/wentorai/Research-Claw --skill output-cards

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill prevents malformed or inconsistent structured outputs by standardizing the exact JSON card formats used by the Research-Claw dashboard.

Core Features & Use Cases

  • Card Schemas for Dashboard Rendering: Defines validated JSON structures for six card types: paper_card, task_card, progress_card, approval_card, file_card, and monitor_digest.
  • Safety-Critical Output Rules: Enforces constraints such as valid academic-only usage for paper_card, approval_id requirements for approval_card, and verbatim copying for file_card from workspace_save/workspace_export outputs.
  • Deterministic Operational Instruction: Requires valid JSON content inside fenced code blocks, with the card type as the language tag, so the dashboard can parse via JSON.parse().

Quick Start

When you need to show an item in the dashboard, output the corresponding card (for example, a task_card) as a fenced code block containing valid JSON using the exact required fields.

Frequently Asked Questions about Output Cards

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

FAQPage Schema
How do I enforce strict JSON schema compliance for dashboard cards?

To enforce strict JSON schema compliance for dashboard cards, output valid JSON inside fenced code blocks labeled with the specific card type tag so the dashboard can parse it via JSON.parse().

What structured output formats are needed for research workflow monitoring?

Research workflow monitoring requires six structured JSON card formats: paper_card, task_card, progress_card, approval_card, file_card, and monitor_digest to render items correctly on the dashboard.

Does generating an approval card require a specific identifier?

Yes, generating an approval_card requires a valid approval_id linkage to connect the approval step correctly within the executive review workflow.

How do I create file cards without fabricating workspace content?

To create file cards without fabricating content, copy verbatim from workspace_save or workspace_export outputs to ensure data integrity and prevent malformed dashboard rendering.

Why are my structured dashboard cards failing to parse?

Structured dashboard cards fail to parse when JSON is invalid or placed outside fenced code blocks, preventing successful JSON.parse() execution and breaking dashboard rendering.