| name | Output Cards |
| description | JSON schema reference for 6 structured output card types used by the Research-Claw dashboard: paper_card, task_card, progress_card, approval_card, file_card, monitor_digest. Read this before outputting any structured card for the first time in a session. |
Output Cards
Use fenced code blocks with the card type as the language tag only for
Agent-authored card semantics. Content MUST be valid JSON — the dashboard
parser uses JSON.parse(). Research-Claw automatically presents successful
Workspace file facts and supported raw literature results; do not copy tool
JSON merely to make those cards appear. Keep ordinary paths and safe links in
the surrounding prose for non-Dashboard channels.
paper_card
ONLY for real academic publications deliberately highlighted by the Agent —
from API queries, library_search, or user-identified papers. NEVER for
concepts, tools, non-scholarly content, or every raw search hit. A raw result is
only retrieved; the fence does not prove it was read, cited, saved, or verified.
Required: type, title, authors (string[]).
Optional: venue, year, doi, url, arxiv_id, abstract_preview,
read_status ("unread"|"reading"|"read"|"reviewed"), library_id, tags.
task_card
Required: type, title, task_type ("human"|"agent"|"mixed"),
status ("todo"|"in_progress"|"blocked"|"done"|"cancelled"),
priority ("urgent"|"high"|"medium"|"low").
Optional: id, description, deadline (ISO 8601), related_paper_title,
related_file_path.
progress_card
Required: type, period, papers_read, papers_added, tasks_completed,
tasks_created. Optional: writing_words, reading_minutes, highlights (max 5).
approval_card
Required: type, action (string), context (string), risk_level ("low"|"medium"|"high").
Required (for exec approvals): approval_id from exec.approval.requested
— without it, dashboard buttons are non-functional.
Optional: details (must be a JSON object, not a string — e.g. {"paper_count": 7}).
file_card
Successful workspace_save, workspace_export, workspace_append, and
workspace_download results are presented automatically. State the ordinary
workspace-relative path in prose; no fence is required. Legacy fences remain
compatible, but NEVER fabricate a path.
monitor_digest
Required: type, monitor_name, source_type (free-form), target,
total_found, findings (array of {title, url?, summary?}, max 10).
Optional: schedule.
