foliko 1.1.71 → 1.1.73

package/plugins/extension-executor-plugin.js

@@ -159,7 +159,7 @@ class ExtensionExecutorPlugin extends Plugin {
         if (plugin === 'mcp' && this._mcpExecutor) {
           const mcpToolDef = this._mcpExecutor.tools?.[tool];
           if (mcpToolDef && mcpToolDef.execute) {
-            log.info(` ext_call [MCP]: tool=${tool}`);
+            //log.info(` ext_call [MCP]: tool=${tool}`);
             return await mcpToolDef.execute(toolArgs || {});
           }
           return { success: false, error: `MCP tool '${tool}' not found` };
@@ -307,22 +307,22 @@ class ExtensionExecutorPlugin extends Plugin {
 
     const ext = this._extensions.get(pluginName);
     const existingIdx = ext.tools.findIndex((t) => t.name === toolDef.name);
+    const toolEntry = {
+      name: toolDef.name,
+      description: toolDef.description || '',
+      inputSchema: toolDef.inputSchema,
+      execute: toolDef.execute,
+    };
+    // 保留额外属性（如 _options）
+    if (toolDef._options) {
+      toolEntry._options = toolDef._options;
+    }
     if (existingIdx >= 0) {
       // 更新已存在的工具
-      ext.tools[existingIdx] = {
-        name: toolDef.name,
-        description: toolDef.description || '',
-        inputSchema: toolDef.inputSchema,
-        execute: toolDef.execute,
-      };
+      ext.tools[existingIdx] = toolEntry;
     } else {
       // 添加新工具
-      ext.tools.push({
-        name: toolDef.name,
-        description: toolDef.description || '',
-        inputSchema: toolDef.inputSchema,
-        execute: toolDef.execute,
-      });
+      ext.tools.push(toolEntry);
     }
 
     log.debug(` Registered tool '${toolDef.name}' for extension '${pluginName}'`);
@@ -413,44 +413,17 @@ class ExtensionExecutorPlugin extends Plugin {
     if (this._extensions.size > 0 || (this._mcpExecutor && Object.keys(this._mcpExecutor.tools || {}).length > 0)) {
       desc += '## 【Extensions】扩展插件\n\n';
       desc += '**使用流程（必须按顺序执行）：**\n';
-      desc += '1. 调用 `ext_skill({ plugin: "<plugin_name>" })` 或 `loadSkill({ skill: "<skill_name>" })` 获取技能命令的详细参数\n';
-      desc += '2. 根据返回的参数定义，使用 `ext_call({ plugin: "skill", tool: "技能名:命令名", args: {...} })` 调用\n\n';
+      desc += '1. 调用 `ext_skill({ plugin: "<plugin_name>" })` 获取技能命令的详细参数\n';
+      desc += '2. 根据返回的参数定义，使用 `ext_call({ plugin: "<plugin_name>", tool: "<tool_name>", args: {...} })` 调用\n\n';
       desc += '> **警告**：禁止在未执行第1步获取参数的情况下直接调用 `ext_call`！\n\n';
 
       for (const [name, ext] of this._extensions) {
-        if (name === 'skill') {
-          // Skill 命令按技能名分组显示
-          const toolsBySkill = {};
-          for (const tool of ext.tools) {
-            // 跳过无效工具
-            if (!tool || !tool.name) continue;
-            // 命令格式: skillname:cmdname
-            const parts = tool.name.split(':');
-            const skillName = parts[0];
-            const cmdName = parts.slice(1).join(':');
-            if (!toolsBySkill[skillName]) {
-              toolsBySkill[skillName] = [];
-            }
-            toolsBySkill[skillName].push({ name: cmdName, description: tool.description });
-          }
-
-          for (const [skillName, cmds] of Object.entries(toolsBySkill)) {
-            desc += `### skill.${skillName}\n`;
-            desc += `**调用方式:**\n`;
-            desc += `1. 先调用 \`loadSkill({ skill: "${skillName}" })\` 获取 \`${skillName}\` 技能的详细参数\n`;
-            desc += `2. 调用 \`ext_call({ plugin: "skill", tool: "${skillName}:<命令名>", args: { args: "参数" } })\`\n\n`;
-            desc += `**可用命令:**\n`;
-            for (const c of cmds) {
-              desc += `- \`${c.name}\`: ${c.description}\n`;
-            }
-            desc += '\n';
-          }
-        } else {
+          if (name === 'mcp'|| name === 'skill') continue; // MCP 和 Skill 工具单独列出
           desc += `### ${ext.name || name}\n`;
           desc += `${ext.description || '无描述'}\n`;
           const validTools = ext.tools.filter(t => t && t.name);
           desc += `**工具:** ${validTools.map(t => `\`${t.name}\``).join(', ')}\n\n`;
-        }
+  
       }
 
       // MCP 服务器工具
@@ -461,7 +434,7 @@ class ExtensionExecutorPlugin extends Plugin {
       }
 
       desc += '\n## 禁止事项\n';
-      desc += '- 不先调用 `ext_skill/loadSkill` 获取参数就直接使用 `ext_call`\n';
+      desc += '- 不先调用 `ext_skill` 获取参数就直接使用 `ext_call`\n';
     }
 
     if (!desc) {
@@ -597,6 +570,7 @@ class ExtensionExecutorPlugin extends Plugin {
       .map(t => ({
         name: t.name.replace(/^([^:]+):(.*)$/, '$1:$2'),
         description: t.description || t.name,
+        options: t._options || null,
       }));
   }
 

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
+```