Deconsolidation

v1.0.0

Deconsolidation reference — container stripping, cargo breakdown, cross-dock operations, and LCL unpacking. Use when planning deconsolidation workflows or op...

0· 122·1 current·1 all-time
byBytesAgain2@ckchzh
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (deconsolidation, LCL, cross-dock) match the included SKILL.md and the bundled scripts/script.sh which implement command handlers that print guidance and checklists. There are no unrelated credentials, binaries, or services requested.
Instruction Scope
Runtime instructions only direct the agent to run the included scripts/script.sh with explicit subcommands (intro, process, lcl, crossdock, equipment, documentation, metrics, checklist, help, version). The script outputs static documentation; it does not reference or exfiltrate files, network endpoints, or secrets in the provided content. The SKILL.md lists an optional DECONSOLIDATION_DIR config (default ~/.deconsolidation/) but the skill does not require or demand it—this is a benign configuration hint.
Install Mechanism
There is no install spec (instruction-only) and the only code is a local shell script included in the package. Nothing is downloaded or written to disk during install beyond the already-provided files.
Credentials
The skill declares no required environment variables, credentials, or config paths. The optional DECONSOLIDATION_DIR is a harmless local path hint and is proportional to the stated purpose.
Persistence & Privilege
always is false and the skill uses the normal user-invocable/autonomous defaults. It does not request elevated privileges or modify other skills or system-wide settings in the provided content.
Assessment
This skill appears to be a self-contained reference: it runs a bundled shell script that prints logistics guidance and checklists and does not request keys or perform network calls in the supplied files. If you want extra assurance: (1) open and review the entire scripts/script.sh (the displayed file was truncated in the listing) to confirm there are no hidden commands (network calls, file writes, or execution of arbitrary code), (2) run the script in a restricted/test environment if you plan to allow autonomous invocation, and (3) if you plan to set DECONSOLIDATION_DIR, prefer a dedicated data directory rather than a sensitive system path. Otherwise it is coherent with its stated purpose.

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

latestvk97dxc7nsgzqd55m4q01gzc92x83bmxx
122downloads
0stars
1versions
Updated 4w ago
v1.0.0
MIT-0

Deconsolidation — Cargo Breakdown & Receiving Reference

Quick-reference skill for deconsolidation operations, container stripping, and warehouse receiving workflows.

When to Use

  • Planning container unloading and cargo breakdown operations
  • Designing cross-dock or deconsolidation workflows
  • Handling LCL (Less than Container Load) shipments
  • Optimizing receiving dock operations
  • Managing multi-destination cargo sorting

Commands

intro

scripts/script.sh intro

Overview of deconsolidation — what it is, why it matters, key terminology.

process

scripts/script.sh process

Step-by-step deconsolidation process from container arrival to dispatch.

lcl

scripts/script.sh lcl

LCL deconsolidation — handling less-than-container-load shipments.

crossdock

scripts/script.sh crossdock

Cross-docking operations — direct transfer without storage.

equipment

scripts/script.sh equipment

Equipment and infrastructure for deconsolidation operations.

documentation

scripts/script.sh documentation

Documentation flow — manifests, BOLs, receiving reports, discrepancy handling.

metrics

scripts/script.sh metrics

Key performance metrics for deconsolidation operations.

checklist

scripts/script.sh checklist

Deconsolidation operations checklist.

help

scripts/script.sh help

version

scripts/script.sh version

Configuration

VariableDescription
DECONSOLIDATION_DIRData directory (default: ~/.deconsolidation/)

Powered by BytesAgain | bytesagain.com | hello@bytesagain.com

Comments

Loading comments...