SKILLEMALL.ai
GitHub ↗ RU Sign in

CD guide-creator

通用项目文档指南生成器：为任何项目创建和维护标准化的 guide 文档体系（start.md + guide/ 目录），覆盖设计理念、技术架构、更新日志、踩坑记录等完整生命周期。支持三种模式：(1) 初始化模式 — 一键创建标准化文档骨架；(2) 更新模式 — 追加 changelog/pitfalls/版本号同步；(3) 上下文恢复 — AI 在新对话中快速理解项目全貌。触发关键词：'初始化项目guide'、'创建项目文档'、'更新guide'、'总结经验教训'、'project guide'、'init guide'、'update guide'、'context recovery'。当用户说'帮我建一套项目文档'、'记录这次的更新和踩坑'、'新对话帮我恢复项目上下文'时触发。

Not recommendedcritical or high security findings
modbender/skill-library-mcp Agent Skills author: modbender MIT 9 files body ≈ 1 463 tokens Open the sourcegithub.com↗ analyzed 2 d ago

通用项目文档指南生成器：为任何项目创建和维护标准化的 guide 文档体系（start.md + guide/ 目录），覆盖设计理念、技术架构、更新日志、踩坑记录等完整生命周期。支持三种模式：(1) 初始化模式 — 一键创建标准化文档骨架；(2) 更新模式 — 追加…

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

ProcedureWriting and documentstype 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
C
67/100
safety, quality, tests
Safety 60%
63
Quality 40%
74
Run on models
none yet
Process rating
D
46/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

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Obfuscation
If you install

The files contain invisible characters, encoded commands or comments hidden from readers but visible to the model. What you read differs from what the agent sees.

For the author

Remove invisible characters (they usually sneak in through copy-paste) and encoded strings: no catalog will pass them. Instructions for the model must be readable by a human too.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. 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 · 3

  • high Obfuscation obf-html-comment-instruction references/templates/sub-doc-templates.md:186
    Hidden instruction inside an HTML comment
    <!-- system prompt 模板 -->
  • high Obfuscation obf-html-comment-instruction references/templates/sub-doc-templates.md:189
    Hidden instruction inside an HTML comment
    <!-- system prompt 模板 -->
Medium and low: 1
  • low Dangerous commands cmd-background-process references/templates/start-template.md:52
    Starts a background / autostarted process
    nohup node server.js > log/server.log 2>&1 &

Files scanned: 9. 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 46/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
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Steps. 82 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1463 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
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +3Description length 345: enough signal without eating the budget
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 82 items
  • +4Has examples (4 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +3All 2 scripts are documented

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