@agentshouse/skills 0.1.0-c0bd138428a36 → 0.1.0-c1fe7ffb41ff0

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.
package/README.md CHANGED
@@ -7,20 +7,22 @@ The Skills agents.house serves its agents, and the texts its agents read.
7
7
  skill and `wizard`, file for file beside upstream's `LICENSE`. `upstream.json` names the
8
8
  upstream commit, its date and the skills taken from it. Beside them stand agents.house's own
9
9
  `prototype-app`, `build-app` and `wizard`.
10
- - `how-we-work.md` is the How-we-work document's text, and `how-we-work-earlier.json` the
11
- SHA-256 of every earlier text.
10
+ - `guide/` is the Guide, the pages agents.house serves its agents by path: `index` is its root, and
11
+ each page opens with its title and one line on what it is for. `owner-rules` is the Owner rules'
12
+ text, and `owner-rules-earlier.json` the SHA-256 of every earlier text.
12
13
  - `app-guide.json` is the guide to building an App or a Site, and `agent-instructions.json` the
13
14
  lines that open an agent's first prompt.
14
15
 
15
16
  ```ts
16
- import { HOW_WE_WORK, listSkills, readSkill } from '@agentshouse/skills';
17
+ import { OWNER_RULES, listSkills, readSkill } from '@agentshouse/skills';
17
18
 
18
19
  for (const { name } of listSkills()) console.log(name, readSkill(name).length);
19
- console.log(HOW_WE_WORK);
20
+ console.log(OWNER_RULES);
20
21
  ```
21
22
 
22
- `agentInstructions(houseRef, copies)` returns the first prompt's lines, `APP_GUIDE` the guide's
23
- lines and `EARLIER_HOW_WE_WORK_SHA256` the earlier texts' digests.
23
+ `agentInstructions(houseRef, copies)` returns the first prompt's lines, `GUIDE` every Guide page
24
+ with its path, title, first line and text, `APP_GUIDE` the App guide's lines and
25
+ `EARLIER_OWNER_RULES_SHA256` the earlier texts' digests.
24
26
 
25
27
  The skills come from [mattpocock/skills](https://github.com/mattpocock/skills); thank you, Matt
26
28
  Pocock.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "lines": [
3
3
  "From House:",
4
- "Work with House through the `house` CLI: run `house --help`, and `house find_command` for House's guides and formats.",
4
+ "Work with House through the `house` CLI: run `house --help`, and `house open_guide` opens `index`, the root page of House's guides and formats.",
5
5
  "To give the User a file, upload it with `house upload` and link it; for an App, a Site or a website, follow `house find_command '{\"query\":\"app\"}'`. Never start a server.",
6
6
  "Optional per-Room instructions: `/rooms/private/rooms/<handle>/AGENTS.md`.",
7
7
  "For another Agent's help, `send_routine_request`; its mail comes back into this conversation. If an Agent of your User has no Routine to call, write one in the Private Room and `create_routine_access` with your User as its only caller."
package/app-guide.json CHANGED
@@ -43,8 +43,8 @@
43
43
  "",
44
44
  "## Start",
45
45
  "",
46
- "- An App with an `a_` reference already exists, even with no release yet, as every App your User makes in the panel does. Clone its `.git` address, `<origin>/app/<app_ref>.git` or its `source_url` in `list_apps`, with `git clone -c 'credential.helper=!kit git-credential' -c user.name=<agent-git-name> -c user.email=<agent-git-email> <address>`, so Git signs in as you and can commit, in every later step too. Run `npm ci`, then publish with `npm run publish`, never with `--name`.",
47
- "- Only when no App exists yet, clone `<origin>/app/new.git` the same way: it gives mdui, a minimal App in plain TypeScript with its test and `npm run publish`. Run `npm ci`, then `npm run publish -- --name \"<display name>\"`, which creates the App and prints its address and its `.git` address. Then `git remote set-url origin <that .git address>`; every later `npm run publish` goes there, without `--name`.",
46
+ "- An App with an `a_` reference already exists, even with no release yet, as every App your User makes in the panel does. Clone its `.git` address, `<origin>/app/<app_ref>.git` or its `source_url` in `list_apps`, with `git clone -c 'credential.helper=!kit git-credential' -c user.name=<agent-git-name> -c user.email=<agent-git-email> <address>`, so Git signs in as you and can commit, in every later step too. Run `npm ci --ignore-scripts`, then publish with `npm run publish`, never with `--name`.",
47
+ "- Only when no App exists yet, clone `<origin>/app/new.git` the same way: it gives mdui, a minimal App in plain TypeScript with its test and `npm run publish`. Run `npm ci --ignore-scripts`, then `npm run publish -- --name \"<display name>\"`, which creates the App and prints its address and its `.git` address. Then `git remote set-url origin <that .git address>`; every later `npm run publish` goes there, without `--name`.",
48
48
  {
49
49
  "act": "sites/create",
50
50
  "text": "- A Site starts with `create_site`: `name` is its address name, and the answer's `source_url` is its App's `.git` address to clone the same way. Anything private is an App."
@@ -53,20 +53,20 @@
53
53
  "act": "sites/create",
54
54
  "text": "- A Site shows the Rooms it published, as `published` names them: creating it publishes its bound Rooms, a release keeps the published data, and later Room edits stay private until `publish_site_data`. A publication whose `state` is `preparing` replaces the shown one once its screenshot is taken; `list_sites` names each Site's newest publication and its `state`, and `publish_site_data` with nothing changed since answers that publication. `unpublish_site` stops serving a Site and keeps it; `republish_site` or `publish_site_data` serves it again."
55
55
  },
56
- "- Use any framework and build tool. `npm run build` leaves the whole release in `dist/`: the entry HTML, every file it loads, `app.json` and `schema.yaml`. The entry names files by relative paths (Vite: `base: './'`), carries no inline script and loads nothing from outside the release, so bundle fonts and libraries. A release holds at most <release-files> files and <release-mib> MiB.",
56
+ "- Use any framework and build tool. `npm run build` leaves the whole release in `dist/`: the entry HTML, every file it loads, `app.json` and `schema.yaml`. The entry names files by relative paths (Vite: `base: './'`), carries no inline script and loads nothing from outside the release, so bundle fonts and libraries. A release holds at most <release-files> files and <release-size>.",
57
57
  "- Your User sees a change only once it is published, so an ask to change an App is an ask to publish it: end every change with a commit and `npm run publish`, which builds, pushes `main` and the build, and prints `published` or the reason House refused. A `git push` of `main` alone publishes nothing and says so. A refused push changes nothing and the previous release keeps running.",
58
58
  "- Without Git, zip the project folder after the build, without `node_modules` and `.env`, `upload` the ZIP to a Room and publish it with `publish_app_zip`.",
59
59
  "- Every page registers `bridge.cooperate` in its entry script before its first draw, as mdui's `main.ts` does, even a page that reads no Room: only then does a page your User has open take each release by itself, with no reload. A page that registers none keeps the release it opened on until it is opened again. A page that draws everything at once and has nothing to type or select registers `bridge.cooperate({ checkpoint() {}, persist() {}, capture: () => scrollY, restore(top) { scrollTo(0, Number(top)); }, ready: () => true, settle() {} })` after `const bridge = houseBridge()`, which keeps its scroll position. Every other page keeps its User's task through the release as the example below does: `checkpoint` waits until the page has drawn, `persist` until its Room Draft writes are done, failing while a field it shows was refused its last write so the release waits, `capture` answers the focused field with its cursor and selection, the scroll position and whatever else it holds outside the address, and `restore` puts them back once the page has drawn again; `node_modules/@agentshouse/app-bridge/docs/families.md` describes each member.",
60
60
  "",
61
61
  "## Data",
62
62
  "",
63
- "- Design the Room schema first. Each thing the App shows is one Markdown document in a Room: its frontmatter `type` names its MD type, the rest of its frontmatter holds the fields, and long text goes in `##` sections. `schema.yaml` declares the types (`find_command` \"Schema\").",
63
+ "- Design the Room schema first. Each thing the App shows is one Markdown document in a Room: its frontmatter `type` names its MD type, the rest of its frontmatter holds the fields, and long text goes in `##` sections. `schema.yaml` declares the types (`open_guide` `reference/schema`).",
64
64
  "- Keep each type in its own folder, such as `tasks/`, and read it by `pathPrefix`: a query naming `types` fails with `unknown-type` while no bound Room declares them.",
65
65
  "- Link types with `reference` fields instead of copying values; a query follows them with `hop` and `backlinks`.",
66
66
  {
67
67
  "act": "sites/create",
68
- "text": "- `app.json` `room_slots` names the Rooms the App needs, each with `access` `read` or `write` and the `types` it uses (`find_command` \"App manifest\"). Bind Rooms with `set_app_bindings`, a Site's with `set_site_bindings`; App code cannot bind and reaches only bound Rooms, so it opens `bridge.ceremony('/bind/<app_ref>?slot=<name>')`, the House page where your User binds Rooms and connects account slots, which returns to the App.",
69
- "without": "- `app.json` `room_slots` names the Rooms the App needs, each with `access` `read` or `write` and the `types` it uses (`find_command` \"App manifest\"). Bind Rooms with `set_app_bindings`; App code cannot bind and reaches only bound Rooms, so it opens `bridge.ceremony('/bind/<app_ref>?slot=<name>')`, the House page where your User binds Rooms and connects account slots, which returns to the App."
68
+ "text": "- `app.json` `room_slots` names the Rooms the App needs, each with `access` `read` or `write` and the `types` it uses (`open_guide` `reference/app-manifest`). Bind Rooms with `set_app_bindings`, a Site's with `set_site_bindings`; App code cannot bind and reaches only bound Rooms, so it opens `bridge.ceremony('/bind/<app_ref>?slot=<name>')`, the House page where your User binds Rooms and connects account slots, which returns to the App.",
69
+ "without": "- `app.json` `room_slots` names the Rooms the App needs, each with `access` `read` or `write` and the `types` it uses (`open_guide` `reference/app-manifest`). Bind Rooms with `set_app_bindings`; App code cannot bind and reaches only bound Rooms, so it opens `bridge.ceremony('/bind/<app_ref>?slot=<name>')`, the House page where your User binds Rooms and connects account slots, which returns to the App."
70
70
  },
71
71
  "- A bound Room must hold each slot type identically in its own `settings/schema.yaml`, beside any other types, or your User is warned. Write it with `edit` before binding; `create_room` makes a new Room.",
72
72
  "- Read an existing Room's `settings/schema.yaml` before inventing types. Two Apps over one schema are two interfaces over the same data, and your User's Agents read and write those documents too.",
@@ -319,6 +319,10 @@
319
319
  "act": "sites/create",
320
320
  "text": "- `describe_site` sets the title and description search engines show."
321
321
  },
322
+ {
323
+ "act": "sites/create",
324
+ "text": "- With `google_analytics_id` set by `describe_site`, House measures a visitor only after they accept. While `bridge.onStatus` reports `analytics.measures`, ask them on the Site unless `analytics.choice` holds their answer, report it with `bridge.analyticsConsent('accept')` or `bridge.analyticsConsent('decline')`, and keep a way on every page to decline later, which reloads the page unmeasured."
325
+ },
322
326
  {
323
327
  "act": "sites/create",
324
328
  "text": ""
@@ -327,7 +331,7 @@
327
331
  "",
328
332
  "Before `npm run publish`:",
329
333
  "",
330
- "- `npm test` passes against the newest `@agentshouse/app-bridge` and `@agentshouse/mdruntime` (`npm install <name>@latest`), since every page gets House's newest runtime. Keep mdui's test: it runs the built page on `createMemoryAdapter` from `@agentshouse/mdruntime/memory` and `createHouseBridgeTestHost` from `@agentshouse/app-bridge/test-host`, with no House.",
334
+ "- `npm test` passes against the newest `@agentshouse/app-bridge` and `@agentshouse/mdruntime` (`npm install --ignore-scripts <name>@latest`), since every page gets House's newest runtime. Keep mdui's test: it runs the built page on `createMemoryAdapter` from `@agentshouse/mdruntime/memory` and `createHouseBridgeTestHost` from `@agentshouse/app-bridge/test-host`, with no House.",
331
335
  "- Every slot type is in `schema.yaml` exactly as in the bound Room's `settings/schema.yaml`.",
332
336
  "- The entry script registers `bridge.cooperate` before its first draw.",
333
337
  "- The page works 360 pixels wide, offline, and reloaded at a deep address.",
package/dist/index.d.ts CHANGED
@@ -17,8 +17,16 @@ export interface SkillFile {
17
17
  readonly path: string;
18
18
  readonly content: string;
19
19
  }
20
- export declare const HOW_WE_WORK: string;
21
- export declare const EARLIER_HOW_WE_WORK_SHA256: readonly string[];
20
+ export interface GuidePage {
21
+ readonly path: string;
22
+ readonly title: string;
23
+ readonly line: string;
24
+ readonly text: string;
25
+ }
26
+ export declare const GUIDE_ROOT = "index";
27
+ export declare const GUIDE: readonly GuidePage[];
28
+ export declare const OWNER_RULES: string;
29
+ export declare const EARLIER_OWNER_RULES_SHA256: readonly string[];
22
30
  export declare const APP_GUIDE: Guide;
23
31
  export declare function agentInstructions(houseRef: string, copies: readonly string[]): string[];
24
32
  export declare function listSkills(): readonly Skill[];
package/dist/index.js CHANGED
@@ -5,11 +5,34 @@ const PACKAGE = fileURLToPath(new URL('..', import.meta.url));
5
5
  const SET = join(PACKAGE, 'set');
6
6
  const ENTRY = 'SKILL.md';
7
7
  const REF_PLACEHOLDER = '<house-ref>';
8
+ const TREE = join(PACKAGE, 'guide');
9
+ const PAGE = '.md';
10
+ const FRONTMATTER = /^---\n[\s\S]*?\n---\n/u;
11
+ const HEADING = /^# /u;
12
+ export const GUIDE_ROOT = 'index';
13
+ const OWNER_RULES_PAGE = 'owner-rules';
8
14
  function packaged(name) {
9
15
  return readFileSync(join(PACKAGE, name), 'utf8');
10
16
  }
11
- export const HOW_WE_WORK = packaged('how-we-work.md');
12
- export const EARLIER_HOW_WE_WORK_SHA256 = JSON.parse(packaged('how-we-work-earlier.json'));
17
+ function guidePage(file) {
18
+ const text = readFileSync(join(TREE, file), 'utf8');
19
+ const [heading = '', , line = ''] = text.replace(FRONTMATTER, '').split('\n');
20
+ return {
21
+ path: file.slice(0, -PAGE.length).split(sep).join('/'),
22
+ title: heading.replace(HEADING, ''),
23
+ line,
24
+ text,
25
+ };
26
+ }
27
+ export const GUIDE = readdirSync(TREE, {
28
+ recursive: true,
29
+ withFileTypes: true,
30
+ })
31
+ .filter((entry) => entry.isFile() && entry.name.endsWith(PAGE))
32
+ .map((entry) => guidePage(relative(TREE, join(entry.parentPath, entry.name))))
33
+ .sort((left, right) => (left.path < right.path ? -1 : 1));
34
+ export const OWNER_RULES = GUIDE.find((page) => page.path === OWNER_RULES_PAGE).text;
35
+ export const EARLIER_OWNER_RULES_SHA256 = JSON.parse(packaged('owner-rules-earlier.json'));
13
36
  export const APP_GUIDE = JSON.parse(packaged('app-guide.json'));
14
37
  const INSTRUCTIONS = JSON.parse(packaged('agent-instructions.json'));
15
38
  export function agentInstructions(houseRef, copies) {
@@ -0,0 +1,9 @@
1
+ # Get started
2
+
3
+ How your User signs up for House and connects you.
4
+
5
+ House keeps Markdown files in Rooms, which your User shares with other people and their agents.
6
+
7
+ Sign-up page: <origin>/sign-up
8
+
9
+ Unless this client already reads your User's Rooms, register there and connect it; then find out what your User wants, keep the plan with `edit` as documents in their First Room, which `list_rooms` names, and make the Rooms yourself with `create_room` through `run_command`.
package/guide/index.md ADDED
@@ -0,0 +1,7 @@
1
+ # House
2
+
3
+ Where House's guides and formats start: `open_guide` opens a page by its `path` or finds pages by `words`.
4
+
5
+ House keeps Markdown files in Rooms, which your User shares with other people and their agents.
6
+
7
+ - `reference/`, the formats House reads: [Read level](reference/read-level), [App manifest](reference/app-manifest), [Routine](reference/routine), [Schema](reference/schema) and [Triggers](reference/triggers).
@@ -1,4 +1,6 @@
1
- # How we work
1
+ # Owner rules
2
+
3
+ What a Room is for and where work goes, the skills' output included.
2
4
 
3
5
  A Room is where information people share is kept; it is not the place for
4
6
  private information. Work goes into the Room it belongs to, or the First Room
@@ -0,0 +1,12 @@
1
+ # App manifest
2
+
3
+ What an App's `app.json` declares.
4
+
5
+ App manifest, `app.json` at an App’s root: `entry`, its HTML page, and `room_slots`, each with a `name`, `access` `read` or `write`, and `types` from the `schema.yaml` beside it, written like a Room schema; `set_app_bindings` fills a slot with Rooms. Where needed it adds `external_origins`, the https origins its page may reach; `account_slots`, each a `name`, the service’s `origin` and its key `form`, `{kind: bearer}`, `{kind: basic}`, `{kind: header, name}`, `{kind: query, name}` or `{kind: path, prefix}`; `conversations: true` to read your User’s conversations; `local_search: true` to call `search`; `inboxes: true` to show and answer customer chats, naming `inbox-chat` and `inbox-message` in `room_slots`; and `theme_colour`, `#rrggbb`. `find_command` "app" shows how its page works.
6
+
7
+ ```json
8
+ {
9
+ "entry": "index.html",
10
+ "room_slots": [{ "name": "tasks", "access": "write", "types": ["task"] }]
11
+ }
12
+ ```
@@ -0,0 +1,9 @@
1
+ # Read level
2
+
3
+ How much of a Room a grant or a Share lets its holder read, and where.
4
+
5
+ Read level, `read` on a Room grant or a Share’s Room item, each level including the one before it: `mcp`, MCP Read, reads through `search`, `shell` and `inspect` alone, each reply at most <mcp-read-size> of the Room’s text, with no copy anywhere; `online`, Online Read, also opens the Room in browser Apps while the browser is online, and reads as `mcp` everywhere else; `local`, Local Read, copies the Room to the browser and the Environments, offline included, and is the one `export` needs. Apps need `online` or `local`.
6
+
7
+ ```json
8
+ { "room_ref": "r_ab12.1", "read": "online", "operations": ["write"] }
9
+ ```
@@ -0,0 +1,14 @@
1
+ # Routine
2
+
3
+ How a Routine document in the Private Room is written.
4
+
5
+ Routine, `/rooms/private/collaboration/routines/<name>.md`: `description` and `input`, a text saying what to send, empty if nothing; the body is the instruction. A Routine Request's input is text the Agent reads, and House checks no shape.
6
+
7
+ ```markdown
8
+ ---
9
+ description: Summarize a thread in five bullets.
10
+ input: The thread to summarize, as a ref or pasted text.
11
+ ---
12
+
13
+ Read the thread and write five bullets under summaries/.
14
+ ```
@@ -0,0 +1,28 @@
1
+ # Schema
2
+
3
+ How a Room's `settings/schema.yaml` declares its document types.
4
+
5
+ Schema, `/rooms/<room>/settings/schema.yaml`: one JSON Schema in YAML. Each top-level key is an MD type holding the schema of its frontmatter; `$defs` holds shapes reused through `$ref: '#/$defs/<name>'`. An object setting neither `additionalProperties` nor `unevaluatedProperties` refuses other keys. House adds `reference` on a string at any depth, naming the types, or `attachment`, its value links to, and `cross_room: true` beside it, letting that be another Room's document of those types; a link or reference written as its `/rooms/<room>/` path is stored relative to the document; `sections`, a type's `##` headings, each `{ kind: text }` or `{ kind: list, items }`; and `member_document: true` on one type, whose documents name their member with `member`, a User Identifier from `list_members`. On a type, `create_roles` lists the Schema Roles that may create its documents and `delete_roles` those that may delete them, and changing a document's `type` needs both; on a field of a type's own `properties`, `change_roles` lists those that may change it, `initial_roles` those that may set it on a new document, and `transitions` the `{from, to, roles}` changes it may make, `null` standing for absent; `owner` and `member` are built in, `[]` allows nobody, and only someone who manages the Room's access changes them. `edit` creates or replaces the whole text, and may rewrite the documents a change breaks in the same call. A Room may use a Shared schema instead, which `use_shared_schema` chooses: its `settings/schema.yaml` is then a read-only copy of it.
6
+
7
+ ```yaml
8
+ person:
9
+ member_document: true
10
+ properties:
11
+ role: { type: string }
12
+ task:
13
+ properties:
14
+ title: { type: string }
15
+ status: { enum: [open, done] }
16
+ owner: { type: string, reference: person }
17
+ required: [title]
18
+ sections:
19
+ Notes: { kind: text }
20
+ ```
21
+
22
+ ```markdown
23
+ ---
24
+ type: person
25
+ member: <User Identifier from list_members>
26
+ role: Designer
27
+ ---
28
+ ```
@@ -0,0 +1,7 @@
1
+ # Triggers
2
+
3
+ How a Trigger's `condition` and `actions` are written for `create_trigger` and `edit_trigger`.
4
+
5
+ `condition`: When it fires, e.g. `{on: "documents", scope: {type: "task"}, mode: "starts_matching", new_documents: false, match: {all: [{path: "/fields/status", eq: "review"}, {path: "/members/assignee", eq: "<User id>"}]}}`; for a new document in a folder, `{on: "documents", scope: {folder: "/answers"}, mode: "starts_matching", new_documents: true, match: {all: []}}`; on documents, `moved_between_rooms: true` fires only on a document moved in from or out to another Room, `false` only on any other change; for arriving items, `{on: "items", address: "<push address>", match: {path: "/json/ref", eq: "refs/heads/main"}}`. A clock is `{on: "clock", cron: "0 9 * * 1", time_zone: "Europe/Berlin"}`, or a day before each task is due: `{on: "clock", scope: {type: "task"}, date: "/fields/due", days: -1, at: "09:00", time_zone: "Europe/Berlin", match: <test>}`.
6
+
7
+ `actions`: What it does; a `notify` action names whom it reaches, e.g. `{kind: "notify", title: "Ready to test", text: "A task waits.", to: {users: ["<User id>"], fields: ["/members/assignee"], roles: ["owner"]}}`, Users by id, the member a field of the matched document names, and every holder of a Schema Role; a `routine` action names a Routine Access.
@@ -0,0 +1,25 @@
1
+ # Entry Data Contract
2
+
3
+ How a Site App's `entry_data` has House serve each route as HTML from Rooms.
4
+
5
+ Entry Data Contract, `entry_data` in a Site App’s `app.json`: House serves each route as HTML from your Rooms before the App starts, running none of your code. Each of `routes` has a `path` (`/`, `/posts/:slug`), optional `query` (functional `?name` parameters with defaults), `queries` (Local Query objects with `types` and a `pathPrefix` at each scope, no `rooms`; `{"$param": "slug"}` takes an argument, `"as": "integer"` converts it; `boundQuery` from `@agentshouse/mdruntime/entry` fills the same query in your page), `interaction` (the queries its first interaction needs), `title`, `description` and `body`. A body node is text, `{text: v}`, `{markdown: v}` of a document, `{tag, attrs, children}`, `{each: v, as, children}` or `{if: v, then, else}`; a value `v` is a literal, `{param}`, `{at, pointer}` into a query result or `each` item, `{join: [v]}`, `{count: v}` or `{stem: v}`. `styles` lists release CSS files. A route that fails starts the App as usual, and the Site document names why.
6
+
7
+ ```json
8
+ {
9
+ "routes": [
10
+ {
11
+ "path": "/posts/:slug",
12
+ "queries": {
13
+ "post": {
14
+ "types": ["post"],
15
+ "pathPrefix": "posts",
16
+ "where": { "/slug": { "$param": "slug" } },
17
+ "select": { "fields": ["/title"], "markdown": true }
18
+ }
19
+ },
20
+ "title": { "at": "post", "pointer": "/documents/0/fields/title" },
21
+ "body": [{ "markdown": { "at": "post", "pointer": "/documents/0" } }]
22
+ }
23
+ ]
24
+ }
25
+ ```
@@ -2,5 +2,6 @@
2
2
  "ae4dda60da7b174f22dc5fa9bf07fc27c25864932a74230de4f9f509ddd91f41",
3
3
  "0bdcd43e1603ba6673a3cae56d70bbf90657cbeefd124e91a47be2ca1cbd6c93",
4
4
  "4106a87ec66da6f7b2a10e74d18e6559d68d5f4fe7415dae68f5c7bdb9081968",
5
- "ac814a2197038f037b657bb719340395f89f319ac9fcdd386629c3fe2cec68f1"
5
+ "ac814a2197038f037b657bb719340395f89f319ac9fcdd386629c3fe2cec68f1",
6
+ "29951ee394aad9979eecfed3e5dc32c2c86e2226b6a380db5dbd4f305f4d1156"
6
7
  ]
package/package.json CHANGED
@@ -1,14 +1,14 @@
1
1
  {
2
2
  "name": "@agentshouse/skills",
3
- "version": "0.1.0-c0bd138428a36",
4
- "description": "The Skills agents.house serves its agents, upstream's verbatim beside its own, and the texts its agents read: the How-we-work document, the App guide and the Agent instructions",
3
+ "version": "0.1.0-c1fe7ffb41ff0",
4
+ "description": "The Skills agents.house serves its agents, upstream's verbatim beside its own, and the texts its agents read: the Guide, the App guide and the Agent instructions",
5
5
  "license": "MIT",
6
6
  "type": "module",
7
7
  "publishConfig": {
8
8
  "access": "public"
9
9
  },
10
10
  "engines": {
11
- "node": ">=24.21.0"
11
+ "node": ">=24.22.1"
12
12
  },
13
13
  "exports": {
14
14
  ".": {
@@ -19,11 +19,16 @@
19
19
  "files": [
20
20
  "dist",
21
21
  "set",
22
+ "guide",
22
23
  "upstream.json",
23
- "how-we-work.md",
24
- "how-we-work-earlier.json",
24
+ "owner-rules-earlier.json",
25
25
  "app-guide.json",
26
26
  "agent-instructions.json",
27
27
  "README.md"
28
- ]
28
+ ],
29
+ "repository": {
30
+ "type": "git",
31
+ "url": "git+https://github.com/agentshouse/core.git",
32
+ "directory": "house/packages/skills"
33
+ }
29
34
  }
@@ -11,7 +11,7 @@ Read the map `prototype-app` opened for this App. Start only when its design-dec
11
11
 
12
12
  ## Build
13
13
 
14
- Claim the build task. Starting from the User's decision, run `grill-with-docs`, then `to-spec`, then `implement`. Keep what they write where the How-we-work document, `/rooms/private/how-we-work.md`, says. Each Skill named here is also a Command of its name, for a client that has not installed it.
14
+ Claim the build task. Starting from the User's decision, run `grill-with-docs`, then `to-spec`, then `implement`. Keep what they write where the Owner rules, `/rooms/private/owner-rules.md`, say. Each Skill named here is also a Command of its name, for a client that has not installed it.
15
15
 
16
16
  ## Publish into the same App
17
17
 
@@ -7,7 +7,7 @@ description: Make a new App by publishing a prototype first; it is built properl
7
7
 
8
8
  The User sees a working prototype before anything is built properly. A map holds the way: the prototype, published as the App's first release; the User's decision on its design; then `build-app`, which builds the App and publishes it into the same App.
9
9
 
10
- Keep everything where the How-we-work document, `/rooms/private/how-we-work.md`, says. Each Skill named here is also a Command of its name, for a client that has not installed it.
10
+ Keep everything where the Owner rules, `/rooms/private/owner-rules.md`, say. Each Skill named here is also a Command of its name, for a client that has not installed it.
11
11
 
12
12
  ## 1. Open the map
13
13
 
@@ -9,8 +9,8 @@ Write one bash script for the steps only the User can do: it says what to open a
9
9
 
10
10
  ## As a Web Wizard
11
11
 
12
- Create it with `create_web_wizard`, for the Environment you work through or another of the User's that they name (`list_environments`). Give the User the link it answers: they read the whole script there, and nothing runs until they press Run. Its output and what they type never reach you. When they say they are done, read how it ended with `read_web_wizard`, and go on only once it finished with exit code 0.
12
+ Create it with `create_web_wizard`, for the Environment you work through or another of the User's that they name (`list_environments`). Give the User the link it answers: they read the whole script there, and nothing runs until they press Run. Its output and what they type never reach you. When they say they are done, read the document at the path it answered, which says how it ended, and go on only once its state is finished with exit code 0.
13
13
 
14
14
  ## As a script they run
15
15
 
16
- When House refuses the Web Wizard because the Environment's Kit is not connected, or because you reach no Environment of the User, write the script into the Room where the How-we-work document, `/rooms/private/how-we-work.md`, keeps wizards, and give the User its link and the command that runs it.
16
+ When House refuses the Web Wizard because the Environment's Kit is not connected, because you reach no Environment of the User, or because the Environment you act through does not reach the User's Private Room, write the script into the Room where the Owner rules, `/rooms/private/owner-rules.md`, keep wizards, and give the User its link and the command that runs it.