One-click install
npx skills add https://github.com/anajuliabit/aeon --skill contributor-spotlight
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: contributor-spotlight
Source: https://github.com/anajuliabit/aeon/tree/main/skills/contributor-spotlight
Command: npx skills add https://github.com/anajuliabit/aeon --skill contributor-spotlight

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, grep, sed, sort, wc, ls, head, base64, date, and includes assets (resource) components.

What problem does it solve?

contributor-spotlight turns existing fork-cohort data into a ready-to-post weekly recognition moment, eliminating the manual work of selecting a standout fork operator and writing a high-signal social post.

Core Features & Use Cases

  • Weekly fork operator recognition: Picks one POWER (or ACTIVE fallback) fork operator from the latest fork-cohort inputs and writes a ~150–180 word spotlight.
  • Newsworthy stack + shipping proof: Includes enabled skill count, recent activity (30-day commits or last-run age), and top enabled skills with clear operator divergence markers.
  • Deduplication and history: Prevents featuring the same fork again within a 4-week window by updating contributor-spotlight-history.
  • Use case: Run weekly to publish a consistent “keep shipping” callout that’s formatted to feed thread/notification workflows.

Quick Start

Run the contributor-spotlight skill with an empty var to auto-pick the best eligible fork from the most recent fork-cohort data, or pass dry-run to generate the article without sending a notification.

Frequently Asked Questions about contributor-spotlight

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

FAQPage Schema
How do I automate a weekly GitHub contributor spotlight for a community newsletter?▼

You can generate a weekly contributor spotlight by selecting an eligible fork operator from cohort data, extracting activity signals like 30-day commits, and rendering a tweetable recognition artifact while maintaining deduplication history to prevent repeats within four weeks.

What is fork operator deduplication in community recognition workflows?▼

Fork operator deduplication prevents the same GitHub fork from being featured again within a four-week window by updating stateful contributor-spotlight history files after each weekly recognition artifact is generated.

Can I generate a community recognition post without sending Telegram notifications?▼

Yes, you can generate a community recognition post without sending Telegram notifications by using the dry-run option, which creates the spotlight article and updates history files while skipping the conditional notify trigger entirely.

Does the weekly newsletter spotlight workflow require specific fork-cohort inputs?▼

The weekly newsletter spotlight workflow requires reading existing fork-cohort articles and local cohort/state JSON files to identify POWER or ACTIVE fork operators, extracting enabled skill counts and recent activity signals to populate the recognition artifact.

What happens when fork-cohort articles are stale during autonomous community engagement?▼

When fork-cohort articles are stale during autonomous community engagement, the spotlight workflow applies reliable fallbacks by dropping from POWER to ACTIVE fork operators to ensure a valid contributor is still selected and recognized weekly.

What GitHub CLI dependencies are needed for automated contributor recognition?▼

Automated contributor recognition requires standard command-line utilities including gh, grep, sed, sort, wc, ls, head, base64, and date to parse fork-cohort JSON, extract repository activity signals, and render the weekly spotlight artifact.