sync-stars

Diff GitHub starred repos against CATALOG.md and generate catalog entries.

2|Updated Jun 15, 2026
One-click install
npx skills add https://github.com/mattbutlerengineering/ai-tooling --skill sync-stars
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-stars
Source: https://github.com/mattbutlerengineering/ai-tooling/tree/main/plugin/skills/sync-stars
Command: npx skills add https://github.com/mattbutlerengineering/ai-tooling --skill sync-stars

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gaps exist between your GitHub starred repos and entries in CATALOG.md. This skill automates the discovery, classification, and ready-to-paste catalog entry generation for these missed items, helping you keep your inventory accurate and up-to-date.

Core Features & Use Cases

  • Diff and surface gaps: compare your starred repos against CATALOG.md to identify missing entries.
  • Classify gaps for cataloging: categorize gaps as AI-tooling or non-AI tooling to determine relevance and placement.
  • Generate ready-to-paste catalog entries: produce catalog-ready rows including category, type, one-liner, and problem statement for quick insertion.
  • Use Case: you want to expand your catalog with newly starred projects without manual lookups or drafting entries.

Quick Start

Run /sync-stars to scan your GitHub stars and generate catalog entries for any missing items.

Frequently Asked Questions about sync-stars

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

FAQPage Schema
How do I find GitHub starred repos missing from my catalog?

Run /sync-stars to scan your starred repos via the GitHub API, parse CATALOG.md, and output structured catalog rows for any missing items.

What is the best way to automate catalog entry generation for newly starred repositories?

This skill automates that workflow by reading GitHub stars via the API and producing ready-to-paste catalog entries aligned with your existing categories.

How does gap analysis work for GitHub stars and markdown catalogs?

It classifies surfaced gaps as AI-tooling or non-AI tooling to determine their relevance and proper placement within the catalog.

Do I need a specific CATALOG.md format to sync my GitHub stars?

It reads the markdown file directly and outputs structured rows matching the categories already present.

Can I classify missing GitHub stars as AI or non-AI tooling before adding them to my catalog?

This classification step ensures generated entries are sorted into the correct existing categories before insertion.

What limitations exist when diffing GitHub stars against a markdown catalog?

It does not automatically insert entries into the markdown file, but rather outputs ready-to-paste rows for manual review and insertion.