foliko 2.0.5 → 2.0.6

package/skills/find-skills/SKILL.md

@@ -1,133 +1,133 @@
----
-name: find-skills
-description: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
----
-
-# Find Skills
-
-This skill helps you discover and install skills from the open agent skills ecosystem.
-
-## When to Use This Skill
-
-Use this skill when the user:
-
-- Asks "how do I do X" where X might be a common task with an existing skill
-- Says "find a skill for X" or "is there a skill for X"
-- Asks "can you do X" where X is a specialized capability
-- Expresses interest in extending agent capabilities
-- Wants to search for tools, templates, or workflows
-- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
-
-## What is the Skills CLI?
-
-The Skills CLI (`npx skills`) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.
-
-**Key commands:**
-
-- `npx skills find [query]` - Search for skills interactively or by keyword
-- `npx skills add <package>` - Install a skill from GitHub or other sources
-- `npx skills check` - Check for skill updates
-- `npx skills update` - Update all installed skills
-
-**Browse skills at:** https://skills.sh/
-
-## How to Help Users Find Skills
-
-### Step 1: Understand What They Need
-
-When a user asks for help with something, identify:
-
-1. The domain (e.g., React, testing, design, deployment)
-2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
-3. Whether this is a common enough task that a skill likely exists
-
-### Step 2: Search for Skills
-
-Run the find command with a relevant query:
-
-```bash
-npx skills find [query]
-```
-
-For example:
-
-- User asks "how do I make my React app faster?" → `npx skills find react performance`
-- User asks "can you help me with PR reviews?" → `npx skills find pr review`
-- User asks "I need to create a changelog" → `npx skills find changelog`
-
-The command will return results like:
-
-```
-Install with npx skills add <owner/repo@skill>
-
-vercel-labs/agent-skills@vercel-react-best-practices
-└ https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
-```
-
-### Step 3: Present Options to the User
-
-When you find relevant skills, present them to the user with:
-
-1. The skill name and what it does
-2. The install command they can run
-3. A link to learn more at skills.sh
-
-Example response:
-
-```
-I found a skill that might help! The "vercel-react-best-practices" skill provides
-React and Next.js performance optimization guidelines from Vercel Engineering.
-
-To install it:
-npx skills add vercel-labs/agent-skills@vercel-react-best-practices
-
-Learn more: https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
-```
-
-### Step 4: Offer to Install
-
-If the user wants to proceed, you can install the skill for them:
-
-```bash
-npx skills add <owner/repo@skill> -g -y
-```
-
-The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.
-
-## Common Skill Categories
-
-When searching, consider these common categories:
-
-| Category        | Example Queries                          |
-| --------------- | ---------------------------------------- |
-| Web Development | react, nextjs, typescript, css, tailwind |
-| Testing         | testing, jest, playwright, e2e           |
-| DevOps          | deploy, docker, kubernetes, ci-cd        |
-| Documentation   | docs, readme, changelog, api-docs        |
-| Code Quality    | review, lint, refactor, best-practices   |
-| Design          | ui, ux, design-system, accessibility     |
-| Productivity    | workflow, automation, git                |
-
-## Tips for Effective Searches
-
-1. **Use specific keywords**: "react testing" is better than just "testing"
-2. **Try alternative terms**: If "deploy" doesn't work, try "deployment" or "ci-cd"
-3. **Check popular sources**: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills`
-
-## When No Skills Are Found
-
-If no relevant skills exist:
-
-1. Acknowledge that no existing skill was found
-2. Offer to help with the task directly using your general capabilities
-3. Suggest the user could create their own skill with `npx skills init`
-
-Example:
-
-```
-I searched for skills related to "xyz" but didn't find any matches.
-I can still help you with this task directly! Would you like me to proceed?
-
-If this is something you do often, you could create your own skill:
-npx skills init my-xyz-skill
-```
+---
+name: find-skills
+description: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
+---
+
+# Find Skills
+
+This skill helps you discover and install skills from the open agent skills ecosystem.
+
+## When to Use This Skill
+
+Use this skill when the user:
+
+- Asks "how do I do X" where X might be a common task with an existing skill
+- Says "find a skill for X" or "is there a skill for X"
+- Asks "can you do X" where X is a specialized capability
+- Expresses interest in extending agent capabilities
+- Wants to search for tools, templates, or workflows
+- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
+
+## What is the Skills CLI?
+
+The Skills CLI (`npx skills`) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.
+
+**Key commands:**
+
+- `npx skills find [query]` - Search for skills interactively or by keyword
+- `npx skills add <package>` - Install a skill from GitHub or other sources
+- `npx skills check` - Check for skill updates
+- `npx skills update` - Update all installed skills
+
+**Browse skills at:** https://skills.sh/
+
+## How to Help Users Find Skills
+
+### Step 1: Understand What They Need
+
+When a user asks for help with something, identify:
+
+1. The domain (e.g., React, testing, design, deployment)
+2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
+3. Whether this is a common enough task that a skill likely exists
+
+### Step 2: Search for Skills
+
+Run the find command with a relevant query:
+
+```bash
+npx skills find [query]
+```
+
+For example:
+
+- User asks "how do I make my React app faster?" → `npx skills find react performance`
+- User asks "can you help me with PR reviews?" → `npx skills find pr review`
+- User asks "I need to create a changelog" → `npx skills find changelog`
+
+The command will return results like:
+
+```
+Install with npx skills add <owner/repo@skill>
+
+vercel-labs/agent-skills@vercel-react-best-practices
+└ https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
+```
+
+### Step 3: Present Options to the User
+
+When you find relevant skills, present them to the user with:
+
+1. The skill name and what it does
+2. The install command they can run
+3. A link to learn more at skills.sh
+
+Example response:
+
+```
+I found a skill that might help! The "vercel-react-best-practices" skill provides
+React and Next.js performance optimization guidelines from Vercel Engineering.
+
+To install it:
+npx skills add vercel-labs/agent-skills@vercel-react-best-practices
+
+Learn more: https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
+```
+
+### Step 4: Offer to Install
+
+If the user wants to proceed, you can install the skill for them:
+
+```bash
+npx skills add <owner/repo@skill> -g -y
+```
+
+The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.
+
+## Common Skill Categories
+
+When searching, consider these common categories:
+
+| Category        | Example Queries                          |
+| --------------- | ---------------------------------------- |
+| Web Development | react, nextjs, typescript, css, tailwind |
+| Testing         | testing, jest, playwright, e2e           |
+| DevOps          | deploy, docker, kubernetes, ci-cd        |
+| Documentation   | docs, readme, changelog, api-docs        |
+| Code Quality    | review, lint, refactor, best-practices   |
+| Design          | ui, ux, design-system, accessibility     |
+| Productivity    | workflow, automation, git                |
+
+## Tips for Effective Searches
+
+1. **Use specific keywords**: "react testing" is better than just "testing"
+2. **Try alternative terms**: If "deploy" doesn't work, try "deployment" or "ci-cd"
+3. **Check popular sources**: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills`
+
+## When No Skills Are Found
+
+If no relevant skills exist:
+
+1. Acknowledge that no existing skill was found
+2. Offer to help with the task directly using your general capabilities
+3. Suggest the user could create their own skill with `npx skills init`
+
+Example:
+
+```
+I searched for skills related to "xyz" but didn't find any matches.
+I can still help you with this task directly! Would you like me to proceed?
+
+If this is something you do often, you could create your own skill:
+npx skills init my-xyz-skill
+```

package/skills/foliko/AGENTS.md

@@ -63,19 +63,18 @@ module.exports = function (Plugin) {
       this.priority = 10;
     }
 
-    install(framework) {
-      const { z } = require('zod');
-      framework.registerTool({
+    onStart(framework) {
+      // Register AI SDK tool
+      this.tool.register({
         name: 'my_tool',
         description: '工具描述',
-        inputSchema: z.object({
-          param: z.string().describe('参数描述'),
+        inputSchema: framework.z.object({
+          param: framework.z.string().describe('参数描述'),
         }),
-        execute: async (args, framework) => {
+        execute: async (args) => {
           return { success: true, result: args.param };
         },
       });
-      return this;
     }
 
     uninstall(framework) {
@@ -119,18 +118,17 @@ class MyPlugin extends Plugin {
     this.priority = 10;
   }
 
-  install(framework) {
-    framework.registerTool({
+  onStart(framework) {
+    this.tool.register({
       name: 'my_tool',
       description: '工具描述',
-      inputSchema: z.object({
-        param: z.string().describe('参数描述'),
+      inputSchema: framework.z.object({
+        param: framework.z.string().describe('参数描述'),
       }),
-      execute: async (args, framework) => {
+      execute: async (args) => {
         return { success: true, result: args.param };
       },
     });
-    return this;
   }
 
   uninstall(framework) {}
@@ -150,47 +148,204 @@ module.exports = { MyPlugin };
 
 ## Lifecycle Methods
 
-| Method                 | Called When        | Required    |
-| ---------------------- | ------------------ | ----------- |
-| `install(framework)`   | Plugin installed   | ✅          |
-| `start(framework)`     | Plugin started     | Recommended |
-| `reload(framework)`    | Hot reload         | Optional    |
-| `uninstall(framework)` | Plugin uninstalled | Recommended |
+| Method | Called When | Required | Description |
+|--------|-------------|----------|-------------|
+| `install(framework)` | Plugin installed | ✅ | Initialize, get framework |
+| `onStart(framework)` | start/enable/reload | Recommended | Register tools, extensions, sub-agents |
+| `onStop()` | disable | Optional | Cleanup resources |
+| `reload(framework)` | Hot reload | Optional | prompts auto cleanup/register |
+| `uninstall(framework)` | Plugin uninstalled | Recommended | Cleanup resources |
+
+### onStart / onStop (Recommended)
+
+**Use `onStart` to register tools and extensions** - base class handles lifecycle automatically:
+
+```javascript
+class MyPlugin extends Plugin {
+  name = 'my-plugin';
+  version = '1.0.0';
+  description = '我的插件';
+
+  onStart(framework) {
+    // Register AI SDK tool (direct call)
+    this.tool.register({
+      name: 'hello',
+      description: '打招呼',
+      inputSchema: framework.z.object({
+        name: framework.z.string().describe('姓名')
+      }),
+      execute: async (args) => ({ message: `Hello, ${args.name}!` }),
+    });
+
+    // Register extension tool (via ext_call)
+    this.extension.register({
+      name: 'greet',
+      description: '打招呼扩展',
+      inputSchema: framework.z.object({
+        name: framework.z.string()
+      }),
+      execute: async (args) => ({ message: `Hi, ${args.name}!` }),
+    });
+  }
+}
+```
+
+### Lifecycle Auto-Management
+
+| Operation | Effect |
+|-----------|--------|
+| `disable` | Auto-remove tools/extensions (keep registration records) |
+| `enable` | Auto re-register tools/extensions |
+| `reload` | Remove and re-register |
+| `uninstall` | Remove and clear registration records |
 
 ## Tool Registration
 
-In `install()` method, register tools using `framework.registerTool()`:
+### Recommended: `this.tool.register()` in `onStart`
+
+```javascript
+onStart(framework) {
+  this.tool.register({
+    name: 'my_tool',
+    description: 'Tool description',
+    inputSchema: framework.z.object({
+      param: framework.z.string().describe('Parameter description')
+    }),
+    execute: async (args) => ({ success: true, result: args.param })
+  });
+}
+```
+
+### Alternative: `this.tools = {}` (ExtensionExecutor auto-scan)
+
+```javascript
+class MyPlugin extends Plugin {
+  name = 'my-plugin';
+
+  tools = {
+    my_tool: {
+      description: 'Tool description',
+      inputSchema: z.object({
+        param: z.string().describe('Parameter description')
+      }),
+      execute: async (args) => ({ success: true })
+    }
+  };
+}
+```
+
+### Legacy: `framework.registerTool()` in `install()`
 
 ```javascript
 install(framework) {
-  const { z } = require('zod')
   framework.registerTool({
     name: 'my_tool',
-    description: '工具描述',
-    inputSchema: z.object({
-      param: z.string().describe('参数描述')
+    description: 'Tool description',
+    inputSchema: framework.z.object({
+      param: framework.z.string().describe('Parameter description')
     }),
-    execute: async (args, framework) => {
-      return { success: true, result: args.param }
-    }
-  })
-  return this
+    execute: async (args) => ({ success: true })
+  });
+  return this;
+}
+```
+
+## Extension Registration
+
+```javascript
+onStart(framework) {
+  this.extension.register({
+    name: 'my_ext_tool',
+    description: 'Extension tool',
+    inputSchema: framework.z.object({
+      param: framework.z.string()
+    }),
+    execute: async (args) => ({ success: true })
+  });
 }
 ```
 
+## Tool/Extension Operations
+
+```javascript
+// Register
+this.tool.register({ name: 'xxx', ... });
+this.extension.register({ name: 'xxx', ... });
+
+// Remove
+this.tool.remove('xxx');
+this.extension.remove('xxx');
+
+// Execute
+const r1 = await this.tool.execute('any-tool', { arg: 'value' });  // Execute any registered tool
+const r2 = await this.extension.execute('xxx', { arg: 'value' });  // Execute current plugin's extension
+const r3 = await this.extension.execute('plugin-name', 'xxx', { arg: 'value' }); // Execute specified plugin's extension
+```
+
+## Workflow Operations
+
+```javascript
+// Register workflow
+this.workflow.register('my-workflow', {
+  name: 'my-workflow',
+  description: 'My workflow',
+  steps: [
+    { type: 'tool', tool: 'hello', args: {} }
+  ]
+});
+
+// Execute workflow
+const result = await this.workflow.execute('my-workflow', { input: 'value' });
+
+// Remove workflow
+this.workflow.remove('my-workflow');
+```
+
+## Agent Operations
+
+```javascript
+// Register sub-agent
+this.agent.register({
+  name: 'my-agent',
+  role: 'Assistant',
+  goal: 'Description',
+  tools: {},
+  parentTools: ['read_file', 'write_file']
+});
+
+// Get sub-agent
+const agent = this.agent.get('my-agent');
+
+// Remove sub-agent
+this.agent.remove('my-agent');
+```
+
+## Prompt Operations
+
+```javascript
+// Register prompt
+this.prompt.register('my-prompt', () => 'Prompt content', {
+  scope: 'global',
+  priority: 50
+});
+
+// Remove prompt
+this.prompt.remove('my-prompt');
+```
+
 ## Framework Object
 
 The framework object provides:
 
-| Method                              | Description                     |
-| ----------------------------------- | ------------------------------- |
-| `framework.registerTool(tool)`      | Register tool                   |
-| `framework.getTools()`              | Get all tools                   |
-| `framework.executeTool(name, args)` | Execute tool                    |
-| `framework.callTool(name, args)`    | Call tool (for installing deps) |
-| `framework.createAgent(config)`     | Create Agent                    |
-| `framework.reloadPlugin(name)`      | Reload single plugin            |
-| `framework.reloadAllPlugins()`      | Reload all plugins              |
+| Method | Description |
+|--------|-------------|
+| `framework.registerTool(tool)` | Register tool (legacy) |
+| `framework.getTools()` | Get all tools |
+| `framework.executeTool(name, args)` | Execute tool |
+| `framework.callTool(name, args)` | Call tool (for installing deps) |
+| `framework.createAgent(config)` | Create Agent |
+| `framework.reloadPlugin(name)` | Reload single plugin |
+| `framework.reloadAllPlugins()` | Reload all plugins |
 
 ## Dependency Management
 
@@ -229,8 +384,6 @@ await framework.callTool('install', {
 
 ## Common Mistakes
 
-1. ❌ Forgetting `install()` - tools won't be registered
-2. ❌ Forgetting `return this` - chain calls will fail
-3. ❌ Using `parameters` instead of `inputSchema`
-4. ❌ Registering tools outside `install()`
-5. ❌ Using same name for folder and file - folder takes priority, file will be ignored
+1. ❌ Using `parameters` instead of `inputSchema`
+2. ❌ Forgetting `framework.` prefix when using `framework.z.object()`
+3. ❌ Using same name for folder and file - folder takes priority, file will be ignored