← All skills

🧰 Lead Time Statement Normalize

Turns messy lead-time and production-window wording from a supplier into a clear schedule table, flags gaps and vague ranges, and never invents calendar dates.

Sourcing & supplier verificationIntermediate · Edit variables or configuration before use.FreePublished Nov 4, 2026
Free download

ZIP with SKILL.md and any reference files.

Download ZIP

What it does

Paste the lead-time, production, and shipping-window lines from a quote or email. The skill rebuilds one schedule table (phase / stated window / units / confidence / notes), then lists gaps, conflicting ranges, and wording that still needs a calendar date.

Use it when: a factory writes “15–20 days after deposit, plus 1 week packing, ship about end of month” and you need a clean window before you promise a retail date.

Works with: Claude Code, Claude.ai (Skills upload), Cursor and Codex. Install the ZIP, then ask your agent to normalize the lead-time statements from the quote text.

It only uses windows and dates you supply. It will not invent a ship-by date or fill a blank production calendar.

Output preview

Preview pending. We publish a before/after comparison here after the first passing test run, using the real output. Until then, no example output is shown.

Install

Unzip first. You get a folder named lead-time-statement-normalize containing SKILL.md.

Claude Code

Put the folder in your personal skills directory, or in the project to share it with your team.

~/.claude/skills/lead-time-statement-normalize/SKILL.md.claude/skills/lead-time-statement-normalize/SKILL.md

Claude Code picks up new skills in the current session (run /reload-skills if the skills folder didn't exist when the session started). The skill loads when a task matches its description.

Claude.ai

Turn on code execution (Settings → Capabilities), then go to Customize → Skills, click +, then Create skill → Upload a skill, and select the ZIP. Full guide.

Cursor

Put the folder in your user or project skills directory. Cursor also reads .claude/skills.

~/.cursor/skills/lead-time-statement-normalize/SKILL.md.cursor/skills/lead-time-statement-normalize/SKILL.md

Codex

Put the folder in your user or repository skills directory, then restart Codex or run /skills to check it is listed.

~/.agents/skills/lead-time-statement-normalize/SKILL.md.agents/skills/lead-time-statement-normalize/SKILL.md

These are the standard skill locations for each tool. The tools a skill is verified on are listed under “Tested on” above, if any.

Test log

Date (UTC)ToolModelRunResultChecksTokens in / out
Nov 4, 2026Codexgpt-5.4-miniTestFailed
1/4
  • ✗ codex exited cleanly (point::responses_websocket: failed to connect to websocket: HTTP error: 403 Forbidden, url: wss://api.openai.com/v1/resp)
  • ✗ skill was loaded (SKILL.md read)
  • ✗ output has substance (80+ words) (0 words)
  • ✓ no obvious secret leak
0 / 0

Each row is a real run recorded by our test runner. For each tool, the latest test run decides whether it appears under “Tested on”. Baseline runs do the same task with no skill installed and never count.