agentleFS
GavinGreenwoodGavinGreenwood/agentic-workflow-template/.agents/skills/morning/SKILL.md

morning

Skill5 starsChanged 45 days agoMITView on GitHub

User-invoked only. Daily routine: main-branch health, nightly CI triage, Dependabot review

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use import-memory, setup and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • amirbironSkill

    import-memory

    Import a memory export from another AI assistant into Claude's memory — conversationally, additively, and with the content treated as data.

    Also in 4 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 6 projects that use this

  • AnthropicSkill

    pptx

    Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.

    Also in 4 projects that use this

  • AnthropicSkill

    pdf

    Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.

    Also in 5 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 5 projects that use this

  • +2 more from anthropics

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 10 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the full morning maintenance sequence in order.

    line 9
  2. Very specific:

    Use the gh CLI to fetch the most recent workflow runs for this repo triggered by a push to the main branch.

    line 15
  3. Distinctive:

    If main is Red:

    line 31
  4. Distinctive:

    Read the logs and identify the root cause.

    line 35
  5. Distinctive:

    Ask: "Should I create a Jira ticket and pick this up now?"

    line 45
  6. Very specific:

    If yes → read and follow .agents/skills/capture/SKILL.md to log it, then read and follow .agents/skills/pickup/SKILL.md with the new ticket …

    line 46
  7. Distinctive:

    If no → note it and continue.

    line 47
  8. Distinctive:

    If main is Green, output: "✅ Main is green." and continue.

    line 49
  9. Distinctive:

    If main is Unknown (no recent push pipelines found), output: "⚪ Main health unknown — no push pipelines found since last check." and …

    line 51
  10. Very specific:

    Read and follow .agents/skills/nightly-check/SKILL.md in full.

    line 57
  11. Distinctive:

    Wait for it to complete before proceeding.

    line 59
  12. Distinctive:

    Wait for it to complete before proceeding.

    line 65
  13. Distinctive:

    If there is nothing to action across all steps, output: "✅ All clear — main is green, nightly runs green, no Dependabot PRs outstanding."

    line 87

“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “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

Morning routine — nightly CI triage + Dependabot review

Run the full morning maintenance sequence in order.


Step 1 — Main branch health check

Use the gh CLI to fetch the most recent workflow runs for this repo triggered by a push to the main branch. Look at the most recent 3 completed push-triggered runs on main (not scheduled runs).

gh run list --branch main --event push --limit 10 --json databaseId,displayTitle,status,conclusion,createdAt,headSha,workflowName

Filter to status: completed runs only (skip any that are in_progress). For each run:

  • Note the run ID, workflow name, commit SHA, triggered-at time, and conclusion.

Determine the current health of main:

  • Green — the most recent push pipeline passed. Main is healthy.
  • Red — the most recent push pipeline failed. Main is broken.
  • Unknown — no recent push pipelines found (e.g. no merges since the last check).

If main is Red:

  1. Fetch the failed jobs: gh run view <run-id> --json jobs
  2. Fetch logs for each failed job: gh run view <run-id> --log-failed
  3. Read the logs and identify the root cause.
  4. Print a prominent warning:
⚠️  MAIN IS BROKEN
Pipeline: <number> — <date>
Failed job: <job name>
Root cause: <one-line summary>
  1. Ask: "Should I create a Jira ticket and pick this up now?"
    • If yes → read and follow .agents/skills/capture/SKILL.md to log it, then read and follow .agents/skills/pickup/SKILL.md with the new ticket key to start work immediately.
    • If no → note it and continue.

If main is Green, output: "✅ Main is green." and continue.

If main is Unknown (no recent push pipelines found), output: "⚪ Main health unknown — no push pipelines found since last check." and continue. Do not treat Unknown as a failure.


Step 2 — Nightly CI check

Read and follow .agents/skills/nightly-check/SKILL.md in full.

Wait for it to complete before proceeding. If it surfaces any tickets that were created and picked up, note the ticket IDs — they are now in progress.

Step 3 — Dependabot review

Read and follow .agents/skills/dependabot-review/SKILL.md in full.

Wait for it to complete before proceeding.

Step 4 — Morning summary

Print a final summary of everything actioned this morning:

## Morning Summary — <today's date>

### Main branch
<Green / Red — root cause if broken, ticket created if actioned>

### Nightly CI
<pass/fail counts, tickets created, any open issues>

### Dependabot
<merged PRs, failing PRs diagnosed, PRs pending>

### Next up
<any tickets now In Progress that need work today>

If there is nothing to action across all steps, output: "✅ All clear — main is green, nightly runs green, no Dependabot PRs outstanding."

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.