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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill transforms ongoing activity in a watched GitHub repository into a structured, thesis-driven article so you get evidence-backed updates without manual writing and editorial gatekeeping.

Core Features & Use Cases

  • Thesis-driven editorial workflow: Research first, then write only when a falsifiable thesis passes the required gate checks.
  • Evidence collection from live repo signals: Pull commit activity, merged PRs, open PRs, issues, releases, and README content to ground claims in concrete artifacts.
  • Quality control and self-edit: Enforces a falsifiable claim, requires explicit “what would change my mind,” and mandates an 8-step self-edit checklist before saving and notifying.

Quick Start

Run the repo-article skill with var set to your desired angle, for example: “repo-article with var=architecture to produce an architecture-focused thesis article for the most active watched repo in the last 7 days.”

Frequently Asked Questions about repo-article

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

FAQPage Schema
How do I generate a thesis-driven article from GitHub repository activity?

To generate a thesis-driven article from GitHub repository activity, configure a watched repo and run the skill with a specific angle. It pulls commit, PR, and issue data via the GitHub API to produce an evidence-backed Markdown article for editorial coverage.

What is the best way to automate research summarization for a watched GitHub repo?

Automating research summarization for a watched GitHub repo involves applying a falsifiable thesis quality gate to recent memory logs. This ensures progress reports and editorial digests are grounded in concrete artifacts rather than manual writing.

How does the editorial quality gate work for repository monitoring digests?

The editorial quality gate for repository monitoring digests works by enforcing a falsifiable claim, requiring explicit counter-arguments, and mandating an 8-step self-edit checklist before saving. This prevents unsupported claims in generated Markdown articles.

Can I use GitHub API data for roadmap analysis and progress reporting?

Yes, you can use GitHub API data for roadmap analysis and progress reporting. The skill queries live repo signals including merged PRs, releases, and README content to ground thesis-driven claims in concrete repository artifacts.

Do I need to configure watched-repo settings before generating change-focused editorial updates?

Yes, you need to configure watched-repo settings and ensure recent memory logs are available before generating change-focused editorial updates. These configurations provide the necessary context for querying GitHub APIs and producing thesis-driven articles.

When should I not use automated thesis writing for developer productivity reports?

You should not use automated thesis writing for developer productivity reports when a repository lacks recent commit activity, open PRs, or issues. Without sufficient live repo signals, the falsifiable thesis quality gate cannot gather enough evidence to pass.