@jayjiang/byoao 2.0.4 → 2.0.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -3,7 +3,8 @@ name: cook
|
|
|
3
3
|
description: >
|
|
4
4
|
The core knowledge compilation skill. Reads raw notes and external sources, then
|
|
5
5
|
distills them into structured, cross-referenced knowledge pages in entities/, concepts/,
|
|
6
|
-
comparisons/, and queries/.
|
|
6
|
+
comparisons/, and queries/. Keeps SCHEMA.md tag and domain taxonomy in sync when new
|
|
7
|
+
tags or domains appear. Use this skill whenever the user mentions compiling notes,
|
|
7
8
|
digesting material, updating the knowledge base, running a cook cycle, or says anything
|
|
8
9
|
like "process my notes", "compile this", "add this to the wiki", "what's new in my notes",
|
|
9
10
|
or "update knowledge pages". Also activate when the user pastes external content and wants
|
|
@@ -71,6 +72,7 @@ When user provides a URL:
|
|
|
71
72
|
### Step 2: Match Against Existing Pages
|
|
72
73
|
- Check `INDEX.base` or scan `entities/`, `concepts/` for existing pages
|
|
73
74
|
- Determine: create new vs. update existing
|
|
75
|
+
- Read `SCHEMA.md` (Obsidian CLI) for current tag and domain taxonomy so new pages prefer existing tags when they fit
|
|
74
76
|
|
|
75
77
|
### Step 3: Create/Update Pages
|
|
76
78
|
- **New entities:** Create in `entities/<name>.md`
|
|
@@ -86,12 +88,21 @@ When user provides a URL:
|
|
|
86
88
|
- Ensure every new/updated page has at least 2 outbound wikilinks
|
|
87
89
|
- Check existing pages link back where relevant
|
|
88
90
|
|
|
89
|
-
### Step 5:
|
|
91
|
+
### Step 5: Sync SCHEMA.md
|
|
92
|
+
After Step 3–4, reconcile agent pages touched this cycle with `SCHEMA.md`:
|
|
93
|
+
|
|
94
|
+
- Re-read `SCHEMA.md` if you have not just read it.
|
|
95
|
+
- If **any** new or updated agent page uses a `tag` not listed under **Current Tags** (or **Domain Taxonomy** / **Knowledge Domains** for a new `domain` value), **update `SCHEMA.md`** via Obsidian CLI: add the missing tag(s) or domain line(s), keep lists alphabetically sorted where the file already uses lists, and **preserve** unrelated sections and the user’s prose.
|
|
96
|
+
- If every tag and domain on those pages already appears in `SCHEMA.md`, **do not** rewrite the file.
|
|
97
|
+
- Do **not** remove tags or domains from `SCHEMA.md` during /cook unless the user explicitly asked to prune taxonomy.
|
|
98
|
+
- Stay consistent with SCHEMA rules: singular tags, 2–5 tags per page on agent pages, new tags documented here before (or as soon as) use.
|
|
99
|
+
|
|
100
|
+
### Step 6: Update Navigation
|
|
90
101
|
- `INDEX.base` auto-updates via Obsidian Base query
|
|
91
102
|
- Append entry to `log.md`
|
|
92
103
|
|
|
93
|
-
### Step
|
|
94
|
-
Present structured summary (see Output Report Format below).
|
|
104
|
+
### Step 7: Report
|
|
105
|
+
Present structured summary (see Output Report Format below). Mention `SCHEMA.md` when you added tags or domains, or say it was unchanged.
|
|
95
106
|
|
|
96
107
|
## Contradiction Handling
|
|
97
108
|
|
|
@@ -130,6 +141,7 @@ Contradiction found:
|
|
|
130
141
|
Want me to create a comparison page?
|
|
131
142
|
|
|
132
143
|
Log: 1 entry added to log.md
|
|
144
|
+
SCHEMA.md: added tags: observability, backend (or: SCHEMA.md — no taxonomy changes)
|
|
133
145
|
```
|
|
134
146
|
|
|
135
147
|
**Design principles:**
|
|
@@ -165,6 +177,7 @@ No `owner` frontmatter field needed.
|
|
|
165
177
|
|
|
166
178
|
- **Evidence-based**: Every knowledge page cites its sources
|
|
167
179
|
- **Never modify user notes**: User notes are read-only during /cook
|
|
180
|
+
- **SCHEMA.md stays accurate**: New tags or domains on agent pages are reflected in `SCHEMA.md` in the same cook cycle when possible
|
|
168
181
|
- **Thresholds matter**: 2+ mentions or central subject to create a page
|
|
169
182
|
- **Split at 200 lines**: Break large pages into sub-topics
|
|
170
183
|
- **Flag contradictions**: Never silently overwrite
|
package/dist/index.js
CHANGED
|
@@ -28262,7 +28262,7 @@ async function configureProvider(provider, gcpProjectId) {
|
|
|
28262
28262
|
|
|
28263
28263
|
// dist/vault/manifest.js
|
|
28264
28264
|
import path4 from "node:path";
|
|
28265
|
-
var PKG_VERSION = "2.0.
|
|
28265
|
+
var PKG_VERSION = "2.0.5";
|
|
28266
28266
|
var InfrastructureSchema = external_exports2.object({
|
|
28267
28267
|
skills: external_exports2.array(external_exports2.string()).default([]),
|
|
28268
28268
|
commands: external_exports2.array(external_exports2.string()).default([]),
|
package/dist/vault/manifest.js
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
import { fs } from "../lib/cjs-modules.js";
|
|
2
2
|
import path from "node:path";
|
|
3
3
|
import { z } from "zod";
|
|
4
|
-
const PKG_VERSION = "2.0.
|
|
4
|
+
const PKG_VERSION = "2.0.5";
|
|
5
5
|
// ── Schema ──────────────────────────────────────────────────────
|
|
6
6
|
const InfrastructureSchema = z.object({
|
|
7
7
|
skills: z.array(z.string()).default([]),
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
import { execSync } from "node:child_process";
|
|
2
2
|
import { semver } from "../lib/cjs-modules.js";
|
|
3
|
-
const PKG_VERSION = "2.0.
|
|
3
|
+
const PKG_VERSION = "2.0.5";
|
|
4
4
|
// ── Constants ───────────────────────────────────────────────────
|
|
5
5
|
const PACKAGE_NAME = "@jayjiang/byoao";
|
|
6
6
|
const REGISTRY_TIMEOUT_MS = 5_000;
|
package/package.json
CHANGED
package/src/skills/cook/SKILL.md
CHANGED
|
@@ -3,7 +3,8 @@ name: cook
|
|
|
3
3
|
description: >
|
|
4
4
|
The core knowledge compilation skill. Reads raw notes and external sources, then
|
|
5
5
|
distills them into structured, cross-referenced knowledge pages in entities/, concepts/,
|
|
6
|
-
comparisons/, and queries/.
|
|
6
|
+
comparisons/, and queries/. Keeps SCHEMA.md tag and domain taxonomy in sync when new
|
|
7
|
+
tags or domains appear. Use this skill whenever the user mentions compiling notes,
|
|
7
8
|
digesting material, updating the knowledge base, running a cook cycle, or says anything
|
|
8
9
|
like "process my notes", "compile this", "add this to the wiki", "what's new in my notes",
|
|
9
10
|
or "update knowledge pages". Also activate when the user pastes external content and wants
|
|
@@ -71,6 +72,7 @@ When user provides a URL:
|
|
|
71
72
|
### Step 2: Match Against Existing Pages
|
|
72
73
|
- Check `INDEX.base` or scan `entities/`, `concepts/` for existing pages
|
|
73
74
|
- Determine: create new vs. update existing
|
|
75
|
+
- Read `SCHEMA.md` (Obsidian CLI) for current tag and domain taxonomy so new pages prefer existing tags when they fit
|
|
74
76
|
|
|
75
77
|
### Step 3: Create/Update Pages
|
|
76
78
|
- **New entities:** Create in `entities/<name>.md`
|
|
@@ -86,12 +88,21 @@ When user provides a URL:
|
|
|
86
88
|
- Ensure every new/updated page has at least 2 outbound wikilinks
|
|
87
89
|
- Check existing pages link back where relevant
|
|
88
90
|
|
|
89
|
-
### Step 5:
|
|
91
|
+
### Step 5: Sync SCHEMA.md
|
|
92
|
+
After Step 3–4, reconcile agent pages touched this cycle with `SCHEMA.md`:
|
|
93
|
+
|
|
94
|
+
- Re-read `SCHEMA.md` if you have not just read it.
|
|
95
|
+
- If **any** new or updated agent page uses a `tag` not listed under **Current Tags** (or **Domain Taxonomy** / **Knowledge Domains** for a new `domain` value), **update `SCHEMA.md`** via Obsidian CLI: add the missing tag(s) or domain line(s), keep lists alphabetically sorted where the file already uses lists, and **preserve** unrelated sections and the user’s prose.
|
|
96
|
+
- If every tag and domain on those pages already appears in `SCHEMA.md`, **do not** rewrite the file.
|
|
97
|
+
- Do **not** remove tags or domains from `SCHEMA.md` during /cook unless the user explicitly asked to prune taxonomy.
|
|
98
|
+
- Stay consistent with SCHEMA rules: singular tags, 2–5 tags per page on agent pages, new tags documented here before (or as soon as) use.
|
|
99
|
+
|
|
100
|
+
### Step 6: Update Navigation
|
|
90
101
|
- `INDEX.base` auto-updates via Obsidian Base query
|
|
91
102
|
- Append entry to `log.md`
|
|
92
103
|
|
|
93
|
-
### Step
|
|
94
|
-
Present structured summary (see Output Report Format below).
|
|
104
|
+
### Step 7: Report
|
|
105
|
+
Present structured summary (see Output Report Format below). Mention `SCHEMA.md` when you added tags or domains, or say it was unchanged.
|
|
95
106
|
|
|
96
107
|
## Contradiction Handling
|
|
97
108
|
|
|
@@ -130,6 +141,7 @@ Contradiction found:
|
|
|
130
141
|
Want me to create a comparison page?
|
|
131
142
|
|
|
132
143
|
Log: 1 entry added to log.md
|
|
144
|
+
SCHEMA.md: added tags: observability, backend (or: SCHEMA.md — no taxonomy changes)
|
|
133
145
|
```
|
|
134
146
|
|
|
135
147
|
**Design principles:**
|
|
@@ -165,6 +177,7 @@ No `owner` frontmatter field needed.
|
|
|
165
177
|
|
|
166
178
|
- **Evidence-based**: Every knowledge page cites its sources
|
|
167
179
|
- **Never modify user notes**: User notes are read-only during /cook
|
|
180
|
+
- **SCHEMA.md stays accurate**: New tags or domains on agent pages are reflected in `SCHEMA.md` in the same cook cycle when possible
|
|
168
181
|
- **Thresholds matter**: 2+ mentions or central subject to create a page
|
|
169
182
|
- **Split at 200 lines**: Break large pages into sub-topics
|
|
170
183
|
- **Flag contradictions**: Never silently overwrite
|