@pillar-ai/sdk 0.2.0 → 0.2.2

package/dist/tools/index.d.ts

@@ -25,4 +25,6 @@
  */
 export { validateToolName, TOOL_NAME_PATTERN } from './types';
 export type { ToolType, ToolDataSchema, ToolDataSchemaProperty, ToolDefinition, ToolDefinitions, ToolManifest, ToolManifestEntry, ClientInfo, Platform, SyncToolDefinition, SyncToolDefinitions, ToolTypeDataMap, NavigateToolData, TriggerToolData, InlineUIData, ExternalLinkData, CopyTextData, QueryToolData, ToolDataType, ToolNames, TypedTaskHandler, TypedOnTask, TypedPillarMethods, ToolExecuteResult, ToolSchemaBase, InlineUIToolSchema, ExecutableToolSchema, ToolSchema, ActionType, ActionDataSchema, ActionDataSchemaProperty, ActionDefinition, ActionDefinitions, ActionManifest, ActionManifestEntry, SyncActionDefinition, SyncActionDefinitions, NavigateActionData, TriggerActionData, QueryActionData, ActionTypeDataMap, ActionDataType, ActionNames, ActionResult, ActionSchema, } from './types';
+export { defineSkill } from './skill';
+export type { SkillDefinition } from './skill';
 export { setClientInfo, getClientInfo, getHandler, getToolDefinition, hasTool, getToolNames, getManifest, clearRegistry, getToolCount, getActionDefinition, hasAction, getActionNames, getActionCount, } from './registry';

package/dist/tools/skill.d.ts

@@ -0,0 +1,33 @@
+/**
+ * Skill definitions for registering instructional content with Pillar.
+ *
+ * Skills are structured markdown instructions that AI agents can load
+ * and follow. They are discovered by the CLI scanner (`npx pillar-sync`)
+ * and synced to the backend, where they're exposed as MCP prompts and resources.
+ *
+ * @example
+ * ```ts
+ * import { defineSkill } from '@pillar-ai/sdk';
+ *
+ * export const setupSkill = defineSkill({
+ *   name: 'setup-guide',
+ *   description: 'How to set up billing in your app',
+ *   content: '# Setup Guide\n\n1. Install the SDK...',
+ * });
+ * ```
+ */
+export interface SkillDefinition {
+    /** Unique skill name (e.g. 'billing-setup') */
+    name: string;
+    /** When/why to use this skill — used for semantic search matching */
+    description: string;
+    /** Full skill content (markdown) */
+    content: string;
+}
+/**
+ * Define a skill for registration with Pillar.
+ *
+ * The CLI scanner (`npx pillar-sync --scan ./src`) discovers these calls
+ * via AST analysis and syncs the skill definitions to the backend.
+ */
+export declare function defineSkill(def: SkillDefinition): SkillDefinition;

package/dist/tools/types.d.ts

@@ -560,6 +560,8 @@ export interface ToolSchemaBase<TInput = Record<string, unknown>> {
      * @default false
      */
     webMCP?: boolean;
+    /** Channels this tool is available on. Client-side tools default to ["web", "api"]. */
+    channelCompatibility?: string[];
 }
 /**
  * Tool schema for `inline_ui` tools that render a component in the chat.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pillar-ai/sdk",
-  "version": "0.2.0",
+  "version": "0.2.2",
   "description": "Product copilot SDK for SaaS and web apps — AI assistant that executes tasks, not just answers questions",
   "type": "module",
   "main": "./dist/pillar.esm.js",