Content
45%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 Membrane CLI operating instructions are genuinely strong — executable commands, a clear connection state machine, and sensible best practices — but they are buried after ~300 lines of irrelevant keyword padding that wastes most of the skill's token budget. Deleting or externalizing the overview list would transform the skill's quality.
Suggestions
Delete the 'Authlete Overview' bullet list (~300 lines of file formats and tracker-module terms irrelevant to OAuth work); it contributes nothing Claude cannot already infer and consumes the bulk of the context window.
Fix the workflow cross-references: label an explicit 'Step 2' (searching/running actions) since the text says 'skip to Step 2', and either populate 'Popular actions' with real action names or remove the section.
If any extended material is genuinely needed (e.g. a curated Authlete API entity reference), move it into a references/ file with a clearly signaled one-level-deep link from SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Authlete Overview' section is roughly 300 lines of padded term-listing (file extensions, audio formats, 'ScreamTracker', 'ProTracker Module') that is irrelevant filler, matching the 'severely verbose; heavily padded' anchor rather than the milder over-explanation of score 2. | 1 / 5 |
Actionability | Concrete executable commands cover the full path (install, login, connection ensure, action list/run with --input JSON, proxy request with a flags table), with only minor gaps such as the 'Popular actions' section listing no actual actions and the vague 'Use action names and parameters as needed'. | 4 / 5 |
Workflow Clarity | The install -> login -> connect -> poll-state -> search-actions -> run -> proxy-fallback sequence is clear with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and error guidance, but 'skip to Step 2' references a step that is never labeled, leaving a minor sequencing gap. | 4 / 5 |
Progressive Disclosure | There are no bundle files and no references; the body is a single file whose dominant content is an inlined 300-line term wall that belongs in a curated reference (or nowhere), matching the 'minimal structure / content that belongs in separate files is inlined' anchor. | 2 / 5 |
Total | 11 / 20 Passed |