star-sync

Synchronize GitHub stars with the active peers list from state/peers.md.

8|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/usurobor/cnos --skill star-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: star-sync
Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.core/skills/ops/star-sync
Command: npx skills add https://github.com/usurobor/cnos --skill star-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronize the GitHub star state with the active peers list from state/peers.md to ensure you star the current set of peer repositories and unstar repos that are no longer peers.

Core Features & Use Cases

  • Keeps GitHub stars aligned with the current peer list by starring repos for active peers and unstarring those that are no longer peers.
  • Derives OWNER/REPO from each peer's hub URL and applies star/unstar actions in an idempotent, auditable manner.
  • Use case: A hub's subscriptions frequently change; star-sync automatically tunes GitHub stars to reflect the live peer set.

Quick Start

From the hub root, run the star-sync skill to align starred repositories with the current peer list.

Frequently Asked Questions about star-sync

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

FAQPage Schema
How do I sync GitHub stars with a peers list automatically?

You can sync GitHub stars with a peers list by running star-sync, which reads peer entries, derives OWNER/REPO from hub URLs, and runs gh repo star or unstar to match the active set.

How do I unstar GitHub repositories that are no longer peers?

To unstar GitHub repositories no longer listed as peers, star-sync compares the current peer list against your starred repos and executes gh repo unstar on any that have disappeared from the list.

Can I use GitHub CLI to automate starring repositories from a markdown file?

Yes, you can automate starring repositories from a markdown file by using star-sync, which parses state/peers.md and executes GitHub CLI commands to star or unstar the derived repositories.

What is the best way to keep GitHub stars aligned with a dynamically changing peer list?

The best way to keep GitHub stars aligned with a changing peer list is using star-sync, which idempotently applies star and unstar actions based on the live peer set derived from hub URLs.

Does star-sync require any external dependencies to manage GitHub stars?

star-sync requires no external dependencies to manage GitHub stars, as it operates directly on the state/peers.md file and executes actions through the standard GitHub CLI.

Why should I automate GitHub star synchronization for peer repositories?

You should automate GitHub star synchronization for peer repositories to ensure your starred state consistently reflects live peers, manually tuning stars as hub subscriptions frequently change is error-prone.