star-sweep

Synchronize INDEX/tools.md with GitHub starred repositories via diffing and archival.

8|1|Updated Apr 20, 2018
One-click install
npx skills add https://github.com/Executioner1939/awesome-engineering-research --skill star-sweep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: star-sweep
Source: https://github.com/Executioner1939/awesome-engineering-research/tree/main/.claude/skills/star-sweep
Command: npx skills add https://github.com/Executioner1939/awesome-engineering-research --skill star-sweep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps your curated tools catalog aligned with your actual GitHub star activity while automatically flagging and archiving repos that become stale or get unstarred.

Core Features & Use Cases

  • Star diffing: Detect newly starred repos by comparing the current GitHub star set against what’s already indexed.
  • Respect unstar intent: Move repos you unstar from the active index into the archived index instead of deleting them.
  • Staleness & archival sweep: Re-check active repos for archiving status or inactivity (e.g., not pushed for more than the staleness window) and move them to _archived/.
  • Label-aware indexing: Derive taxonomy and domain/refinement labels from repo topics and keywords in the description/language.

Quick Start

Run the star-sweep process to sync INDEX/tools.md with your current GitHub starred repos for user Executioner1939 and archive anything stale.

Frequently Asked Questions about star-sweep

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically sync a markdown tools index with my GitHub starred repositories?

To sync a markdown tools index with GitHub starred repositories, run the star-sweep process to fetch paginated star metadata via the GitHub API, parse the markdown table, compute set-based diffs, and append newly starred repos to INDEX/tools.md.

How does automated staleness detection work for GitHub starred repos?

Automated staleness detection works by revalidating each active repo's push date and archive status against a configured staleness window, then moving inactive repositories to an _archived/ directory with reason tracking.

Can I preserve unstarred repositories in my curated tools index instead of deleting them?

Yes, star-sweep respects unstar intent by moving unstarred repositories from the active index into the archived index rather than permanently deleting them, ensuring non-destructive curation.

How do I apply taxonomy labels to a curated GitHub tools index based on repository metadata?

You can apply taxonomy labels by deriving domain and refinement tags from repository topics, description keywords, and language metadata fetched during the GitHub API starred repository synchronization process.

Does GitHub API rate limiting affect automated repository archival and star synchronization?

Yes, GitHub API rate limiting affects synchronization, so star-sweep implements per-repo status and push-date revalidation with rate limiting to safely handle large starred repository sets during archival sweeps.

What's the best way to maintain a fresh GitHub starred tools catalog without manual curation?

The best way to maintain a fresh GitHub starred tools catalog is automating index maintenance with star-sweep, which detects additions, removals, restars, and staleness to keep INDEX/tools.md aligned with actual star activity.