AD 聊天记录生成
从零生成模拟微信群聊记录的 Excel (.xlsx) 文件，包含 group_info / active_members / message_stream 三个 sheet，格式与派平台的群聊训练数据完全兼容。使用场景：(1) 需要生成 AI 助手训练数据的模拟群聊对话；(2) 测试群聊 FAQ/知识库系统；(3) 展示多角色对话 multi-Agent 工作流；(4) 生成任意主题的群聊样本 xlsx 文件。触发词：生成群聊记录、模拟群聊数据、生成聊天记录表格、群聊 xlsx、派聊天记录。
从零生成模拟微信群聊记录的 Excel (.xlsx) 文件，包含 groupinfo / activemembers / messagestream 三个 sheet，格式与派平台的群聊训练数据完全兼容。使用场景：(1) 需要生成 AI 助手训练数据的模拟群聊对话；(2) 测试群聊 FAQ/知识库系统；(3)…
As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 41/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 (聊天记录生成) differs from the folder (chat-record-generator)
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 100Steps. 11 steps
- 100Execution cost. Instruction body is 472 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 249: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 11 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.