skill-lib/skills/zhihu-hotlist-screen/SKILL.md

name, description, version, author, tags

name	description	version	author	tags
zhihu-hotlist-screen	Use when the user wants to turn collected Zhihu hotlist data into a leadership demo dashboard or local HTML presentation artifact.	0.1.0	sgclaw	zhihu browser hotlist echarts dashboard

Zhihu Hotlist Screen

Convert an already collected Zhihu hotlist artifact into a local驾驶舱风格 .html dashboard for leadership demo use.

Use Cases

• The user asks for 知乎热榜大屏、看板、dashboard、或 ECharts 演示页。
• The user wants a local artifact for presentation or handoff.
• An upstream collection step already produced ordered hotlist rows.
• The output deliverable should be .html, not .xlsx.

Not This Skill

• recollecting Zhihu data from scratch when no upstream artifact exists
• replacing zhihu-hotlist with this downstream presenter
• exporting Office files such as .xlsx

Runtime Contract

• zhihu-hotlist remains the collection owner; this skill only transforms artifacts.
• Upstream browser calls remain in sgClaw with expected_domain like www.zhihu.com.
• Selectors in upstream work must remain CSS-only.
• This skill must not create new browser extraction steps.

Required Input Artifact

Input shape (primary payload):

{
  "source": "https://www.zhihu.com/hot",
  "sheet_name": "知乎热榜",
  "columns": ["rank", "title", "heat"],
  "rows": [[1, "标题", "344万"]]
}

• rows is required and ordering must be preserved.
• Do not invent rows or reorder collected data.
• Preserve upstream partial status in the final summary.

Tool Contract

• Call screen_html_export to render the dashboard.
• Return value must include local .html path.
• Return value must include a presentation object for demo handoff.
• Prefer presentation.url as browser-open target.

Workflow

1. Verify ordered rows artifact exists.
2. If the artifact is missing, incomplete, blocked, or explicit login failure, report that upstream collection must be fixed first.
3. Load render-flow.md.
4. Call screen_html_export.
5. Return local .html path and presentation object.
6. State that the final view should open presentation.url.

Output

• artifact type: echarts_dashboard
• source snapshot identifier
• local .html output path
• presentation object
• data completeness (complete/partial)
• optional short demo summary after artifact fields

References

• render-flow.md
• assets/zhihu-hotlist-echarts.html

Common Mistakes

• recollecting data in downstream presentation step
• returning prose only instead of .html path
• dropping presentation contract for tab delivery
• mixing Excel export requirement into dashboard flow