Content
75%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 body delivers excellent, copy-paste-ready CLI guidance with a clear connection lifecycle and state-based checkpoints, and is well organized for a single-file skill. Its main weaknesses are moderate padding (concept intro, duplicated search guidance, a sloppy Agent Types aside) and dangling step references ('Step 2', '1b') that break the workflow numbering.
Suggestions
Label the workflow steps explicitly ('Step 1', 'Step 2') so the 'skip to Step 2' and '#### 1b' references resolve to real sections.
Trim the intro paragraph explaining what Astronomer/Airflow is, tighten the 'Agent Types' aside, and deduplicate the action-list command shown in both 'Searching for actions' and 'Popular actions'.
Either flesh out or remove the bare 'Astronomer Overview' bullet list (Deployment/Release/Workspace/User/Token) — as written it adds no actionable guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The core CLI guidance is efficient, but there is noticeable padding: an intro explaining what Astronomer/Airflow is ('Astronomer is a modern data orchestration platform powered by Apache Airflow. It's used by data engineers and data scientists...'), a rambling 'Agent Types' aside ('Those will be used to adjust tooling to be used best with your harness'), and the same action-list command duplicated in 'Searching for actions' and 'Popular actions'. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than level 4, where excess would be only minor. | 3 / 5 |
Actionability | Commands are fully executable and copy-paste ready: install ('npm install -g @membranehq/cli@latest'), login including the headless flow ('membrane login complete <code>'), connection setup with polling ('membrane connection ensure "https://astronomer.io" --json' plus '--wait'), action discovery and execution with JSON input ('membrane action run <actionId> --connectionId=CONNECTION_ID --input '{"key": "value"}' --json'), and a complete proxy flag table. Specific examples cover the common cases. | 5 / 5 |
Workflow Clarity | The sequence (install → login → connection → discover actions → run → proxy fallback) is clear with explicit state-based checkpoints (READY / BUILDING / CLIENT_ACTION_REQUIRED with re-poll guidance and error states). It is not level 5 because 'skip to Step 2' references a step that is never labeled and '#### 1b' implies an unlabeled '1a', leaving the numbering incoherent. | 4 / 5 |
Progressive Disclosure | The single-file structure is well organized with clear section headers (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) and no bundle files exist or are needed at this size. It is not level 5 because the bare 'Astronomer Overview' bullet list (Deployment/Release/Workspace/User/Token) has no depth, links, or stated purpose — a minor organization gap. | 4 / 5 |
Total | 16 / 20 Passed |