agentleFS
Sign inStart free
aprameyakaprameyak/github-agent-skills/skills/github-today/SKILL.md

github-today

Skill2 starsChanged 43 days agoMITView on GitHub

Account-wide briefing of what needs attention on GitHub: review requests, open PRs, assigned issues, failed automated builds, dependency updates, and stale work. Use when the user asks what needs attention, what's waiting, or "GitHub today".

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not invent urgency or deadlines.

    line 34
  2. Distinctive:

    If permissions block a signal, say so honestly (see snapshot warnings).

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

github-today

Give an actionable briefing of what needs the user's attention — without inventing urgency.

Preconditions

  1. gh auth status succeeds.
  2. github-agent is on PATH.

Workflow

github-agent today
github-agent today --json

Output adaptation

  • One outstanding item → simple direct answer.
  • Many items → prioritize review requests and failed builds before routine dependency noise.
  • Beginner accounts → plain language ("Your automated build is failing") then optional technical detail.

Rules

  • READ ONLY.
  • Do not invent urgency or deadlines.
  • Separate clearly:
    • review requests
    • the user's open PRs
    • assigned issues
    • failed automated builds
    • dependency update PRs
  • If permissions block a signal, say so honestly (see snapshot warnings).
  • No mutations.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free