context-now

Enforce current-time context in OpenClaw end-to-end test fixtures.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ALWAYS-ON time-sensitivity discipline for OpenClaw reference fixtures, ensuring tests remain aligned with the current time and reducing flaky outcomes.

Core Features & Use Cases

  • Enforces continuous time-awareness in test fixtures.
  • Provides deterministic time context for end-to-end validations and deadline-sensitive flows.
  • Use Case: Validate that time-based triggers in the OpenClaw reference tests fire correctly relative to the current time.

Quick Start

Configure the context-now discipline for your OpenClaw e2e tests to automatically apply the current-time context during execution.

Frequently Asked Questions about context-now

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

FAQPage Schema
How do I keep end-to-end tests time-aware and prevent flaky outcomes?

Enforce continuous time-awareness in test fixtures by applying a current-time context during execution, ensuring deterministic timing for deadline-sensitive e2e validations and reducing flaky test results.

Why do time-based triggers in my e2e tests fire incorrectly relative to the current time?

Time-based triggers fire incorrectly when fixtures lack current-time awareness; enforcing timely context checks maps test execution to the current time, validating that triggers fire correctly.

How do I apply deterministic time context to OpenClaw reference tests?

Configure the context-now discipline for your OpenClaw e2e tests to automatically apply a deterministic current-time context during execution, ensuring safe defaults for time-sensitive interactions.

Can I use this time-awareness approach for deadline-sensitive test pipelines?

Yes, this approach is specifically applicable to end-to-end test scenarios and fixtures that require current-time awareness for deadline-sensitive interactions within test and e2e pipelines.

What is the best way to handle time-sensitivity in OpenClaw test fixtures?

The best way to handle time-sensitivity is enforcing an always-on time-awareness discipline that provides a simple time-to-context mapping with safe defaults to avoid flaky tests.

Do I need dependencies to enforce current-time context in my e2e tests?

No dependencies are required to enforce current-time context; the discipline operates independently within your existing OpenClaw test and e2e pipeline environment.