MyLister - Organizer

Lister — Natural Language Task Management

Skill name: lister Description: Natural language task management with MyLister.dev — add, view, update, move, and organize to-do items across lists via conversational commands.

When to Use This Skill

Use this skill whenever the user wants to manage tasks, to-do items, or lists using natural language. Trigger phrases include (but are not limited to):

• "create a new list" — create a new list
• "delete my list" — delete a list
• "add to list" — create a new task item
• "get my lists" — view all lists or items in a list
• "priority items" — see urgent/important items
• "mark done" — complete an item
• "remove item" — delete an item
• "update item" — change an item's text or priority
• "move item" — transfer an item to another list
• "note for item" — attach a note to an item
• "comment on item" — add, view, update, or delete comments on shared items
• "comment on note" — add, view, update, or delete comments on item notes
• "reminder" — add or update simple item reminders
• "project list" — create project lists and project items with start/end/duration/assignee metadata
• "export list" — export a list as JSON or HTML
• "email list" — email a list to someone
• "export priority" — export all priority items
• "email priority" — email priority items to someone
• "export item" — export one item as JSON or HTML
• "email item" — email one item
• "attachment" — upload or remove an item attachment
• "upload image/voice" — upload media and optionally associate it with a list or item
• "API health/version" — inspect the deployed API status

Configuration

The following environment variables must be set before invoking the skill:

How to Invoke

The skill exposes a handleCommand(input: string): Promise function. Pass any natural language string and receive a formatted response.

CLI:

node dist/index.js 

As a module:

import { handleCommand } from './dist/index.js';
const result = await handleCommand('add "buy milk" to my groceries list');
console.log(result);

Supported Commands

1. Add Item

Add a new task to a specific list. Use quotes for the task text. Mark items as priority with the word "priority" or "urgent".

Keywords: add, create, new, put

Create payload support: item creation can include inline notes, inline comments, reminder, and project metadata (startDate, endDate, durationMinutes, assignedTo) when those phrases are present.

Project metadata is accepted by the API for project lists. If no assignee is supplied, the API assigns the item to the project owner. An explicit assignee must be the owner or an edit/admin collaborator.

2. Get / List Items

View all items in a specific list, or show all lists if no list name is given.

Keywords: get, show, list, view, find, search

3. Priority Items

Get all items marked as priority/urgent across all lists.

Keywords: priority, urgent, important (combined with get/show/list)

4. Mark Done

Mark a task item as completed.

Keywords: mark, complete, done, finish

5. Remove Item

Delete a task item permanently.

Keywords: remove, delete, drop, clear

6. Update Item

Change an item's text or set it as priority.

Keywords: update, edit, change, modify, rename

7. Move Item

Transfer an item from its current list to another list.

Keywords: move, transfer

8. Add Note

Attach a note to an item.

Keywords: note, memo

8c. Attachments and Media

Upload files directly from the local filesystem, or remove an existing item attachment/image.

Uploads use multipart form data. The skill keeps the API key header but deliberately lets fetch set the multipart boundary.

8a. Item Comments

Add, view, update, or delete comments on an item. This is useful for shared items.

8b. Note Comments

Add, view, update, or delete comments on a note attached to an item.

9. Export List

Export a list to JSON or HTML format.

Keywords: export, as json, as html, theme, with archived

9a. Export Item

Export one item as JSON or HTML.

10a. Email Item

Email (or send) one item as an HTML export.

10. Email List

Email (or send) a list to yourself or someone else.

Keywords: email, send, to

11. Export Priority Items

Export all priority/urgent items across all lists.

Keywords: export, priority, urgent, important

12. Email Priority Items

Email (or send) all priority items to yourself or someone else.

Keywords: email, send, priority, urgent, important

13. Create List

Create a new list.

Keywords: create, make, add

List types: standard, notebook, and project are supported. journal maps to notebook. An existing list can change type with update my [list] list to project (or notebook/standard).

14. Delete List

Delete an existing list (all items are permanently removed).

Keywords: delete

Note: List name matching is case-insensitive.

Permanent lists require the explicit permanently or force qualifier; the API sends this as ?force=true.

15. Search

Search across all lists and items.

Keywords: search, find (combined with search terms, not list name)

Note: The production API includes notes by default; with notes remains supported for clarity.

16. Lists Summary

Get a summary of all lists with item counts.

Keywords: summary

17. Archive List

Archive a list (hides it from normal views).

Keywords: archive

18. Unarchive List

Restore an archived list.

Keywords: unarchive

Note: archived lists are automatically searched when resolving list names.

19. Share List

Share a list with another user.

Keywords: share, with, as

Permissions: read, edit (default), admin

20. List Users

Show users who have access to a list.

Keywords: users, for, of

21. Remove User From List

Remove a user's access from a shared list.

Keywords: remove user, from

22. Update Note

Edit the text of an existing note on an item.

Keywords: update note, edit note, change note

23. Delete Note

Delete a note from an item.

Keywords: delete note, remove note

24. Update List User Permission

Change a user's permission level on a shared list.

Permissions: read, edit, admin

Keywords: update user, change user, set permission

25. Reorder Lists

Change the display order of lists.

Keywords: reorder lists

26. Reorder Items

Change the display order of items within a list.

Keywords: reorder items

27. Move Completed Items

Move all completed items from one list to another.

Keywords: move completed

28. Update List

Rename or update a list's properties.

Keywords: update list, rename list, edit list

29. Get List Details

View detailed information about a specific list.

Keywords: list details, list info

30. Reorder Notes

Set the order of notes embedded in an item.

31. API Status

Check the deployed public API without touching list data.

31a. API Environment and Credentials

Switch between configured API environments or apply API keys at runtime.

---

API Reference

The skill uses the Public API (/v1/) endpoints on https://api.mylister.dev, which are accessible via API key.

Authentication: API key via the X-API-Key header for all /v1/ endpoints. Bearer tokens are not accepted on this public API surface.

Important: Always use /v1/ endpoints on api.mylister.dev. Exports may return JSON or HTML; uploads/status responses are JSON. The skill validates the response host and content type accordingly.

Response Format

Responses are formatted with emoji indicators:

• ✅ Success — followed by details or item lists
• ❌ Error — with explanation of what went wrong
• ❓ Unknown — with helpful suggestions

Item lists include:

• Numbered entries
• 🔥 for priority items
• ✅ for completed items

Error Handling

The skill validates input before making API calls. Common validation messages:

• Missing quoted text for add/update → prompts user to use quotes
• Missing list name → prompts user to specify a list
• Missing item ID → prompts user to provide an item ID
• List not found → tells user the list name wasn't found
• API errors → surfaces the error message from the API

File Layout

MyLister-Skill/
├── SKILL.md          ← This file (skill definition for OpenClaw)
├── skill.json        ← Skill metadata
├── src/
│   └── index.ts      ← TypeScript source
├── dist/
│   └── index.js      ← Compiled JavaScript (entry point)
├── package.json
└── tsconfig.json

Notes for Agents

1. Always quote item text — the parser extracts text between quotes (" " or ' '). If the user doesn't use quotes, ask them to.
2. List names are case-insensitive — today, Today, and TODAY all match the same list.
3. IDs are 24-character hex strings in the public API (the parser also accepts numeric IDs for compatibility). Responses may include populated creator/assignee data on shared and project items.
4. The skill auto-resolves list names to IDs — users don't need to know internal list IDs; they use friendly names.
5. If the list doesn't exist, the skill will report an error — it does not auto-create lists. The user must create the list first or use an existing one.
6. Archived lists are automatically included in list name resolution — if a list name isn't found in active lists, the skill searches archived lists too.
7. Search uses the /v1/search endpoint. The production API includes note content by default.
8. Sharing requires a user ID (email) and permission level (read, edit, or admin).
9. Item statuses can be new, in-progress, or complete (the in-progress status is new).
10. Item creation no longer requires listId in the request body — it's derived from the URL path.
11. API key creation now returns 201 Created (was 200 OK).
12. Note creation now returns 201 Created (was 200 OK).
13. The default public API host is https://api.mylister.dev. Override with LISTER_BASE_URL, LISTER_PRODUCTION_BASE_URL, or LISTER_STAGING_BASE_URL per environment.
14. Comments are first-class resources on both items and notes. Use the comment endpoints instead of treating item comments as notes.
15. Move completed reorders completed items to the bottom of the same list; it no longer moves them to another list.
16. Notebook lists are created by passing type: "notebook" when the user asks for a notebook or journal list.
17. Project lists are created by passing type: "project" when the user asks for a project list.
18. Item creation with notes/comments uses the notes and comments arrays in the initial /v1/lists/{id}/items request when the user says with note "..." or with comment "...".
19. Project item metadata is sent in the project object with supported fields startDate, endDate, durationMinutes, and assignedTo. The API validates assignedTo; use the owner or an edit/admin collaborator.
20. Project items are intentionally excluded from the priority-items surface by the API; query the project list directly for project work.
21. Archived item reads use GET /v1/lists/{id}/items?includeArchived=true; the skill now forwards with archived for list item reads.
22. The deployed API exposes item exports, note reorder, attachments, media upload, presigned file URLs, health, and version routes in addition to list/task CRUD.