SuperAPI AI Directory

github-daily-brief

Writing & research

View repository

Updated 10-24 16:22

About this skill

GitHub Daily Brief

Generate the "GitHub Today Brief": fetch Trending(Today) and repositories newly created today (created:YYYY-MM-DD), write a roughly 80–120 character Chinese introduction for each project (including subjective suggestions/judgments), and output .md、.html、.pdf three files (optionally also generate a terminal-friendly colored link list).

  • github-brief-YYYY-MM-DD.md
  • github-brief-YYYY-MM-DD.html
  • github-brief-YYYY-MM-DD.pdf(Required: generate from Markdown using the md-to-pdf skill)

When to Use

  • The user says "what new projects / trending projects / brief are there on GitHub today"
  • Needs fixed formatting, copy-pasteable, repeated output every day
  • Needs to provide both .md and .html briefs

Core Principle (don't write scripts)

  • This is aninformation aggregationskill: first use agent-browser to fetch structured information (repo, language, stars, description), then have the LLM follow the template togenerate a Chinese summaryand write it to disk.
  • Do not rely on custom generation scripts such as ps1/py (translation/summary/insights must be produced by the LLM).

Inputs (defaults)

  • Date: by default use the user's local date (China/Xi'an, UTC+8). The user may also explicitly specify YYYY-MM-DD。
  • Trending count: default 10.
  • Count of repositories newly created today: default 5 (criteria:created:YYYY-MM-DD, sorted by Stars, based on the first page).
  • Output directory: default current working directory.

Output Format (Chat)

When outputting in the conversation, keep this structure (user preference):

  • One-sentence overview (including the date)
  • GitHub Trending(Date range: Today)前 N
    • owner / repo(Lang)+X today / Y★
      • 80–120 character Chinese introduction (1 paragraph)
  • 今天新建仓库(created:YYYY-MM-DD,按 Stars 排序)前 M
    • Same as above

Templates (file format written to disk)

  • Markdown template:templates/brief.md.tmpl
  • HTML template:templates/brief.html.tmpl

Generated file names:

  • github-brief-YYYY-MM-DD.md
  • github-brief-YYYY-MM-DD.html
  • github-brief-YYYY-MM-DD.pdf

Data Collection (use agent-browser to fetch data)

Trending(Today)

  • Open:https://github.com/trending?since=daily
  • Fields to collect (per item):owner/repo、url、language、stars_total、stars_today、about/description

Created Today (by Stars)

  • Open (example):https://github.com/search?q=created%3A2026-02-11&sort=stars&order=desc&type=repositories
  • Fields to collect (per item):owner/repo、url、language、stars_total、about/description

Writing Rules (hard constraints for the Chinese summary)

  • Output one paragraph per projectChinesesummary, target 80–120 characters(≈ about 100 characters).
  • Suggested structure (complete within 1 paragraph, do not break lines):
    • What it is (translate/rewrite the English About into Chinese; make reasonable inferences when necessary but don't make things up)
    • Who it's for/where to use it (1 specific scenario)
    • My view/suggestion (things to watch when getting started, risks, why it's worth attention, at least 1 sentence)
  • If the About is clearly a placeholder (such as "Contribute to …"), explicitly say "description missing" and use the page information (topics/language/Stars/repo name) to make aconservative inference。

Optional: Terminal-friendly Links (Ctrl+click in PowerShell)

  • In Windows Terminal/VS Code terminal,directly displaying the full URL usually allows Ctrl+点击 to open it.
  • If the user insists that "the project name itself be blue and clickable", you can additionally output a PowerShell print script using OSC 8 (generated on demand, not written to disk as a fixed skill script file).

HTML Quality (self-check with web-design-guidelines)

  • After generating the HTML, follow the web-design-guidelines skill requirements to fetch the latest rules and perform a review of the output file (heading hierarchy, contrast, focus styles, click target areas, mobile readability).

MUST: PDF output (using md-to-pdf)

  • After .md and .html are written to disk,you mustinvoke the md-to-pdf skill to convert github-brief-YYYY-MM-DD.md into github-brief-YYYY-MM-DD.pdf。

  • After generation, check that the output file exists and can be opened; if it fails, first investigate: whether the path contains spaces, the Node version, and whether a proxy/network affects the PDF rendering dependencies (if any).

  • Data fetching depends on the global agent-browser。

  • If a repository has no clear About (showing placeholder text like "Contribute to ..."), the description should be marked as "description missing", and try as much as possible to supplement with a one-sentence inferred purpose from topics / README (if any), avoiding making things up.

  • The default output must be inChinese, and includea brief subjective judgment/recommendation(e.g., applicable scenarios, onboarding considerations, potential risks), with the goal of about 80–120 characters per entry (≈ around 100 characters).

  • The HTML brief needs to be readable and accessible (heading hierarchy, contrast, keyboard focus styles, hover/focus states, clickable target size). After generation, you can use web-design-guidelines to perform a self-check on the output HTML and fix it.