AD ext4-recovery
从 ext4/ext3 文件系统恢复被误删的文件与目录树(rm -rf、rm、find -delete、GUI 删除等)。当现成工具 extundelete / ext4magic 报 “Loading journal descriptors ... 0 descriptors loaded”、只打印 Filesystem in use 而无任何输出、或恢复失败时,使用本技能直接解析 jbd2 日志环,从日志中重建元数据、并从原始磁盘取出尚未被复用的数据块。适用场景:误删源码目录/仓库元数据/配置文件、卸载清理后的紧急抢救、文件系统取证、判断“还能不能救回”以及能救回多少。
从 ext4/ext3 文件系统恢复被误删的文件与目录树(rm -rf、rm、find -delete、GUI 删除等)。当现成工具 extundelete / ext4magic 报 “Loading journal descriptors ... 0 descriptors loaded”、只打印…
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
medium Dangerous commands
cmd-privilegereferences/tool-limits.md:78Privilege escalation / world-writable permissions2. 设备是否可读? → 否:sudo chown $USER:disk <dev>
-
low Dangerous commands
cmd-privilegescripts/diag.sh:7Privilege escalation / world-writable permissions (string literal in code, not executed; code comment)# 需要能读设备节点(root,或先 `sudo chown $USER:disk <dev>`)。
code literalcomment -
low Dangerous commands
cmd-privilegescripts/diag.sh:21Privilege escalation / world-writable permissions (string literal in code, not executed)echo " sudo chown \$USER:disk $DEV && sudo chmod 660 $DEV"
code literal -
low Dangerous commands
cmd-privilegeSKILL.md:21Privilege escalation / world-writable permissions (quoted — discussed, not commanded)(`sudo chown $USER:disk <dev> && sudo chmod 660 <dev>`),不要用 `sudo mount`。
quoted
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 48/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
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 26 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1073 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low The response is described with custom markup (5 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
- +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
- +5Description quotes 2 example trigger phrases
- +3Description length 290: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 96.