@agent-native/core 0.92.11 → 0.93.0

package/corpus/core/src/usage/store.ts

@@ -197,6 +197,13 @@ export interface UsageRecord {
    * provider-reported dollar cost so two surfaces agree exactly.
    */
   costCentsX100?: number;
+  orgId?: string;
+  runId?: string;
+  threadId?: string;
+  taskId?: string;
+  integrationScopeId?: string;
+  sourcePlatform?: string;
+  sourceId?: string;
 }
 
 let _initPromise: Promise<void> | undefined;
@@ -218,6 +225,13 @@ async function ensureUsageTable(): Promise<void> {
           label TEXT NOT NULL DEFAULT 'chat',
           app TEXT NOT NULL DEFAULT '',
           ref_id TEXT NOT NULL DEFAULT '',
+          org_id TEXT,
+          run_id TEXT,
+          thread_id TEXT,
+          task_id TEXT,
+          integration_scope_id TEXT,
+          source_platform TEXT,
+          source_id TEXT,
           created_at ${intType()} NOT NULL
         )
       `;
@@ -229,6 +243,13 @@ async function ensureUsageTable(): Promise<void> {
         ["label", `TEXT NOT NULL DEFAULT 'chat'`],
         ["app", `TEXT NOT NULL DEFAULT ''`],
         ["ref_id", `TEXT NOT NULL DEFAULT ''`],
+        ["org_id", "TEXT"],
+        ["run_id", "TEXT"],
+        ["thread_id", "TEXT"],
+        ["task_id", "TEXT"],
+        ["integration_scope_id", "TEXT"],
+        ["source_platform", "TEXT"],
+        ["source_id", "TEXT"],
       ];
 
       if (isPostgres()) {
@@ -358,6 +379,13 @@ export async function recordUsage(
     app,
     refId,
     costCentsX100,
+    orgId,
+    runId,
+    threadId,
+    taskId,
+    integrationScopeId,
+    sourcePlatform,
+    sourceId,
   } = record;
 
   // Skip no-op writes (e.g. a stream aborted before any tokens flowed)
@@ -388,8 +416,8 @@ export async function recordUsage(
   const id = Date.now() * 1000 + Math.floor(Math.random() * 1000);
   await client.execute({
     sql: `INSERT INTO token_usage
-      (id, owner_email, input_tokens, output_tokens, cache_read_tokens, cache_write_tokens, cost_cents_x100, model, label, app, ref_id, created_at)
-      VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)`,
+      (id, owner_email, input_tokens, output_tokens, cache_read_tokens, cache_write_tokens, cost_cents_x100, model, label, app, ref_id, org_id, run_id, thread_id, task_id, integration_scope_id, source_platform, source_id, created_at)
+      VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)`,
     args: [
       id,
       ownerEmail,
@@ -402,6 +430,13 @@ export async function recordUsage(
       resolvedLabel,
       resolvedApp,
       resolvedRef,
+      orgId ?? null,
+      runId ?? null,
+      threadId ?? null,
+      taskId ?? null,
+      integrationScopeId ?? null,
+      sourcePlatform ?? null,
+      sourceId ?? null,
       Date.now(),
     ],
   });

package/corpus/templates/analytics/.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/corpus/templates/analytics/.agents/skills/provider-api/SKILL.md

@@ -31,6 +31,29 @@ expose.
   counts, and column names.
 - `delete-staged-dataset` — remove a staged dataset to free scratch storage.
 
+## Clay
+
+Clay is a credentialed GTM data and enrichment provider, not a messaging
+channel. Use the `clay` provider for its Public API:
+
+- Authentication is the configured `CLAY_PUBLIC_API_KEY`, injected server-side
+  in the `clay-api-key` header. Never pass the key in action arguments.
+- Provider requests are restricted to the exact `https://api.clay.com` origin,
+  with `/public/v0` as the default base path. Read the registered official docs
+  or OpenAPI spec on `developers.clay.com` through `provider-api-docs`; do not
+  try to send an authenticated provider request to that documentation host.
+- Searches cover companies and people and use a stateful forward-only iterator:
+  create the search, then repeat its run endpoint while `has_more` is true.
+- Routines are asynchronous. Start the routine, then poll its results endpoint
+  or use a separately verified completion webhook.
+- Tables are query-only, require Enterprise access, and require a known table
+  id. The Public API cannot list, create, or update tables.
+
+The optional local Clay CLI/MCP plugin uses a separate browser-login session.
+It is not required for hosted Agent Native provider access. Do not install or
+vendor that plugin by default; its public repository currently declares no
+license.
+
 ## Workflow
 
 1. Use a first-class action when it exactly fits the request.

package/corpus/templates/analytics/.builder/skills/provider-api/SKILL.md

@@ -17,6 +17,21 @@ body, pagination mode, or API version needed, use:
 - `provider-api-request` to make the exact HTTP call. Credentials are injected
   server-side, private/internal URLs are blocked, and secrets are redacted.
 
+## Clay
+
+Clay is a credentialed GTM provider capability, not a messaging channel. Use
+provider `clay`; the server injects `CLAY_PUBLIC_API_KEY` with the official
+`clay-api-key` header and restricts requests to the exact
+`https://api.clay.com` origin, with `/public/v0` as the default base path. Use
+`provider-api-docs` for the registered official docs and OpenAPI spec on
+`developers.clay.com`.
+
+Clay searches are stateful company/people iterators, routines are asynchronous,
+and table queries are read-only, Enterprise-only, and require a known table id.
+The optional local Clay CLI/MCP browser login is separate from hosted Agent
+Native credentials. Do not install or vendor that plugin by default; its public
+repository currently declares no license.
+
 Examples:
 
 ```bash

package/corpus/templates/analytics/actions/save-monitor.ts

@@ -2,6 +2,8 @@ import { defineAction } from "@agent-native/core";
 import {
   getRequestOrgId,
   getRequestUserEmail,
+  buildDeepLink,
+  getAppProductionUrl,
 } from "@agent-native/core/server";
 import { z } from "zod";
 
@@ -65,7 +67,7 @@ const statusMatcherSchema = z
 
 export default defineAction({
   description:
-    "Create or update an uptime monitor that pings a URL on a schedule and alerts when it is down, returns the wrong status, is too slow, or its body is missing/contains specific text.",
+    "Create or update an uptime monitor that pings a URL on a schedule and alerts when it is down, returns the wrong status, is too slow, or its body is missing/contains specific text. Returns the saved monitor and a focused Analytics link.",
   schema: z.object({
     id: z.string().optional().describe("Existing monitor id to update."),
     name: z
@@ -154,6 +156,27 @@ export default defineAction({
     if (!email) throw new Error("no authenticated user");
     const orgId = getRequestOrgId() || null;
     const name = args.name?.trim() || deriveNameFromUrl(args.url);
-    return saveMonitor({ ...args, name }, { email, orgId });
+    const monitor = await saveMonitor({ ...args, name }, { email, orgId });
+    return {
+      ...monitor,
+      monitorAppUrl: `${getAppProductionUrl()}/monitoring?view=uptime&monitor=${encodeURIComponent(monitor.id)}`,
+    };
+  },
+  link: ({ result }) => {
+    const saved = result as { id?: string; monitorAppUrl?: string } | null;
+    const id = saved?.id;
+    if (!id) return null;
+    return {
+      url:
+        saved?.monitorAppUrl ??
+        buildDeepLink({
+          app: "analytics",
+          view: "monitoring",
+          to: `/monitoring?view=uptime&monitor=${encodeURIComponent(id)}`,
+          params: { monitoringView: "uptime", monitorId: id },
+        }),
+      label: "Open monitor in Analytics",
+      view: "monitoring",
+    };
   },
 });

package/corpus/templates/analytics/app/lib/data-sources.ts

@@ -481,6 +481,34 @@ export const dataSources: DataSource[] = [
       },
     ],
   },
+  {
+    id: "clay",
+    name: "Clay",
+    description:
+      "GTM search, enrichment routines, and read-only table queries through Clay's Public API",
+    category: "crm",
+    icon: IconUserSearch,
+    envKeys: ["CLAY_PUBLIC_API_KEY"],
+    docsUrl: "https://developers.clay.com/",
+    walkthroughSteps: [
+      {
+        title: "Create a Clay Public API key",
+        description:
+          "In Clay, go to Settings > Account > API keys (beta) and create a key for the user and workspace this connection should access.",
+        url: "https://developers.clay.com/public-api/authentication",
+        linkText: "Clay API authentication",
+      },
+      {
+        title: "Enter your Public API key",
+        description:
+          "This hosted API credential is separate from the optional local clay CLI/MCP browser-login session.",
+        inputKey: "CLAY_PUBLIC_API_KEY",
+        inputLabel: "Public API key",
+        inputPlaceholder: "your-clay-public-api-key",
+        inputType: "password",
+      },
+    ],
+  },
 
   // --- Engineering ---
   {

package/corpus/templates/analytics/changelog/2026-07-10-agent-created-uptime-monitors-now-return-a-direct-link-to-th.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-07-10
+---
+
+Agent-created uptime monitors now return a direct link to their Analytics detail view

package/corpus/templates/analytics/changelog/2026-07-10-dashboard-email-reports-still-arrive-when-screenshot-capture-temporarily-fails.md

@@ -0,0 +1,6 @@
+---
+type: fixed
+date: 2026-07-10
+---
+
+Dashboard email reports still arrive when screenshot capture temporarily fails.

package/corpus/templates/analytics/server/jobs/dashboard-report.ts

@@ -46,13 +46,9 @@ export async function runDashboardReportsOnce(): Promise<{
             userEmail: sub.ownerEmail,
             orgId: sub.orgId ?? undefined,
           },
-          () =>
-            sendDashboardReportSubscription(sub, { requireScreenshot: true }),
+          () => sendDashboardReportSubscription(sub),
         );
-        if (result.screenshotAttached) {
-          await markDashboardReportResult(sub, "success");
-        } else {
-          failed++;
+        if (!result.screenshotAttached) {
           const message = result.screenshotError
             ? `Dashboard screenshot unavailable: ${result.screenshotError}`
             : "Dashboard screenshot unavailable";
@@ -60,8 +56,8 @@ export async function runDashboardReportsOnce(): Promise<{
             `[dashboard-report] Subscription ${sub.id} sent without a screenshot:`,
             message,
           );
-          await markDashboardReportResult(sub, "error", message);
         }
+        await markDashboardReportResult(sub, "success");
       } catch (err: any) {
         failed++;
         const message = err?.message ?? String(err);

package/corpus/templates/analytics/server/lib/credential-keys.ts

@@ -78,6 +78,12 @@ export const credentialKeys: CredentialKeyConfig[] = [
   { key: "GONG_API_BASE", label: "Gong API Base URL", required: false },
   // Apollo
   { key: "APOLLO_API_KEY", label: "Apollo", required: false },
+  // Clay
+  {
+    key: "CLAY_PUBLIC_API_KEY",
+    label: "Clay Public API Key",
+    required: false,
+  },
   // GitHub
   { key: "GITHUB_TOKEN", label: "GitHub token", required: false },
   // Jira
@@ -232,6 +238,11 @@ export const credentialProviderConfigs: CredentialProviderConfig[] = [
     label: "Apollo",
     requiredKeys: ["APOLLO_API_KEY"],
   },
+  {
+    provider: "clay",
+    label: "Clay",
+    requiredKeys: ["CLAY_PUBLIC_API_KEY"],
+  },
   {
     provider: "github",
     label: "GitHub",
@@ -309,6 +320,7 @@ const credentialAliases: Record<string, string[]> = {
   amplitude: ["AMPLITUDE_API_KEY", "AMPLITUDE_SECRET_KEY"],
   apollo: ["APOLLO_API_KEY"],
   bigquery: ["GOOGLE_APPLICATION_CREDENTIALS_JSON", "BIGQUERY_PROJECT_ID"],
+  clay: ["CLAY_PUBLIC_API_KEY"],
   commonroom: ["COMMONROOM_API_TOKEN"],
   dataforseo: ["DATAFORSEO_LOGIN", "DATAFORSEO_PASSWORD"],
   ga4: ["GOOGLE_APPLICATION_CREDENTIALS_JSON", "GA4_PROPERTY_ID"],

package/corpus/templates/analytics/server/lib/dashboard-report.ts

@@ -428,7 +428,11 @@ async function captureDashboardPng(
 }
 
 function errorMessage(err: unknown): string {
-  return err instanceof Error ? err.message : String(err);
+  const message = err instanceof Error ? err.message : String(err);
+  return message.replace(
+    new RegExp(`(${EMBED_TOKEN_QUERY_PARAM}=)[^&\\s]+`, "g"),
+    "$1[REDACTED]",
+  );
 }
 
 async function captureDashboardPngWithFallback(

package/corpus/templates/analytics/server/lib/provider-credentials.ts

@@ -11,6 +11,8 @@ export const HUBSPOT_ANALYTICS_CREDENTIAL_KEYS = [
   "HUBSPOT_ACCESS_TOKEN",
 ] as const;
 
+export const CLAY_ANALYTICS_CREDENTIAL_KEYS = ["CLAY_PUBLIC_API_KEY"] as const;
+
 export const GONG_ANALYTICS_CREDENTIAL_KEYS = [
   "GONG_ACCESS_KEY",
   "GONG_ACCESS_SECRET",

package/corpus/templates/analytics/server/routes/api/test-connection.post.ts

@@ -6,6 +6,7 @@ import {
   withRequestContextFromEvent,
 } from "../../lib/credentials";
 import {
+  CLAY_ANALYTICS_CREDENTIAL_KEYS,
   HUBSPOT_ANALYTICS_CREDENTIAL_KEYS,
   resolveAnalyticsGongCredentials,
   resolveAnalyticsProviderCredential,
@@ -94,6 +95,21 @@ export default defineEventHandler(async (event) => {
           return { ok: true };
         }
 
+        case "clay": {
+          const credential = await resolveAnalyticsProviderCredential({
+            provider: "clay",
+            keys: CLAY_ANALYTICS_CREDENTIAL_KEYS,
+            ctx,
+          });
+          const key = credential?.value;
+          if (!key) return { ok: false, error: "Missing Clay Public API key" };
+          const res = await fetch("https://api.clay.com/public/v0/me", {
+            headers: { "clay-api-key": key },
+          });
+          if (!res.ok) return { ok: false, error: "Invalid Clay API key" };
+          return { ok: true };
+        }
+
         case "hubspot": {
           const credential = await resolveAnalyticsProviderCredential({
             provider: "hubspot",

package/corpus/templates/assets/.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/corpus/templates/brain/.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/corpus/templates/calendar/.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)