@capybara-hq/plugin-sdk 0.1.0-rc.4 → 0.1.0-rc.5

package/agent-docs/agent-templates.md

@@ -1,4 +1,4 @@
-# Agent templates
+# Authoring: agent templates
 
 An agent template describes a whole agent: instructions, tools, skills, connectors and the
 sub-agents it may dispatch. A member creates a private agent from a template; org admins can also

package/agent-docs/concepts.md

@@ -2,6 +2,10 @@
 
 Read this first. It explains the vocabulary the other topics use.
 
+The other topics are for *authoring*: writing an extension, building a plugin, skills, templates,
+connector templates, tool naming and extension points. To *use* the platform (install, switch on,
+configure, manage), use the operations: `browse`, `search`, `describe` and `call`.
+
 ## Platform and org
 
 - The **platform** is one deployment. The **super admin** runs it: imports plugins into the

package/agent-docs/connector-templates.md

@@ -1,4 +1,4 @@
-# Connector templates
+# Authoring: connector templates
 
 A connector template is a ready-made connection to an external system: a protocol connector
 (`connector-mcp`, `connector-openapi`), a preset endpoint and the auth shape. An org installs it

package/agent-docs/extension-points/channel.md

@@ -1,4 +1,4 @@
-# Extension point: channel
+# Authoring: extension point channel
 
 <!-- generated:extension-point -->
 - Name: `channel` (a ref is `channel@<major>`)

package/agent-docs/extension-points/config-source.md

@@ -1,4 +1,4 @@
-# Extension point: config-source
+# Authoring: extension point config-source
 
 <!-- generated:extension-point -->
 - Name: `config-source` (a ref is `config-source@<major>`)

package/agent-docs/extension-points/connector.md

@@ -1,4 +1,4 @@
-# Extension point: connector
+# Authoring: extension point connector
 
 <!-- generated:extension-point -->
 - Name: `connector` (a ref is `connector@<major>`)

package/agent-docs/extension-points/counter.md

@@ -1,4 +1,4 @@
-# Extension point: counter
+# Authoring: extension point counter
 
 <!-- generated:extension-point -->
 - Name: `counter` (a ref is `counter@<major>`)

package/agent-docs/extension-points/directory.md

@@ -1,4 +1,4 @@
-# Extension point: directory
+# Authoring: extension point directory
 
 <!-- generated:extension-point -->
 - Name: `directory` (a ref is `directory@<major>`)

package/agent-docs/extension-points/file-preview.md

@@ -1,4 +1,4 @@
-# Extension point: file-preview
+# Authoring: extension point file-preview
 
 <!-- generated:extension-point -->
 - Name: `file-preview` (a ref is `file-preview@<major>`)

package/agent-docs/extension-points/identity-source.md

@@ -1,4 +1,4 @@
-# Extension point: identity-source
+# Authoring: extension point identity-source
 
 <!-- generated:extension-point -->
 - Name: `identity-source` (a ref is `identity-source@<major>`)

package/agent-docs/extension-points/model-provider.md

@@ -1,4 +1,4 @@
-# Extension point: model-provider
+# Authoring: extension point model-provider
 
 <!-- generated:extension-point -->
 - Name: `model-provider` (a ref is `model-provider@<major>`)

package/agent-docs/extension-points/object-store.md

@@ -1,4 +1,4 @@
-# Extension point: object-store
+# Authoring: extension point object-store
 
 <!-- generated:extension-point -->
 - Name: `object-store` (a ref is `object-store@<major>`)

package/agent-docs/extension-points/sandbox.md

@@ -1,4 +1,4 @@
-# Extension point: sandbox
+# Authoring: extension point sandbox
 
 <!-- generated:extension-point -->
 - Name: `sandbox` (a ref is `sandbox@<major>`)

package/agent-docs/extension-points/secret-store.md

@@ -1,4 +1,4 @@
-# Extension point: secret-store
+# Authoring: extension point secret-store
 
 <!-- generated:extension-point -->
 - Name: `secret-store` (a ref is `secret-store@<major>`)

package/agent-docs/extension-points/web-fetch.md

@@ -1,4 +1,4 @@
-# Extension point: web-fetch
+# Authoring: extension point web-fetch
 
 <!-- generated:extension-point -->
 - Name: `web-fetch` (a ref is `web-fetch@<major>`)

package/agent-docs/extension-points/web-search.md

@@ -1,4 +1,4 @@
-# Extension point: web-search
+# Authoring: extension point web-search
 
 <!-- generated:extension-point -->
 - Name: `web-search` (a ref is `web-search@<major>`)

package/agent-docs/extensions.md

@@ -1,4 +1,4 @@
-# Writing an extension
+# Authoring: writing an extension
 
 An extension is TypeScript code a plugin ships. It runs in the platform's process with full
 trust: approval by the super admin is governance, not a sandbox. It sees only the SDK's `ctx`

package/agent-docs/plugin-format.md

@@ -1,4 +1,4 @@
-# Plugin format
+# Authoring: the plugin format
 
 A plugin is a directory, packed into a `.tgz` with `capybara-plugin pack` (the published
 `@capybara-hq/plugin-tools`; `npx capybara-plugin check` runs the checks).

package/agent-docs/skills.md

@@ -1,4 +1,4 @@
-# Skills
+# Authoring: skills
 
 A skill is a folder with a `SKILL.md` (the Agent Skills format) and any files it needs. The agent
 sees only the skill's `name` and `description` until it loads the skill, so the description is

package/agent-docs/tool-naming.md

@@ -1,4 +1,4 @@
-# Tool naming
+# Authoring: tool naming
 
 The model-visible tool key grammar:
 

package/dist/index.d.ts

@@ -1,4 +1,4 @@
-export declare const SDK_VERSION = "0.1.0-rc.4";
+export declare const SDK_VERSION = "0.1.0-rc.5";
 export * from "./agent-template.js";
 export * from "./bootstrap.js";
 export * from "./cards.js";

package/dist/index.js

@@ -1,4 +1,4 @@
-export const SDK_VERSION = "0.1.0-rc.4";
+export const SDK_VERSION = "0.1.0-rc.5";
 export * from "./agent-template.js";
 export * from "./bootstrap.js";
 export * from "./cards.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@capybara-hq/plugin-sdk",
-  "version": "0.1.0-rc.4",
+  "version": "0.1.0-rc.5",
   "description": "Capybara plugin SDK: the types and pure functions plugins are written against",
   "license": "Apache-2.0",
   "repository": {