From knowgt
Generates plain-language GitHub Trending briefings from WebFetch/WebSearch, compares against prior reports, and writes daily/weekly trend summaries with 4 structured sections.
How this skill is triggered — by the user, by Claude, or both
Slash command
/knowgt:knowgtThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a plain-language briefing from GitHub Trending. Prefer WebFetch/WebSearch over local scraping scripts. The value of this skill is trend interpretation, not crawler maintenance.
Create a plain-language briefing from GitHub Trending. Prefer WebFetch/WebSearch over local scraping scripts. The value of this skill is trend interpretation, not crawler maintenance.
Determine scope:
daily.weekly and monthly when requested.Fetch current data:
https://github.com/trending?since=daily, weekly, or monthly.Find history:
trending_reports/, read the newest 2-5 markdown reports.Compare:
Write the briefing:
Save markdown output when working in a repo:
trending_reports/trending_briefing_YYYY-MM-DD.md (quick overview, exactly 4 sections)trending_reports/trending_detailed_YYYY-MM-DD.md (deep-dive using "Repository Explanations (Detailed)" template)[Optional] Generate HTML report:
skills/productivity/github-trending-briefing/reference/briefing-template.html to understand its CSS and DOM structure. The template is a single-page, two-tab design that merges both briefing and detailed views.trending_reports/trending_briefing_YYYY-MM-DD.html using the exact same CSS and DOM structure as the template. Fill every section with real data:
.detail-list): for each first-time project, render a full .project-card with header (rank, name+link, lang-tag, stars) and body (what-is-it, analogy in .proj-analogy, helps-list in .proj-helps, who-needs-it with .persona tags). For projects already covered in prior reports, render a shorter .project-card with lower opacity and a note referencing the earlier report instead of repeating the full breakdown.<script>: keep the exact switchTab() function from the template so tabs work.<style>, all JS inline in <script>.open trending_reports/trending_briefing_YYYY-MM-DD.htmlxdg-open trending_reports/trending_briefing_YYYY-MM-DD.htmlstart trending_reports/trending_briefing_YYYY-MM-DD.html (cmd) or Start-Process trending_reports/trending_briefing_YYYY-MM-DD.html (PowerShell)Use this structure unless the user asks for something else:
# GitHub Trending Briefing - YYYY-MM-DD
> Generated: YYYY-MM-DD
> Source: github.com/trending
> Baseline: <recent report dates or "none">
## New On The List
| Rank | Project | Language | Stars Gained | Plain-English Use |
|------|---------|----------|--------------|-------------------|
## Recent Best
| Project | Evidence | Why It Matters |
|---------|----------|----------------|
## Trend Read
Short paragraphs explaining the strongest pattern in normal language.
## Full List
| Rank | Project | Language | Total Stars | Stars Gained |
|------|---------|----------|-------------|--------------|
Use only in detailed reports. Keep "Plain-English Use" column in briefings concise.
Analyze this GitHub Trending project. Requirements:
- No jargon like "architecture", "paradigm", "empowerment", "leverage"
- Keep important domain terms when they are useful: LLM, RAG, agent, API, TTS, Markdown, token, crawler
- Focus on project positioning, the problem it solves, and the scenario where it matters
- Use analogies only when they add clarity; do not infantilize the explanation
- Name concrete people and situations, not "developers" or "engineers"
Output format:
What is it? (1-2 clear sentences)
Analogy (Optional; only if it clarifies the project)
What can it help you do? (3 items, each starts with a verb)
Help you...
Let you...
Save you from...
Who actually needs it? (Be specific, not "developers")
Example: A marketing specialist who makes daily PPTs for the boss
Example: A new hire inheriting messy legacy code
After writing, check each item. Rewrite if anything fails:
npx claudepluginhub wahahaazhe/knowgt --plugin knowgtGenerates Chinese GitHub Trending briefings from web data, compares with historical reports, and writes daily/weekly trend summaries. Useful for analyzing popular repos, explaining them in plain language, and creating repeatable reports for coding assistants.
Manages GitHub Stars with auto-discovery from content, update tracking (releases/commits), and an HTML dashboard for visualizing starred projects.
Generates interactive HTML project recap of current state, recent git activity, key decisions, architecture, and cognitive debt hotspots. Auto-activates on recap/summary/status requests; accepts time window (2w/30d/3m).