Content
82%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is concise, actionable, and well-structured with a clear workflow and one-level reference to installation docs. Main improvements are adding an explicit transcription-output validation checkpoint and a concrete example tool invocation.
Suggestions
Add an explicit validation step after transcription (e.g. verify segments are non-empty and timestamps are monotonic) before proceeding to summarize or translate.
Provide one complete example `mcp__funasr__transcribe_audio` invocation with a concrete `audio_path` and expected output shape.
Format the docs reference as a markdown link (e.g. `[funasr-installation.md](../../docs/funasr-installation.md)`) to make navigation explicit.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence, providing only operational detail (install command, tool name, path handling) without explaining what audio or ASR is; every line earns its place. | 5 / 5 |
Actionability | It gives concrete executable commands (`npm --prefix "..." run install:asr`, `mcp__funasr__transcribe_audio` with `language: "auto"`) but the PilotDeck directory is a placeholder and a full example invocation is not shown. | 4 / 5 |
Workflow Clarity | The five-step workflow is clearly sequenced with an install/retry checkpoint, but it lacks an explicit validation/verification step for the transcription output before downstream summarization. | 4 / 5 |
Progressive Disclosure | Content is well-organized into sections with a single clearly signaled one-level-deep reference to `../../docs/funasr-installation.md` for troubleshooting detail; minor gap is the absence of inline-link formatting for the reference. | 4 / 5 |
Total | 17 / 20 Passed |