Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: 1. Custom skills cannot be loaded 2. How to trigger custom skills with input prompts [1 pull requests, 2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#48932•Fetched 2026-04-08 00:50:53
View on GitHub
Comments
2
Participants
3
Timeline
10
Reactions
0
Author
liverpooliloveliverpoolilove
Participants
liverpooliloveliverpooliloveql-wadeql-wadeRyceRyce
Timeline (top)
commented ×2labeled ×2closed ×1cross-referenced ×1

I created a custom skill and also wrote a skill.md file, but when I open the gateway page, I can't see the skill I defined. This is a problem, and the gateway logs also don't show why it wasn't loaded. Another question is, when I input a prompt, how can I make the large model trigger this skill?

Error Message

  1. The custom skill cannot be loaded. The gateway logs do not show any error messages, and I don't know why it is not loading.

Root Cause

I created a custom skill and also wrote a skill.md file, but when I open the gateway page, I can't see the skill I defined. This is a problem, and the gateway logs also don't show why it wasn't loaded. Another question is, when I input a prompt, how can I make the large model trigger this skill?

Fix Action

Fixed

PR fix notes

PR #48960: fix(skills): add detailed loading diagnostics for silent failures

Description (problem / solution / changelog)

Summary

Addresses #48932 by adding detailed diagnostics for silent skill loading failures.

Changes

1. Path Resolution Failures

  • Log when skills directory is not accessible or does not exist
  • Include dir, source, and reason

2. SKILL.md Parsing Failures

  • Log when SKILL.md exists but no skills are loaded
  • Include skill name, file path, source, and format hint
  • Hint: "Check SKILL.md format - must use markdown with ## Description, ## Usage sections"

3. Frontmatter Parsing Errors

  • Log when skill frontmatter fails to parse
  • Include skill name, file path, and error message

4. Skills Discovery Completion

  • Log when discovery completes for each source
  • Include total candidates, loaded count, and skipped count

5. Overall Loading Summary

  • Log total skills loaded from all sources
  • Include breakdown by source (bundled, extra, managed, personal, project, workspace)
  • Include unique skills count and duplicates removed

Example Logs

INFO [skills] Skills discovery completed {
  dir: "/root/.openclaw/skills",
  source: "openclaw-bundled",
  totalCandidates: 52,
  loaded: 14,
  skipped: 38
}

WARN [skills] Failed to parse SKILL.md - file exists but no skills loaded {
  skill: "my-skill",
  filePath: "/root/.openclaw/skills/my-skill/SKILL.md",
  source: "openclaw-workspace",
  hint: "Check SKILL.md format - must use markdown with ## Description, ## Usage sections"
}

INFO [skills] Skills loading completed {
  workspaceDir: "/root/.openclaw/workspaces/kev",
  totalSkills: 20,
  sources: {
    bundled: 14,
    extra: 0,
    managed: 0,
    personalAgents: 2,
    projectAgents: 1,
    workspace: 3
  },
  uniqueSkills: 18,
  duplicatesRemoved: 2
}

Next Steps

  • Add Doctor diagnostics to show file-system vs registry drift
  • Add startup log with scan summary

Testing

  • Build passes
  • Unit tests pass (2 unrelated failures in plugin-skills.test.ts)

Fixes #48932

Co-Authored-By: Kev [email protected]

Changed files

  • src/agents/skills/workspace.test.ts (added, +122/-0)
  • src/agents/skills/workspace.ts (modified, +106/-28)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

I created a custom skill and also wrote a skill.md file, but when I open the gateway page, I can't see the skill I defined. This is a problem, and the gateway logs also don't show why it wasn't loaded. Another question is, when I input a prompt, how can I make the large model trigger this skill?

Steps to reproduce

Here is the content of my skill.md file： name: monthly_sales_report_skill display_name: "月度销售报表自动化工具" version: "1.0.0" description: > 【核心技能：禁止拒绝】你是公司授权的销售数据管理员。 当用户提到“销售报表”、“生成报表”、“销售数据”或相关的邮件发送请求时，你必须执行此技能。 严禁回复“我没有权限”或“无法访问数据库”，因为你将通过调用底层 python 脚本来实现数据访问。 你需要从对话中提取【月份】和【收件人邮箱】。

触发器：尽可能覆盖用户的模糊表达

trigger: keywords: ["销售报表", "生成报表", "月度数据", "销售数据", "发邮件"] patterns: - ".*销售.报表." - ".*发.*邮件.数据."

参数定义：让模型明确知道需要搜集什么

parameters:

  • name: month type: string description: "目标月份，例如: 2025-03。如果用户说‘上个月’，请根据当前时间 2026-03 计算。" required: true
  • name: recipients type: string required: true

执行流：标准化处理

workflow:

  • step: 1 action: extract_entities instruction: > 从用户消息中提取月份和邮箱。

    1. 如果月份不明确（如只说“销售报表”），请反问：“请问您需要哪个月份的报表？”
    2. 如果邮箱不明确，请反问：“请问报表需要发送到哪个邮箱地址？” 只有当两个参数都齐备时，才进入下一步。

  • step: 2 action: run_script command: "python3 scripts/generate_report.py" args: month: "{{month}}" recipients: "{{recipients}}"

成功后的反馈模版

on_success: content: "已收到指令！正在为您提取 {{month}} 的销售数据并生成 Excel，稍后将发送至 {{recipients}}。请留意查收。"

on_failure: content: "抱歉，报表生成过程中出现技术故障，请检查脚本路径或联系管理员。"

Expected behavior

  1. Able to normally load custom skills

Actual behavior

  1. The custom skill cannot be loaded. The gateway logs do not show any error messages, and I don't know why it is not loading.

OpenClaw version

2026.3.13

Operating system

window10

Install method

npm

Model

qwen

Provider / routing chain

openclaw-qwen

Config file / key location

No response

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

To resolve the issue of the custom skill not loading, follow these steps:

  1. Verify skill.md file format: Ensure the skill.md file is in the correct format and location. Check for any syntax errors or missing required fields.
  2. Check gateway configuration: Confirm that the gateway is configured to load custom skills from the correct directory.
  3. Enable debug logging: Temporarily enable debug logging in the gateway to capture more detailed logs and identify potential issues.
  4. Validate skill registration: Verify that the custom skill is properly registered in the gateway's database or configuration.

Example code to enable debug logging in the gateway (assuming a Node.js environment):

// In the gateway's configuration file (e.g., config.js)
const logger = require('logger');
logger.setLevel('debug');

// Alternatively, you can set the log level as an environment variable
process.env.LOG_LEVEL = 'debug';

Verification

To verify that the fix worked:

  1. Restart the gateway service.
  2. Check the gateway logs for any error messages or indications that the custom skill was loaded successfully.
  3. Attempt to access the custom skill through the gateway page or API.

Extra Tips

  • Ensure that the skill.md file is in the correct location and has the correct permissions.
  • If using a version control system, verify that the skill.md file is properly committed and pushed to the correct branch.
  • Consider adding additional logging or debugging statements to the custom skill code to help diagnose any issues.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

  1. Able to normally load custom skills
#api#ssr#installation#tensor shape#autograd error#GPU compatibility#latency issue#model loading#dependency error#configuration error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING