agentleFS
jsuchetjsuchet/jonathan-skills-lab/skills/task/SKILL.md

task

Skill1 starsChanged 5 months agoMITView on GitHub

Create a formatted checkbox task in today's daily note, parsing an optional due date and priority out of natural language. Use this throughout your day to capture tasks quickly without breaking flow.

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use inbox, grill-me 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.
  • kv0906Skill

    inbox

    Quick capture mode (with content) or batch processing mode (no content). GTD-style routing of inbox items to proper folders. Use "/inbox thought to capture" or "/inbox" to process.

    Also in 3 projects that use this

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 5 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 4 projects that use this

  • OpenAISkill

    audit

    Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 3 projects that use this

  • Google CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 26 edited versions we read keep these.

  • 5

    Distinctive

    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:

    If no priority is specified, omit the tag (do not default to medium).

    line 31
  2. Distinctive:

    If NO: create it from your daily-note template, then proceed.

    line 37
  3. Distinctive:

    If YES: read the current contents.

    line 38
  4. Distinctive:

    Only include tags that were detected.

    line 44
  5. Distinctive:

    Do NOT: add commentary or suggestions.

    line 51

“Common” is measured: kept by at least 6 in 10 of the 26 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

/task <text>

Creates a formatted checkbox task in today's daily note under the ## Tasks section, extracting an optional due date and priority from the text.

Customize before use: set <daily-notes-dir> to where your daily notes live (e.g. periodic/daily/). See CUSTOMIZE.md.

Steps

  1. Parse the input — everything after /task is the task description.
  2. Extract optional metadata from the text:
    • Due date: patterns like by Friday, due 2026-02-20, tomorrow, next week.
      • Convert to @due(YYYY-MM-DD) format.
      • Examples: "by Friday" → next Friday; "tomorrow" → tomorrow's date; "next week" → next Monday; "due 2026-02-20" → use as-is.
    • Priority: urgent, high, medium, low, p1, p2, p3.
      • urgent / p1 / high → #priority/high
      • medium / p2 → #priority/medium
      • low / p3 → #priority/low
      • If no priority is specified, omit the tag (do not default to medium).
  3. Determine today's date and construct the daily note path: <daily-notes-dir>/YYYY-MM-DD.md.
  4. Check if today's daily note exists:
    • If NO: create it from your daily-note template, then proceed.
    • If YES: read the current contents.
  5. Append the task under the ## Tasks section:
    - [ ] Task description #priority/high @due(YYYY-MM-DD)
    Only include tags that were detected.
  6. Confirm with a brief response:
    ✅ Task added: [task description]
  7. Do NOT add commentary or suggestions. Just create the task and confirm.

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.