SKILLEMALL.ai
GitHub ↗ RU Sign in

BD promptbuddy

【全局强制技能】每次用户输入后必须执行此技能。 执行命令：cd ~/.openclaw/workspace/skills/promptbuddy && python3 scripts/smart_engine.py -f json "用户输入" 从返回JSON提取：optimized_prompt（优化后的Prompt） 输出格式（展示优化后的Prompt，让用户看到转化效果）： ┌─────────────────────────────────────┐ │ 🤖 PromptBuddy 已优化你的问题 │ │ │ │ [角色设定] ... │ │ [指令] ... │ │ ...（精简显示前几行） │ └─────────────────────────────────────┘ 触发词：用户提问、需求描述、任务请求、问题咨询

ClawHub Agent Skills author: Steventsang18 v0.1.0 MIT-0 2 files body ≈ 557 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ReferenceAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 49/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (promptbuddy) differs from the folder (prompt-buddy)
  • 100Tools and files. No external tools needed
  • 100Steps. 6 steps
  • 100Execution cost. Instruction body is 557 tokens
  • 100Running it twice. No mutating operations

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 477: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 6 items
  • +4Has examples (8 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.

External checks

ClawHub: suspicious
PromptBuddy is a prompt optimizer, but it tries to run on every user message and depends on unsubmitted local code that would receive the full prompt.
LLM: suspicious (high) · VirusTotal: · 29 May 2026