Agent skill · Design & Presentation

network-design

When the user wants to design or optimize a supply chain network, determine facility locations, or configure distribution strategies. Also use when the user mentions "network optimization," "facility location," "DC location," "distribution network," "greenfield analysis," "brownfield optimization," or "hub-and-spoke." For transportation routing within an existing network, see route-optimization.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill network-design-kishorkukreja-awesome-supply-chain --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 23 KB
Bundled scripts: none
Path: skills/analysis/network-design-kishorkukreja-awesome-supply-chain/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

The skill directs the agent to design or optimize a supply chain network by choosing facility locations, network echelons, and flow strategies, and to explore hub-and-spoke concepts and distribution strategies. It treats network design as balancing facility, transportation, inventory, and service costs. It explains types of facilities (manufacturing plants, DCs, cross-docks, forward stocking locations, 3PLs) and flow strategies (Make-to-stock, Make-to-order, Configure-to-order, Drop ship). It also covers high-level optimization problem types (Uncapacitated Facility Location, Capacitated Facility Location, P-Median, P-Center, Hub Location) and provides a Mixed-Integer Programming model with decision variables, objective, and constraints, plus a PuLP-based Python implementation skeleton for solving the network design problem. It includes sections on cost components (Fixed Facility Costs, Transportation Costs, Inventory Costs, Service Level Metrics) and a step-by-step network design process (Data Collection & Validation, Network Strategy Definition, Scenario Modeling, Optimization & Trade-off Analysis, Recommendation & Implementation Planning). It lists tools and techniques, including optimization software and Python network design code examples, and demonstrates a multi-scenario optimization workflow. It instructs how to prepare data (customers, facilities, demand, costs) and how to run optimizations to obtain opened facilities and flow allocations.

How it works

  • Begin with an Initial Assessment gathering Business Context, Strategic Objectives, Data Availability, and Constraints.
  • Use the Network Design Framework to decide Strategic Network Decisions: Number of Echelons, Facility Types, and Flow Strategies.
  • Apply Network Optimization Models for Facility Location (UFL, CFL, P-Median, P-Center, Hub Location).
  • Use the Mathematical Optimization Approach (Mixed-Integer Programming) with variables y_j (binary, facility opened) and x_ij (flow from facility to customer). Define Objective to minimize fixed facility costs, transportation costs, handling costs, and inventory costs. Enforce constraints: demand satisfaction, facility capacity, and that flows exist only from opened facilities.
  • Provide a Python Implementation snippet using PuLP that sets up the problem, defines decision variables, builds the objective and constraints, solves, and extracts results like total_cost, open_facilities, and flows.
  • Outline Cost Components (Fixed Facility Costs, Transportation Costs, Inventory Costs, Service Level Metrics) with typical ranges and simple formulas (e.g., Square Root Law for safety stock).
  • Describe the Network Design Process in phases: Data Collection, Strategy Definition, Scenario Modeling, Optimization & Trade-off Analysis (including a multi-scenario loop and Pareto frontier), and finally Recommendation & Implementation Planning.
  • List Tools & Techniques including commercial solvers (LLamasoft, Gurobi, CPLEX, etc.) and Open Source options (PuLP, Pyomo, OR-Tools, JuMP). It provides a Python network design example skeleton and distance calculations to support modeling.

When to use it

Use when the user wants to design or optimize a supply chain network, determine facility locations, or configure distribution strategies. It is also applicable when the user mentions network optimization, facility location, DC location, distribution network, greenfield analysis, brownfield optimization, or hub-and-spoke. For transportation routing within an existing network, refer to route-optimization. The skill supports exploring base, optimized current, greenfield, and growth scenarios with sensitivity analyses and multi-scenario optimization.

What it can touch

  • Open facilities (binary decisions) and flows (continuous decisions) as part of the MIP model.
  • It references data inputs like customer locations, demand, facility costs, capacities, and transportation/handling costs to drive the optimization.

Caveats

  • The content is framed around a modeling approach and example code; real-world results depend on data accuracy and solver availability. It presents typical cost components, ranges, and modeling assumptions, but does not guarantee outcomes.
From the SKILL.md

# Network Design You are an expert in supply chain network design and optimization. Your goal is to help design cost-effective, service-efficient supply chain networks that balance facility costs, transportation costs, inventory costs, and service levels. ## Initial Assessment Before designing the network, understand: 1. **Business Context** - What's the geographic scope? (regional, national, global) - What's driving this analysis? (growth, consolidation, cost reduction) - Current network structure? (# of DCs, plants, locations) - Greenfield (new network) or brownfield (optimize existing)? 2. **Strategic Objectives** - Primary goal? (minimize cost, maximize service, both) - Service level targets? (delivery time, fill rate) - Budget constraints or investment limits? - Timeline for implementation? 3. **Data Availability** - Customer demand by location? - Current facility costs and capacities? - Transportation rates and distances? - Product characteristics (cube, weight, value)? - Landed costs, duties, taxes? 4. **Constraints** - Existing facilities that must remain? - Union or labor agreements? - Customer-specific requirements? - Regulatory or compliance needs? --- ## Network Design

What's inside
Steps it walks through
  1. Initial Assessment
  2. Network Design Framework
  3. Strategic Network Decisions
  4. Network Optimization Models
  5. Facility Location Problem Types
  6. Mathematical Optimization Approach
  7. Mixed-Integer Programming (MIP) Model
  8. Python Implementation (PuLP)
  9. Cost Components
  10. 1. Fixed Facility Costs
  11. 2. Transportation Costs
  12. 3. Inventory Costs
  13. 4. Service Level Metrics
  14. Network Design Process
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the network-design skill do?

When the user wants to design or optimize a supply chain network, determine facility locations, or configure distribution strategies. Also use when the user mentions "network optimization," "facility location," "DC location," "distribution network," "greenfield analysis," "brownfield optimization," or "hub-and-spoke." For transportation routing within an existing network, see route-optimization.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill network-design-kishorkukreja-awesome-supply-chain --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going