Menu
Real-time shipment monitoring and exception management skill with proactive alerting and customer communication
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.
Based on SOC occupation classification
Reference for querying the Atlas knowledge graph through its MCP tools — the SECONDARY enrichment/comparison layer that adds best-practice context to systems you have ALREADY scanned from your real sources (`az`, repos, dirs). Use when you need to look up nodes, edges, kinds, clusters, stats, or wiki pages in Atlas to compare against your real inventory. (atlas graph, query atlas, atlas mcp, search the graph, graph neighbors, atlas record, atlas kinds, enrichment layer)
Atlas turns your STATED NEED into a real systems atlas by SCANNING your actual sources (Azure via `az`, git repos, local dirs) and process/data mining them, THEN enriching against the Atlas knowledge graph. Use this skill when asked to inventory/map your real systems, scan your cloud + repos + directories, mine the real processes or data they contain, or collect their real constraints/gotchas. (atlas, scan my systems, inventory our azure account, map my repos, real systems atlas, process mining, data mining, collect nuances, system discovery)
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable processes, babysitter plugins, and reusable procedural insights. Searches GitHub for SKILL.md files, classifies repos by archetype, and maintains structured research under docs/reference-repos/.
JavaScript and TypeScript documentation generation using JSDoc and TSDoc. Parse source code, generate API documentation, validate coverage, and integrate with TypeDoc for comprehensive developer documentation.
Structured debugging methodology using hypothesis-driven investigation, log analysis, and bisection to isolate and resolve defects.
Zero-knowledge circuit development using Circom and Noir languages. Supports constraint optimization, ZK-friendly cryptographic primitives, proof generation (Groth16, PLONK), and Merkle tree implementations.
| name | shipment-visibility-tracker |
| description | Real-time shipment monitoring and exception management skill with proactive alerting and customer communication |
| allowed-tools | ["Read","Write","Glob","Grep","Bash","WebFetch"] |
| metadata | {"specialization":"logistics","domain":"business","category":"transportation","priority":"high"} |
| graph | {"domains":["domain:logistics"],"skillAreas":["skill-area:procurement-management","skill-area:data-analytics","skill-area:customer-success"],"roles":["role:supply-chain-analyst","role:operations-analyst","role:customer-success-manager"]} |
The Shipment Visibility Tracker provides real-time shipment monitoring and exception management capabilities with proactive alerting and automated customer communication. It integrates with multiple carriers and tracking sources to deliver comprehensive visibility across the supply chain.
skill: shipment-visibility-tracker
inputs:
shipment:
shipment_id: "SHP-2026-12345"
carrier: "CARRIER001"
tracking_number: "1Z999AA10123456784"
origin: "Chicago, IL"
destination: "New York, NY"
planned_delivery: "2026-01-25T14:00:00Z"
monitoring:
alert_on_delay_hours: 2
customer_notification: true
notification_milestones: ["picked_up", "in_transit", "out_for_delivery", "delivered"]
outputs:
current_status:
status: "in_transit"
location: "Toledo, OH"
last_update: "2026-01-24T08:30:00Z"
predicted_eta: "2026-01-25T12:30:00Z"
eta_confidence: 92
milestones:
- event: "picked_up"
timestamp: "2026-01-23T15:00:00Z"
location: "Chicago, IL"
- event: "departed_facility"
timestamp: "2026-01-24T02:00:00Z"
location: "Chicago Distribution Center"
exceptions: []
notifications_sent:
- type: "status_update"
channel: "email"
timestamp: "2026-01-24T08:35:00Z"