foliko 1.0.36 → 1.0.38

package/.claude/settings.local.json

@@ -77,7 +77,10 @@
       "Bash(node -e \"const sdk = require\\('@larksuiteoapi/node-sdk'\\); console.log\\(Object.keys\\(sdk\\)\\);\")",
       "Bash(node -e \"const { WSClient } = require\\('@larksuiteoapi/node-sdk'\\); const sdk = new WSClient\\({}\\); console.log\\(Object.getOwnPropertyNames\\(Object.getPrototypeOf\\(sdk\\)\\)\\);\")",
       "Bash(node -c src/core/framework.js 2>&1)",
-      "Bash(node -c plugins/telegram-plugin.js 2>&1)"
+      "Bash(node -c plugins/telegram-plugin.js 2>&1)",
+      "Bash(node -c src/capabilities/skill-manager.js 2>&1)",
+      "Bash(node -c plugins/feishu-plugin.js 2>&1)",
+      "Bash(node debug-skills.js)"
     ]
   }
 }

package/cli/bin/foliko.js

@@ -1,4 +1,4 @@
-#!/usr/bin/env node
+#!/usr/bin/env node
 /**
  * Foliko CLI 入口
  * Usage: foliko <command> [options]

package/cli/src/commands/chat.js

@@ -100,9 +100,13 @@ async function chatCommand(args) {
   // 创建 Agent
   const agent = framework.createAgent({
     name: 'FolikoAgent',
-    systemPrompt: '你是一个有帮助的助手，擅长回答问题和执行任务。',
-    sharedPrompt: '工作目录: {{WORK_DIR}}',
-    sharedPrompt: '工作目录: {{WORK_DIR}}',
+    systemPrompt: `你是一个有帮助的助手，擅长回答问题和执行任务。
+    **注意事项：**
+      1、遇到npx skills add,npx skills remove, npx skills list 命令时:
+        --添加"-a openclaw","-y"参数
+        --不要加-g 参数
+    `,
+    sharedPrompt: `工作目录: {{WORK_DIR}}`,
     metadata: {
       WORK_DIR: process.cwd()  // 覆盖内置的 WORK_DIR
     }

package/cli/src/ui/chat-ui.js

@@ -146,7 +146,7 @@ class ChatUI {
       let lineBuffer = ''
       const renderState = { inThink: false, inCodeBlock: false }
 
-      console.log(colored('Agent:', GREEN))
+      console.log(colored('● ', GREEN))
       console.log()
 
       for await (const chunk of this.agent.chatStream(message, { sessionId: this.sessionId })) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "foliko",
-  "version": "1.0.36",
+  "version": "1.0.38",
   "description": "简约的插件化 Agent 框架",
   "main": "src/index.js",
   "bin": {

package/plugins/default-plugins.js

@@ -20,7 +20,7 @@ function loadAgentConfig(agentDir = '.agent') {
     skillsDirs: [],
     agentsDir: null    // 子Agent配置目录
   }
-
+  const cmdDir=path.resolve(process.cwd())
   const resolvedDir = path.resolve(process.cwd(), agentDir)
 
   if (!fs.existsSync(resolvedDir)) {
@@ -135,6 +135,16 @@ function loadAgentConfig(agentDir = '.agent') {
     config.skillsDirs.push(skillsDir)
   }
 
+  // 添加 .agent/skills 目录（不存在则创建）
+  const cmdskillsDir = path.join(cmdDir, 'skills')
+  if (fs.existsSync(resolvedDir) && !fs.existsSync(cmdskillsDir)) {
+    fs.mkdirSync(cmdskillsDir, { recursive: true })
+    console.log(`[AgentConfig] Created skills directory: ${cmdskillsDir}`)
+  }
+  if (fs.existsSync(cmdskillsDir)) {
+    config.skillsDirs.push(cmdskillsDir)
+  }
+
   // 添加 agentDir 父目录的 skills/ 目录
   const parentDir = path.dirname(__dirname)
   const rootSkillsDir = path.join(parentDir, 'skills')

package/plugins/feishu-plugin.js

@@ -128,8 +128,8 @@ module.exports = function(Plugin) {
       try {
         // 解析消息数据 - SDK 事件格式
         // data 结构: { message: { chat_id, content, sender: { sender_id: { open_id }, ... }, message_type } }
-        if (!data || !data.message) {
-          console.log('[Feishu] Invalid message data:', JSON.stringify(data).substring(0, 500))
+        if (!data || !data.message || Object.keys(data.message).length === 0) {
+          console.log('[Feishu] Invalid or empty message data:', JSON.stringify(data).substring(0, 500))
           return
         }
 
@@ -140,7 +140,13 @@ module.exports = function(Plugin) {
         // 注意: 群组消息可能没有 sender 字段，此时使用 chat_id 作为会话标识
         const openId = message.sender?.sender_id?.open_id || message.sender?.open_id || message.open_id || chatId
         const messageType = message.message_type
-        const content = message.content ? JSON.parse(message.content) : {}
+        let content = {}
+        try {
+          content = message.content ? JSON.parse(message.content) : {}
+        } catch (e) {
+          console.log('[Feishu] Failed to parse message content:', message.content?.substring?.(0, 100))
+          return
+        }
 
         // 消息去重
         if (messageId && this._processedMessages.has(messageId)) {
@@ -199,7 +205,7 @@ module.exports = function(Plugin) {
         }
 
       } catch (err) {
-        console.error('[Feishu] Error handling message:', err)
+        console.error('[Feishu] Error handling message:', err.message, err.stack)
       }
     }
 

package/plugins/weixin-plugin.js

@@ -20,7 +20,7 @@ module.exports = function(Plugin) {
       this.priority = 80
       // 默认不启用，需要在 plugins.json 中设置 enabled: true
       this.enabled = false
-      this.path=`./agent/data`
+      this.path=`.agent/data`
       this.systemPrompt='你是一个微信助手。回复内容不要使用markdown格式文本'
 
       this.config = {

package/skills/find-skills/AGENTS.md

@@ -0,0 +1,162 @@
+# AGENTS.md
+
+This file provides guidance to AI coding agents working on the `skills` CLI codebase.
+
+## Project Overview
+
+`skills` is the CLI for the open agent skills ecosystem.
+
+## Commands
+
+| Command                       | Description                                         |
+| ----------------------------- | --------------------------------------------------- |
+| `skills`                      | Show banner with available commands                 |
+| `skills add <pkg>`            | Install skills from git repos, URLs, or local paths |
+| `skills experimental_install` | Restore skills from skills-lock.json                |
+| `skills experimental_sync`    | Sync skills from node_modules into agent dirs       |
+| `skills list`                 | List installed skills (alias: `ls`)                 |
+| `skills check`                | Check for available skill updates                   |
+| `skills update`               | Update all skills to latest versions                |
+| `skills init [name]`          | Create a new SKILL.md template                      |
+
+Aliases: `skills a` works for `add`. `skills i`, `skills install` (no args) restore from `skills-lock.json`. `skills ls` works for `list`. `skills experimental_install` restores from `skills-lock.json`. `skills experimental_sync` crawls `node_modules` for skills.
+
+## Architecture
+
+```
+src/
+├── cli.ts           # Main entry point, command routing, init/check/update
+├── cli.test.ts      # CLI tests
+├── add.ts           # Core add command logic
+├── add.test.ts      # Add command tests
+├── list.ts          # List installed skills command
+├── list.test.ts     # List command tests
+├── agents.ts        # Agent definitions and detection
+├── installer.ts     # Skill installation logic (symlink/copy) + listInstalledSkills
+├── skills.ts        # Skill discovery and parsing
+├── skill-lock.ts    # Global lock file management (~/.agents/.skill-lock.json)
+├── local-lock.ts    # Local lock file management (skills-lock.json, checked in)
+├── sync.ts          # Sync command - crawl node_modules for skills
+├── source-parser.ts # Parse git URLs, GitHub shorthand, local paths
+├── git.ts           # Git clone operations
+├── telemetry.ts     # Anonymous usage tracking
+├── types.ts         # TypeScript types
+├── mintlify.ts      # Mintlify skill fetching (legacy)
+├── providers/       # Remote skill providers (GitHub, HuggingFace, Mintlify)
+│   ├── index.ts
+│   ├── registry.ts
+│   ├── types.ts
+│   ├── huggingface.ts
+│   └── mintlify.ts
+├── init.test.ts     # Init command tests
+└── test-utils.ts    # Test utilities
+
+tests/
+├── sanitize-name.test.ts     # Tests for sanitizeName (path traversal prevention)
+├── skill-matching.test.ts    # Tests for filterSkills (multi-word skill name matching)
+├── source-parser.test.ts     # Tests for URL/path parsing
+├── installer-symlink.test.ts # Tests for symlink installation
+├── list-installed.test.ts    # Tests for listing installed skills
+├── skill-path.test.ts        # Tests for skill path handling
+├── wellknown-provider.test.ts # Tests for well-known provider
+└── dist.test.ts              # Tests for built distribution
+```
+
+## Update Checking System
+
+### How `skills check` and `skills update` Work
+
+1. Read `~/.agents/.skill-lock.json` for installed skills
+2. For each skill, get `skillFolderHash` from lock file
+3. POST to `https://add-skill.vercel.sh/check-updates` with:
+   ```json
+   {
+     "skills": [{ "name": "...", "source": "...", "skillFolderHash": "..." }],
+     "forceRefresh": true
+   }
+   ```
+4. API fetches fresh content from GitHub, computes hash, compares
+5. Returns list of skills with different hashes (updates available)
+
+### Why `forceRefresh: true`?
+
+Both `check` and `update` always send `forceRefresh: true`. This ensures the API fetches fresh content from GitHub rather than using its Redis cache.
+
+**Without forceRefresh:** Users saw phantom "updates available" due to stale cached hashes. The fix was to always fetch fresh.
+
+**Tradeoff:** Slightly slower (GitHub API call per skill), but always accurate.
+
+### Lock File Compatibility
+
+The lock file format is v3. Key field: `skillFolderHash` (GitHub tree SHA for the skill folder).
+
+If reading an older lock file version, it's wiped. Users must reinstall skills to populate the new format.
+
+## Key Integration Points
+
+| Feature                    | Implementation                              |
+| -------------------------- | ------------------------------------------- |
+| `skills add`               | `src/add.ts` - full implementation          |
+| `skills experimental_sync` | `src/sync.ts` - crawl node_modules          |
+| `skills check`             | `POST /check-updates` API                   |
+| `skills update`            | `POST /check-updates` + reinstall per skill |
+
+## Development
+
+```bash
+# Install dependencies
+pnpm install
+
+# Build
+pnpm build
+
+# Test locally
+pnpm dev add vercel-labs/agent-skills --list
+pnpm dev experimental_sync
+pnpm dev check
+pnpm dev update
+pnpm dev init my-skill
+
+# Run all tests
+pnpm test
+
+# Run specific test file(s)
+pnpm test tests/sanitize-name.test.ts
+pnpm test tests/skill-matching.test.ts tests/source-parser.test.ts
+
+# Type check
+pnpm type-check
+
+# Format code
+pnpm format
+```
+
+## Code Style
+
+This project uses Prettier for code formatting. **Always run `pnpm format` before committing changes** to ensure consistent formatting.
+
+```bash
+# Format all files
+pnpm format
+
+# Check formatting without fixing
+pnpm prettier --check .
+```
+
+CI will fail if code is not properly formatted.
+
+## Publishing
+
+```bash
+# 1. Bump version in package.json
+# 2. Build
+pnpm build
+# 3. Publish
+npm publish
+```
+
+## Adding a New Agent
+
+1. Add the agent definition to `src/agents.ts`
+2. Run `pnpm run -C scripts validate-agents.ts` to validate
+3. Run `pnpm run -C scripts sync-agents.ts` to update README.md

package/skills/find-skills/SKILL.md

@@ -0,0 +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
+```

package/src/capabilities/skill-manager.js

@@ -219,23 +219,55 @@ class SkillManagerPlugin extends Plugin {
     this._loaded = true
   }
 
+  /**
+   * 递归查找 SKILL.md 或 AGENTS.md（支持多层嵌套目录）
+   * @param {string} dir - 要搜索的目录
+   * @returns {string|null} 找到的 markdown 文件路径
+   */
+  _findSkillMarkdown(dir) {
+    if (!fs.existsSync(dir) || !fs.statSync(dir).isDirectory()) {
+      return null
+    }
+
+    const entries = fs.readdirSync(dir, { withFileTypes: true })
+
+    // 第一遍：优先查找 SKILL.MD
+    for (const entry of entries) {
+      if (entry.isFile() && entry.name.toUpperCase() === 'SKILL.MD') {
+        return path.join(dir, entry.name)
+      }
+    }
+
+    // 第二遍：查找 AGENTS.MD
+    for (const entry of entries) {
+      if (entry.isFile() && entry.name.toUpperCase() === 'AGENTS.MD') {
+        return path.join(dir, entry.name)
+      }
+    }
+
+    // 如果没找到，递归搜索子目录（排除 node_modules）
+    for (const entry of entries) {
+      if (entry.isDirectory() && entry.name !== 'node_modules') {
+        const subPath = path.join(dir, entry.name)
+        const found = this._findSkillMarkdown(subPath)
+        if (found) return found
+      }
+    }
+
+    return null
+  }
+
   /**
    * 加载单个 skill
    */
   _loadSkill(name, skillPath) {
-    // 查找 markdown 文件，优先加载 SKILL.md 或 AGENTS.md
-    const mdFiles = fs.readdirSync(skillPath).filter(f => f.endsWith('.md'))
-
-    if (mdFiles.length === 0) {
+    // 查找 markdown 文件，优先加载 SKILL.md 或 AGENTS.md（支持多层嵌套）
+    const skillMdPath = this._findSkillMarkdown(skillPath)
+    if (!skillMdPath) {
       throw new Error('No markdown file found')
     }
 
-    // 优先选择 SKILL.md 或 AGENTS.md
-    let mainFileName = mdFiles.find(f => f.toUpperCase() === 'SKILL.MD') ||
-                       mdFiles.find(f => f.toUpperCase() === 'AGENTS.MD') ||
-                       mdFiles[0]
-
-    const mainFile = path.join(skillPath, mainFileName)
+    const mainFile = skillMdPath
     const content = fs.readFileSync(mainFile, 'utf-8')
     const frontmatter = parseFrontmatter(content)