Results for “business-hours”

Extended hours trading support for pre-market and after-hours sessions via Alpaca

YC Office Hours — two modes. (gstack)

Use this skill when the user asks about Hours of Service (HOS) rules under 49 CFR 395 — the 11-hour driving limit, 14-hour on-duty window, 60/70 hour rule, 30-minute break, 10-hour off-duty reset, 34-hour restart, sleeper berth provisions, split sleeper berth, short-haul exemption (150-air-mile), agricultural exemption, adverse driving conditions, ELD malfunction handling, personal conveyance, yard moves, or anything related to driver duty status. Cite specific 49 CFR 395 subsection. If the question involves a non-standard operation (passenger carrier, oilfield, agricultural, military), confirm which set of rules applies.

YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours", or "is this worth building". Proactively invoke this skill (do NOT answer directly) when the user describes a new product idea, asks whether something is worth building, wants to think through design decisions for something that doesn't exist yet, or is exploring a concept before any code is written. Use before /plan-ceo-review or /plan-eng-review. (gstack)

当需要系统性地提升工作专注度和生产力，实现高质量成果时

Design team offsites with objectives, agenda flow, exercises, logistics, and post-offsite actions.

Use to recover a day in real time when volume, handle time or availability diverge from plan — reforecasting decisions, break moves, overtime, callbacks and skill flex without burning tomorrow. Trigger for "intraday management", "real-time reforecast", "we are underwater at 11am", move breaks or lunches, call people back in, flex agents between queues, ride out the spike, or when the WFM plan is wrong before close of business.

Time-Series Data

Build and maintain a browser-based office dashboard that visualizes .harness runtime state including missions, CXX status, hired workers, events, archive state, and ops exceptions.

Temporal Data

Use to design overnight and follow-the-sun support — coverage models, handoff quality and measuring what is lost between shifts. Trigger for "after-hours coverage", "follow the sun", overnight support design, night shift vs defer async, handoff packet, shift handover quality, global coverage gaps, or when customers reopen tickets after every handoff.

Use this skill when the user asks about team driving — two-driver OTR operations, how teams maximize miles, HOS rules with sleeper berth swap, pay structures, equipment requirements (sleeper berth specs), team retention, and common challenges. Reference 49 CFR 395.1(g).

Automate time tracking, project management, and invoicing in Harvest by logging hours, managing projects, clients, and tasks through natural language commands.

Book-of-Business Analyst

Brief

Burn HUD

Translate design decisions into business value by reading financials, mapping competitive landscapes, and defending design work in ROI terms.

Use this skill when the user asks about the agricultural exemption from Hours of Service (HOS) rules under 49 CFR 395.1(k) — what qualifies as agricultural commodity, the 150-air-mile radius rule, state-declared planting/harvest seasons, livestock hauling specifics, and how to document operations under the exemption. Cite 49 CFR 395.1(k) and 49 USC 5117.

Use to analyse touch time vs elapsed time across the resolution path — queue wait, customer wait, back-office wait, and where elapsed time hides real delay. Trigger for "flow efficiency", "touch time vs elapsed time", "where is the time going", "customers waiting on us", back-office bottlenecks, idle time in cases, or end-to-end time much longer than handle time.