Results for “morning-checkin”

当需要启动一天，建立积极基调并获取初始能量时

Filters the last 24 hours of Hugging Face Papers to surface one must-read paper with a structured brief covering the central claim, why it's worth an hour, where it might be wrong, and a time-budgeted read order.

Use when the user says "plan my morning" or wants to fill out morning journaling (Gratitude, Better Day, Daily Affirmation) and personal/work tasks for today's daily note.

Track water and sleep with JSON file storage.

Guide for the first days with a new human. Use when: the `init` memory block exists (pointing you here), you have no persona/communication blocks yet, or a human explicitly asks about setup. This skill is about having good conversations — not filling out forms.

Meta-skill codifying the no-wakeup-polling pattern. Describes the ScheduleWakeup anti-pattern, the fix (--auto merge + detached watcher), and when to still use wakeups. Reduces handoff spam by 80%.

Turn a cold start into a warm one. Build a single orientation document for a project, account, or workspace, what it is, where things live, the decisions made so far, the open items, and the next move, so a new session or a new teammate is productive in minutes instead of days. Trigger on "get me up to speed", "onboard someone to this", "what's the context here", "brief a new session", "orient me on this account", or any cold-start on work already in motion.

Eng manager-mode plan review. (gstack)

Brain Dump Journaling

Produce a ready-to-run onboarding plan — pre-boarding checklist, day-1 agenda, first-week plan, and 30/60/90 ramp milestones with owners.

Produce a daily or weekly cross-source digest — mentions, action items, and decisions that need attention, not raw activity.

Multi-tiered memory management (HOT/WARM/COLD) for context compaction. Invoke ONLY for explicit compaction events: post-`/compact` cleanup, MEMORY.md tier promotion, archive batch, or "trim my context". NOT for general recall (use deep-recall) or routine memory writes (use storage-router). Triggers: "compact memory", "promote to durable", "archive old context", "tier this".

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.

Configures autonomous heartbeat and cron-based proactive routines (e.g., morning briefing setup, unanswered-message scan cadence). Invoke when user is SETTING UP or MODIFYING a proactive routine, not when the routine itself fires. Cron crons execute their own logic — they do NOT load this skill. Triggers: "set up proactive check", "configure heartbeat", "add morning briefing", "tune cron cadence".

Onboard a new small-business owner — connect their first two tools, run one recipe, interview them, store context, and set a weekly check-in.

YC Office Hours — two modes. (gstack)

扫描全 wiki 发现健康问题，生成修复建议报告（覆盖全 9 种 entity + graph 一致性）

Turn "which leads should I work?" into a lead-by-lead work plan. Per-lead status (never-touched, engaged-not-replied, gone-cold, hot), days-dark per lead, last-touch quality, a re-engagement ranker, and a recommended next action for every lead. Built for SDRs and full-cycle reps, customizable to your CRM and your outreach tool. Trigger on "which leads should I work?", "who haven't I touched?", "show me cold leads", "hot leads to follow up on", "who's gone dark?", "re-engagement candidates", or any lead-level work-assignment question.

Use to turn a one-off support search into a standing monitor or alert that stays useful instead of being muted within a fortnight. Trigger for "alert me when a customer mentions X", "notify the team when complaints spike", "keep watching for this", "set up a daily monitor for", turning an ad-hoc sweep into something recurring, or an existing alert nobody reads any more.

Turn churned and downgraded accounts into an early-warning system. Reads the customers who left or shrank, extracts the themes behind why, builds a warning checklist from the real causes, then reads your active book and flags which accounts look like the ones that just churned. Built for B2B retention teams, customizable to your CRM and your customer data. Trigger on "why do customers churn", "what do churned accounts have in common", "build me a churn early-warning list", "which accounts are at risk of churning", "who looks like a recent churner", or any retention post-mortem.

Approach an app, tool, codebase, website, or product as a genuine first-time user with zero insider context — try it out using only the information provided, get confused where a real newcomer would, and surface the "obvious" questions that people who built or use the thing daily can no longer see. Use this whenever the user wants a first-time-user test, a fresh perspective, a naive walkthrough, a cold read of their README/onboarding/docs/UI, or says things like "pretend you've never seen this", "would a new user get this?", "test my app like a beginner", "what would confuse someone new?", or "give me fresh eyes on this". Also use it when someone wants to find gaps in onboarding, docs, or first-run experience — even if they don't say "fresh eyes" explicitly.

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)

Automates app maintenance by assessing health, prioritizing by staleness and debt, and running targeted fix pipelines that commit directly to main.

Generates a concise status briefing after session-start reconciliation — synthesizing current state, open decisions, key risks, and today's priority actions. Use at session start, for "pk-resume", a briefing, catch-up, or today's focus.

Most teams run one test — expected peak for ten minutes — and believe they have