context-now

Detect and report time-sensitive status for OpenClaw reference fixtures.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/ltdrew/Agent-brain-2 --skill context-now-ltdrew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-now
Source: https://github.com/ltdrew/Agent-brain-2/tree/main/test/fixtures/openclaw-reference-minimal/skills/context-now
Command: npx skills add https://github.com/ltdrew/Agent-brain-2 --skill context-now-ltdrew

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill keeps you aware of time-sensitive events in the OpenClaw reference fixture, ensuring you never miss deadlines during tests or demos.

Core Features & Use Cases

  • Time checks on scheduled events and milestones.
  • Quick answers to timing questions during development and QA.
  • Consistent behavior across test runs with deterministic outputs.

Quick Start

Ask the skill to tell you how much time remains until a deadline in your OpenClaw reference fixture.

Frequently Asked Questions about context-now

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

FAQPage Schema
How do I check time remaining until a deadline during OpenClaw e2e tests?

This skill computes current time context against predefined triggers from OpenClaw reference fixtures, outputting concise timing results to answer how long until a deadline during e2e tests.

What is deterministic timing context in OpenClaw runtime agent interactions?

Deterministic timing context in OpenClaw runtime agent interactions means the skill reads predefined triggers from metadata and reports time-sensitive status consistently across all test runs.

Can I use time checks to detect if I am late for scheduled events in OpenClaw?

Yes, you can use time checks to detect if you are late for scheduled events in OpenClaw by reading predefined triggers from metadata and computing current time context against those milestones.

Does OpenClaw time scheduling require any external dependencies to report time-sensitive status?

OpenClaw time scheduling requires no external dependencies to report time-sensitive status, as the skill internally reads predefined triggers from metadata and computes timing results directly.

Why does my time check return inconsistent results across test runs?

If time checks return inconsistent results, this skill solves that by providing deterministic behavior that reads predefined triggers from metadata and outputs consistent timing results across all test runs.