CtrlK
BlogDocsLog inGet started
Tessl Logo

maaend-issue-log-analysis

分析 MaaEnd 上游仓库公开 Issue(`https://github.com/MaaEnd/MaaEnd/issues/...` 或 `#1234`)。自动抓取 issue 正文和评论中的 `MaaEnd-logs-*.zip` 附件,下载解压后从 `maafw.log`、`maafw.bak.*.log`、`go-service.log`、`mxu-tauri.log`、`mxu-web-*.log`、`mxu-agent*.log`、`config/*`、`on_error/` 中筛选关键证据,并结合 MaaEnd、MaaFramework、MXU 的代码和文档判断根因、给出修复方案,供用户在让你分析 MaaEnd issue、日志包、识别失败、任务卡死、控制器差异、Pipeline/Agent/MXU 问题时使用。

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, highly actionable analysis workflow with strong sequencing and validation loops and good delegation to sibling skills. The main weaknesses are a redundant Reminders section that reprises the Workflow and inline reference material (Log Map, Common Patterns) that could be split into separate files.

Suggestions

Reconcile the Reminders section with Workflow steps 3–5: convert the redundant multi-part-zip and DMP reminders into a short checklist that references the steps rather than restating their rules, to recover token budget.

Move the Log Map and Common Patterns sections into a separate reference file (e.g., references/log-map.md) and keep SKILL.md as an overview that links to it, improving progressive disclosure and reducing the inline reference burden.

Consolidate the multi-part-zip handling so it is stated once with full detail (download → verify all parts non-empty → extract) instead of being elaborated across both step 3 and step 4 before being reprised in Reminders.

DimensionReasoningScore

Conciseness

Content is dense and domain-specific (no padding with concepts Claude already knows), but the Reminders section reprises workflow rules already stated in steps 3–5 (multi-part zip, DMP handling) and the multi-part-zip guidance is elaborated across steps 3 and 4 before being restated again — minor trimmable redundancy, above anchor 3 but below the every-token-earns-its-place bar of anchor 5.

4 / 5

Actionability

Provides copy-paste-ready commands (`curl -L`, `git clone --depth 1 --branch "v<VERSION>"`, `git checkout vXXX`), concrete cache paths (`.cache/issue-logs/issue-<number>/`), specific grep signals (`Tasker.Task.Starting`, `Node.Recognition.Failed`, `post_task returned task_id`), and a full output-format template, matching the score-5 anchor for fully executable guidance covering common cases.

5 / 5

Workflow Clarity

The 8-step Workflow is clearly sequenced with explicit validation/feedback loops for the batch multi-part-zip operation ('必须…确认每个文件都存在且非空,才能开始解压'; '不得解压;应返回 issue 正文和评论继续查找') and DMP recovery ('符号化失败…仍必须输出 module+offset'), satisfying the batch/destructive feedback-loop requirement rather than triggering the cap-at-3 rule.

5 / 5

Progressive Disclosure

Well-organized into clear sections and delegates specialized work via well-signaled one-level-deep references (`.agents/skills/dmp-analysis/SKILL.md`, `.agents/skills/tasks/`), but substantial reference material (the ~80-line Log Map, Common Patterns) is inlined rather than split into separate files, leaving minor organization gaps relative to the score-5 anchor.

4 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific, third-person description that covers concrete capabilities, natural trigger terms, explicit use-when guidance, and a distinct niche. It neither pads nor over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 抓取 `MaaEnd-logs-*.zip` 附件、下载解压、从命名日志文件(maafw.log/go-service.log/mxu-tauri.log 等)筛选证据、结合代码文档判断根因、给出修复方案 — with comprehensive coverage, matching the score-5 anchor.

5 / 5

Completeness

It explicitly answers 'what' (analyze issue, fetch/extract logs, filter evidence, correlate code/docs, root-cause, fix) and 'when' (explicit '供用户在…时使用' trigger clause with concrete phrases), matching the score-5 anchor for both what and when.

5 / 5

Trigger Term Quality

The clause '供用户在让你分析 MaaEnd issue、日志包、识别失败、任务卡死、控制器差异、Pipeline/Agent/MXU 问题时使用' provides comprehensive natural trigger terms plus file extensions (.zip, .log, #1234, issue URLs), matching the score-5 anchor including synonyms and extensions.

5 / 5

Distinctiveness Conflict Risk

Scoped to a very narrow niche (MaaEnd/MaaFramework/MXU) with repo URLs, specific log filenames, and distinct triggers, giving minimal conflict risk with other skills — matches the score-5 anchor.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 11 missing, 9 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
MaaEnd/MaaEnd
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.