Content
53%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 is a dense, largely executable API reference with lean prose and real error-handling examples, which makes it highly actionable. Its structural weakness dominates, though: everything is inlined in one 583-line SKILL.md with no reference files, no explicit integration workflow, and 'Related Skills' links that don't resolve within the bundle.
Suggestions
Split per-platform SDK references (iOS, Android, React Native, Flutter) into separate reference files under references/ and keep only the SDK overview table, setup quick-starts, and token-generation flow in SKILL.md.
Add an explicit integration workflow section (generate auth token on backend -> initConnection -> enable scheduler -> read/write data) with validation checkpoints, e.g. checking the connection callback success flag before fetching data.
Replace placeholder arguments ('user_id=...', 'VERSION') in code examples with realistic values so snippets are copy-paste ready, and remove the 'Related Skills' section or verify those sibling skills exist in the bundle.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Prose is lean — it assumes Claude's competence and devotes nearly all tokens to code — but getActivity/getSleep/getDaily blocks repeat across six platforms, and the 'When to Use Each SDK' table duplicates the SDK Overview table's Use Case column. It is mostly efficient with tightening opportunities, matching anchor 3 rather than 4. | 3 / 5 |
Actionability | Concrete install commands, setup code, method references, error handling (ApiError/TerraError), and manifest permissions are provided for every platform. Minor gaps keep it below anchor 5: placeholder arguments like 'user_id=...', undefined variables like startDate/endDate, and 'VERSION' placeholders in the gradle and pubspec snippets. | 4 / 5 |
Workflow Clarity | Per-platform sections follow an implicit order (installation, setup, connect, read, write) and 'Backend Token Generation' ties the mobile flow together with token expiration details, but no explicit sequence ('first... then...') and no validation or checkpoint guidance exist beyond one error-handling snippet. This matches anchor 3 — sequence present but checkpoints missing or implicit. | 3 / 5 |
Progressive Disclosure | The body is a monolithic 583-line reference with no bundle files at all; per-platform API references that clearly belong in separate files are inlined, matching anchor 2. The 'Related Skills' section points to terra-auth, terra-connections, terra-data, and terra-webhooks, none of which exist in this bundle, making them dead pointers rather than well-signaled references. | 2 / 5 |
Total | 12 / 20 Passed |