current-date
About
This skill provides the current UTC date and time by executing a bash command, ensuring reliable temporal context. It is essential for starting time-sensitive tasks or when incorrect date assumptions are detected. The skill strictly requires command execution and reporting of the actual output, never relying on memory or assumptions.
Quick Install
Claude Code
Recommended/plugin add https://github.com/majiayu000/claude-skill-registrygit clone https://github.com/majiayu000/claude-skill-registry.git ~/.claude/skills/current-dateCopy and paste this command in Claude Code to install this skill
Documentation
Current Date
Get the current UTC date and time to ensure correct temporal context for all operations.
CRITICAL EXECUTION REQUIREMENT
This skill requires COMMAND EXECUTION, not assumption-based answers.
When this skill loads, you MUST:
- EXECUTE the bash command shown in Quick Start section below
- REPORT the actual command output (not an assumed date)
- NEVER state a date from memory or assumptions
- NEVER skip execution thinking "I know the date"
Why this matters: This skill exists precisely because date assumptions are unreliable. Model training cutoffs, context issues, and stale information mean assumptions about "today" are frequently wrong. The ONLY reliable source is executing the date command and reporting actual output.
Overview
This skill provides a simple, reliable way to verify the current date and time. It addresses situations where Claude Code or subagents may have incorrect assumptions about the current date due to model training cutoffs.
Why a dedicated skill?
- Date/time assumptions are unreliable due to model training cutoffs
- This skill enforces execution-based verification instead of guessing
- Essential for time-sensitive operations (deadlines, versioning, temporal ordering)
What this skill does NOT do:
- Time zone conversions
- Time arithmetic or duration calculations
- Date parsing or validation
When to Use This Skill
IMPORTANT: This is an execution-only skill. Always run the command; never state dates from memory.
Use this skill when:
- Starting a new task or conversation
- Working on time-sensitive operations (deadlines, schedules, versioning)
- Verifying temporal context before making date-based decisions
- Correcting date misunderstandings during a conversation
- Needed by subagents to establish correct date context
- Creating timestamps or version numbers
- Writing documentation with "Last Verified" dates
Quick Start
Get current UTC date and time:
date -u +"%Y-%m-%d %H:%M:%S UTC (%A)"
Expected output:
2025-11-09 18:31:10 UTC (Sunday)
Format explanation:
2025-11-09- ISO 8601 date format (YYYY-MM-DD)18:31:10- 24-hour time with seconds (UTC)UTC- Coordinated Universal Time(Sunday)- Day of week
Execution Checklist:
- Execute the command (don't assume the date)
- Verify output includes UTC timezone
- Report actual output (not paraphrased)
Usage Patterns
At Task Start
date -u +"%Y-%m-%d %H:%M:%S UTC (%A)"
# Then proceed with task...
For Documentation
date -u +"%Y-%m-%d"
# Use for "Last Verified" dates
For Timestamps
date -u +"%Y%m%d-%H%M%S"
# Use in filenames
Best Practices
- Always use UTC: Avoid timezone confusion
- Run at task start: Verify date when beginning time-sensitive work
- Share with subagents: Include current UTC date in Task agent prompts
- Use ISO 8601 format: Unambiguous, internationally recognized
Reference Loading Guide
Load on demand based on context:
| Reference | When to Load |
|---|---|
| references/platform-alternatives.md | Windows users, PowerShell needed |
| references/format-reference.md | Need alternative output formats |
| references/troubleshooting.md | Errors or issues occur |
| references/testing/evaluations.md | During skill testing or audit |
| references/testing/model-notes.md | Multi-model testing |
Version History
- v1.3.0 (2025-11-25): Refactored to hub + references architecture
- Extracted platform alternatives, format reference, troubleshooting to references/
- Extracted evaluations and model testing notes to references/testing/
- SKILL.md reduced from ~420 lines to ~140 lines (67% reduction)
- v1.2.0 (2025-11-19): Added Table of Contents, enhanced Overview
- v1.1.1 (2025-11-17): Added evaluations, multi-model testing notes
- v1.1.0 (2025-11-17): Added PowerShell alternatives, cross-platform docs
- v1.0.1 (2025-11-12): Added action verbs to description
- v1.0.0 (2025-11-09): Initial release
Last Updated
Date: 2025-11-28 Model: claude-opus-4-5-20251101
GitHub Repository
Related Skills
algorithmic-art
MetaThis Claude Skill creates original algorithmic art using p5.js with seeded randomness and interactive parameters. It generates .md files for algorithmic philosophies, plus .html and .js files for interactive generative art implementations. Use it when developers need to create flow fields, particle systems, or other computational art while avoiding copyright issues.
subagent-driven-development
DevelopmentThis skill executes implementation plans by dispatching a fresh subagent for each independent task, with code review between tasks. It enables fast iteration while maintaining quality gates through this review process. Use it when working on mostly independent tasks within the same session to ensure continuous progress with built-in quality checks.
executing-plans
DesignUse the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.
cost-optimization
OtherThis Claude Skill helps developers optimize cloud costs through resource rightsizing, tagging strategies, and spending analysis. It provides a framework for reducing cloud expenses and implementing cost governance across AWS, Azure, and GCP. Use it when you need to analyze infrastructure costs, right-size resources, or meet budget constraints.
