Verk Task Management

Manage tasks, projects, and workflows in Verk — AI-powered task management. Create, update, assign, and track tasks. Add comments, change status, list automa...

Security Scan

The skill mostly matches a Verk task-management wrapper, but the bundled CLI defaults to an opaque AWS execute-api domain (not the declared verkapp.com site) to receive your API key and data — this mismatch is suspicious and should be verified before use.

Purpose & Capability

Name, description, declared binaries (node), and required env vars (VERK_API_KEY, VERK_ORG_ID) align with a Verk task-management CLI. The included commands and README match the stated purpose. Minor documentation mismatch: README mentions 'flows trigger <id>' but the CLI only implements flows list.

Instruction Scope

SKILL.md instructs the agent to run the included node script to call Verk APIs and parse JSON. The runtime instructions only reference the declared env vars and the bundled CLI; they do not ask the agent to read unrelated files or system state.

Install Mechanism

No install spec; this is an instruction-only skill with a local script file. Nothing is downloaded or extracted at install time, and the script has no external package installs (uses Node built-in fetch).

Credentials

The skill requires only VERK_API_KEY and VERK_ORG_ID (proportionate). However, the CLI defaults API requests to an AWS execute-api endpoint (https://c0x9lrm7ih.execute-api.us-east-1.amazonaws.com/v1) rather than the public Verk domain referenced in the README (verkapp.com). The CLI will send the VERK_API_KEY in the X-API-Key header to that default endpoint unless VERK_API_URL is overridden — this is a potentially significant mismatch that could result in keys and organization data being sent to an unexpected host.

Persistence & Privilege

Skill does not request always: true, does not persist beyond its files, and does not modify other skill or system configurations. It runs only when invoked.

What to consider before installing

This skill is largely what it says (a Node-based CLI wrapper for Verk), but there is a red flag you should clear before installing or using it: the bundled CLI defaults to an AWS API Gateway domain (execute-api...) rather than the Verk domain referenced in the README. That means your VERK_API_KEY and organization data will be sent to that endpoint unless you set VERK_API_URL to a verified Verk endpoint. Steps to reduce risk: - Verify the correct Verk API base URL with Verk/support or official docs. Do not assume the execute-api URL belongs to Verk. - If you proceed, use a Verk API key with the minimal permissions needed (or a throwaway/test org/key) and monitor its use. - Inspect network logs or use a proxy to confirm where requests actually go when the CLI runs. - Consider editing the script to hardcode the official Verk API_URL (if confirmed) or require VERK_API_URL to be explicitly set before sending requests. - Ask the publisher (owner ID) for provenance: where did the execute-api endpoint come from, and is it an official Verk-hosted gateway? Given the mismatch, do not provide production credentials until you confirm the endpoint is legitimate.

You can manage tasks, projects, and automation flows in Verk using the verk-cli.mjs CLI tool.

Available Commands

Tasks

• List tasks: node scripts/verk-cli.mjs tasks list [--status STATUS] [--priority PRIORITY] [--search QUERY]
• Get task: node scripts/verk-cli.mjs tasks get <taskId>
• Create task: node scripts/verk-cli.mjs tasks create --title "Title" [--description "Desc"] [--status STATUS] [--priority PRIORITY] [--assigned userId1,userId2]
• Update task: node scripts/verk-cli.mjs tasks update <taskId> [--title "New Title"] [--status STATUS] [--priority PRIORITY] [--assigned userId1,userId2]
• Delete task: node scripts/verk-cli.mjs tasks delete <taskId>
• Comment on task: node scripts/verk-cli.mjs tasks comment <taskId> --text "Comment text"

Projects

• List projects: node scripts/verk-cli.mjs projects list

Flows (Automation Workflows)

• List flows: node scripts/verk-cli.mjs flows list

Valid Values

• Status: Backlog, Todo, In-Progress, Review, Done
• Priority: Urgent, High, Medium, Low, None

When to Use Each Command

• When asked to see what tasks exist, use tasks list. Add --status or --priority to filter, or --search to find specific tasks.
• When asked about a specific task, use tasks get <taskId>.
• When asked to create a task, use tasks create with at least a --title.
• When asked to update, change, or modify a task, use tasks update <taskId> with the fields to change.
• When asked to mark a task as done/complete, use tasks update <taskId> --status Done.
• When asked to assign a task, use tasks update <taskId> --assigned userId.
• When asked to delete or remove a task, use tasks delete <taskId>.
• When asked to comment on or add a note to a task, use tasks comment <taskId> --text "...".
• When asked about projects, use projects list.
• When asked about automation workflows, use flows list.
• To see comments on a task, use tasks get <taskId> — comments are included in the task response.

Output Format

All commands return JSON. Parse the output to extract relevant information for the user. When listing tasks, summarize key fields (title, status, priority, assignee) rather than dumping raw JSON.

Examples

# List all high-priority tasks
node scripts/verk-cli.mjs tasks list --priority High

# Create a task and assign it
node scripts/verk-cli.mjs tasks create --title "Review Q2 roadmap" --priority High --status Todo

# Mark a task as done
node scripts/verk-cli.mjs tasks update task-abc123 --status Done

# Add a comment
node scripts/verk-cli.mjs tasks comment task-abc123 --text "Completed the review, looks good"