emos

Create a new GitHub issue (optionally added to a GitHub Project board) following the project's standard format — gathers the details, shows a draft for confirmation, then creates it via the `gh` CLI. Use when the user wants to file, open, or create a GitHub issue. Optionally pass the repo and/or issue title as args.

Explore a remote GitHub repository read-only via the `gh` CLI — search code, read a file at a ref, view repo structure, trace the history/PRs touching a path, and blame lines. Use when investigating an incident or working an assignment against code you don't have checked out, across one or more repos. Pass the repo(s) (`owner/repo`) and what you're looking for as args.

Fetch a GitHub pull request as a structured bundle (metadata, diff, changed files with stats, commits, CI/check status, and existing review comments) via the `gh` CLI. Transport-only — it retrieves, it does not judge. Used by the tool-agnostic `pr-review` skill; you normally won't invoke it directly. Pass a PR number, URL, or branch (and optionally `owner/repo`) as args.

Sync a GitHub Project board into an emOS report grouped by status. Use when the user wants an up-to-date snapshot of a GitHub Projects (v2) board pulled into 10-reports/. Optionally pass a project number/URL, an owner, or a status filter as args.

Do a first-line review pass on a pull request — summarize the changes, flag obvious issues, highlight architectural/dependency changes, and escalate what needs human attention. It hands you structured input to act on; it does NOT auto-approve or post to the code host. Use when the user wants a PR reviewed, triaged, or summarized before they dig in. Pass a PR number, URL, or branch as args.

Import any document by URL into emOS. Detects the transport (Confluence, Google Docs, GitHub, or a generic web page), delegates to the medium-specific provider skill when its capability is configured, classifies the content, files it, and pulls any action items assigned to the owner into the current week's plan. Use when the user gives a URL and wants its content brought into the vault. Pass the URL (and optionally a hint about the doc type) as args.

Create the planning file for the current week, carrying forward open TODOs and follow-ups from the previous week. Use when the user wants to start a new week's plan. No args needed.

Fetch a Confluence page by URL, save it into 00-inbox with import frontmatter, classify its content, and propose (but not execute) where it should live in emOS. Use when the user gives a Confluence URL and wants it imported into emOS. Pass the page URL as args.

Append accomplishments to your evergreen impact log (brag doc), creating it if absent, so self-reviews and weekly snippets write themselves. With no args, harvest recent wins from your weeklies, completed projects, decisions, and incidents and propose entries to add. Use when the user wants to log a win, update their brag doc / impact log, or record an accomplishment. Pass the accomplishment as args, or none to harvest.

Create a technical design doc / RFC in a project's docs/ from the design-doc template. Use when the user wants to write, draft, or start a design doc, RFC, technical design, tech spec, or engineering proposal for how to build something — "RFC" and "design doc" mean the same artifact here. Pass the title and/or its project as args (e.g. "Idempotent retries for payments-platform").

Gather evidence and draft a review narrative — a self-review / brag-doc for yourself, or a review of someone else — from 1-on-1s, weekly mentions, projects, and incidents, without inventing ratings. Use when the user wants to prepare or update a performance review or self-review. Pass the person's name as args, or none for a self-review.

Create an experiment / A-B test brief in a project's docs/experiments/ from the experiment template. Use when the user wants to design, plan, or start an experiment, A/B test, or growth test. Pass the experiment name and/or its project as args (e.g. "One-tap reorder test for payments-platform").

Create a Product Requirements Document (PRD) in a project's docs/ from the prd template. Use when the user wants to write, draft, or start a PRD, product spec, or requirements doc for a feature or initiative. Pass the PRD title and/or its project as args (e.g. "Guest checkout for payments-platform").

Create a user-research note (interviews, usability test, survey, discovery) in 09-knowledge/research/ from the user-research template. Use when the user wants to plan or capture user research, customer interviews, usability testing, or discovery findings. Pass the study topic and optionally its project as args (e.g. "Onboarding interviews for payments-platform").

Create a product roadmap (Now / Next / Later) in 07-strategy/roadmaps/ from the roadmap template. Use when the user wants to start, draft, or plan a roadmap for a horizon, quarter, or half. Pass the roadmap name/horizon as args (e.g. "Payments H2 2026").

Health-check the vault for integrity problems — missing or invalid frontmatter, bad status values, rotted project links, unmapped @mentions, misfiled files, broken cross-links, and stale dashboards or rollups. Read-only: it reports findings and suggests fixes but changes nothing on its own. Use when the user wants to lint, check, validate, audit, or health-check the vault, or asks "what's broken?". Optionally pass a folder path or a check name (frontmatter · projects · people · links · dashboards · naming) as args to narrow the scope.

Google Calendar: read the agenda and manage events.

Google Docs: read and create documents.

Google Docs: Append text to a document.

Google Drive: search, read, export, and upload files.

Google Drive: Upload a file with automatic metadata.

Gmail: Read a message and extract its body or headers.

Gmail: read, search, and send email.

Gmail: Show unread inbox summary (sender, subject, date).

gws CLI: shared auth, global flags, and output conventions. Read before any other gws-* skill.

Google Sheets: Read values from a spreadsheet.

Google Sheets: read and write spreadsheet values.

Google Slides: read and create presentations.

Process one item from 00-inbox/ — classify its contents (action, project-seed, person-note, decision-point, knowledge, meeting-note, incident-signal, hiring-note, unclear), recommend where each piece should go, and wait for confirmation before moving or deleting anything. Use when the user wants to triage inbox items. Optionally pass a filename or search term as args to target a specific item.

Capture a Slack thread or message into 00-inbox as a classified markdown note (decision, action-items, or discussion). Use when the user wants to save a Slack conversation into emOS. Pass a Slack URL, channel plus search terms, or a description as args.

Prepare a 1-on-1 session prep file for someone — pulls their profile, unresolved carry-over from the last session, recent weekly mentions, and project context, framed by your relationship to them (report, manager, peer, or stakeholder). Use when the user asks to prep, prepare, or get ready for a 1-on-1 with someone. Pass the person's name as args.

Interactively set up or update your emOS configuration — owner, team, people, which tools you use (issue tracker, wiki, chat, docs), and their coordinates. Use for first-time setup or to change settings later. Nobody should hand-edit YAML; run this instead. No args (or pass a section name like "tools" or "people" to jump straight to it).

Draft and save your weekly status / async report by synthesizing the current weekly file, this week's 1-on-1s (if any), active projects, and incidents — formatted for your role (manager async, IC snippets, PM product status, or director portfolio update). Use when the user needs to write their weekly status update. No args needed.

Give a terse morning briefing — open TODOs, blockers/follow-ups, active incidents, upcoming P0/P1 project deadlines, and this week's scheduled 1-on-1s. Use when the user asks for a morning briefing or "what's on my plate today". Optionally pass a date as args.

Regenerate all _index.md dashboard files (weekly, people, projects, decisions, incidents, hiring, strategy) from current content. Use when the user asks to rebuild, refresh, or regenerate the dashboards/indexes. No args needed.

Run the end-of-week review — tally task completion, scan 1-on-1s/projects/incidents for the week, and mark the current weekly file completed with a retrospective. Use when the user wants to close out the current week. No args needed.

Create a new Jira ticket in your workspace following the project's standard format — gathers the details, shows a draft for confirmation, then creates it via MCP. Use when the user wants to file, open, or create a Jira ticket or issue. Optionally pass the ticket summary as args.

Quick-capture a short piece of text into today's inbox file with a timestamp — no analysis or reformatting. Use when the user says "capture this", wants a quick note jotted down, or wants something saved to 00-inbox fast. Pass the text to capture as args.

Push a local emOS markdown file to Confluence under the team space, creating or updating the page as needed. Use when the user wants to publish or sync a local emOS file to Confluence. Pass the file path as args.

Create a new Architecture Decision Record (ADR) with the next sequential number, from the decision-record template. Use when the user wants to record or start a new architectural or technical decision. Pass the decision title as args.