add-command

Automate creation of CLI commands and subcommands for the Todoist CLI.

275|17|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Doist/todoist-cli --skill add-command-doist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-command
Source: https://github.com/Doist/todoist-cli/tree/main/.agents/skills/add-command
Command: npx skills add https://github.com/Doist/todoist-cli --skill add-command-doist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of adding new CLI commands or subcommands to the Todoist CLI, simplifying the implementation of new SDK endpoints and extending CLI functionality.

Core Features & Use Cases

  • Automated Command Creation: Streamlines the creation of new CLI commands and subcommands.
  • SDK Endpoint Integration: Facilitates the implementation of new SDK endpoints.
  • CLI Functionality Extension: Enables the expansion of the Todoist CLI's capabilities.
  • Use Case: When developing a new SDK endpoint for the Todoist CLI, this Skill can automate the process of adding the corresponding CLI command and subcommands, reducing manual work and potential errors.

Quick Start

Run the 'add-command' skill to start the process of adding a new CLI command to the Todoist CLI.

Frequently Asked Questions about add-command

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add new CLI commands to the Todoist CLI?

To add new CLI commands to the Todoist CLI, you can automate the creation process by running the 'add-command' skill, which streamlines command generation and integrates new SDK endpoints. This requires modifying the CLI's source code.

What is the best way to integrate new SDK endpoints into a Todoist CLI architecture?

The best way to integrate new SDK endpoints is to use an automated command creation process that extends CLI functionality and generates corresponding subcommands. This approach reduces manual work and potential errors.

Do I need knowledge of the Todoist CLI architecture to automate subcommand creation?

Yes, automating subcommand creation requires existing knowledge of the Todoist CLI architecture and the ability to modify its source code. This prerequisite ensures correct integration of new commands and SDK endpoints.

Why does automating CLI command creation reduce manual work when extending Todoist SDK functionality?

Automating CLI command creation reduces manual work by streamlining the implementation of new SDK endpoints and automatically generating the required commands and subcommands, thereby minimizing potential human errors.

What are the limitations of using an automated skill for CLI command generation?

The main limitation is that the automated command generation process is specifically tailored to the Todoist CLI architecture and requires direct modification of the CLI's source code, making it unsuitable for unsupported platforms.