メニュー
Create personal calendar time blocks — focus time, task blocks, deep work. Finds free slots, proposes options, confirms before any write — no attendees, ever. For reminders, use /myna:reminder. Does not handle meeting prep or scheduling others.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | block-time |
| description | Create personal calendar time blocks — focus time, task blocks, deep work. Finds free slots, proposes options, confirms before any write — no attendees, ever. For reminders, use /myna:reminder. Does not handle meeting prep or scheduling others. |
| user-invocable | true |
| argument-hint | reserve [duration] [when] for [what] | block [duration] on [day] for [purpose] | find me a slot for [task] |
If vault_path is not in context, read ~/.myna/config.yaml first. If the file does not exist, tell the user to run /myna:setup and stop.
Creates personal calendar time blocks — focus time, task slots, deep work. Every calendar write is personal-only — no attendees, ever. For reminders, use /myna:reminder.
Intent check: Before reading an external source (email/Slack/calendar) or making your first vault write — proceed only if the user's request addressed Myna (contains "myna") or explicitly named this action. Otherwise, confirm intent before proceeding.
Triggers: "reserve 2 hours Thursday for the design doc", "block 3 hours this week for deep work", "find me a good slot for [task]"
Use /myna:plan for general planning and prioritization advice. This skill handles only specific blocking requests.
Step 1: Determine scope and duration
Extract duration (required), when (day, "this week", "morning", etc.), and purpose.
Step 2: Find available slots
Read workspace.yaml for work_hours.start, work_hours.end, and timezone. Query the calendar MCP for events in the target window. Identify contiguous free slots of at least the requested duration.
For a specific day: List up to 3 available slots that fit. If the day has no slots of the requested size, say so and offer the closest alternatives (shorter slot today, or the requested size on an adjacent day).
For "this week" or "find a good time": Scan Monday–Friday within work hours. Present up to 3 available slots in chronological order. Let the user pick. Do not pick for them.
Step 3: Confirm event details
Show all parameters before creating:
📅 Proposed time block:
Title: [Myna:Focus] {purpose}
When: {day}, {start time}–{end time} ({duration})
No attendees.
Create this event? (yes / pick a different slot / cancel)
Event type labels and the base prefix are hardcoded: [Myna], [Myna:Focus].
Step 4: Create the event
Only after explicit user confirmation. Apply the three-layer calendar protection from the safety steering skill: verify no attendees and title has hardcoded prefix [Myna] before calling the MCP tool. If either check fails, stop and report.
Call the calendar MCP to create the event with:
title: [Myna:Focus] {purpose}start: ISO datetimeend: ISO datetimedescription: optional context about the taskIf creation succeeds, confirm: "✅ Time block created: {title}, {day} {start}–{end}."
Calendar MCP unavailable: Inform the user and stop. "Calendar MCP is unavailable — can't check free slots or create events. Try again when it's connected."
Reminder request: This skill does not handle reminders. Say: "For reminders, use /myna:reminder." Do not attempt to process reminder requests here.
No free slots of requested duration: "No {duration}-hour slots available on {day}. Closest options: {slot-A} ({shorter-duration}), or {next-available-day} for a full {duration}-hour block."
Ambiguous request — day not specified: Ask before proceeding. "Which day? (or say 'find the best time this week' and I'll scan the week)"
Duration exceeds work day: "That's {N} hours — longer than your work day. Want multiple shorter blocks instead?"
User specifies an already-booked time: Show what's on the calendar at that time and offer the nearest free slots instead. Don't overwrite existing events.
Analyze 1:1 patterns with a specific person — action item follow-through, recurring topics, carry-forward rate. Reports facts from notes only. Does NOT assess relationship quality. Use for any 1:1 pattern analysis: "analyze my 1:1s with X", "1:1 trends with X", "1:1 patterns", "how are my 1:1s with X going?"
Scan the entire vault for blockers — explicit blocker callouts and overdue tasks. Separates your blockers from tasks assigned to others. Use for any blockers query: "what's blocked?", "show me blockers", "any blockers?", "what's holding things up?"
Deep-dive briefing on one person — role, shared projects, open items, pending feedback, 1:1 history, personal notes. Works for directs, peers, manager, or cross-team. (For all directs at once, use /myna:team-health.)
Catch me up on a project — quick (3-5 bullet TL;DR) or full (status, timeline, blockers, tasks, dependencies, upcoming meetings). Use for any project status or update request: "catch me up on X", "status of X", "how is X going", "where are we with X", "what's the latest on X".
Save information to the vault — quick notes, observations, tasks, recognition, project status. Use when: "capture: [text]", "log this", "add task: [desc]", "observation about [person]", "create recurring task". NOT for processing email/messages (/myna:process-updates), meeting notes (/myna:process-meeting), or inbox triage (/myna:email-triage). For links, use /myna:links.
Daily brief / "good morning" / "set up my day" — reads inbox and Slack in parallel, surfaces action items in the daily note, generates meeting prep, surfaces overdue tasks and review queue. Handles "plan tomorrow" and weekly note creation.