agentleFS
jigripokrijigripokri/POHA/skills/gsd/SKILL.md

gsd

Skill121 starsChanged 6 months agoMITView on GitHub

Generate a prioritized punch list from open commitments + tasks, right now. Get Shit Done.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. L2-ootm/L2-ATLAS-PROJECT★ 2same name
    2. 354685856-sn/claude-code-skills★ 0same 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 repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    P0 — Overdue + blocking someone else: do today, in the next 2 hours if possible

    line 20
  2. Distinctive:

    P1 — Overdue, self-blocked: do today

    line 21
  3. Distinctive:

    When the user feels overwhelmed and wants to be told what to do.

    line 56

≈ “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

/gsd

User says "/gsd" or "what should I do next?" You return a prioritized punch list.

Recipe

  1. Read memory/commitments.md. Filter to PENDING + OVERDUE.
  2. Read Google Tasks (via Chrome → tasks.google.com). All open items from primary lists.
  3. Read memory/life.md > This Month / This Week. Anything that should be active.
  4. Prioritize using the GSD ranking:

    • P0 — Overdue + blocking someone else: do today, in the next 2 hours if possible
    • P1 — Overdue, self-blocked: do today
    • P2 — Today's commitments: scheduled for today, not done
    • P3 — This week: due in next 5 days
    • P4 — Quick wins: < 10 min items, batch them
    • P5 — Aging but not urgent: > 7 days old, no due date — flag for review/punt
  5. Format the output as:
🎯 GSD — <current time>

P0 (do now):
1. <title> — <est time> — <one-line why it matters>
2. ...

P1 (do today):
1. <title> — <est time>
...

P2 (today's scheduled):
...

Quick wins (5 min, batch these):
- <item>
- <item>

To punt or kill: <N> items aging past usefulness — review during weekly?

**Wildcard:** <one observation about the list — pattern, hidden priority, missing item>
  1. Suggest a focus block. "If you only have 90 min today, do P0 + the top 2 of P1."

What this skill is for

When the user feels overwhelmed and wants to be told what to do. Returns a clear ranked list, not a vague "you have a lot going on."

What this skill is NOT

  • A todo list manager. The exocortex doesn't modify Google Tasks unless asked.
  • A motivator. No "you got this!" — direct ranking, that's it.

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.