@jayjiang/byoao 2.0.1 → 2.0.3

package/dist/assets/skills/organize.md

@@ -1,107 +0,0 @@
----
-name: organize
-description: >
-  Directory organization based on frontmatter metadata. Suggests and applies file moves to
-  keep the vault structured. Use when the user wants to reorganize notes, fix directory
-  placement, or clean up the vault structure.
----
-
-# /organize — Directory Organization
-
-You are a librarian. Your job is to ensure every note lives in the right place based on its frontmatter metadata, type, and domain — and to suggest improvements to the overall vault structure.
-
-## Prerequisites Check
-
-```bash
-obsidian --version
-```
-
-If this fails, STOP and display the Obsidian CLI availability message (see /prep).
-
-## Parameters
-
-- **scope** (optional): `all` (full vault), `agents` (agent pages only), `sources` (user notes), or a specific directory. Default: `all`.
-- **dry_run** (optional): `true` to only suggest, `false` to apply changes. Default: `true`.
-
-## Process
-
-### Step 1: Scan Current Structure
-
-```bash
-obsidian list
-```
-
-Build a picture of:
-- Current directory structure
-- Notes in each directory
-- Notes that seem misplaced based on their frontmatter
-
-### Step 2: Check Agent Pages
-
-Agent pages should live in their designated directories:
-
-| `type` frontmatter | Expected directory |
-|-------------------|-------------------|
-| `entity` | `entities/` |
-| `concept` | `concepts/` |
-| `comparison` | `comparisons/` |
-| `query` | `queries/` |
-
-For each agent page, check:
-- Does its current directory match its `type`?
-- If not, suggest a move
-
-### Step 3: Check User Notes
-
-User notes should **remain** in their existing directories (`Projects/`, `Daily/`, personal folders, etc.). Do not suggest moving them into agent directories. Suggest organization only if:
-
-- A user note has been placed in an agent directory (`entities/`, `concepts/`, `comparisons/`, `queries/`) — this is likely a mistake; propose moving it back to an appropriate user area
-- Multiple user notes about the same topic are scattered across **user** directories when they could be grouped there (never into agent dirs unless they are true agent pages with correct `type` frontmatter)
-
-### Step 4: Check Naming Conventions
-
-Per SCHEMA.md conventions:
-- File names should be lowercase with hyphens, no spaces
-- Names should match the page title (abbreviated, hyphenated)
-- No duplicate names with different suffixes (e.g., `feature-a.md` and `feature-a-1.md`)
-
-Flag any naming violations.
-
-### Step 5: Suggest Moves
-
-For each misplaced file:
-
-```
-Move: entities/wrong-place.md → concepts/wrong-place.md
-  Reason: type=concept but currently in entities/
-
-Move: Projects/random-notes.md → Projects/feature-a/
-  Reason: Content is about Feature A, should be grouped with other Feature A notes
-```
-
-### Step 6: Apply Moves (If Confirmed)
-
-Use Obsidian CLI to rename/move files:
-
-```bash
-obsidian rename file="old-path.md" new_name="new-path.md"
-```
-
-Always show the full plan before applying. Never move files silently.
-
-### Step 7: Update Wikilinks
-
-After moving files, check that all wikilinks to the moved files are still valid:
-
-```bash
-obsidian backlinks "moved-file"
-```
-
-Obsidian typically handles wikilink updates on rename automatically, but verify for safety.
-
-## Key Principles
-
-- **Suggest first, act second.** Default to dry_run mode. Show the full plan before making any changes.
-- **Agent directories are sacred.** Only agent pages should live in `entities/`, `concepts/`, `comparisons/`, `queries/`.
-- **User notes are user territory.** Suggest organizational improvements but never move user notes without explicit confirmation.
-- **Obsidian is first workbench.** All note operations go through Obsidian CLI.

package/dist/assets/skills/prep.md

@@ -1,63 +0,0 @@
----
-name: prep
-description: >
-  Shared prerequisites check — verifies Obsidian CLI is available and displays a correct
-  error message with installation guidance. Referenced by all skills via "(see /prep)".
----
-
-# /prep — Prerequisites Check
-
-## Obsidian CLI Availability
-
-Before using any BYOAO skill, verify the Obsidian CLI is available:
-
-```bash
-obsidian --version
-```
-
-If this fails, STOP and display:
-
-```
-Obsidian CLI is not available. The Obsidian CLI is bundled with the Obsidian
-app (v1.12+) and cannot be installed separately.
-
-1. Install or update Obsidian from: https://obsidian.md/download
-2. Open Obsidian and enable the CLI:
-   Settings → General → Advanced → Command-line interface
-3. Make sure Obsidian is running, then try again.
-```
-
-## Graph Enrichment
-
-Scan all user notes and enrich frontmatter, suggest cross-references.
-
-### Step 1: Scan Notes
-- Read all `.md` files outside agent directories
-- Extract entities, key terms, and potential wikilink targets
-
-### Step 2: Enrich Frontmatter
-For each note missing frontmatter:
-- Add `title` (from filename or first heading)
-- Add `date` (from file creation time or content)
-- Suggest `tags` based on content
-
-For notes with partial frontmatter:
-- Fill in missing required fields
-- Never overwrite existing values
-
-### Step 3: Suggest Cross-References
-- Identify recurring terms mentioned across notes
-- Suggest converting mentions to `[[wikilinks]]`
-- Propose new entries for `SCHEMA.md` tag taxonomy
-
-### Step 4: Report
-Present a summary:
-- Notes enriched: X
-- Wikilinks suggested: Y
-- New schema terms proposed: Z
-Ask for approval before applying any changes.
-
-### Key Behaviors
-- Idempotent — running twice won't duplicate changes
-- Never overwrites existing frontmatter values
-- Asks before applying wikilink suggestions

package/dist/assets/skills/trace.md

@@ -1,141 +0,0 @@
----
-name: trace
-description: >
-  Chronological timeline of an idea across notes. Detects phases, turning points, and
-  contradictions in how a topic evolved. Use when the user asks "how did X evolve",
-  "trace the history of Y", "timeline of Z", or wants to understand how an idea changed over time.
----
-
-# /trace — Chronological Timeline
-
-You are a historical detective. Your job is to trace how a specific idea, decision, or topic evolved over time across the user's vault — finding phases, turning points, contradictions, and the full narrative arc.
-
-## Prerequisites Check
-
-```bash
-obsidian --version
-```
-
-If this fails, STOP and display the Obsidian CLI availability message (see /prep).
-
-## Parameters
-
-- **topic** (required): The idea, decision, or concept to trace.
-- **depth** (optional): `summary` (key milestones only) or `detailed` (all mentions with context). Default: `summary`.
-
-## Process
-
-### Step 1: Locate All Mentions
-
-Search for the topic across all notes:
-
-```bash
-obsidian search "<topic>"
-obsidian tags "<topic>"
-```
-
-Also search agent-maintained pages under `entities/`, `concepts/`, `comparisons/`, and `queries/`:
-
-```bash
-obsidian read file="entities/<topic>.md"
-obsidian read file="concepts/<topic>.md"
-obsidian read file="comparisons/<topic>.md"
-obsidian read file="queries/<topic>.md"
-```
-
-Read `INDEX.base` to check if there's already a compiled page for this topic.
-
-### Step 2: Build Timeline
-
-For each note that mentions the topic:
-
-1. Read the full content using `obsidian read`
-2. Extract the date (from frontmatter or filename for daily notes)
-3. Identify what the note says about the topic:
-   - **New idea proposed** — first mention of the concept
-   - **Decision made** — commitment to a specific approach
-   - **Change/evolution** — modification of previous understanding
-   - **Contradiction** — statement that conflicts with an earlier note
-   - **Confirmation** — validation of a previous position
-   - **Abandoned** — idea dropped or superseded
-
-### Step 3: Detect Phases
-
-Group the timeline into phases:
-
-- **Inception** — topic first appears, initial framing
-- **Exploration** — multiple approaches considered, debate
-- **Decision** — specific approach chosen
-- **Implementation** — execution details, adjustments
-- **Resolution** — outcome, lessons learned (or abandonment)
-
-A topic may skip phases, cycle back, or have multiple parallel tracks.
-
-### Step 4: Identify Turning Points
-
-Highlight moments where the trajectory changed:
-
-- "We switched from X to Y" — explicit change
-- Data or evidence that contradicted previous assumptions
-- New stakeholder or constraint that shifted direction
-- External event (tech release, policy change) that affected the topic
-
-### Step 5: Find Contradictions
-
-Compare statements across time:
-
-- "In Note A (March 1): we decided X"
-- "In Note B (April 15): actually Y is better because..."
-- Is this a genuine contradiction, an evolution of thinking, or a context-dependent difference?
-
-Flag genuine contradictions. Note the dates, sources, and nature of the conflict.
-
-### Step 6: Present Timeline
-
-```markdown
-# Timeline: {topic}
-
-Traced across {N} notes spanning {start date} to {end date}.
-
----
-
-## Phase 1: {Phase Name} ({date range})
-
-**What was happening**: {brief context}
-
-- **{date}** — [[Note A]]: {what happened / what was decided}
-- **{date}** — [[Note B]]: {what changed / what was added}
-
-**Key insight**: {what this phase reveals}
-
----
-
-## Phase 2: {Phase Name} ({date range})
-...
-
----
-
-## Turning Points
-
-1. **{date}**: {what changed and why it mattered} — [[source note]]
-
-## Contradictions Found
-
-- ⚠ [[Note A]] says X, but [[Note B]] says Y — {resolution if known}
-
-## Current State
-
-{Where things stand now — the most recent position on this topic}
-
-## Unanswered Questions
-
-{What the vault doesn't tell us about this topic's evolution}
-```
-
-## Key Principles
-
-- **Chronology is authority.** The timeline must follow actual note dates, not inferred order.
-- **Evidence-based.** Every claim in the timeline must cite a specific note.
-- **Show the messiness.** Ideas rarely evolve linearly. Show the false starts, reversals, and parallel tracks.
-- **Flag contradictions.** Don't resolve them — present both sides and let the user decide.
-- **Obsidian is first workbench.** All note operations go through Obsidian CLI.

package/dist/assets/skills/wiki.md

@@ -1,126 +0,0 @@
----
-name: wiki
-description: >
-  Generate and maintain INDEX.base — the dynamic knowledge map for v2 agent pages (`type`:
-  entity | concept | comparison | query). Uses Obsidian Base queries to list agent-maintained
-  pages; SCHEMA.md defines tag taxonomy. Use when the user runs /wiki or wants to see the current
-  state of the knowledge base.
----
-
-# /wiki — Knowledge Map
-
-**Metaphor:** The menu board — shows what's been prepared and what's on offer.
-
-## Purpose
-
-Generate and maintain `INDEX.base`, the dynamic knowledge map that lists all agent-maintained pages grouped by v2 `type` (`entity`, `concept`, `comparison`, `query`). Unlike static index files, INDEX.base uses Obsidian Base queries to stay current automatically. Use `SCHEMA.md` for tag taxonomy when summarizing or grouping entries.
-
-## Process
-
-### Step 1: Prerequisites Check
-
-```bash
-obsidian --version
-```
-
-If this fails, STOP and display the Obsidian CLI availability message (see /prep).
-
-### Step 2: Read SCHEMA.md
-
-```bash
-obsidian read file="SCHEMA.md"
-```
-
-Understand the current tag taxonomy, domain definitions, and page conventions.
-
-### Step 3: Generate INDEX.base Content
-
-Query all agent-maintained pages by v2 frontmatter `type` (`entity`, `concept`, `comparison`, `query`) so each page is listed under the correct section:
-
-```bash
-obsidian properties type=entity
-obsidian properties type=concept
-obsidian properties type=comparison
-obsidian properties type=query
-```
-
-For each type, compile entries with:
-- Page name (as wikilink)
-- Title from frontmatter
-- Brief summary (from content's first paragraph or definition section)
-- Tags and domain
-
-Format by section:
-
-```markdown
-# Knowledge Index
-
-## Entities
-- [[feature-a]] — Response time monitoring feature (tags: monitoring, backend)
-- [[zhang-san]] — Senior engineer on Feature A team (tags: team, engineering)
-
-## Concepts
-- [[response-time-metrics]] — Why median replaced avg for trigger calculation (tags: metrics, decisions)
-- [[search-trigger-rules]] — Search trigger rule design principles (tags: search, configuration)
-
-## Comparisons
-- [[avg-vs-median-for-trigger]] — Side-by-side analysis of avg vs median as trigger metrics (tags: metrics, decisions)
-
-## Queries
-- [[why-did-we-choose-median]] — "Why did we choose median over avg?" — detailed answer (tags: metrics, history)
-```
-
-### Step 4: Check Obsidian Base Configuration
-
-INDEX.base relies on Obsidian Base (saved search) configuration. Verify:
-
-1. The Base query covers all four agent directories
-2. The query filters by `type` frontmatter field
-3. Results are grouped by type
-
-If the Base doesn't exist or is misconfigured, guide the user to set it up:
-- Open Obsidian → Bases → Create new base
-- Name it "Knowledge Index"
-- Query: `path:entities/ OR path:concepts/ OR path:comparisons/ OR path:queries/`
-- Group by: `type`
-
-### Step 5: Present the Index
-
-Show the current INDEX.base content to the user:
-
-```markdown
-# Knowledge Index
-
-Generated on YYYY-MM-DD
-
-Total pages: N (X entities, Y concepts, Z comparisons, W queries)
-
-## By Domain
-- backend: N pages
-- frontend: M pages
-- infrastructure: K pages
-
-## Most Connected
-- [[page-name]] — N inbound links
-- [[page-name]] — M inbound links
-
-## Recently Updated
-- [[page-name]] — updated YYYY-MM-DD
-- [[page-name]] — updated YYYY-MM-DD
-```
-
-### Step 6: Suggest Gaps
-
-Based on the index, identify knowledge gaps:
-- Entity mentioned in multiple concepts but no entity page exists
-- Concept referenced in entity pages but no concept page exists
-- Domains with very few pages (under-represented areas)
-- Tags used frequently but no corresponding concept page
-
-## Key Principles
-
-- **INDEX.base is dynamic.** The Obsidian Base query keeps it current — no manual regeneration needed on every cook cycle.
-- **Summary quality.** Each entry's one-line summary should be genuinely informative, not just the page title repeated.
-- **Navigation first.** INDEX.base exists to help humans find knowledge quickly. Structure it for scanning, not completeness.
-- **Obsidian is first workbench.** All note operations go through Obsidian CLI.
-- **Agent pages only.** INDEX.base covers only `entities/`, `concepts/`, `comparisons/`, `queries/` — not user notes.