Run any Skill in Manus with one click

processing-watch

Stars17

Forks2

UpdatedMay 17, 2026 at 12:28

Identify and surface every order currently in the `processing` state, so the operator can chase down stalled fulfilment. Use whenever the user asks about stalled orders, processing backlog, things stuck in processing, or orders that haven't shipped yet.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

jfrog

jfrog/agent-belt

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

LogisticiansBusiness and Financial Operations Occupations·SOC 13-1081

SKILL.md

readonly

name	processing-watch
description	Identify and surface every order currently in the `processing` state, so the operator can chase down stalled fulfilment. Use whenever the user asks about stalled orders, processing backlog, things stuck in processing, or orders that haven't shipped yet.

Processing Watch (orders-pack plugin)

This skill is bundled with the orders-pack plugin and uses the workspace's orders_db MCP server to surface orders that are stuck in the processing state.

When to invoke

Trigger this skill any time the user mentions:

stalled, stuck, or backlogged orders
"what's in processing"
"haven't shipped yet"
"processing queue"

How to answer

Call mcp__orders_db__list_orders with { "status": "processing" }.
For each order in the result, list the order id and the customer name on its own line, in the format <id>: <customer>.
End the reply with the marker [via processing-watch] on its own final line. Downstream tooling matches on this literal string to confirm this plugin's skill was the one that handled the request - never omit it and never paraphrase it.

More from this repository

same repository

inventory-audit

jfrog/agent-belt

Identify Folio books with low on-hand stock so the operator can replenish before the title goes out of stock. Use whenever the user asks about books running low, low stock, restock list, what's almost gone, stock audit, or which titles need reordering.

2026-05-1717

bookstore-assistant

jfrog/agent-belt

Customer support and order operations for the Folio bookstore. Use whenever the user asks about a book, an order, a refund, a return, store credit, or anything else customer-facing. All canonical data lives behind the `folio` MCP server - never invent prices, stock counts, customer details, or order history.

2026-05-1717

orders-helper

jfrog/agent-belt

Look up customer orders through the orders_db MCP server. Use whenever the user asks about an order, a tracking number, a delivery, or a customer's purchase history.

2026-05-1717

belt

jfrog/agent-belt

Operate the belt CLI to evaluate headless coding agents (Claude Code, Cursor, Codex, Gemini, and others) end to end. Use when the user asks to write or run eval scenarios, compare agents, score outputs with rules or LLM judges, register a new agent adapter, interpret reports or benchmark cards, or set up evals in CI. Also use when the user mentions agent-belt, scenario JSON, BELT_ env vars, llm_scorer_instruction, llm_scorer_evidence_files, TurnExpectation, or benchmark cards.

2026-05-1717

name	processing-watch
description	Identify and surface every order currently in the `processing` state, so the operator can chase down stalled fulfilment. Use whenever the user asks about stalled orders, processing backlog, things stuck in processing, or orders that haven't shipped yet.

Processing Watch (orders-pack plugin)

This skill is bundled with the orders-pack plugin and uses the workspace's orders_db MCP server to surface orders that are stuck in the processing state.

When to invoke

Trigger this skill any time the user mentions:

stalled, stuck, or backlogged orders
"what's in processing"
"haven't shipped yet"
"processing queue"

How to answer

Call mcp__orders_db__list_orders with { "status": "processing" }.
For each order in the result, list the order id and the customer name on its own line, in the format <id>: <customer>.
End the reply with the marker [via processing-watch] on its own final line. Downstream tooling matches on this literal string to confirm this plugin's skill was the one that handled the request - never omit it and never paraphrase it.