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
- toddcox-doit/claude-skillstheir own version, first seen Nov 16, 2026
- delorenj/skillstheir own version, first seen Nov 7, 2026
- thatmike1/claude-skillstheir own version, first seen Oct 26, 2026
- sammollaei/law-firm-skillstheir own version, first seen Oct 17, 2026
- shahbazaliofficial/Claude-Skillstheir own version, first seen Oct 13, 2026
- gufranco/claude-engineering-rulestheir own version, first seen Oct 12, 2026
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.
amirbironSkillimport-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
VercelSkillsetup
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
AnthropicSkillpptx
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
AnthropicSkillpdf
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
SentrySkillskill-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
Other versions21 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 21
- seandavi/lifeos-template★ 46same name
- Hassaan146/claude-skills★ 18same name
- delorenj/skills★ 17same name
- thatmike1/claude-skills★ 10same name
- gufranco/claude-engineering-rules★ 3same name
- Azul-Digital-Partners/cos-kit★ 2same name
- Jerovino/EngineeringOS-template★ 2same name
- Rish-Modi/career-agent★ 2same name
- yuchenz27/wikigarden★ 2same name
- InanisV/my-claude-skills★ 1same name
11 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- assign-epicSkill
- briefingSkill
- bump-versionSkill
- captureSkill
- consultantSkill
- dependabot-reviewSkill
- fix-cicdSkill
- log-timeSkill
- morlockSkill
- multi-repoSkill
- nightly-checkSkill
- pickupSkill
- pr-action-review-mine-loopSkill
- pr-action-reviewSkill
- pr-choreSkill
- pr-review-loopSkill
- prSkill
- pushSkill
- qa-review-actionSkill
- refineSkill
- runSkill
- syncSkill
- wrap-upSkill
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
- Distinctive: line 9
Run the full morning maintenance sequence in order.
- Very specific: line 15
Use the gh CLI to fetch the most recent workflow runs for this repo triggered by a push to the main branch.
- Distinctive: line 31
If main is Red:
- Distinctive: line 35
Read the logs and identify the root cause.
- Distinctive: line 45
Ask: "Should I create a Jira ticket and pick this up now?"
- Very specific: line 46
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 …
- Distinctive: line 47
If no → note it and continue.
- Distinctive: line 49
If main is Green, output: "✅ Main is green." and continue.
- Distinctive: line 51
If main is Unknown (no recent push pipelines found), output: "⚪ Main health unknown — no push pipelines found since last check." and …
- Very specific: line 57
Read and follow .agents/skills/nightly-check/SKILL.md in full.
- Distinctive: line 59
Wait for it to complete before proceeding.
- Distinctive: line 65
Wait for it to complete before proceeding.
- Distinctive: line 87
If there is nothing to action across all steps, output: "✅ All clear — main is green, nightly runs green, no Dependabot PRs outstanding."
“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.
Files
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,workflowNameFilter 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:
- Fetch the failed jobs:
gh run view <run-id> --json jobs - Fetch logs for each failed job:
gh run view <run-id> --log-failed - Read the logs and identify the root cause.
- Print a prominent warning:
⚠️ MAIN IS BROKEN
Pipeline: <number> — <date>
Failed job: <job name>
Root cause: <one-line summary>- Ask: "Should I create a Jira ticket and pick this up now?"
- If yes → read and follow
.agents/skills/capture/SKILL.mdto log it, then read and follow.agents/skills/pickup/SKILL.mdwith the new ticket key to start work immediately. - If no → note it and continue.
- If yes → read and follow
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."
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
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.

