repo-actions

Generates five anchored, priority-ranked action ideas for a watched GitHub repository.

Updated May 25, 2026
One-click install
npx skills add https://github.com/Cbowcrptex/CBOWCRYPTEX --skill repo-actions-cbowcrptex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-actions
Source: https://github.com/Cbowcrptex/CBOWCRYPTEX/tree/main/skills/repo-actions
Command: npx skills add https://github.com/Cbowcrptex/CBOWCRYPTEX --skill repo-actions-cbowcrptex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers of watched GitHub repositories often struggle to decide what to work on next, defaulting to vague ideas like "improve docs" or "clean up code". This Skill produces five concrete, implementable action ideas anchored to the repo's real current state — open issues, stale PRs, TODO comments, missing CI files, or outdated dependencies — each scored and priority-ranked with a Top Pick verdict. ## Core Features & Use Cases - Anchored idea generation: Every idea must cite a real anchor such as an open issue number, a grep-matched TODO, a missing LICENSE or CI workflow, or a named dependency at a known version. - Four quality gates: Specificity linting rejects filler phrases, novelty checks prevent repeating ideas from the last 14 days, an implementability gate demotes items needing human decisions to a Monitor section, and a leverage/concreteness/novelty score ranks survivors. - Single-call state fetch: Pulls repo metadata, README, manifest files, issues, and PRs via one GitHub GraphQL query, with retry and degraded-mode fallbacks. - Use Case: A developer watching several repos runs the skill each morning and receives an article at articles/repo-actions-<date>.md listing five ranked actions, a Top Pick for tomorrow, and a notification summary. ## Quick Start Ask the agent to run the repo-actions skill to generate today's five prioritized action ideas for the watched repository configured in memory/watched-repos.md.

Frequently Asked Questions about repo-actions

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

FAQPage Schema
How do I generate prioritized action ideas for a GitHub repository?▼

Add owner/repo entries to memory/watched-repos.md and run the skill. It fetches repo state via a single gh api graphql call, builds 8-10 anchored candidates, applies four quality gates, and writes five ranked ideas to articles/repo-actions-<date>.md.

What makes a repo action idea specific enough to ship?▼

Each idea must anchor to a concrete source: an open issue number, a stale PR, a grep-matched TODO, a named dependency at a known version, a missing file like LICENSE or CI, or a README stub section. Titles containing bare phrases like improve, enhance, or clean up are rejected.

Does the skill work without the GitHub CLI?▼

The primary path uses gh api and gh api graphql with the GITHUB_TOKEN environment variable. If gh fails, it falls back to WebFetch of the repo's GitHub page for README-only scraping and marks the source status as degraded.

Why does the skill sometimes output fewer than five ideas?▼

When fewer than three candidates clear all four gates, the skill enters THIN mode and ships only what passed rather than padding with filler. If today's article exists and the repo has not been pushed to since, it exits silently with NO_CHANGE.

Can I filter ideas to a specific category like security or performance?▼

Yes, set the var parameter to a supported filter such as features, community, integrations, security, dx, performance, content, or growth. Candidates whose type does not match the filter are dropped; unknown strings act as freeform topic filters.