← Skills

morning-ops

Morning operational brief — overnight summary, system health, alerts

Morning Ops Skill

Purpose

Consolidated morning operations for Alfred (orchestrator). Covers the 8:00–9:30 AM Bolivia time morning block.

morning-brief

Schedule: 8:00 AM daily | Agent: Alfred

Prepare the daily morning brief for Clayton:

  1. Check overnight system health — scan for failed cron jobs, gateway errors, agent session issues
  2. Review any pending approvals that need Clayton's attention
  3. Run agent status checks — verify all 8 agents are responsive
  4. Identify priority tasks for today from TODO.md and daily plan
  5. Surface any alerts or failures from overnight cron runs (check state.lastRunStatus and state.lastError in jobs.json)
  6. Deliver summary via Telegram — concise bullet points, not essays

daily-plan

Schedule: 8:30 AM daily | Agent: Alfred

Create today's action plan:

  1. Review pending TODOs from TODO.md
  2. Check active projects and upcoming deadlines
  3. Assign tasks to agents based on priority and availability
  4. Prioritize revenue-generating activities (outreach, proposals, follow-ups)
  5. Coordinate with Rick on sales pipeline status
  6. Coordinate with Devin on delivery queue
  7. Flag any blockers that need Clayton's input
  8. Post plan to Telegram

daily-standup

Schedule: 9:00 AM weekdays | Agent: Alfred

Lead the daily team standup:

  1. Check each agent's last session activity and any errors from overnight cron runs
  2. Compile: what was accomplished yesterday, what's planned today, any blockers
  3. Check pipeline metrics: npm --prefix C:/Users/Administrator/.openclaw/workspace/leadspanther-lead-engine run query:pipeline
  4. Review TODO.md for priority tasks
  5. Assign today's priorities to relevant agents
  6. Post standup summary to Telegram team group — bullet points, not essays

email-triage

Schedule: 9:30 AM weekdays | Agent: Alfred

Triage incoming emails for Clayton:

  1. Use gog to check Gmail inbox for unread messages from the last 24h
  2. Categorize each email:
    • Urgent: needs Clayton's response today
    • Actionable: can be delegated to an agent
    • Informational: FYI only
    • Spam/Ignore: skip
  3. For delegatable items, assign to the appropriate agent:
    • Rick for sales inquiries
    • Friedrich for finance/billing
    • Laura for legal matters
  4. Post triage summary to Telegram: list emails requiring Clayton's personal response
  5. Flag any time-sensitive items (deadlines within 48h)
View raw SKILL.md
# Morning Ops Skill

## Purpose
Consolidated morning operations for Alfred (orchestrator). Covers the 8:00–9:30 AM Bolivia time morning block.

## morning-brief
**Schedule**: 8:00 AM daily | **Agent**: Alfred

Prepare the daily morning brief for Clayton:
1. Check overnight system health — scan for failed cron jobs, gateway errors, agent session issues
2. Review any pending approvals that need Clayton's attention
3. Run agent status checks — verify all 8 agents are responsive
4. Identify priority tasks for today from TODO.md and daily plan
5. Surface any alerts or failures from overnight cron runs (check `state.lastRunStatus` and `state.lastError` in jobs.json)
6. Deliver summary via Telegram — concise bullet points, not essays

## daily-plan
**Schedule**: 8:30 AM daily | **Agent**: Alfred

Create today's action plan:
1. Review pending TODOs from TODO.md
2. Check active projects and upcoming deadlines
3. Assign tasks to agents based on priority and availability
4. Prioritize revenue-generating activities (outreach, proposals, follow-ups)
5. Coordinate with Rick on sales pipeline status
6. Coordinate with Devin on delivery queue
7. Flag any blockers that need Clayton's input
8. Post plan to Telegram

## daily-standup
**Schedule**: 9:00 AM weekdays | **Agent**: Alfred

Lead the daily team standup:
1. Check each agent's last session activity and any errors from overnight cron runs
2. Compile: what was accomplished yesterday, what's planned today, any blockers
3. Check pipeline metrics: `npm --prefix C:/Users/Administrator/.openclaw/workspace/leadspanther-lead-engine run query:pipeline`
4. Review TODO.md for priority tasks
5. Assign today's priorities to relevant agents
6. Post standup summary to Telegram team group — bullet points, not essays

## email-triage
**Schedule**: 9:30 AM weekdays | **Agent**: Alfred

Triage incoming emails for Clayton:
1. Use gog to check Gmail inbox for unread messages from the last 24h
2. Categorize each email:
   - **Urgent**: needs Clayton's response today
   - **Actionable**: can be delegated to an agent
   - **Informational**: FYI only
   - **Spam/Ignore**: skip
3. For delegatable items, assign to the appropriate agent:
   - Rick for sales inquiries
   - Friedrich for finance/billing
   - Laura for legal matters
4. Post triage summary to Telegram: list emails requiring Clayton's personal response
5. Flag any time-sensitive items (deadlines within 48h)