last7Days

Resolves a rolling 7-day window into ISO dates and UTC instants.

1|Updated Aug 23, 2026
One-click install
npx skills add https://github.com/foxmaster77/12BOT --skill last7days-foxmaster77
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: last7Days
Source: https://github.com/foxmaster77/12BOT/tree/main/munder-difflin-main/munder-difflin-main/resources/skills/last7Days
Command: npx skills add https://github.com/foxmaster77/12BOT --skill last7days-foxmaster77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually computing date ranges for "last 7 days" queries is error-prone, especially across timezones and month boundaries. This Skill resolves the phrase into exact, ready-to-use date bounds so your queries and reports always use the correct window. ## Core Features & Use Cases - Deterministic Date Resolution: Runs a bundled Node.js resolver that returns inclusive civil dates (YYYY-MM-DD) in your local timezone. - UTC Instant Output: Provides a half-open [start, end) range of exact UTC instants for timestamp-based database or API queries. - Read-Only Operation: Performs no writes and no network calls, making it safe to run before any time-bounded task. - Use Case: Before querying an analytics database for "signups in the last 7 days", run this Skill to get the exact start and end dates plus UTC bounds, then plug them directly into your SQL WHERE clause. ## Quick Start Ask the AI to resolve the last 7 days into concrete dates before running your time-bounded query or report.

Frequently Asked Questions about last7Days

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get the exact date range for the last 7 days?▼

Run the bundled resolver with node and the argument last7Days. It prints inclusive start and end dates in your local timezone plus exact UTC instants, so you never compute the window by hand.

How to use last 7 days dates in SQL timestamp queries?▼

Use the startUtc and endExclusiveUtc fields from the resolver output as a half-open [start, end) range in your WHERE clause. This avoids boundary errors that inclusive date comparisons often cause at midnight.

Does the last7Days resolver handle timezones correctly?▼

Yes, it returns civil dates in your local timezone along with the corresponding UTC instants, and includes the timezone name in its JSON output. The resolver is the source of truth, so no manual timezone conversion is needed.

Can I resolve other ranges like last 45 days or 6 months?▼

This Skill only resolves the rolling 7-day window. For arbitrary ranges such as last45days or last6months, the documentation points to the separate /temporal skill, which covers the full window list.

Does the date resolver make network calls or modify files?▼

No, the resolver is strictly read-only with no writes and no network access. It only computes dates relative to the current run time and prints the result to stdout.