task-store

Read and update Shipwright task store records via HTTP API.

9|2|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/app-vitals/shipwright --skill task-store
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-store
Source: https://github.com/app-vitals/shipwright/tree/main/plugins/shipwright/skills/task-store
Command: npx skills add https://github.com/app-vitals/shipwright --skill task-store

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction of manually tracking and updating Shipwright work items by giving you a reliable way to read, claim, pause, complete, and create tasks through the task store API.

Core Features & Use Cases

  • Queue triage: Pick the next ready task or resume work already in progress.
  • Lifecycle updates: Move tasks through status changes such as in_progress, blocked, pr_open, and merged while preserving the required metadata.
  • Task creation: Add new tasks with the fields needed for routing, ownership, and dependency handling.
  • Use case: When an agent finishes implementation and opens a pull request, use this Skill to record the PR number, timestamp, and final merge status without touching the database directly.

Quick Start

Use the task-store skill to check the queue, claim the next task assigned to you, and update its status through the Shipwright task store API.

Frequently Asked Questions about task-store

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

FAQPage Schema
How do I update Shipwright task status transitions through the REST API?

Update Shipwright task status transitions by applying lifecycle-aware updates like in_progress, blocked, pr_open, and merged through curl-based REST calls to the task store HTTP API. This preserves required metadata while moving tasks between states.

How do I record a pull request number when a Shipwright task is completed?

Record a pull request number by linking the PR to the task store record through the HTTP API. You can append the PR number, timestamp, and final merge status to the task without touching the database directly.

Can I use bearer-token authentication to triage a Shipwright task queue?

Yes, bearer-token authentication is required to triage the Shipwright task queue. You can read and claim the next ready task or resume work in progress across repo-scoped queues using curl-based REST calls.

What's the best way to handle blocked tasks and dependency-safe selection in a task store?

Handle blocked tasks and ensure dependency-safe selection by querying the repo-scoped task queue through the HTTP API. The task store supports lifecycle-aware updates to mark tasks as blocked while preserving routing and ownership metadata.

How do I create new tasks with routing and ownership fields for local or managed agents?

Create new tasks by submitting the required routing, ownership, and dependency fields to the Shipwright task store API. This allows proper task queue assignment and handling for both local and managed agents.

Do I need curl to manage Shipwright task store records?

Yes, curl-based REST calls are required to interact with the Shipwright task store HTTP API. You need bearer-token authentication to securely read, claim, update, and create task records.