Supplier Sync Manager

v1.0.0

Build a supplier sync control brief for inventory, catalog, pricing, order-handoff, and onboarding workflows. Use when a team needs to spot mapping gaps, lat...

0· 84·0 current·0 all-time
byhaidong@harrylabsj

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for harrylabsj/supplier-sync-manager.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Supplier Sync Manager" (harrylabsj/supplier-sync-manager) from ClawHub.
Skill page: https://clawhub.ai/harrylabsj/supplier-sync-manager
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install supplier-sync-manager

ClawHub CLI

Package manager switcher

npx clawhub@latest install supplier-sync-manager
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the behavior: the skill turns a textual prompt into a structured control brief. It requires no cloud credentials, no unrelated binaries, and the code only performs local text analysis and rendering consistent with that purpose.
Instruction Scope
SKILL.md is narrowly scoped: it describes producing heuristic briefs and explicitly states it does not query live ERP/WMS/OMS/APIs. The handler code reads the SKILL.md file and the provided prompt and performs keyword-based inference; it does not access other files, environment variables, or network endpoints.
Install Mechanism
No install spec is provided (instruction-only). There are Python source and test files, but nothing installs external packages or downloads code from remote URLs.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. The code does not attempt to read environment secrets or other system credentials.
Persistence & Privilege
Flags show always:false and normal model invocation; the skill does not request permanent presence or modify other skills/config. It only reads its own SKILL.md at runtime.
Assessment
This skill appears internally consistent and low-risk: it processes the input prompt locally and produces a heuristic brief without contacting external systems or requiring credentials. Still: (1) treat the generated brief as advisory — review and approve any operational or SLA actions before applying them to production systems; (2) if you plan to run the included tests or execute the handler, do so in a controlled environment (the test modifies sys.path and imports the handler); and (3) if you need absolute assurance, inspect the remainder of handler.py (the file was partially shown) to confirm there are no hidden network calls or writes to unexpected locations.

Like a lobster shell, security has layers — review code before you run it.

latestvk972kh5qjcv3132f8n0pekjgg984t2qg
84downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

Supplier Sync Manager

Overview

Supplier Sync Manager turns a short operations prompt into a practical control brief for supplier-to-system synchronization work. It is useful when you need a fast operating view of sync scope, likely failure themes, control questions, and exception ownership.

Use this skill when

  • inventory or availability updates are lagging across supplier feeds and internal systems
  • catalog, SKU, pack-size, or pricing mappings look inconsistent
  • order, shipment, or fulfillment events are duplicating, missing, or drifting between systems
  • a new supplier onboarding, file template rollout, or cutover needs a risk checklist
  • the team needs a concise exception-management brief instead of a raw troubleshooting dump

What the skill does

The handler reads the prompt, infers likely context, and produces a structured brief with:

  1. Primary sync objective such as inventory synchronization, catalog and pricing alignment, order handoff, onboarding, or exception review
  2. Operating cadence such as real-time, daily, weekly, or launch preparation
  3. Systems referenced including ERP, WMS, OMS, PIM, marketplace/storefront, or supplier portal workflows
  4. Priority risk themes such as SKU mapping mismatch, inventory latency, price mismatch, pack-size confusion, duplicate events, or supplier SLA drift
  5. Control recommendations covering first-check questions, default responses, watchlists, exception-queue design, and assumptions

Recommended input patterns

Use plain language. Helpful details include:

  • sync objective or pain point
  • cadence or business timing
  • systems involved
  • known discrepancies or failure symptoms
  • whether the need is daily operations, launch readiness, or post-incident review

Example prompts:

  • Need daily inventory sync between supplier feed and ERP to avoid stock lag.
  • Review duplicate order retries and shipment tracking gaps in the OMS handoff.
  • Prepare a launch cutover plan for catalog mapping and supplier onboarding.
  • Our ERP, WMS, and Shopify storefront show price mismatch and pack size mapping issues.

Output shape

The skill returns a markdown brief with sections such as:

  • Sync Scope Summary
  • Recommended Control Table
  • Field Mapping Watchlist
  • Cadence Notes
  • Exception Queue Design
  • Assumptions and Limits

Boundaries

  • This skill is heuristic. It does not query live ERP, WMS, OMS, marketplace, or supplier APIs.
  • It helps frame operational controls and investigation priorities, not replace production monitoring or master-data governance.
  • Final reruns, field changes, SLA decisions, and supplier escalations should remain human-approved.

Comments

Loading comments...