Menu
System behavior rules — config reload, graceful degradation, error recovery with inline reporting, relative date resolution, fuzzy name resolution
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | steering-system |
| disable-model-invocation | true |
| description | System behavior rules — config reload, graceful degradation, error recovery with inline reporting, relative date resolution, fuzzy name resolution |
| user-invocable | false |
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.
Read config files at the start of each new session — not on every prompt. Configs don't change mid-conversation.
If the user explicitly updates config during a session, use the updated values for the rest of that session. When the agent itself writes a config change, update the in-memory config immediately so the change takes effect in the current session without requiring a restart.
Explicit reload command: When the user says "reload config", "refresh config", "re-read config", "reload my config", or any semantically equivalent phrasing (e.g. "load the latest config", "pick up the config changes"), re-read all five user config files fresh from disk:
{vault_path}/myna/_system/config/workspace.yaml{vault_path}/myna/_system/config/projects.yaml{vault_path}/myna/_system/config/people.yaml{vault_path}/myna/_system/config/communication-style.yaml{vault_path}/myna/_system/config/tags.yamlUpdate session context with the values just read. Then confirm: "Config reloaded. {summary of key loaded values — name, timezone, project count, people count.}"
When an external MCP (email, Slack, calendar) is unavailable:
Missing config sections cause the related feature to be skipped, not an error.
When a multi-step operation partially fails:
Example inline failure report:
Partial success — 3 of 4 items written.
✓ Projects/auth-migration.md — task added
✓ People/sarah-chen.md — observation added
✓ Journal/contributions-2026-04-07.md — contribution logged
✗ Projects/aurora-dashboard.md — file not found (create it first or route to review queue)
Convert "by Friday", "next week", "in 3 days", "tomorrow" to absolute dates using the timezone from workspace.yaml and today's date. Always store the resolved date, never the relative reference.
Resolve person, project, and meeting names against config using this cascade:
Outcomes:
Use Claude Code built-in tools (Read, Write, Edit, Grep, Glob) for all plain file I/O against the vault. These are faster and work even when Obsidian isn't running.
Use external MCP tools only for services outside the vault: email, Slack, calendar. Skills call MCP tools directly by the names available in the Claude Code session — the skill instructions describe the intent; Claude Code resolves the tool call.
Before executing any Myna skill, check whether a user override file exists at:
~/.myna/overrides/skills/{skill-name}.md
where {skill-name} matches the skill's name field (e.g., sync.md for /myna:sync, email-triage.md for /myna:email-triage).
If the file exists, read it before the skill body takes effect. Override content takes precedence over built-in skill defaults when they conflict. If the file does not exist, proceed with the built-in skill as normal.
This directory is outside the plugin directory and survives plugin updates, allowing users to customize skill behavior persistently.
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?"
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.
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.