austine-daily-ops
Daily execution and trip-ops command system for Austine. Use when asked to run daily brief/checklist/status workflows, track priorities, or plan and procure trip logistics (transport, lodging, reservations, vendor quotes, recommendation + decision handoff).
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install openclaw-skills-austine-daily-ops
Repository
Skill path: skills/austineyapp/austine-daily-ops
Daily execution and trip-ops command system for Austine. Use when asked to run daily brief/checklist/status workflows, track priorities, or plan and procure trip logistics (transport, lodging, reservations, vendor quotes, recommendation + decision handoff).
Open repositoryBest for
Primary workflow: Research & Ops.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: openclaw.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install austine-daily-ops into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/openclaw/skills before adding austine-daily-ops to shared team environments
- Use austine-daily-ops for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
---
name: austine-daily-ops
description: Daily execution and trip-ops command system for Austine. Use when asked to run daily brief/checklist/status workflows, track priorities, or plan and procure trip logistics (transport, lodging, reservations, vendor quotes, recommendation + decision handoff).
---
# Austine Daily Ops
## Overview
Run Austine’s day-to-day operating cadence with concise, action-first outputs, and handle travel operations like a sourcing assistant (options scan, quote gathering, recommendation, and execution handoff).
## Core Capabilities
### 1) Daily execution cadence
Use this pattern for daily operations asks.
- Output max 5 bullets unless user asks for depth.
- Always include: current status, blocker (or "No blocker"), next action.
- Prefer concrete actions over commentary.
When asked for daily planning:
1. List Top 3 priorities.
2. List next 72h critical deadlines/reminders.
3. Suggest one automation and one quick win (<15 min).
4. End with “next action I’ll take.”
### 2) Trip operations management
Use this for travel planning/procurement tasks.
Workflow:
1. **Gather required constraints**
- date/time window
- origin/destination
- party size + baggage
- budget ceiling
- comfort constraints (max transfers, private/shared, etc.)
2. **Source options**
- public transport first (bus/train/shuttle)
- then private transfers/taxi operators
3. **Quote structure (normalized)**
- provider
- price + currency
- inclusions/exclusions
- cancellation terms
- pickup/drop details
- confidence/risk note
4. **Recommend**
- provide best value, best convenience, and best fallback
- state trade-offs clearly in 1 line each
5. **Decision handoff**
- ask for one explicit choice (Option A/B/C)
- after user chooses, prepare exact next step/message draft
### 3) Vendor follow-up mode
When waiting for confirmations (driver details, seat confirmations, check-in QR, etc.):
- Keep a short pending list with owner + due date.
- Trigger reminders with time buffer (day-before or earlier for critical items).
- Escalate if no response by cutoff.
## Output Rules
- Bullet-first, concise, high signal.
- No fluff.
- If data is uncertain, say so explicitly.
- For recommendations, always include one fallback.
## References
- For trip transport procurement templates and comparison format, read `references/transport-procurement.md`.
- For daily operating output templates, read `references/daily-ops-templates.md`.
---
## Referenced Files
> The following files are referenced in this skill and included for context.
### references/transport-procurement.md
```markdown
# Transport Procurement Template
Use this template whenever Austine asks to arrange inter-city transfer (e.g., Niseko → Sapporo).
## Inputs to collect
- Date
- Pickup time window
- Pickup location
- Drop-off location
- Passengers
- Luggage count/size
- Budget target
- Preferred mode (bus/train/private)
- Hard constraints (max transfers, kid seats, ski gear, etc.)
## Option table (text bullets)
For each option:
- Option: [A/B/C]
- Provider:
- Mode:
- Departure → Arrival:
- Total travel time:
- Price (all-in):
- Capacity fit:
- Cancellation policy:
- Notes/Risk:
## Recommendation format
- Best Value:
- Best Convenience:
- Best Fallback:
- Decision ask: “Reply A/B/C and I’ll proceed with next step.”
## Follow-up checklist after user selects option
- Confirm final passenger and luggage count
- Confirm pickup contact + reachable number
- Confirm payment method and expected total
- Confirm cancellation/no-show terms
- Save confirmation ID to master trip brief
```
### references/daily-ops-templates.md
```markdown
# Daily Ops Templates
## A) Proactive Status Pulse
- Worked on:
- In progress:
- Blocker/decision needed: (or "No blocker")
- Next action:
## B) Daily Execution Checklist
- [ ] Top Priority 1
- [ ] Top Priority 2
- [ ] Top Priority 3
- [ ] Critical in next 72h
- [ ] One automation to run today
- [ ] One strategic move (side-hustle / AI frontier)
- [ ] One quick win (<15 min)
## C) Morning Brief Structure
1) Daily Location Brief (short forecast only)
2) Top World Events (specific links)
3) Business Updates (markets + AI)
4) Overnight Work Log
5) Top 3 actions today
```
---
## Skill Companion Files
> Additional files collected from the skill directory layout.
### _meta.json
```json
{
"owner": "austineyapp",
"slug": "austine-daily-ops",
"displayName": "Austine Daily Ops",
"latest": {
"version": "1.0.0",
"publishedAt": 1772459721254,
"commit": "https://github.com/openclaw/skills/commit/5953cce67f0763d8ede12db612232120bb288ec8"
},
"history": []
}
```