agentleFS
Cassius2584Cassius2584/claude-uni-workspace/.claude/skills/whats-due/SKILL.md

whats-due

Skill5 starsChanged 26 days agoMITView on GitHub

Summarise upcoming uni and job-application deadlines from the workspace. Use when the user asks "what's due", "what's coming up", "what should I work on", "deadlines this week/month", or asks about their workload.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read every assessment note (kind: assessment in projects/*/assessments/) whose status isn't Submitted or Marked, and …

    line 8
  2. Very specific:

    Put applications in the same table with module "Careers", and tasks with module = their area (weight "–").

    line 19
  3. Distinctive:

    If a Google Calendar connector is available, add one line on how busy the next few days look (lectures and events), so the advice fits the …

    line 20
  4. Very specific:

    If the student tells you something's been submitted or marked, update that assessment note's status/mark and add a log line.

    line 24
  5. Distinctive:

    Keep it tight. It's a glance, not a report.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

What's due

  1. Read every assessment note (kind: assessment in projects/*/assessments/) whose status isn't Submitted or Marked, and careers/APPLICATIONS.md if it exists (or, if careers/TRACKER.md exists, the roles in that tracker, whether Obsidian role notes or a spreadsheet, with a deadline or next-step date that aren't expired, rejected, withdrawn or filtered out) (closing dates and next steps for applications not yet submitted), and, if tasks/ exists, every task note (kind: task) whose status isn't Done and that has a due date or status: Doing. Use today's date. Default window: the next 14 days, plus anything overdue and not marked Submitted. Use the window the student asks for if they give one.
  2. For each item in the window, look in the module's coursework/<item>/ folder (linked from the assessment note) to judge progress: is there a brief, a draft, nothing? Items with a blank due but a due_note in the window (e.g. "Jan 2027 exam period") count as due then.
  3. Reply with a short table in date order: date · module · item · weight · days left · status/progress. Put applications in the same table with module "Careers", and tasks with module = their area (weight "–"). If a Google Calendar connector is available, add one line on how busy the next few days look (lectures and events), so the advice fits the free time. Then give 1–3 lines on what to do first, weighted by due date × weight × how little is done. Call out clusters, formative deadlines worth doing anyway, and admin items (group registration, preference forms) that are easy to miss.
  4. If the student tells you something's been submitted or marked, update that assessment note's status/mark and add a log line.

Keep it tight. It's a glance, not a report.

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.