- Home
- Skills
- Agents & Orchestration
- Repair DST Recurrence Scheduling Bugs
More screenshots
Works with the AI Agents you already use
Repair DST Recurrence Scheduling Bugs
Repair recurring-schedule bugs where DST gaps/folds, time-zone rule updates, UTC conversion, or retry logic shift local-time intent or execute a recurrence twice.
$1
Repair DST Recurrence Scheduling Bugs
Example session with this skill installed
A weekly 02:30 Europe/Amsterdam job is stored as a UTC offset captured at creation. After DST changes it runs at the wrong local hour, and the fall-back fold can produce duplicates. Repair while preserving the user's local-time intent.
- Read your context and instructions
- Compiled the repair dst recurrence
A fixed offset cannot represent a recurring civil-time rule. The repair stores the IANA zone plus local recurrence intent, resolves each occurrence using an explicit gap/fold policy, assigns one stable occurrence identity for dedupe/retry, and tests spring-forward, fall-back, tzdata changes, and normal weeks.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Recurring schedules often break during daylight-saving time transitions, leading to skipped tasks, double executions, or incorrect wall-clock alignment. These bugs are notoriously difficult to debug because they involve complex interactions between IANA time zones, UTC normalization, and retry logic.
What it does
- Identifies inconsistencies in wall-clock intent versus UTC instant storage across the codebase.
- Patches logic for DST gaps (non-existent times) and folds (ambiguous duplicate times).
- Standardizes identity and state ownership for recurring tasks to prevent race conditions.
- Implements deterministic local fixtures and time-warping tests to verify fixes.
- Refactors validation logic to catch scheduling errors before irreversible state mutations.
Why this beats prompting it yourself
General-purpose prompts often miss edge cases like tzdata updates or the specific "missed-run" policies required for business logic. This skill follows a strict protocol to map trust boundaries and state ownership, ensuring that fixes don't just "look right" but are architecturally sound and verifiable through local regression tests.
Use cases
- Fixing cron jobs that fire twice or zero times during a DST transition.
- Correcting calendar event offsets after a system-level IANA time-zone database update.
- Ensuring retry and catch-up policies respect the user's original local time intent.
- Adding deterministic test suites for scheduling logic without using brittle sleep commands.
Known limitations
This skill cannot access production services or live secrets. It is designed for repository-level logic repairs and local test fixtures only.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.
Cannot redesign user-visible local schedule intent, recurrence rule, time-zone choice, missed-run policy, retry policy, and public errors; cannot verify production infrastructure or prove every runtime, proxy, network, storage, clock, or scheduler ordering.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 months ago
Permissions
Run on a clean branch with repository files and disposable local fixtures. Review patches and validation before merge. Keep production services, real credentials, customer payloads, and deployment out of scope.