Dianel555/DSkills / skills/github-trending-analyzer
github-trending-analyzer
VerifiedCrawl GitHub trending repositories, analyze with LLM for Chinese insights, categorize by themes, compute diffs against history, and generate Markdown reports. Default brief mode stops at trend analysis; optional detailed mode appends per-project analysis. Supports incremental gap-filling and selective re-analysis with caching.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.1 KB |
| report_template_brief.md | markdown | 1.4 KB |
| report_template_detailed.md | markdown | 1.7 KB |
| theme_rules.json | config | 2.1 KB |
report_template_brief.md
View on GitHub<!--
BRIEF template = the shared header + table sections, ending at 'Trend Analysis'.
The shared header/tables below are identical to report_template_detailed.md (lines 7-41).
Keep them in sync; for the canonical full layout, see report_template_detailed.md.
-->
# GitHub Trending Report - {date}
> Generated: {date}
> Source: github.com/trending?since={since}
> Baseline: {baseline_date}
## π₯ New Entries
| Rank | Project | Language | β Stars | π Today | One-liner |
|------|---------|----------|---------|---------|-----------|
| 1 | [org/repo](url) | Python | 12.3k | +500 | What it does |
## β Sustained Hot
| Project | Language | β Stars | π Today | Why notable |
|---------|----------|---------|---------|-------------|
| [org/repo](url) | Go | 8.5k | +300 | What makes it special |
## π Dropped Off
| Project | What it might mean |
|---------|-------------------|
| org/repo | Hype cycle cooling |
## π― Theme Breakdown
**π€ AI/LLM** (5 projects): org/repo1(+600), org/repo2(+450), ...
**π οΈ Dev Tools** (3 projects): org/tool1(+200), org/tool2(+150), ...
## π‘ Trend Analysis
{trend_insight_paragraph}
Current wave: {dominant_theme} projects surge due to {driver}. Notable shift from {previous_trend}.
<!--
Boundary marker: brief mode ends here. Do not append per-project
blocks; for the detailed mode use report_template_detailed.md.
-->
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |