obsidian-tasks-syntax
Skill2 starsChanged 2 months agoMITView on GitHub
Creates and edits Obsidian Tasks plugin task lines with emoji-based or Dataview-style dates, priorities, recurrence, dependencies, and statuses. Use when the user asks to add a task, create a todo, set a due date, change priority, add recurrence, make a recurring reminder, edit a checkbox line, or anything involving task emoji signifiers (📅⏳🛫🔁) or Dataview-style task fields ([due:: ...], [priority:: ...]). Also use when the user says "remind me to", "add a todo", "new checkbox", or wants to understand the task format.
In this repository8 other files it gives its agents.
- obsidian-chartsSkill
- obsidian-dataviewSkill
- obsidian-graph-auditSkill
- obsidian-graphSkill
- obsidian-heatmapSkill
- obsidian-meta-bindSkill
- obsidian-tasks-cliSkill
- obsidian-tasks-querySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 62
Choosing between dates: Use 📅 due for deadlines. Use ⏳ scheduled to defer a task you don't want cluttering today's view.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Creating Tasks
Task Format Setting
The Tasks plugin has two mutually exclusive ways to write metadata on a task line, chosen in Settings → Tasks → Task Format:
- Tasks Emoji Format (default) — emoji signifiers, positional. Covered below.
- Dataview Format — inline fields (
[key:: value]), read by both Tasks and the Dataview plugin.
Check which one a vault uses before writing a task line — check taskFormat in the Tasks plugin's data.json ("emoji" or "dataview"), or ask the user. Writing emoji signifiers into a vault set to Dataview format (or vice versa) means Tasks won't parse the metadata at all.
Task Line Format — Tasks Emoji Format
- [ ] Task description 🔼 🔁 every week 🛫 2025-01-01 ⏳ 2025-01-05 📅 2025-01-10Order matters: description first, then priority, then recurrence, then dates. The Tasks plugin parses emoji signifiers by position — putting them out of order can cause misreads. Dates are always YYYY-MM-DD — natural language like "tomorrow" is not recognized on task lines (it only works in query blocks).
Task Line Format — Dataview Format
- [ ] Task description [priority:: medium] [repeat:: every week] [start:: 2025-01-01] [scheduled:: 2025-01-05] [due:: 2025-01-10]Fields are matched by name, not position — order does not matter. Each field is its own [key:: value] bracket; don't combine several keys inside one bracket. Dates are still always YYYY-MM-DD.
Emoji → Dataview field name:
| Emoji | Dataview field | Note |
| 📅 due date | due | |
| ⏳ scheduled date | scheduled | |
| 🛫 start date | start | |
| ➕ created date | created | |
| ✅ done date | completion | not done |
| ❌ cancelled date | cancelled | |
| 🔺⏫🔼🔽⏬ priority | priority | values: highest, high, medium, low, lowest (omit for Normal) |
| 🔁 recurrence | repeat | not recurrence; rule text unchanged (every week, etc.) |
| 🆔 id | id | |
| ⛔ dependsOn | dependsOn |
onCompletion (auto-delete/archive on done, no emoji equivalent) is also available as [onCompletion:: delete] / [onCompletion:: keep].
Dates
| Emoji | Name | When to use |
| 📅 | Due date | The deadline — when the task must be finished |
| ⏳ | Scheduled date | When you plan to work on it (hides task from views until this date) |
| 🛫 | Start date | Earliest date the task becomes actionable (blocks it before then) |
| ➕ | Created date | Auto-set by Tasks plugin, or add manually for tracking |
| ✅ | Done date | Auto-set when completing a task |
| ❌ | Cancelled date | Auto-set when cancelling |
Choosing between dates: Use 📅 due for deadlines. Use ⏳ scheduled to defer a task you don't want cluttering today's view. Use 🛫 start for tasks that literally can't begin before a date (e.g., waiting for access). Most tasks only need 📅 due.
Priority (decreasing)
🔺 Highest · ⏫ High · 🔼 Medium · (none = Normal) · 🔽 Low · ⏬ Lowest
Normal sits between Low and Medium — tasks without a priority emoji are higher than Low. Only add priority when it meaningfully differs from normal.
Recurrence
🔁 followed by a rule starting with every. Requires at least one date.
- [ ] Weekly review 🔁 every Friday 📅 2025-01-10
- [ ] Pay rent 🔁 every month on the 1st 📅 2025-02-01
- [ ] Water plants 🔁 every 3 days when done 📅 2025-01-10Patterns: every day, every weekday, every week on Monday, Wednesday, every 2 weeks, every month on the 1st, every month on the last Friday, every year, every January on the 15th.
when done — add this to base the next occurrence on the completion date instead of the original date. Use it for flexible-interval tasks (like watering plants) where the gap matters more than a fixed schedule.
Dependencies
| Emoji | Field |
| 🆔 | id — identifies this task |
| ⛔ | dependsOn — blocks until the referenced id is done |
- [ ] Write draft 🆔 draft1
- [ ] Review draft ⛔ draft1A blocked task (⛔) won't appear in "not blocked" queries until its dependency is completed.
Statuses
| Checkbox | Type | Query match |
[ ] | TODO | not done |
[/] | IN_PROGRESS | not done |
[x] | DONE | done |
[-] | CANCELLED | done |
Custom statuses (ON_HOLD, NON_TASK, etc.) depend on theme/CSS configuration.
Examples
- [ ] Buy groceries 📅 2025-04-10
- [ ] Weekly review 🔼 🔁 every Friday 📅 2025-04-11
- [ ] Start writing article 🛫 2025-04-07 📅 2025-04-14
- [ ] Research topic ⏳ 2025-04-08 📅 2025-04-12
- [/] Working on presentation 📅 2025-04-10
- [ ] Prepare slides 🆔 slides1 📅 2025-04-09
- [ ] Send presentation ⛔ slides1 📅 2025-04-10
- [ ] Water plants 🔁 every 3 days when done 📅 2025-04-08
- [ ] Pay rent 🔺 🔁 every month on the 1st 📅 2025-05-01Does 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.

