---
name: capabilities
description: Explain what the agent + vault can do and how to use it — a skimmable, per-vault tour of the features (task tracking with P-tier priorities, the daily digest, the knowledge base, People contacts, the daily debrief, areas of responsibility) with the how-to for each, plus whatever optional modules are turned on. Use when the owner says "what can you do", "help", "capabilities", "features", "what can I ask you", "how do I …", "getting started", "show me around", or "give me a tour". Reads the vault's config so it presents only what's actually enabled. NOT for changing settings (that's the settings skill), NOT the daily debrief, and NOT for filing pasted content (that's vault-ingestion).
served: true
---

# Capabilities — what this vault can do

A guided tour of everything the agent + vault can do, tailored to what's turned on **here**. The canonical, browsable version is **[[Guide]]** (`Guide.md` at the vault root — Core, refreshed on every update); this skill presents it conversationally and points into the detail. **Don't restate feature specifics from memory** — read them from `Guide.md`, `Agent/config.json`, and the [[AGENTS]] sections/schemas they name, so nothing drifts.

When this skill fires:

1. **See what's actually on.** Read `Agent/config.json` — `modules.enabled`, `areas`, `owner_digests`, `team`, `peers`, `automation.runner`/`send_hour_local` — and skim **[[Guide]]**. Present only what's enabled; mention a disabled feature only as *"I can turn on …"*.
2. **Pick the transport** per AGENTS "Transports: reaching the vault" — probe the local Semantic MCP first for the markdown, GitHub connector as fallback; say so if you fall back.
3. **Give a skimmable tour**, following the owner's [[Working Style]] (lead with the answer, keep it tight). Group by what they can *do* — one line of *what it is* + the exact phrase to *say* — not by internal structure:
   - **Track tasks & priorities** — per-area todos with **P0–P4** tiers and `due`/`check` dates, the auto-built [[Action Board]], and pinning today's focus in the daily note's `## Priorities`.
   - **Your morning brief** — the daily digest: what's in it, how to get one now (*"good morning"* / *"send my digest now"*), and tuning/splitting it. Check `automation.runner` before saying when it lands: with no runner it is **on-demand only** — present it that way, never as arriving by itself.
   - **Remember & retrieve** — the knowledge base (PEAK), *"file this"* for anything pasted/dropped, and *"what do we know about …"*.
   - **People** — a contact note per person with history; *"what's my history with [[Name]]"*.
   - **Close the day** — *"let's debrief"* (routes the day into the pillars) and *"log this"* (daily-progress).
   - **Areas** — *"add / rename an area"*.
   - **Tune me** — *"settings"* (name, voice, working style, digest, areas, team).
   - **Turned-on extras** — ONLY the enabled modules (team briefs, email-your-vault, *"what needs me"* triage, peer sharing, iMessage / WhatsApp reads, Contacts import).
   - **Stay current** — *"update yourself"*.
4. **Offer depth, don't dump.** Close by inviting a follow-up (*"want the detail on any of these?"*) and point to **[[Guide]]** for the full written how-to and `Agent/schemas/` for exact note formats. If they pick one, walk it in detail from the Guide + the relevant schema.

Key rules:
- **Adaptive, never generic.** A module not in `modules.enabled` is presented as *available to enable*, never as if it's running. Reflect the owner's real areas/team/digests from config.
- **Read, don't recite.** [[Guide]], [[AGENTS]], and `Agent/schemas/` are the source of truth; this skill orchestrates presenting them — it holds no feature facts of its own.
- **Read-only.** This skill only explains. Route *"change X"* to **settings**, *"file this"* to **vault-ingestion**, *"let's debrief"* to the debrief workflow — offer, don't do.
