// Read and write agent storage — memory and rules with environment-aware fallback
| name | inbox-memory |
| description | Read and write agent storage — memory and rules with environment-aware fallback |
| tools | ["memory","execute","bash","read","view","edit"] |
This skill reads and writes persistent memory and rules files for the Inbox agent. It abstracts storage so all agents use a single skill instead of calling #memory directly.
github-inbox-memory.md — session context, patterns, preferencesgithub-inbox-rules.md — user's rules and preferencesTry the #memory tool first (available in VS Code Chat). If #memory is not available (e.g. Copilot CLI), fall back to the file system under ~/.copilot/:
~/.copilot/github-inbox-memory.md~/.copilot/github-inbox-rules.md#memory with { "command": "view", "path": "/memories/github-inbox-memory.md" }.#memory is available. Use it for all reads and writes.Via #memory:
{ "command": "view", "path": "/memories/github-inbox-memory.md" }
{ "command": "view", "path": "/memories/github-inbox-rules.md" }
Via file system (fallback):
Read ~/.copilot/github-inbox-memory.md or ~/.copilot/github-inbox-rules.md using #read (VS Code) or #view (CLI). If the file doesn't exist, treat as empty / first-time user.
Via #memory:
{ "command": "delete", "path": "/memories/github-inbox-memory.md" }
{ "command": "create", "path": "/memories/github-inbox-memory.md", "file_text": "<content>" }
If the file doesn't exist yet, skip the delete and just use create.
Via file system (fallback):
~/.copilot/ exists: mkdir -p ~/.copilot#edit or via terminal: write full content to ~/.copilot/github-inbox-memory.md./memories/repo/) — only the files listed aboveDeep research on a given topic. Use for comprehensive topic exploration — technical subjects, market analysis, architecture deep-dives, competitive analysis, etc. Also use when the user asks to 'research', 'deep dive', 'investigate', or 'find out about' a topic that requires multi-source synthesis. You should run MULTIPLE subagents in parallel to explore multiple angles and topics.
High-signal feedback on plans, designs, implementations, and partial progress. Catches bugs, logic errors, and design flaws that may not be apparent to the original author. Call this skill for any non-trivial task to get a second opinion — the best time is after planning but before implementing. Call it early and often during development to course correct before problems compound. Will NOT comment on style, formatting, or trivial matters.
Multi-model council planning for implementation and architecture decisions. Use when the user asks to 'plan with council', 'multi-model plan', 'get different perspectives on approach', 'council plan', or wants multiple models to independently propose plans for the same task. Also use when the user asks to 'debate approaches', 'compare strategies', or 'cross-plan'.
Multi-model council review for diffs, pull requests, and risky changes. It is CRITICAL to use this skill after ANY non-trivial development phase — changes are usually not 100% correct. Development CANNOT be called done until the code has been reviewed. Use whenever the user asks for a review, PR feedback, a bug hunt in recent edits, or wants multiple models to inspect the same change independently. Also use when the user asks to 'discuss findings', 'cross-review', or 'debate' review results between models.
Monitor a pull request until CI status or Copilot review is available. Use when: monitor PR, watch PR, land PR, wait for CI, wait for checks, wait for review, check PR status. Starts two async terminal tasks (CI + Copilot review) and reacts when either completes.
Analyze VS Code rolling build health on Azure DevOps. Use when: the rolling build is red right now, you need a report for the last 100 builds, you need to identify the commit range that broke the build, you are on build champ duty, or you need a build health report.