Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a strong, operational skill: concrete executable commands, a clearly sequenced flow, and explicit validation/recovery loops for fragile attach steps. Its main weaknesses are repeated restatements of the same anti-isolation rule and a dangling reference to a non-existent mcporter-config.md.
Suggestions
Consolidate the 'never use isolated browser tooling' rule into a single stated-once section and cross-reference it, instead of restating it in Route, Live UI Proof, and elsewhere.
Either add the referenced mcporter-config.md to the bundle and link it properly, or remove the 'Config repair details live in mcporter-config.md' line so there are no dangling references.
Consider moving the lengthy Peekaboo attach-prompt recovery block into a references file (e.g. attach-recovery.md) to keep the core route/flow overview lean while keeping it one level deep.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is largely lean and command-driven, but the 'avoid isolated browser / prefer existing profile' rule is restated three or more times across Route, Live UI Proof, and adjacent prose, so it could be tightened. | 2 / 3 |
Actionability | It provides fully executable, copy-paste-ready mcporter and Peekaboo bash commands with real flags and realistic placeholders (pageId, uid, allow coordinates) throughout every section. | 3 / 3 |
Workflow Clarity | The Typical Flow is a clear sequenced process, and Check MCP includes explicit validation ('list_pages must show the user's real open tabs') plus feedback loops for attach-prompt and DevToolsActivePort recovery. | 3 / 3 |
Progressive Disclosure | Sections are well-organized with clear headers, but the only external reference ('mcporter-config.md') is a dangling code-span to a file absent from the bundle, and all content lives inline in SKILL.md. | 2 / 3 |
Total | 10 / 12 Passed |