@rubytech/create-realagent 1.0.842 → 1.0.843

package/payload/platform/plugins/admin/skills/skill-builder/SKILL.md

@@ -77,37 +77,36 @@ Using the lean pattern from `references/lean-pattern.md`, compose:
 
 Show the user the complete SKILL.md content and each reference file. Ask them to review.
 
-## Step 7: Save to Memory
+## Step 7: Save the Skill as a Plugin File
 
-Use `memory-write` to save the composed skill to the knowledge graph:
+Use `store-skill` to write the composed skill to disk as part of an admin-managed plugin. The tool computes the path internally — supply the names and content only.
+
+Pick a `pluginName` that groups related operator-authored skills (e.g. `beacons-skills`, `my-utils`). Reuse the same `pluginName` across calls so the skill joins existing operator skills under one plugin. If this is the first skill in a new plugin, the tool creates the `PLUGIN.md` automatically.
 
 ```
-memory-write({
-  labels: ["CreativeWork"],
-  properties: {
-    title: "Skill: {name}",
-    abstract: "{full SKILL.md content including frontmatter}"
-  }
+store-skill({
+  pluginName: "{kebab-case plugin name}",
+  skillName: "{kebab-case skill name}",
+  description: "{the one-sentence description from Step 1}",
+  publicEmbed: false,
+  body: "{SKILL.md body content WITHOUT frontmatter — activation conditions, behaviour rules, references index}",
+  references: [
+    { filename: "{kebab-case-name}.md", content: "{full reference body}" }
+  ]
 })
 ```
 
-If the skill has reference files, save each as a separate `CreativeWork` node:
+Set `publicEmbed: true` only when the user wants this skill surfaced to the public agent. Default to `false` for admin-only skills.
 
-```
-memory-write({
-  labels: ["CreativeWork"],
-  properties: {
-    title: "Skill Reference: {name}/{filename}",
-    abstract: "{full reference file content}"
-  }
-})
-```
+`references` is optional — pass `[]` (or omit) when the skill has no detailed procedures or templates.
 
 ## Step 8: Confirm
 
 Tell the user:
 
-> "Your skill has been saved to memory. I can recall it when the situation matches. You can update it at any time — just ask me to edit the skill."
+> "Your skill is saved on disk as part of the `{pluginName}` plugin and is active right now for the admin agent. I can use it when the situation matches. To edit it later, ask me to update the skill — I'll re-run `store-skill` with the new content."
+
+If `publicEmbed: true`, add: "It will surface in the public agent on the next session start."
 
 ---
 

package/payload/platform/plugins/docs/references/plugins-guide.md

@@ -90,6 +90,16 @@ Tell {{productName}}:
 
 Ask {{productName}}: "What plugins do I have?" or "List my plugins."
 
+## Operator-Authored Plugins (skill-builder output)
+
+Skills you create at runtime through the admin `skill-builder` skill are saved on disk as their own plugin under `data/accounts/{accountId}/plugins/{pluginName}/`. The admin agent calls `mcp__admin__store-skill`, which composes `PLUGIN.md` (on first call) and `skills/{skillName}/SKILL.md` plus any reference files. The agent supplies `pluginName`, `skillName`, `description`, `publicEmbed`, `body`, and optional references — the path is computed by the tool, never by the agent.
+
+These operator-authored plugins survive reinstall because the installer's wipe zone excludes `data/`. At admin session start the platform mirrors `data/accounts/{accountId}/plugins/*` into the runtime plugins directory so the same `parsePluginFrontmatter` / `assemblePublicPluginContent` / `loadEmbeddedPlugins` loaders that read shipped and premium plugins also pick up operator-authored ones — no special-case loader path. The admin agent sees every operator skill by default; per-skill `publicEmbed: true|false` controls which skills surface to the public agent.
+
+To edit an operator-authored skill later, ask {{productName}} to update it — the admin agent re-runs `store-skill` for the same `pluginName`/`skillName` and the new content overwrites in place. To remove one, delete the directory under `data/accounts/{accountId}/plugins/{pluginName}/skills/{skillName}/` (or the whole plugin) — the next session start re-mirrors the remaining skills only.
+
+`pluginName` collisions with shipped plugin names are refused by `store-skill` with a structured error. See [.docs/agents.md](../../../../.docs/agents.md) § "Operator-authored skills as plugin files" for the full contract.
+
 ## Brand Templating (for plugin and skill authors)
 
 Skill content, plugin manifests, agent templates, and reference files reference the operator-visible brand name only via the literal `{{productName}}` placeholder. The platform substitutes from `brand.json.productName` at read time — Maxy installs render `Maxy`, Real Agent installs render `Real Agent`, all from the same source content.