SKILLEMALL.ai
GitHub ↗ RU Sign in

BF project-manager

项目上下文隔离与状态管理系统 v2.7.0。核心解决：对话中遗忘、跨天上下文丢失、新话题漏记录。新增：甘特图自动生成、项目风险自动识别、依赖关系管理。触发词: /project, 新建项目, 回到项目, 记录项目, 继续项目, 项目列表, 甘特图

ClawHub Agent Skills author: Krislu v2.7.2 MIT-0 7 files body ≈ 3 452 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process F 35/100 · Will not run — References files that are not bundled: SECURITY.md

ProcedureInfrastructuretype 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
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
60
Run on models
none yet
Process rating
F
35/100
Will not run
References files that are not bundled: SECURITY.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
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.
  2. The text references files that are not there: add them or drop the references.
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: 7. 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")
  • warning missing-ref reference to a missing file: SECURITY.md

Process rating: all ten parameters 35/100

Will not run. References files that are not bundled: SECURITY.md
  • 0Tools and files. 1 referenced file(s) missing: SECURITY.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 40Consistency. Frontmatter name (project-manager) differs from the folder (agent-project-manager)
  • 55Failures and branches. 1 branches
  • 100Steps. 164 steps
  • 100Execution cost. Instruction body is 3452 tokens
  • 100Progress reporting. Reports progress
  • low 11 top-level sections: this looks like several domains in one skill

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
  • -5TODO / placeholder text left in the skill
  • -229 emoji in the instructions: noise for the model
  • +2Single-language instructions
  • +3Description length 123: enough signal without eating the budget
  • +4Structure: 55 headings
  • +3Step-by-step instructions: 164 items
  • +4Has examples (8 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This is a local project-memory skill rather than malware, but it needs review because it can persist and periodically scan conversation-derived project data with inconsistent consent boundaries.
LLM: suspicious (high) · VirusTotal: · 28 May 2026