atris 3.74.4 → 3.74.5

package/atris/skills/endgame/SKILL.md

@@ -5,34 +5,34 @@ version: 1.2.0
 tags: [planning, vision, reverse-engineer, atris, wiki, todo, flow]
 ---
 
-> **Sister skill: /flow** — flow runs the same engine in reverse. flow chains forward from identity (who you are → today's next move). endgame chains backward from horizon (where you're going → today's next move). They meet at the same point: the next thing the agent should ship. Use both. Run flow at sunrise to set identity, run endgame at every TODO.md boundary to set horizon, and let /autopilot tick between them.
+> **Sister skill: /flow**: flow runs the same engine in reverse. flow chains forward from identity (who you are → today's next move). endgame chains backward from horizon (where you're going → today's next move). They meet at the same point: the next thing the agent should ship. Use both. Run flow at sunrise to set identity, run endgame at every TODO.md boundary to set horizon, and let /autopilot tick between them.
 
 # /endgame
 
-**Purpose:** help the human (or agent) reach their intent and goal **faster** by leveraging what the wiki already knows. Without endgame, they redo thinking. With endgame, they reach the next move in one pass — and write that move into TODO.md so the autopilot loop can pursue it without re-asking.
+**Purpose:** help the human (or agent) reach their intent and goal **faster** by leveraging what the wiki already knows. Without endgame, they redo thinking. With endgame, they reach the next move in one pass, and write that move into TODO.md so the autopilot loop can pursue it without re-asking.
 
 Most planning is forward-greedy: *what's the next ticket?* Endgame is backward: *what does winning look like, and what's the shortest path from here?*
 
-> "You can't connect the dots looking forward; you can only connect them looking backward." — Steve Jobs
+> "You can't connect the dots looking forward; you can only connect them looking backward.": Steve Jobs
 
-## Step 0 — CHECK FOR EXISTING ENDGAME FIRST
+## Step 0: CHECK FOR EXISTING ENDGAME FIRST
 
-Before anything else, read `atris/TODO.md`. If it already has a `## Endgame` section AND uncompleted `[endgame]`-tagged tasks in `## Backlog`, **do not pick a new endgame**. Instead reply: "current endgame `<slug>` still active — N steps remaining. Run `/autopilot` to continue, or `force /endgame` to reset." Then exit.
+Before anything else, read `atris/TODO.md`. If it already has a `## Endgame` section AND uncompleted `[endgame]`-tagged tasks in `## Backlog`, **do not pick a new endgame**. Instead reply: "current endgame `<slug>` still active, N steps remaining. Run `/autopilot` to continue, or `force /endgame` to reset." Then exit.
 
 This rule exists so the loop pursues the current horizon to completion instead of constantly repicking.
 
-## Step 1 — READ THE INBOX, WIKI, LOGS
+## Step 1: READ THE INBOX, WIKI, LOGS
 
 Before picking a new horizon, read what already exists. The wiki + logs are the user's paid-for memory; not using them means they're paying twice.
 
-- `atris/lessons.md` — past surprises and failures the validator wrote down. Read this FIRST. Avoid horizons that hit the same rocks.
-- `atris/wiki/STATUS.md` — current state, last loop findings, suggested next ingests
-- `atris/wiki/index.md` — what pages already exist
-- `atris/wiki/briefs/` — most recent cross-cutting brief pages (often already contain a horizon)
-- `atris/MAP.md` — what code exists today
-- `atris/TODO.md` — what's queued, what's done
-- `atris/logs/YYYY/` — last 7-14 days of journals; scan `## Inbox` sections for unfulfilled ideas (these are user-seeded horizons)
-- `atris/PERSONA.md` — current identity (paired with /flow's forward direction)
+- `atris/lessons.md`: past surprises and failures the validator wrote down. Read this FIRST. Avoid horizons that hit the same rocks.
+- `atris/wiki/STATUS.md`: current state, last loop findings, suggested next ingests
+- `atris/wiki/index.md`: what pages already exist
+- `atris/wiki/briefs/`: most recent cross-cutting brief pages (often already contain a horizon)
+- `atris/MAP.md`: what code exists today
+- `atris/TODO.md`: what's queued, what's done
+- `atris/logs/YYYY/`: last 7-14 days of journals; scan `## Inbox` sections for unfulfilled ideas (these are user-seeded horizons)
+- `atris/PERSONA.md`: current identity (paired with /flow's forward direction)
 - `atris/business/<slug>/BUSINESS.md` if a business workspace
 
 **Inbox items are the primary horizon source.** If recent journal `## Inbox` sections have unfulfilled ideas, pick the oldest one and run the three moves on it. Only fall back to reactive signals (wiki staleness, broken refs) if the inbox is empty.
@@ -41,13 +41,13 @@ If the horizon is genuinely unreadable from those sources, ask **1–3 sharp que
 
 ## The three moves
 
-1. **HORIZON** — One paragraph. What does the world look like when we win? Concrete. Falsifiable. Not a slogan.
-2. **REVERSE PATH** — Chain backward from HORIZON. Last move before winning, the one before, etc. **Include eliminate steps** — what gets deleted on the way to the endgame, not just what gets added. Stop when you hit something doable this week. 5–7 links max.
-3. **NEXT MOVE** — The first link in the chain. One concrete action, one session, no hedging.
+1. **HORIZON**: One paragraph. What does the world look like when we win? Concrete. Falsifiable. Not a slogan.
+2. **REVERSE PATH**: Chain backward from HORIZON. Last move before winning, the one before, etc. **Include eliminate steps**: what gets deleted on the way to the endgame, not just what gets added. Stop when you hit something doable this week. 5–7 links max.
+3. **NEXT MOVE**: The first link in the chain. One concrete action, one session, no hedging.
 
-> **v1.1.0 cut:** prior versions had two more moves — `IDENTITY` ("who are we when we've arrived") and `GAP` ("already true vs not yet"). Identity was philosophical overhead; GAP was just the diff between HORIZON and current state, which the wiki + MAP already give you. Three moves is enough. Less drift surface, faster ticks, fewer phrases for the validator to verify.
+> **v1.1.0 cut:** prior versions had two more moves, `IDENTITY` ("who are we when we've arrived") and `GAP` ("already true vs not yet"). Identity was philosophical overhead; GAP was just the diff between HORIZON and current state, which the wiki + MAP already give you. Three moves is enough. Less drift surface, faster ticks, fewer phrases for the validator to verify.
 
-## Step 2 — WRITE TO TODO.md
+## Step 2: WRITE TO TODO.md
 
 After running the three moves, write the result to `atris/TODO.md`:
 
@@ -64,9 +64,9 @@ After running the three moves, write the result to `atris/TODO.md`:
 
 **Horizon voice rule (non-negotiable).** The horizon renders verbatim on every boot to whoever opens the workspace: engineer, operator, or a first-day outsider. Write it so a new teammate in any domain gets it on first read: one sentence, plain words, no em dashes, no ids/flags/insider jargon (no "dispatch", "lane", "fast-tier", "receipt path"), and it names the observable proof ("proven the day X happens"). If a term only means something to the people who built the system, translate it or cut it.
 
-2. **Add each REVERSE PATH step as a tagged task — through the task db when one exists.**
+2. **Add each REVERSE PATH step as a tagged task: through the task db when one exists.**
 
-**Durable-db workspaces (any repo with `.atris/state/tasks.projection.json` / the `atris task` verb):** markdown task lines written into TODO.md DO NOT SURVIVE — the next `atris task render` regenerates the file from the db and silently wipes them (learned 2026-07-12, lesson `endgame-tasks-must-be-durable-db-rows`; the `## Endgame` header block survives, the tasks vanish). Create each step as a real row instead:
+**Durable-db workspaces (any repo with `.atris/state/tasks.projection.json` / the `atris task` verb):** markdown task lines written into TODO.md DO NOT SURVIVE: the next `atris task render` regenerates the file from the db and silently wipes them (learned 2026-07-12, lesson `endgame-tasks-must-be-durable-db-rows`; the `## Endgame` header block survives, the tasks vanish). Create each step as a real row instead:
 
 ```bash
 atris task add "<step description>" --tag endgame
@@ -107,7 +107,7 @@ Use `T1`, `T2`, `T3` … as IDs (or `W1`/`E1`/etc per endgame domain). Single up
 4. **Append the full endgame to today's journal `## Notes`** so the reasoning is preserved:
 
 ```markdown
-### Endgame picked — HH:MM PDT
+### Endgame picked: HH:MM PDT
 
 slug: <slug>
 source: <where>
@@ -129,14 +129,14 @@ NEXT MOVE
   Why this first: <one line>
 ```
 
-This is the archive — once the endgame closes, future `/endgame` runs can read this to learn what worked.
+This is the archive, once the endgame closes, future `/endgame` runs can read this to learn what worked.
 
-## Step 3 — ARCHIVE PRIOR ENDGAME (if any)
+## Step 3: ARCHIVE PRIOR ENDGAME (if any)
 
 If there was a `## Endgame` section in TODO.md before this run AND all its `[endgame]` tasks are done, append a closing entry to today's journal `## Notes`:
 
 ```markdown
-### Endgame closed — HH:MM PDT
+### Endgame closed: HH:MM PDT
 
 slug: <prior-slug>
 shipped: N/N steps
@@ -148,7 +148,7 @@ Then remove the old `## Endgame` section from TODO.md before writing the new one
 
 ## Output shape (when called interactively)
 
-When a human runs `/endgame` directly (not from a cron tick), show the three moves on screen first, ask one yes/no for confirmation, then write to TODO.md only after the human says go. When called from autopilot at a boundary, skip the confirmation — write straight to TODO.md and journal it.
+When a human runs `/endgame` directly (not from a cron tick), show the three moves on screen first, ask one yes/no for confirmation, then write to TODO.md only after the human says go. When called from autopilot at a boundary, skip the confirmation: write straight to TODO.md and journal it.
 
 ```
 HORIZON
@@ -163,7 +163,7 @@ REVERSE PATH
 
 NEXT MOVE
   [one concrete action, doable in one session]
-  Verify: [deterministic check — test, grep, file, exit code]
+  Verify: [deterministic check, test, grep, file, exit code]
   Why this first: [one line]
 ```
 
@@ -173,7 +173,7 @@ NEXT MOVE
 - **Read inbox + wiki first.** The whole point is leveraging what exists.
 - **HORIZON before REVERSE PATH.** Vision before steps.
 - **REVERSE PATH includes eliminate.** Half of strategy is removal. Forward-greedy planning never asks this. Endgame must.
-- **The chain must terminate this week.** If it can't, the horizon is too far — pick a closer one and say so.
+- **The chain must terminate this week.** If it can't, the horizon is too far: pick a closer one and say so.
 - **5–7 links max in the chain.** More than that = horizon is too vague.
 - **Every task must have a Verify line.** Deterministic check (test, grep, file, exit code). Allows the validator to score the endgame autonomously.
 - **Cite wiki pages** with `[[atris/wiki/...]]` refs.
@@ -181,11 +181,11 @@ NEXT MOVE
 - **One chain, not three.** Pick the shortest defensible one.
 - **No "we could also"** anywhere in NEXT MOVE. There is one move.
 - **Reject mysticism.** Vision is necessary but not sufficient. The chain must be falsifiable and doable.
-- **Tag format is `[endgame]` only** — no colons, no slugs in the tag. Slug lives in the section header.
+- **Tag format is `[endgame]` only**, no colons, no slugs in the tag. Slug lives in the section header.
 
-## Phase 2 — agent runs this on itself
+## Phase 2: agent runs this on itself
 
-This skill is designed to be runnable by the agent on its own state, not just by humans. When `atris autopilot` finishes the last `[endgame]` task in the current horizon, the next tick's boundary check invokes `/endgame` against the new state, picks the next horizon from inbox/wiki, writes it to TODO.md, and queues the next move — without a human pulling the trigger.
+This skill is designed to be runnable by the agent on its own state, not just by humans. When `atris autopilot` finishes the last `[endgame]` task in the current horizon, the next tick's boundary check invokes `/endgame` against the new state, picks the next horizon from inbox/wiki, writes it to TODO.md, and queues the next move, without a human pulling the trigger.
 
 ## When to use vs other skills
 
@@ -208,5 +208,5 @@ This skill is designed to be runnable by the agent on its own state, not just by
 - Chain longer than 7 links. Shorten the horizon.
 - Three "next moves." There is one.
 - Quoting goals from a deck. Read the wiki, look at reality.
-- Tagging tasks with `[endgame:slug]` — parser only accepts `[\w+]`, will fail silently.
-- Padding with IDENTITY or GAP sections — those were cut in v1.1.0 as autopilot overhead.
+- Tagging tasks with `[endgame:slug]`, parser only accepts `[\w+]`, will fail silently.
+- Padding with IDENTITY or GAP sections, those were cut in v1.1.0 as autopilot overhead.

package/atris/skills/magic-inbox/SKILL.md

@@ -10,7 +10,7 @@ tags:
 
 # Magic Inbox
 
-You are an inbox agent. You read email, decide what matters, draft replies, archive noise, and notify the user. You do this using your own intelligence — no separate LLM calls needed. You ARE the model.
+You are an inbox agent. You read email, decide what matters, draft replies, archive noise, and notify the user. You do this using your own intelligence. No separate LLM calls needed. You ARE the model.
 
 ## Bootstrap (ALWAYS Run First)
 
@@ -41,11 +41,11 @@ export ATRIS_TOKEN="$TOKEN"
 
 Before triaging, ALWAYS read these context files from the skill directory. They tell you who matters and how to behave.
 
-- `~/.claude/skills/magic-inbox/contacts.md` — priority contacts and noise patterns
-- `~/.claude/skills/magic-inbox/priorities.md` — current work streams
-- `~/.claude/skills/magic-inbox/voice.md` — how to write replies
-- `~/.claude/skills/magic-inbox/rules.md` — hard rules that override everything
-- `~/.claude/skills/magic-inbox/log.md` — action log (append after each run)
+- `~/.claude/skills/magic-inbox/contacts.md`: priority contacts and noise patterns
+- `~/.claude/skills/magic-inbox/priorities.md`: current work streams
+- `~/.claude/skills/magic-inbox/voice.md`: how to write replies
+- `~/.claude/skills/magic-inbox/rules.md`: hard rules that override everything
+- `~/.claude/skills/magic-inbox/log.md`: action log (append after each run)
 
 Read ALL context files before scoring. They are your memory.
 
@@ -97,8 +97,8 @@ Using YOUR judgment, score each email:
 | 5 | Noise | Archive |
 
 **Scoring signals:**
-- Check `contacts.md` — is sender a priority contact?
-- Check `priorities.md` — is topic related to current work?
+- Check `contacts.md`: is sender a priority contact?
+- Check `priorities.md`: is topic related to current work?
 - Has `has_unsubscribe: true` → almost certainly 4-5
 - Addressed directly (not a list) → lean toward 1-3
 - From a real person at a real company → lean toward 1-3
@@ -146,14 +146,14 @@ Append to `~/.claude/skills/magic-inbox/log.md` what you did this run.
 ## Summary Format
 
 ```
-Inbox Triage — 23 emails processed
+Inbox Triage: 23 emails processed
 
 Needs you (2):
-  - Suhas (via Maya) — FDE candidate intro. Draft ready. [check drafts]
-  - Michelle at Stripe — Build Day March 4, demo opportunity. Draft ready.
+  - Suhas (via Maya): FDE candidate intro. Draft ready. [check drafts]
+  - Michelle at Stripe: Build Day March 4, demo opportunity. Draft ready.
 
 This week (1):
-  - Kim (angel, 9x founder) — intro.co intro. Worth a call.
+  - Kim (angel, 9x founder): intro.co intro. Worth a call.
 
 Handled (20):
   - 12 archived (newsletters, marketing)
@@ -167,7 +167,7 @@ Rules for summary:
 - Use real names, not email addresses
 - Include WHY something is important (from context files)
 - For drafts, tell the user to check Gmail drafts
-- Be concise — this is a briefing, not a report
+- Be concise. This is a briefing, not a report
 - Show the count reduction (was X, now Y)
 
 ---
@@ -179,7 +179,7 @@ Follow `voice.md`. General rules:
 - Casual, direct, no fluff
 - No "I hope this email finds you well"
 - No "Just circling back" or "Per my last email"
-- Short — 2-4 sentences max
+- Short: 2-4 sentences max
 - Match the energy of the incoming email
 - For intros: be warm, suggest a time, keep it to 2 sentences
 - For RSVPs: be enthusiastic, confirm attendance
@@ -193,7 +193,7 @@ Hard rules that override everything:
 1. NEVER auto-send. Always save as draft for user review.
 2. NEVER archive emails from priority contacts (even if they look like noise).
 3. NEVER reply to emails with List-Unsubscribe header.
-4. Always show the user what you did — no silent actions.
+4. Always show the user what you did. No silent actions.
 5. If unsure about priority, err toward keeping it (don't archive).
 6. Log every action to log.md.
 

package/atris/skills/notion/SKILL.md

@@ -411,7 +411,7 @@ Common block types for creating content:
 
 ## Important Notes
 
-- **Notion tokens don't expire** — once connected, it stays connected
+- **Notion tokens don't expire.** Once connected, it stays connected
 - **Page IDs**: Notion uses UUIDs like `12345678-abcd-1234-abcd-123456789abc`. You can get them from URLs or search results
 - **Database pages**: When adding rows to a database, the "page" properties must match the database schema
 - **Content = Blocks**: A page's visible content is a list of blocks. Use the blocks endpoint to read/write content

package/atris/skills/ramp/SKILL.md

@@ -11,7 +11,7 @@ tags:
 
 # Ramp
 
-Corporate spend management via Ramp API. No OAuth needed — API key auth.
+Corporate spend management via Ramp API. No OAuth needed: API key auth.
 
 ## Setup
 
@@ -48,12 +48,12 @@ curl -s "https://api.ramp.com/developer/v1/transactions?page_size=50" \
 ```
 
 Filter params:
-- `from_date` / `to_date` — ISO 8601 (e.g. `2026-03-01`)
-- `department_id` — filter by department
-- `merchant_id` — filter by merchant
-- `user_id` — filter by cardholder
-- `min_amount` / `max_amount` — in cents
-- `state` — PENDING, CLEARED, DECLINED
+- `from_date` / `to_date`: ISO 8601 (e.g. `2026-03-01`)
+- `department_id`: filter by department
+- `merchant_id`: filter by merchant
+- `user_id`: filter by cardholder
+- `min_amount` / `max_amount`: in cents
+- `state`: PENDING, CLEARED, DECLINED
 
 ### Get Transaction
 ```bash

package/atris/skills/research-search/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: research-search
-description: "Fast research sweep — arxiv, semantic scholar, github, web. Finds papers, scores relevance, extracts actionable insights, stores to wiki. Triggers on: research search, find papers, latest research, arxiv, what's new in, sweep papers, research sweep."
+description: "Fast research sweep: arxiv, semantic scholar, github, web. Finds papers, scores relevance, extracts actionable insights, stores to wiki. Triggers on: research search, find papers, latest research, arxiv, what's new in, sweep papers, research sweep."
 version: 1.0.0
 tags:
   - research
@@ -10,7 +10,7 @@ tags:
   - ingestion
 ---
 
-# /research — Fast Research Sweep
+# /research: Fast Research Sweep
 
 Find the latest research on a topic, score it for relevance, extract what you can BUILD with it, store the best finds.
 
@@ -38,24 +38,24 @@ Read `atris/skills/research/program.md` for:
 
 For the given topic, search ALL of these sources in parallel (use Agent tool for parallelism):
 
-**Source A — arxiv API**
+**Source A: arxiv API**
 Run via Bash:
 ```bash
 python3 atris/skills/research/arxiv_search.py "<topic>" --after 2025-10-01 --limit 20
 ```
 Returns JSON array of papers with title, authors, abstract, date, url, categories.
 
-**Source B — Semantic Scholar API**
+**Source B: Semantic Scholar API**
 Run via Bash:
 ```bash
 python3 atris/skills/research/scholar_search.py "<topic>" --after 2025-10-01 --limit 20
 ```
 Returns JSON array with title, authors, abstract, date, url, citation count, venue.
 
-**Source C — Web search**
+**Source C: Web search**
 Use WebSearch tool: `"<topic>" site:arxiv.org OR site:github.com 2025..2026`
 
-**Source D — GitHub**
+**Source D: GitHub**
 Use WebSearch tool: `"<topic>" site:github.com stars:>100 pushed:>2025-10-01`
 
 ### Step 2: Deduplicate and rank
@@ -155,7 +155,7 @@ The research program evolves:
 1. After each sweep, note which papers scored highest and from which source
 2. If a paper leads to a successful implementation (tracked via /storysim or /autoresearch), boost that topic's weight
 3. If a sweep produces nothing actionable, refine the search queries
-4. The program.md file is the "policy" — update it as you learn what works
+4. The program.md file is the "policy": update it as you learn what works
 
 ## Rules
 

package/atris/skills/slides/SKILL.md

@@ -69,7 +69,7 @@ curl -s -X POST "https://api.atris.ai/api/integrations/google-slides/presentatio
 
 ## Updating Slides (batch-update)
 
-All slide mutations use the batch-update endpoint. This is the most powerful endpoint — it can add slides, insert text, add shapes, images, change formatting, and more.
+All slide mutations use the batch-update endpoint. This is the most powerful endpoint: it can add slides, insert text, add shapes, images, change formatting, and more.
 
 ```bash
 curl -s -X POST "https://api.atris.ai/api/integrations/google-slides/presentations/{id}/batch-update" \
@@ -308,12 +308,12 @@ Returns `{"pdf_base64": "...", "content_type": "application/pdf"}`.
 
 ## Important Notes
 
-- **Shares Drive OAuth** — no separate connection needed. If Drive is connected, Slides works
-- **Batch update is everything** — all slide mutations (add, edit, delete, style) go through batch-update
-- **Object IDs** — every slide, shape, text box, image has an ID. Get them from `GET /presentations/{id}`
-- **Slide size** — default is 10x5.63 inches (720x406.5 PT). Position elements accordingly
-- **Images** — must be publicly accessible URLs. For private images, upload to Drive first
-- **Templates** — use replaceAllText with `{{placeholder}}` patterns for template-based decks
+- **Shares Drive OAuth**: no separate connection needed. If Drive is connected, Slides works
+- **Batch update is everything**: all slide mutations (add, edit, delete, style) go through batch-update
+- **Object IDs**: every slide, shape, text box, image has an ID. Get them from `GET /presentations/{id}`
+- **Slide size**: default is 10x5.63 inches (720x406.5 PT). Position elements accordingly
+- **Images**: must be publicly accessible URLs. For private images, upload to Drive first
+- **Templates**: use replaceAllText with `{{placeholder}}` patterns for template-based decks
 
 ---
 

package/atris/skills/tidy/SKILL.md

@@ -11,7 +11,7 @@ tags:
 
 # /tidy
 
-Finds what's rotting in your workspace and fixes it. Not just broken refs — ghost names, stale lessons, duplicate data, language drift, dead code.
+Finds what's rotting in your workspace and fixes it. Not just broken refs: ghost names, stale lessons, duplicate data, language drift, dead code.
 
 ## When to use
 
@@ -30,25 +30,25 @@ Finds what's rotting in your workspace and fixes it. Not just broken refs — gh
 
 ### What to look for
 
-**Ghost names** — terms that don't match the current identity. Check package.json `name` and `description`, README title, and PERSONA. Grep the codebase for old names (e.g., "atrisDev" when the product is "atris"). Flag any user-facing string that uses a dead name.
+**Ghost names**: terms that don't match the current identity. Check package.json `name` and `description`, README title, and PERSONA. Grep the codebase for old names (e.g., "atrisDev" when the product is "atris"). Flag any user-facing string that uses a dead name.
 
-**Stale wiki pages** — pages with `last_compiled` frontmatter where the source files have been modified since. The page content may be wrong.
+**Stale wiki pages**: pages with `last_compiled` frontmatter where the source files have been modified since. The page content may be wrong.
 
-**Broken MAP.md references** — file:line refs that point to code that moved or was deleted. The auto-healer fixes what it can; report what it can't.
+**Broken MAP.md references**: file:line refs that point to code that moved or was deleted. The auto-healer fixes what it can; report what it can't.
 
-**Stale lessons** — lessons about bugs that have since been fixed. Grep the named files for the bug pattern. If it's gone, tag the lesson `[resolved]`.
+**Stale lessons**: lessons about bugs that have since been fixed. Grep the named files for the bug pattern. If it's gone, tag the lesson `[resolved]`.
 
-**Duplicate scorecards** — same slug appearing twice in scorecards.md. Keep the one with more data, delete the other.
+**Duplicate scorecards**: same slug appearing twice in scorecards.md. Keep the one with more data, delete the other.
 
-**Abandoned tasks** — in-progress tasks claimed more than 3 days ago. Either finish them, re-scope them, or delete them.
+**Abandoned tasks**: in-progress tasks claimed more than 3 days ago. Either finish them, re-scope them, or delete them.
 
-**Orphan docs** — markdown pages under atris/ that nothing links to. They're invisible and probably stale.
+**Orphan docs**: markdown pages under atris/ that nothing links to. They're invisible and probably stale.
 
-**Dead exports** — functions in module.exports that nothing imports. They add surface area for no reason.
+**Dead exports**: functions in module.exports that nothing imports. They add surface area for no reason.
 
-**Stale TODO items** — tasks older than 14 days that haven't moved. Run `isStillTrue` on each. Tag stale ones `[unverified]`.
+**Stale TODO items**: tasks older than 14 days that haven't moved. Run `isStillTrue` on each. Tag stale ones `[unverified]`.
 
-**Empty sections** — TODO.md sections with placeholder text like "(empty)" or "(clean)".
+**Empty sections**: TODO.md sections with placeholder text like "(empty)" or "(clean)".
 
 4. Present findings as a numbered list, sorted by impact. For each:
    - What's wrong (specific file, line, or term)

package/atris/skills/wake/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wake
-description: "Wake a team member by name — use gm [member] or wake up [member] — and run ONE closed-loop tick: boot, inbox, claim, one bounded slice, verify, commit+push, proof, receipt. Optionally dispatch the build to an engine (codex/cursor/devin). Triggers on: gm, good morning, wake up [member], wake the team, run a tick as [member]."
+description: "Wake a team member by name, use gm [member] or wake up [member], and run ONE closed-loop tick: boot, inbox, claim, one bounded slice, verify, commit+push, proof, receipt. Optionally dispatch the build to an engine (codex/cursor/devin). Triggers on: gm, good morning, wake up [member], wake the team, run a tick as [member]."
 version: 1.0.0
 tags:
   - wake
@@ -10,28 +10,28 @@ tags:
   - autonomous-org
 ---
 
-# Wake — one tick of a team member
+# Wake: one tick of a team member
 
 "gm [member]" means: that member does one real unit of work, end to end, with proof. No status theater. If there is nothing real to do, say so and stop.
 
 ## Resolving the member
 
-Look for `atris/team/{member}/` (or `team/{member}/`) in the current repo. If the member has a `WAKE.md`, follow it exactly — it overrides this skill. If not, run the default tick below and offer to write a `WAKE.md` from it.
+Look for `atris/team/{member}/` (or `team/{member}/`) in the current repo. If the member has a `WAKE.md`, follow it exactly: it overrides this skill. If not, run the default tick below and offer to write a `WAKE.md` from it.
 
 Wake-enabled lanes as of 2026-06-12: `neo` (atrisos-backend), `frontend-core-systems` (atrisos-web), `ios-engineer` (terrace), `mission-lead` (project-obelisk).
 
 ## The tick
 
-1. **Boot** — read `MEMBER.md`, `goals.md`, latest log in `logs/`, and `atris/MAP.md`.
-2. **Inbox** — today's log (`atris/logs/{year}/{date}.md`) section `## Feedback inbox`: promote bullets to the plane (`atris task add --tag {product}`), delete promoted bullets.
-3. **Claim** — `atris task queue`; claim the top unclaimed task `--as {member}`. Claimed by someone else → skip, no quick fixes. Nothing unclaimed → find ONE small genuine defect/improvement, add it to the plane, claim that.
-4. **Work** — ONE bounded slice. `git status` first; stage only own files; never destructive git; branch or worktree on shared checkouts. Build-heavy slice? Dispatch to an engine via the `engines` skill — the member still owns verification and the receipt.
-5. **Verify** — run the relevant build/tests. Evidence carries a timestamp.
-6. **Ship** — commit and PUSH to GitHub (at minimum once per completed slice). Then `atris task ready {id} --proof "{evidence}"`.
-7. **Receipt** — one line in today's log. Blocked on a human → `waiting-on-human` task ("WAITING ON {who}: {exact action}"). Nothing to do → say so and end quietly.
+1. **Boot**: read `MEMBER.md`, `goals.md`, latest log in `logs/`, and `atris/MAP.md`.
+2. **Inbox**: today's log (`atris/logs/{year}/{date}.md`) section `## Feedback inbox`: promote bullets to the plane (`atris task add --tag {product}`), delete promoted bullets.
+3. **Claim**: `atris task queue`; claim the top unclaimed task `--as {member}`. Claimed by someone else → skip, no quick fixes. Nothing unclaimed → find ONE small genuine defect/improvement, add it to the plane, claim that.
+4. **Work**: ONE bounded slice. `git status` first; stage only own files; never destructive git; branch or worktree on shared checkouts. Build-heavy slice? Dispatch to an engine via the `engines` skill. The member still owns verification and the receipt.
+5. **Verify**: run the relevant build/tests. Evidence carries a timestamp.
+6. **Ship**: commit and PUSH to GitHub (at minimum once per completed slice). Then `atris task ready {id} --proof "{evidence}"`.
+7. **Receipt**: one line in today's log. Blocked on a human → `waiting-on-human` task ("WAITING ON {who}: {exact action}"). Nothing to do → say so and end quietly.
 
 ## Hard rules
 
 - Only members claim; visiting agents may add/say/delegate, never claim.
-- Human acceptance (`atris task accept*`) is human-only — the CLI enforces it; never spoof agent detection to get past it.
+- Human acceptance (`atris task accept*`) is human-only: the CLI enforces it; never spoof agent detection to get past it.
 - One tick per wake. The loop's value is the receipt trail, not the volume.

package/atris/skills/writing/SKILL.md

@@ -17,11 +17,11 @@ Structured writing process with approval gates.
 INBOX → OUTLINE → PANEL → WRITE → PASSES
 ```
 
-1. **Inbox** — Capture raw ideas, no structure
-2. **Outline** — Topic skeleton with evidence underneath
-3. **Panel** — AI pokes holes, human approves
-4. **Write** — Section by section, approval each step
-5. **Passes** — Argument (AI), out loud (human), sanity (both)
+1. **Inbox**: Capture raw ideas, no structure
+2. **Outline**: Topic skeleton with evidence underneath
+3. **Panel**: AI pokes holes, human approves
+4. **Write**: Section by section, approval each step
+5. **Passes**: Argument (AI), out loud (human), sanity (both)
 
 ## Key Rules
 

package/atris/team/_template/SOUL.md

@@ -6,11 +6,11 @@ born: YYYY-MM-DD
 
 # Soul
 
-What this agent believes, values, and has learned — not what it does (that's MEMBER.md) or how it communicates (that's PERSONA.md). This is who it is when the rules run out.
+What this agent believes, values, and has learned, not what it does (that's MEMBER.md) or how it communicates (that's PERSONA.md). This is who it is when the rules run out.
 
 ## Beliefs
 
-What you hold true about your work. Not rules — convictions.
+What you hold true about your work. Not rules, convictions.
 
 - (Replace with 3-5 beliefs that guide judgment in ambiguous situations)
 
@@ -35,6 +35,6 @@ Where this agent's judgment is strong and where it's weak. Honest self-assessmen
 
 ## Voice
 
-Not communication style (that's PERSONA.md). This is the inner voice — the thing the agent says to itself before deciding.
+Not communication style (that's PERSONA.md). This is the inner voice: the thing the agent says to itself before deciding.
 
 - (One sentence that captures how this agent thinks)

package/atris/team/brainstormer/MEMBER.md

@@ -18,7 +18,7 @@ permissions:
 tools: []
 ---
 
-# Brainstormer — Idea & Reality Shaper
+# Brainstormer: Idea & Reality Shaper
 
 > **Source:** Inbox items, raw ideas
 > **Style:** Read `atris/PERSONA.md` for communication style.
@@ -271,7 +271,7 @@ When you finish a brainstorm session:
 **Pattern:** What you learned about the user's thinking style
 ```
 
-Your log tracks how ideas evolve — the navigator reads it to understand context.
+Your log tracks how ideas evolve: the navigator reads it to understand context.
 
 ---
 

package/atris/team/launcher/MEMBER.md

@@ -19,7 +19,7 @@ permissions:
 tools: []
 ---
 
-# Launcher — The Closer
+# Launcher: The Closer
 
 > **Source:** Completed tasks, validation results
 > **Style:** Read `atris/PERSONA.md` for communication style.
@@ -116,7 +116,7 @@ Launch Checklist:
 ✓ Journal entry: [timestamp]
 ✓ Ready to publish: [where?]
 
-🎉 SHIPPED! 🎉
+SHIPPED!
 ```
 
 ---

package/atris/team/mission-lead/MISSION.md

@@ -1,8 +1,8 @@
-# Mission — mission-lead
+# Mission: mission-lead
 
 ## North Star
 
-Find and ship one real, verifiable improvement to `atris-cli` per overnight tick — bug fix, UX polish, or doc/code drift correction. Push immediately. Don't sit on green commits.
+Find and ship one real, verifiable improvement to `atris-cli` per overnight tick: bug fix, UX polish, or doc/code drift correction. Push immediately. Don't sit on green commits.
 
 ## Acceptance
 
@@ -22,11 +22,11 @@ A tick is "done" when:
 
 ## Domains in Order
 
-1. **Help-flag handling** — every command should respect `-h`/`--help` without auth checks or API calls.
-2. **Pluralization / output polish** — single/plural forms, truncation markers, regex matches.
-3. **Doc drift** — MAP.md broken refs, CLAUDE.md vs actual command surface.
-4. **Test hygiene** — flaky tests (time-dependent, timezone-dependent), hardcoded values that age out.
-5. **Cross-command consistency** — same flag means the same thing, same output format.
+1. **Help-flag handling**: every command should respect `-h`/`--help` without auth checks or API calls.
+2. **Pluralization / output polish**: single/plural forms, truncation markers, regex matches.
+3. **Doc drift**: MAP.md broken refs, CLAUDE.md vs actual command surface.
+4. **Test hygiene**: flaky tests (time-dependent, timezone-dependent), hardcoded values that age out.
+5. **Cross-command consistency**: same flag means the same thing, same output format.
 
 ## Stop Condition