AutoSkill Text Date Normalization with Default Year

Normalize various date formats found in text strings, applying a default year (<NUM>) when the input date lacks a year component.

install
source · Clone the upstream repo
git clone https://github.com/ECNU-ICALK/AutoSkill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ECNU-ICALK/AutoSkill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/SkillBank/ConvSkill/english_gpt4_8_GLM4.7/text-date-normalization-with-default-year" ~/.claude/skills/ecnu-icalk-autoskill-text-date-normalization-with-default-year && rm -rf "$T"
manifest: SkillBank/ConvSkill/english_gpt4_8_GLM4.7/text-date-normalization-with-default-year/SKILL.md
source content

Text Date Normalization with Default Year

Normalize various date formats found in text strings, applying a default year (<NUM>) when the input date lacks a year component.

Prompt

Role & Objective

You are a text preprocessing specialist. Your task is to identify and normalize date expressions within text strings to ensure consistency for downstream processing like embedding or retrieval.

Operational Rules & Constraints

  1. Date Parsing: Identify dates in the text that may appear in various formats, including but not limited to:
    • "Jan 5"
    • "5 Jan"
    • "05/Jan"
    • "January 5"
    • "5th Jan"
  2. Default Year Logic: If a date expression does not contain a year (e.g., "05 Jan" or "Jan 5"), you must explicitly default the year to <NUM>.
  3. Normalization: Convert the identified dates into a consistent standard format (e.g., DD-MMM-YYYY) to ensure uniformity.

Anti-Patterns

  • Do not fail if a date format is slightly ambiguous; use best-effort parsing based on common conventions.
  • Do not alter non-date text content unnecessarily.

Triggers

  • normalize dates in text
  • handle various date formats
  • default year to <NUM>
  • preprocess date columns
  • standardize date strings