Relative Date Resolver
v1.0.0Converts natural language day references into the soonest future calendar date in ISO format (YYYY-MM-DD) for accurate scheduling.
⭐ 1· 87·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name, description, SKILL.md instructions, and the included Python implementation all focus on converting natural-language relative date expressions to an upcoming ISO date. The requested runtime footprint (no env vars, no binaries) matches that purpose.
Instruction Scope
SKILL.md limits the tool's scope to date resolution (when to call it, expected return format, example usage). It does not instruct the agent to read unrelated files, access secrets, or send data to external endpoints.
Install Mechanism
There is no install spec (instruction-only), which is low risk, but the code imports dateutil.parser (python-dateutil) without declaring it. That missing dependency can cause runtime failures in environments that don't already have python-dateutil installed.
Credentials
The skill requests no environment variables, credentials, or config paths — appropriate and minimal for the stated function.
Persistence & Privilege
always is false and the skill doesn't request persistent system privileges or modify other skills/config. Autonomous invocation is allowed (platform default) which is normal for a tool of this type.
Assessment
This skill appears coherent and low-risk: it doesn't ask for credentials or access, and it doesn't perform network I/O. Before installing or relying on it, test with a range of inputs (e.g., 'this Wed' when today is Wed, 'next weekend', ambiguous phrases) because the implementation has a few practical issues: 1) it imports dateutil but doesn't declare or install that dependency — ensure python-dateutil is available in your environment; 2) the timezone parameter is accepted but not applied (the code uses naive datetime.now()/fromisoformat without timezone handling), so time-zone-sensitive behavior may be incorrect; 3) parsing relies on dateutil.parse with fuzzy=True which can behave unpredictably for some free-form inputs — validate edge cases you care about. If you plan to deploy this broadly, consider adding an explicit install step to pin python-dateutil and either implement timezone handling or document that results are computed in the system's local time.Like a lobster shell, security has layers — review code before you run it.
latestvk97dcc82q8pn8dd1e690rmysgh838hbk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.