AF backup-douyin-chat
Safely operate the local Douyin group-chat backup tool to log in by QR code, list conversations, perform full or incremental history backups, export JSON or JSONL, verify completeness, and optionally download encrypted image media. Use when the user asks to back up, export, inspect, verify, update, or recover Douyin/抖音 private-message or group-chat history, including requests such as 备份抖音群聊、导出聊天记录、增量更新聊天、检查备份完整性、下载聊天图片.
Safely operate the local Douyin group-chat backup tool to log in by QR code, list conversations, perform full or incremental history backups, export JSON or…
As a process F 45/100 · Will not run — References files that are not bundled: scripts/tool.sh, references/interpretation.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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
missing-refreference to a missing file: scripts/tool.sh - warning
missing-refreference to a missing file: references/interpretation.md
Process rating: all ten parameters 45/100
- 0Tools and files. 2 referenced file(s) missing: scripts/tool.sh, references/interpretation.md
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Inputs and preconditions. Does not say what the process needs to start
- 70When it triggers. States when to use, but not when not to
- 100Steps. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 932 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (7 tags): a typed call is more reliable
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 423: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.