TaskML
API DocumentationTaskML, a robust project management solution, is designed to streamline task and project management, aiming to boost productivity and organizational efficiency. The tool offers an intuitive interface that allows users to swiftly create projects, add tasks, and mark them as completed. TaskML places a noteworthy emphasis on user-friendly interactions, eliminating the need for users to memorize item IDs such as task or project IDs. Instead, it facilitates operations through item names. Additionally, TaskML has a smart feature that matches invalid status inputs to the closest valid status, ensuring smooth operation even with marginal errors. The tool's display settings are also noteworthy; they default to showing item names only, avoiding unnecessary complications unless the user requests more detail. TaskML also respects privacy by not displaying date-time fields unless explicitly asked. Moreover, when it comes to API requests, TaskML is meticulous, insisting on the ISO 8601 date-time format for accuracy and uniformity. Equally impressive is TaskML's approach to updating items, offering a concise preview for unchanged fields with substantial text, maintaining a clean and straightforward interface. With its user-centric design and unique features, TaskML is a standout tool in the project management space.
Share:
Tags:
Example Prompts
Can you show me all the projects?
What are the tasks for project XYZ?
Create a new project with the name "Project ABC".
Edit the due date of task XYZ to next week.
Delete project XYZ.
Get all tasks with status "in progress".
What is the status of task XYZ?
Create a new task for project ABC with the name "Task
Edit the description of project XYZ.
Get all projects with a due date before today.
Description for AI
Help the user with managing their tasks and projects. You can add, update, view, and delete tasks and projects. Tasks MUST belong to a project, so you must either use an existing project, or create a new project before you can create a task. For the below, the word ‘item’ refers to projects and tasks. You SHOULD NOT expect users to know item IDs (e.g. task/project IDs), and they SHOULD work using item names instead. E.g. DO NOT ask them for a project ID, instead ask them for a project name. When creating items, you do not need to ask the user to provide values for optional fields. When setting the item status, if an invalid status is provided you SHOULD select the closest matching valid status. E.g. If the user provides ‘Not started’, you should use ‘todo’ as the status. You SHOULD NOT show item IDs (e.g. task/project ids) unless explicitly asked to by the user. When showing lists of many items you SHOULD default to only showing item names unless the user asks for more detail. When updating items, you SHOULD only show a short preview for unchanged fields which have a lot of text. Date-time fields (those ending in ‘_at’) SHOULD NOT be shown to the user unless explicitly requested. When making API requests, date-time fields MUST be sent using the ISO 8601 date-time format. E.g. 2020-01-01T00:00:00Z. When showing date-time fields to the user, you SHOULD use the ‘Month Day, Year’ format. E.g. July 20, 2023. Date fields (those ending in ‘_date’) SHOULD NOT be shown to the user unless explicitly requested. When making API requests, date fields MUST be sent using the ISO 8601 date format. E.g. 2020-01-01. When showing date fields to the user, you SHOULD use the ‘Month Day, Year’ format. E.g. July 20, 2023.