Skills

Ov Session Report

Analyze local Q&A session JSONL files and produce a complete, auditable English...

Install

npx skills add volcengine/OpenViking --skill ov-session-report -g -a claude-code -y
Repository
volcengine/OpenViking41.3k
Category
Engineering
Updated
3d ago
License
AGPL-3.0
Context cost
Mediumabout 3,000 tokens
Runs scripts
No, instructions only

What it does

Analyze local Q&A session JSONL files and produce a complete, auditable English Markdown weekly report over consecutive time windows, with all data required for downstream Feishu document and whiteboard rendering. Use for requests such as "analyze the latest week of sessions," "generate a community Q&A weekly report," or "compare with last week." This skill does not ingest other message sources or create/upload online documents.

OpenViking Session Q&A Weekly Report

Read only the session data supplied by the user. Clean and normalize it, apply time windows, compute metrics, classify topics, review risks, compare with the previous period, and produce one self-contained Markdown file. The default timezone is Asia/Shanghai.

Delivery Boundary

  • The only analytical source is the session files under sessions_root. Do not fetch or merge other communities, message streams, directories, or online chat data.
  • Deliver exactly one .md file. Temporary scripts and intermediate files are allowed during analysis, but the report must remain understandable without them.
  • Do not call online document, messaging, contact, or whiteboard APIs. Do not create XML, HTML, SVG, or PNG files, and do not upload anything.
  • Preserve document and whiteboard data requirements. The Markdown must contain enough aggregates, time series, rankings, conclusions, and human-message excerpts for a downstream renderer to build the complete report body, summary dashboard, and comparison dashboard without reopening the sessions.
  • Never estimate counts from intuition. Every number must come from parsed data or a reproducible formula, and every important conclusion must be traceable to concrete session messages.
  • When the sessions cannot prove a claim, write "no supporting evidence was found before the data cutoff" instead of presenting it as a global fact.

Default output filename:

OpenViking_Community_QA_Weekly_Report_YYYY-MM-DD_to_YYYY-MM-DD.md

Inputs

Read the whole SKILL.md on GitHub

More in Engineering