Results for “timelink”

Anchors work at the current moment and places events as spatial distances ahead or behind to improve temporal reasoning.

Build, validate, and troubleshoot deep links for Codex, Cursor, VS Code, Visual Studio, and similar tools. Use when users ask for clickable links (especially in Slack) that open threads, files, folders, or app settings.

Track elapsed time from a set epoch with tamper-evident locking, supporting count-up, count-down, and count-between modes, milestones, and email notifications.

Rekonstruiert den zeitlichen Ablauf eines Datenschutzvorfalls für die DSGVO-Meldung, prüft Fristen, Form, Zuständigkeit und Rechtsweg und liefert eine Fristen- und Risikoampel mit Sofortmaßnahmen.

Local CLI issue tracker for todos, follow-ups, structured records, and the canonical pattern for decomposing multi-step work into a parent + subissues with acceptance criteria, dependency edges, and priority. Use when the user mentions a task to remember, a bug to track, an open question, anything that needs to outlive the current turn, or when planning multi-heartbeat work that needs `chainlink issue ready`-driven pickup across sessions. Includes guidance on writing descriptions future-you can act on (handles, success path, failure path) and idempotency tactics for actions that might fire twice (boundary firing, overlapping heartbeats, retried subagent completion). Pairs with five-whys (chainlink is the storage backend for RCA trees). Storage is local — issues live under a `.chainlink/` directory in the operator's repo.

Daily live-trend scan for any active brand — surfaces timely topics, launches, news, and community pain points in the brand's niche, scored for relevance and timeliness, deduplicated against a rolling log, and written as candidate topics the social calendar can pull.

Provides real-time US visa wait times, border crossing delays, and FAA airport status through three MCP tools.

Use when planning a USENIX FAST project timeline from venue fit through choosing a Spring or Fall deadline, double-blind submission, the author-response period, shepherding or a one-shot revision, artifact evaluation, and the open-access camera-ready, with backward-planning offsets tuned to storage evaluation and honest handling of the two-deadline cycle.