deadlines
Skill0 starsChanged 29 days agoMITView on GitHub
List todos due today and overdue pending ones (frontmatter only, cheap). Use when the user asks: what's due, what's overdue, what do I have this week, check deadlines.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- anthropics/claude-for-legaltheir own version, first seen May 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- anthropics/claude-for-legal★ 9.5ksame name
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 repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-entrySkill
- add-todoSkill
- complete-todoSkill
- financeSkill
- financial-summarySkill
- kb-add-folderSkill
- kb-archiveSkill
- kb-auditSkill
- kb-promoteSkill
- kbSkill
- kb-synthesizeSkill
- meetingSkill
- studySkill
- study-statusSkill
- study-unstudiedSkill
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
- Distinctive: line 8
Read-only skill. No lock needed.
- Distinctive: line 20
Do not auto-trigger on every session start — only when the user asks, or when a task explicitly relates to deadlines / scheduling.
≈ “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.
Files
/deadlines
Read-only skill. No lock needed.
- Dispatch an Explore subagent with this task:
Read frontmatter ONLY from every file in
todos/*.md(ignoretodos/completed/*andtodos/INDEX.md). Extract thedeadline:andstatus:fields from each — use grep (deadline:andstatus:) rather than full file reads, to keep this cheap. Return a compact list:- "Due today": items where
status == pendingANDdeadline == today - "Overdue": items where
status == pendingANDdeadline < today, sorted by how overdue (most overdue first) - "No pending deadlines today or overdue": if the lists are empty.
Format each item:
- <deadline> — <title> (P:<priority>) — <slug>.
- "Due today": items where
- Receive the list; surface to user.
- For overdue items, gently prompt: "Want to mark complete (
/complete-todo <slug>), update the deadline, or cancel?"
Do not auto-trigger on every session start — only when the user asks, or when a task explicitly relates to deadlines / scheduling.
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.