@agent-native/core 0.92.11 → 0.93.0

package/src/templates/workspace-core/.agents/skills/capture-learnings/SKILL.md

@@ -11,11 +11,14 @@ metadata:
 
 # Capture Learnings
 
-This is background knowledge, not a slash command. **Your memory index is loaded at the start of every conversation.** Use `save-memory` proactively when you learn something worth remembering.
+This is background knowledge, not a slash command. **Organization learnings and your personal memory index are loaded at the start of every conversation, including Slack/integration turns.** Capture durable context proactively when you learn something worth remembering.
 
 ## How to Read & Write Memories
 
-Memories are stored as **resources** in the SQL database (personal scope), not as files on disk.
+Memories are stored as **resources** in the SQL database, not as files on disk.
+
+- **Team/organization knowledge:** shared `LEARNINGS.md`. Read it first, merge the new fact, then write the full updated file with the `resources` tool using `scope: "shared"`. Shared scope resolves to the active organization; it must never leak to another organization in the same deployment.
+- **Personal knowledge:** `memory/MEMORY.md` plus `memory/<name>.md`, written with `save-memory`.
 
 - **Save a memory:** `save-memory --name <name> --type <type> --description "..." --content "..."`
 - **Read a memory:** `resource-read --path memory/<name>.md`
@@ -33,6 +36,14 @@ Memories are stored as **resources** in the SQL database (personal scope), not a
 
 ## When to Capture
 
+### Team and organization knowledge (`LEARNINGS.md`, shared scope)
+- Canonical destinations and workflows (for example, which Content database receives a type of Slack request)
+- Required intake fields, ownership, prioritization conventions, metric definitions, and approved terminology
+- Durable external references that the whole team needs, including the canonical page/database URL
+- Corrections or decisions that should affect every organization member's future Slack and app conversations
+
+Store the fact and a concise provenance link when available. Do not paste full private conversations, customer data, credentials, or secrets into learnings. Put stable always-on policy in shared `AGENTS.md`; put learned facts and evolving conventions in shared `LEARNINGS.md`.
+
 ### User Preferences & Memory (`user`)
 - **Tone and style** — "I prefer casual tone", "don't use emojis", "keep replies short"
 - **Personal context** — contacts, relationships, habits ("my wife's email is...", "I'm in PST timezone")
@@ -58,19 +69,21 @@ Memories are stored as **resources** in the SQL database (personal scope), not a
 - Things obvious from reading the code
 - Standard language/framework behavior
 - Temporary debugging notes
-- Anything already in AGENTS.md or skills
+- Anything already in AGENTS.md, shared LEARNINGS.md, or skills
 - Ephemeral task details (use tasks/plans instead)
 
 ## Key Rules
 
-1. **Save proactively — don't ask permission.** When you learn something, save it immediately.
-2. **One memory per topic** — e.g. `coding-style`, `project-alpha`, not one giant dump
-3. **Read before updating** — if a memory exists, read it first and merge, don't overwrite
-4. **Keep descriptions concise** — the index is loaded every conversation
-5. **Memories are SQL-backed** — safe for personal info, persist across sessions, not in git
+1. **Save proactively — don't ask permission.** When you learn something durable, save it immediately at the correct scope.
+2. **Choose scope by audience.** Organization workflow or reference → shared `LEARNINGS.md`; one person's preference/context → personal memory.
+3. **One memory per topic** — e.g. `coding-style`, `project-alpha`, not one giant dump
+4. **Read before updating** — if a memory exists, read it first and merge, don't overwrite
+5. **Keep descriptions concise** — the index is loaded every conversation
+6. **Memories are SQL-backed** — they persist across sessions and are not in git; still minimize sensitive content
 
 ## Graduation
 
 When a memory is referenced repeatedly, it may belong in AGENTS.md or a skill:
-- Saving a memory is lightweight (auto-apply, personal scope)
+- Saving a personal memory is lightweight (auto-apply, personal scope)
+- Shared LEARNINGS.md is the lightweight organization knowledge layer
 - Updating AGENTS.md or a skill is heavier (affects all users/agents)

package/src/templates/workspace-core/.agents/skills/extension-points/SKILL.md

@@ -195,9 +195,12 @@ the `slot-installs` query and the host re-renders without the iframe.
 - **Not a slot manifest.** Slot targets live in the `tool_slots` table
   (Drizzle export `extensionSlots`), not in the extension's HTML content.
   The agent can re-target an extension without rewriting it.
-- **Not for arbitrary code modification.** If a user wants to change how
-  the app itself behaves (not add a sandboxed widget), use the
-  `self-modifying-code` skill instead.
+- **Not for arbitrary code modification.** If the exact request needs UI inside
+  a native component or at a location with no slot, do not stop at "slots
+  cannot do that" or silently move it elsewhere. Treat it as full app
+  customization: use `connect-builder` for the Builder.io Cloud Agent/local
+  editing handoff in hosted chat, or follow `self-modifying-code` in a local
+  code-editing surface.
 
 ## Cross-references
 

package/src/templates/workspace-core/.agents/skills/extensions/SKILL.md

@@ -51,6 +51,31 @@ and Alpine.js runtime.
 - Action files in `actions/`
 - Routes
 
+## When the Request Needs Code Instead
+
+Route by the user's exact outcome, not by whether they called it an
+"extension." Extensions render only on their own page or inside an existing
+named `ExtensionSlot`; they cannot inject UI into arbitrary native components,
+replace built-in views, or appear at a location where the host app has no slot.
+
+If the requested placement or behavior requires changing native components,
+host layout/styles/routes/business logic, or adding a new slot:
+
+1. Briefly explain the extension boundary.
+2. Do **not** stop at "an extension cannot do that," and do not silently move the
+   UI to a less useful slot.
+3. Continue through the normal source-code customization flow:
+   - In hosted/app-rendered chat, call `connect-builder`. When its
+     `builderEnabled` result is true, offer the Builder.io Cloud Agent handoff;
+     when false, say the change can be made with local code editing, Agent
+     Native Desktop, or Builder.io cloud editing.
+   - In a local development or outer code-editing surface, follow the
+     `self-modifying-code` skill and edit the app source directly.
+
+Full source-code customization is a core Agent Native capability. Extensions
+are the fast, sandboxed, no-deploy layer—not the limit of what the app can
+become.
+
 **When a user asks to "make an extension", "create an extension", or "build
 a ... extension" (or the older phrasings "make a tool" / "create a tool"):**
 

package/src/templates/workspace-core/.agents/skills/integration-webhooks/SKILL.md

@@ -298,6 +298,21 @@ queue + retry job for at-least-once delivery.
 6. **Reply not delivered?** The processor likely succeeded but
    `adapter.sendResponse` failed — check the adapter's outbound logs.
 
+## Automation connectors
+
+Workflow systems such as n8n and Zapier are not messaging channels. Do not add
+them as `PlatformAdapter`s or route them through `provider-api`.
+
+For n8n-style workflow invocation and callbacks, use
+`@agent-native/core/automation` with static workflow IDs and allow-listed
+origins. Agents provide structured input, never a target URL or credential.
+Callbacks must verify a configured secret/signature, claim a durable event ID,
+enqueue work through the established queue, and acknowledge quickly.
+
+Zapier is blueprint-only unless the app implements Zapier's explicit REST Hook
+subscribe/unsubscribe contract or configures a separate Zapier MCP connection.
+Do not imply a generic Zapier workflow-execution API exists.
+
 ## Related Skills
 
 - `server-plugins` — How `/_agent-native/` routes get mounted

package/src/templates/workspace-core/AGENTS.md

@@ -71,8 +71,9 @@ agent should know.
 
 ## Adding Apps
 
-When a user asks from Dispatch chat or by tagging `@agent-native` in Slack to
-create, build, make, scaffold, or generate an "agent", classify the ask first.
+When a user asks from Dispatch chat or through `@agent-native` in Slack or
+Telegram to create, build, make, scaffold, or generate an "agent", classify
+the ask first.
 Simple Dispatch-native behavior such as a reminder, digest, monitor, routing
 rule, saved instruction, or recurring workflow can stay in Dispatch as a
 recurring job/resource/destination. Robust unique products or teammates that