From 7a909a4cd647322df9bb63ee0187ef2babc9df64 Mon Sep 17 00:00:00 2001 From: Agent Skills Bot Date: Fri, 21 Aug 2026 13:01:40 +0000 Subject: [PATCH] =?UTF-8?q?=E5=90=8C=E6=AD=A5=20latest=20skill=20releases?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .dist-sync/versions.json | 1 + skills/disk-master/SKILL.md | 122 ++++++++++++++++++++++-------------- 2 files changed, 77 insertions(+), 46 deletions(-) diff --git a/.dist-sync/versions.json b/.dist-sync/versions.json index 035dcb3..4b36026 100644 --- a/.dist-sync/versions.json +++ b/.dist-sync/versions.json @@ -1,5 +1,6 @@ { "baimiao-table-ocr": "v1", + "disk-master": "v1", "everything-file-search": "v1", "teach-me": "v2", "think-twice": "v3.1" diff --git a/skills/disk-master/SKILL.md b/skills/disk-master/SKILL.md index c390a12..35ac372 100644 --- a/skills/disk-master/SKILL.md +++ b/skills/disk-master/SKILL.md @@ -1,63 +1,93 @@ --- name: disk-master -description: Diagnose Windows disk usage with disk-master.exe, explain what is filling the drive, and generate an interactive SpaceSniffer-style HTML report. +description: > + Diagnose Windows disk usage with the bundled read-only disk-master.exe. Use + when a user asks why C: or another Windows drive is full, wants the largest + files or folders, needs AppData or installed app/game space analysis, or asks + for a SpaceSniffer-style HTML disk report. The scan stays local and does not + delete, uninstall, move, or clean anything. Do not use for non-Windows or + network-drive analysis, or as an automatic cleanup tool. --- # Disk Master -Use this skill when the user asks why a Windows drive is full, wants to find large files or folders, wants to inspect C: drive software/AppData usage, or wants an interactive disk report. +Disk Master collects Windows drive data as JSON, explains what is consuming +space, and can turn the same JSON into an interactive HTML report. -## Workflow +## When to use -1. If the user does not specify a drive, first inspect available local drives, then ask which drive to analyze. Also ask whether they approve a UAC prompt for faster NTFS/MFT scanning. Explain that the scan is local and read-only. -2. Run `disk-master.exe scan --drive C: --scan quick --out result.json` for a fast estimate, or `disk-master.exe scan --drive C: --scan full --out result.json` when the user asks for a complete scan. -3. If the user explicitly agrees to a UAC prompt for privileged NTFS/MFT scanning, add `--elevate --mode mft` and keep `--out `. -4. After scanning, use the CLI status output to report the JSON path and a short human-readable summary. Do not run an extra file-existence check unless the command fails or the path is missing. -5. Read `result.json` and explain the disk state: largest directories, largest files, file types, user folders, AppData hotspots, installed apps/games, and advice items. -6. Generate an interactive static HTML report from `template.html` by replacing `%%DATA%%` with the JSON text. -7. Present the summary first, then link the JSON path and HTML report path. Make clear that all suggestions are review-only and no cleanup was performed. +Use it for: -## Clarifying Questions +- Diagnosing a full Windows drive or low free space. +- Finding the largest directories, files, and file types. +- Inspecting AppData, user folders, installed applications, or games. +- Producing a local SpaceSniffer-style disk report. +- Getting an application inventory or a quick text-only disk summary. -When the request is ambiguous, ask concise interactive questions before scanning: +Use another approach for non-Windows systems, UNC/network drives, or requests to +automatically delete, uninstall, move, or clean data. Disk Master may identify +candidates for review; it does not prove that a file is safe to remove. -- Drive: choose from detected local drives, for example `C:` or `D:`. -- Scan depth: quick estimate or full scan. -- UAC/MFT: whether to allow an administrator prompt for the faster NTFS engine. -- Output: whether to generate only JSON or also an HTML report. +## Safety boundary -Recommended wording: "我可以全程本地只读扫描。允许 UAC 的话，NTFS 盘会优先用更快的 MFT 引擎；不允许也可以用普通模式，只是更慢。你想分析哪个分区？" +The executable does not modify scanned user data. This workflow writes the +requested JSON and, when requested, an HTML report generated from that JSON; +elevation may also use temporary status/output files for process handoff. Treat +every recommendation as review-only and state that no cleanup was performed. -## SOP +## Workflow (SOP) -1. Stop and ask before scanning if any required detail is not confirmed. Use the available interactive question tool when possible instead of guessing. -2. Confirm the target drive. If the user only says "scan my disk" or similar, list local fixed drives first, then ask which one to analyze. -3. Confirm whether to use fast index mode. Explain it as: "快速索引需要管理员权限，会优先使用 NTFS/MFT 引擎，速度更快；不授权也可以用普通遍历模式，只是更慢。" -4. Confirm scan scope when unclear: quick scan for a fast estimate, full scan for the final report. -5. Confirm output expectation: JSON only, natural-language analysis, HTML report, or all of them. Default to JSON + HTML report when the user asks for a report. -6. If fast index mode is enabled, tell the user before running the command: "接下来会出现一个 Windows UAC/授权弹窗，请选择允许；扫描只读、仅在本机运行。" -7. Run the scan with an explicit output path. Prefer timestamped names such as `result-.json` and `report-.html` to avoid overwriting prior reports. -8. Expect the report JSON to be large. Be prepared to read it in chunks or use targeted extraction instead of assuming one read will return the whole file. -9. Generate the HTML report by injecting the JSON into `template.html`. If the environment can display or open the HTML directly for the user, do so; otherwise provide the absolute report path. -10. Present results in this order: short human summary, JSON path, HTML path, top findings, safety note. Never imply that cleanup was performed. +1. Choose the operation from the user's goal: + - Full diagnosis or final report: `scan --scan full`. + - Fast, incomplete estimate: `scan --scan quick`. + - Installed applications only: `apps`. + - Short text-only overview: `summary`. +2. Resolve the target drive. If the user did not name one, list available + Windows drive letters and ask which to scan. Do not silently assume `C:`. +3. Before every `scan` or `summary`, ask once whether the user allows a Windows + UAC prompt. Explain that approval lets `--mode auto` use the faster NTFS/MFT + path when eligible; declining keeps the local read-only scan in normal mode. + Combine this with the drive question when both are needed. `apps` does not + require this scan confirmation. +4. Infer scope and output from the request instead of asking a confirmation + checklist. Words such as “quick”, “rough”, or “estimate” select `quick`; + “complete”, “full”, “final”, or “report” select `full`. Otherwise use `full`. + Generate HTML only when the user asks for a report, visualization, treemap, + or SpaceSniffer-style view. +5. For each JSON-producing operation, create an explicit absolute output path. + A drive scan and its optional HTML report share one timestamped basename: + `disk-master--.json` and `.html`. Remove the colon + from the drive token, for example `disk-master-C-20260519-170000.json` and + `disk-master-C-20260519-170000.html`. Name an app-only inventory + `disk-master-apps-.json`. +6. Run the bundled executable from the skill directory. Use `--mode auto` for + normal operation and add `--elevate` only after the user approves UAC: -Minimum confirmations before execution: + ```text + disk-master.exe scan --drive C: --scan full --mode auto --out + disk-master.exe scan --drive C: --scan quick --mode auto --out + disk-master.exe scan --drive C: --scan full --mode auto --elevate --out + disk-master.exe apps --out + disk-master.exe summary --drive C: --mode auto + ``` -- Target drive, for example `C:` or `D:`. -- Fast index / administrator permission: yes or no. -- Scan scope: quick or full. -- Output format: JSON, HTML, or both. + Optional public flags are `--depth `, `--top `, `--no-apps`, and + `--mode `. `--depth` limits quick-scan depth and JSON tree + depth. Prefer `auto`; force `mft` or `walk` only when the user requests it or + when diagnosing scan behavior. +7. On a successful `scan`, use the command's status output as the authoritative + JSON path. For `apps`, use the explicit output path after a successful exit. + Read large JSON in chunks or extract relevant fields. Cover the disk state, + scan completeness and errors, largest directories/files, extension totals, + user folders, AppData hotspots, applications, and advice that materially + affects the answer. Label a quick scan as incomplete. +8. If HTML was requested, read `template.html`, replace the single `%%DATA%%` + marker with the raw JSON text, and write the matching `.html` path from step + 5. The CLI has no `report` command. +9. Present the result in this order: concise diagnosis, highest-impact findings, + uncertainty or scan errors, JSON/HTML absolute paths, then the safety note + that all actions remain suggestions and no cleanup occurred. -## Report Sections - -- Summary cards: used/free space, largest directory, number of high-priority suggestions. -- SpaceSniffer section: interactive treemap with drill-down, breadcrumbs, search, and detail panel. -- Diagnostic details: large files, user paths, AppData, C: drive apps/games, file extensions. -- Advice tutorials: each recommendation expands into step-by-step safe handling guidance. -- Scan metadata: mode, permissions, MFT state, errors, and raw JSON summary. - -## Safety - -The tool is read-only for user data. Do not delete files, uninstall applications, clean the registry, or modify user data as part of this skill. - -Never present a recommendation as an automatic cleanup action. Use language like "建议检查", "可以考虑", and "请先确认" for uncertain items. +If a command fails or UAC is declined/cancelled, report the error plainly and +offer the non-elevated `--mode auto` scan when applicable. Do not claim an +output file exists unless the command reported success.