sb-task
/sb-task
Manage tasks in the Trilium Symbiont: create under a hub, area or project with a Board clone, set status, move. Use when the user wants a new task or to change one. Card order stays human-owned.
- Author
- chaeller ↗
- Repository
- trilium-symbiont ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Manage tasks in the Trilium Symbiont: create under a hub, area or project with a Board clone, set status, move. Use when the user wants a new task or to change one. Card order stays human-owned.
Original author description
Manage tasks in the Trilium Symbiont: create under a hub, area or project with a Board clone, set status, move. Use when the user wants a new task or to change one. Card order stays human-owned.
How it works
SKILL.md has no level-two headings · 49 lines, 554 words
SKILL.md preview
--- name: sb-task description: "Manage tasks in the Trilium Symbiont: create under a hub, area or project with a Board clone, set status, move. Use when the user wants a new task or to change one. Card order stays human-owned." --- # Task — task mechanics (Hubs + Cockpit Board) You are operating on the user's **Trilium Symbiont** via the Trilium MCP server. **First** (umbrella `_Schema` §1): load the umbrella `_Schema` (`#sbType=schema` directly under `root`) and read it fully; check that `#sbVersion` has major version `1` (e.g. `1.0.0`); read the **Principles** hub page; then read the **Cockpit** `_Schema` (Board, tasks, Model X) and the **Hubs** `_Schema` (homes). **A task** is a note with a `status` label (no `#sbType`). Its **original lives in its home** — a hub, area or project in Hubs; the Kanban Board (`#viewType=board` within Cockpit) holds a **clone**. The columns are the options of the Board's `label:status` definition — read them, never assume them. **Operations:** - **New task:** find the home the user names (search `#sbType=hub|area|project` within Hubs; confirm if several match). **No home named →** offer a fitting one once (from `Hubs/_Index` and the Principles); if none fits or the user declines, create the task **directly on the Board** (a plain to-do needs no home). Never create a hub, area or project unless the user asks for it. Create the note under the home or on the Board (`type=text`, the user's wording as title, details as content), set `status` = the Board's **first** column, set other card attributes the user gives (e.g. due date → `startTime`, only attributes the Board defines), icon `bx bx-task`; then `clone_note` it into the Board. - **New subtask (Model X):** a child note under the parent task — **no `status`, no Board clone**. If subtasks need their own cards, suggest turning the parent into a project. - **Set status / move column:** set `status` to one of the Board's columns. Unknown column → ask, never invent one. - **Done:** a finished task is **deleted** or gets **`#archived`** — never a "done" column (Cockpit `_Schema` §2). Ask which one if the user doesn't say; delete only after an explicit yes. Archiving or deleting the original also removes its Board card. - **Move home:** `move_note` the original under the new hub, area or project (tree position = membership) and make sure the Board clone still exists (re-clone if the move detached it). - **Give a Board task a home** (on request): move the original under the hub, area or project and clone it back onto the Board. Home-less tasks on the Board are allowed; never move one without a request. - **Reorder / reprioritize:** card order is priority and **human-owned** — drag and drop per column. The agent cannot reorder over MCP (no branch-position tool; `move_note` would re-parent the card). Suggest an order, considering the Principles, and never attempt it. - **Project ↔ area:** changing `#sbType=project` to `area` (or finishing a project with `#archived`) only on explicit request. **Rules:** respect `#sbControl` of the home (umbrella §5) — with effective control `propose`, file a proposal instead of changing an existing task; creating a task the user explicitly asks for is always allowed. Log every mutation as one line in `Hubs/_Log`. Link the task (clickable) in your answer. **End your output with exactly one status marker** on its own final line (see steering "End-of-run status marker"): `✅ Done` / `❓ Needs your answer` / `⏸️ Awaiting confirmation` / `⚠️ Done with caveats` / `🚫 Refused (out of scope)`. Input: the user's request (for a slash command, the text after it).
Versions
The database has no other skills named sb-task.
Database snapshot: 13.11.2026 · package version 6772b054909a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90sb-hub
Create a hub in the Trilium Symbiont on request, refresh a hub page or its synthesis, or propose a split when a hub grows too big. Use when the user asks for a new hub or to update one. - 96sb-triage
Process open captures (Cockpit / Untriaged) of the Trilium Symbiont: file each under a hub, area or project, make it a task, keep it in the journal or discard it. Use when the user asks to triage. - 90trilium-workflows
Task recipes and safety rules for working with a Trilium Notes instance through the trilium MCP server beyond plain create/search - journal and day notes, the inbox, organizing the tree (move, clone, reorder), labels and relations, attachments, revisions and recovering lost… - 90workspace-assistant
This skill should be used when the user asks to create quick tasks, log bugs, track one-off work items, or manage tasks in the default project. Triggers on phrases like 'add a task', 'log a bug', 'track this', 'create a quick task', 'update task status'. - 100trilium-capture
Write findings, clipped material and long documents into a self-hosted Trilium Notes instance over its native MCP, filed under a project, labelled from a controlled vocabulary, and revised in place rather than duplicated. Use when the user says to store, capture, save or file… - 100tasknotes
Manage tasks in Obsidian via TaskNotes plugin API. Use when user wants to create tasks, list tasks, query by status or project, update task status, delete tasks, or check what they need to do.