Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Bill Of Lading

ASecurity

Drafts a U.S. ocean Bill of Lading (B/L) functioning as receipt, contract of carriage, and document of title under COGSA or Hague-Visby. Covers negotiable and straight B/Ls, cargo description, freight allocation, and core carriage clauses. Use when drafting or reviewing a bill of lading, master/house B/L, ocean shipment documentation, or title transfer. Trigger keywords: bill of lading, B/L, ocean carriage, COGSA, Hague-Visby, negotiable, straight, master bill, house bill.

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
devopsgoexpresssecuritydocumentation

Works with

terminal

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill bill-of-lading --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Bill Of Lading?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Bill Of Lading
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-bill-of-lading/badge)](https://www.skillsdirectory.com/skills/lev-os-bill-of-lading)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: bill-of-lading
description: >-
  Drafts a U.S. ocean Bill of Lading (B/L) functioning as receipt, contract of
  carriage, and document of title under COGSA or Hague-Visby. Covers negotiable
  and straight B/Ls, cargo description, freight allocation, and core carriage
  clauses. Use when drafting or reviewing a bill of lading, master/house B/L,
  ocean shipment documentation, or title transfer. Trigger keywords: bill of
  lading, B/L, ocean carriage, COGSA, Hague-Visby, negotiable, straight,
  master bill, house bill.
tags:
  - agreement
  - drafting
  - regulatory
---

# Bill of Lading

Produces a complete B/L that memorializes shipment, allocates risk, and complies with the governing carriage regime. Populate every field from source documents only — never invent data.

## Prerequisites

1. **Parties** — shipper, consignee, notify party legal names, addresses, contacts
2. **Booking & voyage** — booking confirmation, vessel/voyage, ports, delivery terms
3. **Cargo details** — packing list, commercial invoice, marks/numbers, weights, measurements
4. **Commercial terms** — Incoterms, freight payment (prepaid/collect), currency, charges
5. **Special requirements** — insurance/declared value instructions, special handling, hazmat data (UN number, IMDG class) if applicable

## Output Structure

### 1) Document Header

| Field | Req | Notes |
|---|---|---|
| B/L Number | Yes | Unique identifier |
| B/L Type | Yes | `Negotiable` or `Straight (Non-negotiable)` |
| Issue Place/Date | Yes | City, country, date |
| Carrier / Shipper / Consignee | Yes | Legal name and address each |
| Notify Party | Opt | If applicable |
| Vessel/Voyage / Booking No. | Opt | If known |
| Container/Seal Nos. | Opt | If applicable |

### 2) Shipment Routing

| Field | Req | Notes |
|---|---|---|
| Place of Receipt | Yes | Terminal or facility |
| Port of Loading / Discharge | Yes | Port code if available |
| Place of Delivery | Yes | Final destination |
| Transshipment | Opt | Intermediate ports |

### 3) Cargo Description

| Field | Req | Notes |
|---|---|---|
| Description of Goods | Yes | Trade description; do not speculate |
| Packages/Units | Yes | Count and unit type |
| Gross Weight | Yes | With unit |
| Marks/Numbers / HS Code | Opt | As on packages; shipper-provided |
| Measurement / Packaging | Opt | CBM; type and condition |
| Declared Value | Opt | If higher liability requested |
| Special Handling | Opt | Fragile, reefer, etc. |
| HazMat | Cond | IMDG class, UN number |

### 4) Freight and Charges

| Field | Req | Notes |
|---|---|---|
| Freight Term | Yes | Prepaid or Collect |
| Rate Basis | Yes | Per container/weight/measure |
| Currency | Yes | ISO code |
| Additional Charges | Opt | THC, docs, fuel, security |
| Payment Due | Opt | Date or upon release |

### 5) Core Clauses Checklist

- [ ] Receipt in apparent good order unless claused
- [ ] Carrier duty of due diligence — vessel seaworthiness
- [ ] Liability limitation: COGSA $500/package or customary freight unit unless higher value declared and paid [VERIFY]
- [ ] Notice of loss/damage timing (apparent vs. concealed) [VERIFY]
- [ ] Time bar: COGSA one year from delivery or due date [VERIFY]
- [ ] Exceptions: perils of the sea, act of God, inherent vice, shipper fault
- [ ] General average clause and GA contribution security
- [ ] Carrier lien for unpaid freight/charges
- [ ] Governing law, forum selection, or arbitration clause
- [ ] Himalaya clause extending defenses to agents/subcontractors
- [ ] Both-to-blame collision clause (if used by carrier)

### 6) Negotiability and Originals

- State number of originals issued; surrender of one renders others void
- Straight B/L: state non-negotiable, identify consignee
- Electronic B/L: specify system and rules governing eBL transfer

### 7) Signature Blocks

- Carrier or agent: signature, name, title, date
- Shipper signature if required by carrier practice
- Clausing space for exceptions to condition/quantity

## Guidelines

- Mirror packing list, booking, and shipper instructions exactly — never fabricate data
- If Hague-Visby or another regime governs, state it expressly and remove conflicting COGSA language [VERIFY]
- For L/C shipments, issue clean B/L only if no visible damage; otherwise clause accurately
- Align freight term with Incoterms and buyer/seller responsibilities
- Multimodal or door-to-door: clarify scope and liability regime for each leg
- Treat HS codes, weights, and counts as shipper-provided; avoid guarantees
- Flag jurisdiction-specific mandates or carrier standard terms that must attach

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Terraform Module Library

Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.

393431 votes

sematext-otel

Wire a service's OpenTelemetry output to Sematext Cloud. Walks through region, App-type, instrumentation flow (managed OTLP endpoint vs Sematext Agent), and signal selection (traces/metrics/logs), then produces the exact env-var block and points at a runnable reference example in this repo. Invoke when instrumenting a new app for Sematext.

01 votes

Deployment Patterns

Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.

2459130 votes

Babysit

Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.

929660 votes

V7 Roster

Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.

805540 votes
View all in devops →