Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Generate and deliver a Hacker News daily report (Top-N) with article summaries and multi-view comment synthesis, in user-selected language, with optional fil...
Generate and deliver a Hacker News daily report (Top-N) with article summaries and multi-view comment synthesis, in user-selected language, with optional fil...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
v0.7.0: Add concurrent retry profile for schedule reliability (primary run + immediate retry + delayed retry) with idempotent completion checks to avoid timeout-caused misses. v0.6.0: Brand rename for distribution as "HN Daily Brief" + full copy cleanup to English-only wording. v0.5.1: Language cleanup for public distribution (English-first docs; localized markers still supported). v0.5.0: First public release.
language: output language (default: current user conversation language) topN: number of items (default: 10) style: strict | lite (default: strict) outputDir: output directory (default: /home/ubuntu/.openclaw/workspace/output/hn-daily/) persist: whether to save file + update index (default: true) reminderTime: cron time in user timezone, or off
On first load (or when user changes params), show effective params once and confirm. Otherwise, reuse last confirmed params.
Retry preflight check (required for retry jobs): If this run is a retry/compensation run, first check whether today's report already exists and is complete (at minimum includes ## Top 10). If already complete, return NO_REPLY and stop (idempotent exit). Always fetch fresh inputs for this run (required): Re-pull current HN Top-N items, article snippets, and comments at run time. Do not reuse previous report body as source input. Collect materials via script (data collection only, never user-facing): scripts/generate_hn_daily.py --style <style> --top <topN> --language <language> --outdir /tmp/hn-daily-draft --materials /tmp/hn-daily-draft/HN-materials.json Script must only output HN-materials.json (no user-facing report body). Use HN-materials.json as the only source for final writing. LLM generation (required, prompt-driven quality): Use a single strict prompt template to generate final report in selected language. All content quality constraints (summary depth, comment synthesis style, anti-template wording) must be enforced by prompt, not by script templates. No โsummarize then translateโ; generate directly in target language. Re-check completion before send (required for retry jobs): If another concurrent run has already persisted a complete report, do not send duplicate content; return NO_REPLY. Send full final report body to current chat. If persist=true, write final report to <outputDir>/HN-daily-YYYY-MM-DD.md and update <outputDir>/HN_DAILY_INDEX.md.
persist=false: success = full report body delivered in chat. persist=true: success = chat delivery + file write + index update. Under concurrent retry profile: success can be achieved by primary run or any retry run; retries must skip if the report is already complete. If any required condition fails, treat run as failed (do not claim completion).
Send only report body to user (no receipts/status metadata). Never send script draft markdown directly; user-facing report must come from LLM rewrite over materials JSON. Output must use one language only: the selected language for the run (no bilingual/mixed-language output). Real markdown newlines only; never output literal \n in user-visible content. Top-N structure per item: Title Link HN link Heat Source summary Comment viewpoint synthesis
Default hard rule: source summary must be >=300 chars in zh (>=200 words in en; equivalent depth for others). Elastic exception: only when source content is genuinely short/information-limited, summary may be shorter than default target. Comment viewpoint summary target: zh>=80 chars (equivalent depth for others), with the same short-source exception. When exception is used, explicitly mark "source is short / info limited" (or equivalent in selected language), prioritize verifiable facts + discussion context + actionable implications, and keep concise but information-dense output. Never inflate length with generic filler text.
Must be in selected language. Multi-perspective (not binary pro/con). Per item, output 5 comment viewpoints when available. If username exists in source comment, it must be preserved in output. Only use "insufficient comments" when no usable comments are available. Summarize viewpoints; do not paste long raw quotes.
If reminderTime != off, create/update a 3-job retry ladder automatically (no duplicates): Primary run at reminderTime (e.g. HN Daily 06:50) Immediate retry at reminderTime + 1m (e.g. HN Daily 06:51 Retry) Delayed retry at reminderTime + 15m (e.g. HN Daily 07:05 Retry) All retry jobs must be idempotent via completion checks (see Mandatory execution order step 1 and step 5). Keep job names aligned with schedule and retry role. Cron payload must be execution-oriented (not passive reminder). Rationale: cron has no built-in on-failure callback; this retry ladder is the required equivalent for timeout/failure recovery.
Generate directly in selected language. Source summary length must meet selected-language threshold. Each comment viewpoint summary must meet selected-language threshold. Summaries must be article-specific and fact-based; avoid reusable boilerplate. Comment section must synthesize viewpoints (not raw quote dumping), with usernames when available.
Validate final report before sending: zh summary default >=300 chars per item; zh comment viewpoint default >=80 chars per viewpoint. Recommended command: scripts/validate_report.py --report <final_report_path> --language <language> If an item/viewpoint is below default threshold, it must explicitly include a short-source marker (e.g. source is short / info limited). If gate fails, rewrite and re-check; do not send failing report.
If prompt-driven LLM generation path is not available/validated, keep cron disabled until fixed. If primary + both retries all fail on the same day, send a concise failure alert to the current chat with the first actionable error cause (do not silently drop the run).
Writing, remixing, publishing, visual generation, and marketing content production.
Largest current source with strong distribution and engagement signals.