logistics-optimize — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited logistics-optimize (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
You are an autonomous logistics optimization agent. Do NOT ask the user questions.
This skill chains five skills in sequence for comprehensive logistics system analysis:
/route-optimizer -- Vehicle routing and delivery optimization analysis/warehouse-ops -- Warehouse management and operations review/inventory-forecast -- Inventory demand forecasting and replenishment analysis/supply-chain-risk -- Supply chain risk identification and mitigation review/load-test -- System stress testing under peak logistics loadINPUT: $ARGUMENTS Pass the system name, specific logistics domain to focus on, or optimization objectives.
============================================================ PHASE 1: ROUTE OPTIMIZATION (/route-optimizer) ============================================================
Follow the instructions defined in the /route-optimizer skill exactly.
Analyze vehicle routing and delivery optimization:
Record identified bottlenecks and optimization gaps for cross-referencing with subsequent phases.
============================================================ PHASE 2: WAREHOUSE OPERATIONS (/warehouse-ops) ============================================================
Follow the instructions defined in the /warehouse-ops skill exactly.
Review warehouse management system implementation:
IMPORTANT: Cross-reference warehouse throughput capacity with route optimization from Phase 1. Flag mismatches where routing assumes warehouse processing speed that the WMS cannot sustain.
============================================================ PHASE 3: INVENTORY FORECASTING (/inventory-forecast) ============================================================
Follow the instructions defined in the /inventory-forecast skill exactly.
Analyze inventory demand forecasting and replenishment:
IMPORTANT: Verify inventory forecasts align with warehouse capacity from Phase 2 and delivery schedules from Phase 1. Flag any forecasting assumptions that conflict with operational constraints.
============================================================ PHASE 4: SUPPLY CHAIN RISK (/supply-chain-risk) ============================================================
Follow the instructions defined in the /supply-chain-risk skill exactly.
Identify and evaluate supply chain risk management:
IMPORTANT: Cross-reference risk scenarios with routing alternatives from Phase 1, warehouse overflow handling from Phase 2, and safety stock adequacy from Phase 3.
============================================================ PHASE 5: LOAD TESTING (/load-test) ============================================================
Follow the instructions defined in the /load-test skill exactly.
Stress test the logistics system under peak conditions:
IMPORTANT: Target the specific APIs and services identified in Phases 1-4. Use realistic payload sizes based on actual order and shipment data models. Identify which logistics subsystem becomes the bottleneck under peak load.
============================================================ SELF-HEALING VALIDATION (max 3 iterations) ============================================================
After completing all phases, validate the combined output:
STOP when:
IF STILL FAILING after 3 iterations:
============================================================ OUTPUT ============================================================
| Phase | Skill | Status | Details |
|---|---|---|---|
| 1 | /route-optimizer | PASS/FAIL | {N} routing gaps, {optimization potential} |
| 2 | /warehouse-ops | PASS/FAIL | {N} workflow issues, {throughput assessment} |
| 3 | /inventory-forecast | PASS/FAIL | {N} forecasting gaps, {accuracy assessment} |
| 4 | /supply-chain-risk | PASS/FAIL | {N} risk factors, {N} unmitigated risks |
| 5 | /load-test | PASS/FAIL | p95={N}ms, error rate={N}%, bottleneck={subsystem} |
System health: {OPTIMIZED / NEEDS IMPROVEMENT / CRITICAL GAPS} Peak readiness: {READY / AT RISK / NOT READY} Top bottleneck: {identified subsystem and constraint}
[Misalignments between logistics subsystems -- highest optimization impact]
NEXT STEPS:
/security-review to audit logistics platform APIs and access controls/monitoring to set up alerting for logistics KPIs/arch-review to evaluate microservice architecture for logistics scale/load-test to verify improvementsDO NOT:
============================================================ SELF-EVOLUTION TELEMETRY ============================================================
After producing output, record execution metadata for the /evolve pipeline.
Check if a project memory directory exists:
~/.claude/projects/skill-telemetry.md in that memory directoryEntry format:
### /logistics-optimize — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.