How do I install the Task API Helper skill?

Run npx skillmds@latest add tkubica12/task-api-helper in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Task API Helper safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Task API Helper?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Task API Helper free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Task API Helper?

tkubica12 (@tkubica12) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Task API Helper by tkubica12 — Agent Skill

Name: Task API Helper
Author: tkubica12

Task API Helper

Helper skill for teams using the shared Task API REST service and its task_cli.py wrapper. Use when the user needs to interact with project tasks: list tasks, filter them by status, fetch task details, add comments, and work within the current shared Task API workflow. The skill knows the API contract, CLI command set, and the improvement process for proposing upstream enhancements when teams discover repetitive or awkward workflows.

tkubica12 3eb208a 5 files · 18.8 KB Updated Sep 17, 2026

File contents

task-api-helper

Overview

This skill helps you work with the Task API — a shared REST service for project task management — and its companion CLI wrapper task_cli.py. Use this skill when you need to:

Query or update project tasks via the REST API
Run the task_cli.py wrapper commands
Understand the current shared Task API workflow
Navigate the improvement process to propose a new command upstream

Environment Setup

# Preferred: configure the installed skill locally
cp .env.example .env

# Then edit .env
TASK_API_URL="https://tasks.internal.example.com"

# Optional: authentication token
TASK_API_TOKEN="<your-token>"

The installed skill reads configuration in this order:

--api-url / --token
.env in the installed skill folder
shell environment variables

Using .env in the installed skill folder is the preferred demo setup because the agent may execute in a different shell than the one where environment variables were exported.

Supported CLI Commands

list-tasks

python task_cli.py list-tasks [--status <status>] [--api-url <url>]

Lists all tasks. Use --status to filter by any status value the API supports, for example waiting-for-response or resolved. Omit --status to return all tasks.

get-task

python task_cli.py get-task TASK_ID [--api-url <url>]

Fetches a single task by ID including its comment thread.

add-comment

python task_cli.py add-comment TASK_ID "Your comment text" [--api-url <url>]

Appends a comment to a single task. The comment text is a positional argument.

Workflow evolution

This skill is intentionally centrally maintained. If you discover that a common workflow feels repetitive, awkward, or missing a useful higher-level command, do not jump straight to an upstream issue.

First:

try a temporary local proof of concept in the current repo
verify whether it actually helps
capture the exact command or behavior you tested
remove the local patch

Only then open an enhancement issue in the catalog repository using the Task API Enhancement template. See references/IMPROVEMENT-PROCESS.md for the full flow.

Quick Diagnostics

# Verify CLI is functional
python task_cli.py --help

# List tasks waiting for a response using the configured .env / --api-url / env var
python task_cli.py list-tasks --status waiting-for-response

Improvement Requests

This skill is centrally maintained. Proposed enhancements should be backed by a short local proof of concept in the consumer repo before an upstream issue is opened. Reference the issue number in any PR that implements the change. See references/IMPROVEMENT-PROCESS.md for the full lifecycle.

---name: task-api-helperdescription: Helper skill for teams using the shared Task API REST service and its task_cli.py wrapper. Use when the user needs to interact with project tasks: list tasks, filter them by status, fetch task details, add comments, and work within the current shared Task API workflow. The skill knows the API contract, CLI command set, and the improvement process for proposing upstream enhancements when teams discover repetitive or awkward workflows.license: MIT---# task-api-helper## OverviewThis skill helps you work with the **Task API** — a shared REST service for project task management — and its companion CLI wrapper `task_cli.py`. Use this skill when you need to:- Query or update project tasks via the REST API- Run the `task_cli.py` wrapper commands- Understand the current shared Task API workflow- Navigate the improvement process to propose a new command upstream---## Environment Setup```bash# Preferred: configure the installed skill locallycp .env.example .env# Then edit .envTASK_API_URL="https://tasks.internal.example.com"# Optional: authentication tokenTASK_API_TOKEN="<your-token>"```The installed skill reads configuration in this order:1. `--api-url` / `--token`2. `.env` in the installed skill folder3. shell environment variablesUsing `.env` in the installed skill folder is the preferred demo setup becausethe agent may execute in a different shell than the one where environmentvariables were exported.---## Supported CLI Commands### list-tasks```bashpython task_cli.py list-tasks [--status <status>] [--api-url <url>]```Lists all tasks. Use `--status` to filter by any status value the API supports, for example `waiting-for-response` or `resolved`. Omit `--status` to return all tasks.### get-task```bashpython task_cli.py get-task TASK_ID [--api-url <url>]```Fetches a single task by ID including its comment thread.### add-comment```bashpython task_cli.py add-comment TASK_ID "Your comment text" [--api-url <url>]```Appends a comment to a single task. The comment text is a positional argument.---## Workflow evolutionThis skill is intentionally centrally maintained. If you discover that a commonworkflow feels repetitive, awkward, or missing a useful higher-level command,do **not** jump straight to an upstream issue.First:1. try a temporary local proof of concept in the current repo2. verify whether it actually helps3. capture the exact command or behavior you tested4. remove the local patchOnly then open an enhancement issue in the catalog repository using the**Task API Enhancement** template. See`references/IMPROVEMENT-PROCESS.md` for the full flow.---## Quick Diagnostics```bash# Verify CLI is functionalpython task_cli.py --help# List tasks waiting for a response using the configured .env / --api-url / env varpython task_cli.py list-tasks --status waiting-for-response```---## Improvement RequestsThis skill is centrally maintained. Proposed enhancements should be backed by ashort local proof of concept in the consumer repo before an upstream issue isopened. Reference the issue number in any PR that implements the change. See`references/IMPROVEMENT-PROCESS.md` for the full lifecycle.

Frequently asked questions