/shipping
When the user wants to create or optimize a shipping or delivery information page. Also use when the user mentions "shipping," "delivery," "shipping policy," "delivery times," "shipping page," "free shipping," "shipping rates," "delivery options," "shipping info," "cross-border
$ npx -y skills add kostja94/marketing-skills --skill shipping --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/shipping
Context preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to create or optimize a shipping or delivery information page. Also use when the user mentions "shipping," "delivery," "shipping policy," "delivery times," "shipping page," "free shipping," "shipping rates," "delivery options," "shipping info," "cross-border
SKILL.md
shipping.SKILL.mdname: shipping-page-generator
description: When the user wants to create or optimize a shipping or delivery information page. Also use when the user mentions "shipping," "delivery," "shipping policy," "delivery times," "shipping page," "free shipping," "shipping rates," "delivery options," "shipping info," "cross-border shipping," "international delivery," or "order tracking." For legal overview, use legal-page-generator.
metadata:
version: 1.1.0
Pages: Shipping / Delivery
Guides shipping and delivery information page content for e-commerce, covering domestic and cross-border logistics, regulatory compliance, and AI-era discoverability.
**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
Initial Assessment
Identify: 1. **Shipping scope**: Domestic only, cross-border, or global — see §Shipping Scope 2. **Product type**: Physical goods (standard), digital/physical bundles, print-on-demand, dropshipping 3. **Carriers & methods**: Standard, express, overnight; carrier names; real-time vs flat-rate 4. **Regulatory exposure**: EU (2026 customs changes, AI Act), cross-border compliance 5. **AI discoverability**: Can delivery terms be parsed by AI shopping agents? — see §AI-Era Readiness
---
Shipping Scope
| Scope | Key Considerations | |---|---| | **Domestic Only** | Simplest; focus on carrier options, timelines, cutoffs, free-shipping thresholds | | **Regional** (e.g., EU-wide) | Harmonized customs within single market; local carrier partnerships; OOH networks | | **Cross-Border / Global** | DDP vs DDU; customs duties transparency; multi-carrier tracking normalization; per-market configurability |
---
AI-Era Readiness — Critical for 2026
The most significant shift in 2025–2026: **58% of consumers have replaced traditional search engines with GenAI tools** for product research and price comparison (Capgemini 2026). AI shopping agents compare delivery dates, costs, return terms, and total landed costs **before** the shopper ever visits your site.
**What this means for shipping policies**:
- Delivery terms must be **machine-readable and structured** — an AI agent scraping your site must be able to extract delivery promises, costs, cut-off times, and geographic availability
- If your delivery terms are buried in unstructured paragraphs, AI agents may **exclude your brand** from consideration entirely
- Standardize delivery options in consistent formats: option name | cost | timeline | cutoff | regions
**Practical recommendations**:
- Use structured data (schema.org `OfferShippingDetails`) on product and checkout pages
- State delivery promises as clearly as shipping-rate tables — avoid prose-only descriptions
- Keep policy page content synchronized with structured data (mismatches erode AI trust)
---
EU Regulatory Deadlines (2026)
Two major compliance deadlines converge in summer 2026:
EU Customs — July 1, 2026
A fixed **€3 customs duty** applies to all consignments valued under €150 entering the EU. This covers **93% of e-commerce imports** into the EU.
**Shipping policy impact**:
- **Landed-cost transparency at checkout is mandatory** — customers must see the total price including duties, taxes, and fees before completing purchase
- If using DDU (duties collected at delivery), explicitly warn: "Additional customs fees of approximately €X may be collected on delivery"
- **DDP (Delivered Duty Paid) is strongly recommended** — surprise duties at the door are the #1 cause of refused parcels and lost repeat purchases
EU AI Act — August 2026
Online marketplaces and e-commerce platforms using AI for shipping decisions (carrier selection, delivery predictions, automated refund/reroute decisions) must comply with transparency obligations:
- Automated decisions affecting delivery, refunds, or reroutes must be **auditable** — show what rule fired, what evidence supports the outcome
- Customers must be informed when interacting with AI-driven delivery systems
- Governance trails for automated logistics decisions are required
---
DDP vs DDU Decision Framework
This is now a commercial decision, not just a shipping detail:
| Model | Pros | Cons | Best For | |---|---|---|---| | **DDP** (Delivered Duty Paid) | No doorstep surprises; higher conversion; better AI agent compatibility | Higher upfront logistics complexity; need duty calculation infrastructure | Cross-border brands prioritizing customer experience | | **DDU** (Delivered Duty Unpaid) | Simpler for merchant; lower displayed price at checkout | Doorstep shock; high refused-parcel rates; damages repeat purchase | Low-frequency exporters; items where duties are unpredictable |
**Policy language for DDP**: "All duties, taxes, and customs fees are included in the price shown at checkout. You will not be charged additional fees on delivery."
**Policy language for DDU**: "International orders may be subject to customs duties and import taxes. These charges are your responsibility and are collected by the carrier upon delivery. Estimated fees: [range or calculator link]."
---
Cross-Border Shipping Essentials
Tracking Normalization
Cross-border shipments pass through multiple carriers (origin carrier → customs broker → destination carrier → last-mile). Customers need **one coherent tracking story**, not fragmented statuses from each handoff.
Policy should state:
- How tracking is provided (single tracking page/number even across carriers)
- When tracking becomes available (typically 24–48 hours after shipment)
- What to do if tracking shows no movement for [X] days
Route Volatility (2025–2026 Reality)
- 2,500+ trade restrictions imposed globally in the first 10 months of 2025 alone (World Bank)
- Policy should include: "Delivery times are estimates and may be affected by customs processing, weather, or ot
Read more
name: shipping-page-generator description: When the user wants to create or optimize a shipping or delivery information page. Also use when the user mentions "shipping," "delivery," "shipping policy," "delivery times," "shipping page," "free shipping," "shipping rates," "delivery options," "shipping info," "cross-border shipping," "international delivery," or "order tracking." For legal overview, use legal-page-generator. metadata: version: 1.1.0
Pages: Shipping / Delivery
Guides shipping and delivery information page content for e-commerce, covering domestic and cross-border logistics, regulatory compliance, and AI-era discoverability.
**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
Initial Assessment
Identify: 1. **Shipping scope**: Domestic only, cross-border, or global — see §Shipping Scope 2. **Product type**: Physical goods (standard), digital/physical bundles, print-on-demand, dropshipping 3. **Carriers & methods**: Standard, express, overnight; carrier names; real-time vs flat-rate 4. **Regulatory exposure**: EU (2026 customs changes, AI Act), cross-border compliance 5. **AI discoverability**: Can delivery terms be parsed by AI shopping agents? — see §AI-Era Readiness
---
Shipping Scope
| Scope | Key Considerations | |---|---| | **Domestic Only** | Simplest; focus on carrier options, timelines, cutoffs, free-shipping thresholds | | **Regional** (e.g., EU-wide) | Harmonized customs within single market; local carrier partnerships; OOH networks | | **Cross-Border / Global** | DDP vs DDU; customs duties transparency; multi-carrier tracking normalization; per-market configurability |
---
AI-Era Readiness — Critical for 2026
The most significant shift in 2025–2026: **58% of consumers have replaced traditional search engines with GenAI tools** for product research and price comparison (Capgemini 2026). AI shopping agents compare delivery dates, costs, return terms, and total landed costs **before** the shopper ever visits your site.
**What this means for shipping policies**:
- Delivery terms must be **machine-readable and structured** — an AI agent scraping your site must be able to extract delivery promises, costs, cut-off times, and geographic availability
- If your delivery terms are buried in unstructured paragraphs, AI agents may **exclude your brand** from consideration entirely
- Standardize delivery options in consistent formats: option name | cost | timeline | cutoff | regions
**Practical recommendations**:
- Use structured data (schema.org `OfferShippingDetails`) on product and checkout pages
- State delivery promises as clearly as shipping-rate tables — avoid prose-only descriptions
- Keep policy page content synchronized with structured data (mismatches erode AI trust)
---
EU Regulatory Deadlines (2026)
Two major compliance deadlines converge in summer 2026:
EU Customs — July 1, 2026
A fixed **€3 customs duty** applies to all consignments valued under €150 entering the EU. This covers **93% of e-commerce imports** into the EU.
**Shipping policy impact**:
- **Landed-cost transparency at checkout is mandatory** — customers must see the total price including duties, taxes, and fees before completing purchase
- If using DDU (duties collected at delivery), explicitly warn: "Additional customs fees of approximately €X may be collected on delivery"
- **DDP (Delivered Duty Paid) is strongly recommended** — surprise duties at the door are the #1 cause of refused parcels and lost repeat purchases
EU AI Act — August 2026
Online marketplaces and e-commerce platforms using AI for shipping decisions (carrier selection, delivery predictions, automated refund/reroute decisions) must comply with transparency obligations:
- Automated decisions affecting delivery, refunds, or reroutes must be **auditable** — show what rule fired, what evidence supports the outcome
- Customers must be informed when interacting with AI-driven delivery systems
- Governance trails for automated logistics decisions are required
---
DDP vs DDU Decision Framework
This is now a commercial decision, not just a shipping detail:
| Model | Pros | Cons | Best For | |---|---|---|---| | **DDP** (Delivered Duty Paid) | No doorstep surprises; higher conversion; better AI agent compatibility | Higher upfront logistics complexity; need duty calculation infrastructure | Cross-border brands prioritizing customer experience | | **DDU** (Delivered Duty Unpaid) | Simpler for merchant; lower displayed price at checkout | Doorstep shock; high refused-parcel rates; damages repeat purchase | Low-frequency exporters; items where duties are unpredictable |
**Policy language for DDP**: "All duties, taxes, and customs fees are included in the price shown at checkout. You will not be charged additional fees on delivery."
**Policy language for DDU**: "International orders may be subject to customs duties and import taxes. These charges are your responsibility and are collected by the carrier upon delivery. Estimated fees: [range or calculator link]."
---
Cross-Border Shipping Essentials
Tracking Normalization
Cross-border shipments pass through multiple carriers (origin carrier → customs broker → destination carrier → last-mile). Customers need **one coherent tracking story**, not fragmented statuses from each handoff.
Policy should state:
- How tracking is provided (single tracking page/number even across carriers)
- When tracking becomes available (typically 24–48 hours after shipment)
- What to do if tracking shows no movement for [X] days
Route Volatility (2025–2026 Reality)
- 2,500+ trade restrictions imposed globally in the first 10 months of 2025 alone (World Bank)
- Policy should include: "Delivery times are estimates and may be affected by customs processing, weather, or ot
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
Other skills on kostja94-marketing-skills.
- /google-search-console
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries,"
Open skill - /seo-monitoring
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document,"
Open skill - /ai-traffic
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to
Open skill - /traffic
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel
Open skill - /tracking
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event
Open skill - /community-forum
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia,"
Open skill

