Content
71%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.
This is a dense, expert-level procedural skill: nearly every token encodes non-obvious repository-specific contracts (canonical pairs, metadata-based hashing, content deferral, retry budgets) and it ends with a strong verification checklist. Its weaknesses are structural — a monolithic single-file layout where selector tables and worked pattern examples belong in reference files — plus a duplicated section, and the absence of an explicit post-implementation validate-and-fix loop.
Suggestions
Move the 'Available selector keys' table and the two canonical-pair worked examples into a references/ file (e.g. references/selectors.md), keeping a brief rule summary in SKILL.md with a clearly signaled link.
Remove the duplicate 'Reference Implementations' section (lines 383-388 vs 496-502) by merging them into the single list near the end.
Add an explicit verification step after registration (e.g. run validateConfig, typecheck/build, and confirm the connector appears in the modal), with a fix-and-retry loop before declaring the task complete.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Almost all content is non-obvious, repo-specific knowledge (canonical pairs, contentDeferred invariant, metadata-hash strategy, fetchWithRetry budgets) rather than concepts Claude already knows. However, at ~525 lines it has trimmable material: two full canonical-pair worked examples (Airtable and Jira), a 16-row selector table, and a duplicated 'Reference Implementations' section (lines 383-388 and 496-502). | 4 / 5 |
Actionability | Concrete TypeScript templates with real imports, exact file paths, hash-format patterns, and a one-line registry wiring snippet, plus five named reference implementations to copy from. Minor gaps: connector method bodies are comment stubs, the API-key example elides configFields (/* ... */), and no complete pagination-loop example is shown, so it is not fully copy-paste ready. | 4 / 5 |
Workflow Clarity | A clear four-step sequence up front (read API docs, determine auth, create config, register), an explicit 'Sync Engine Behavior (Do Not Modify)' boundary section, and a comprehensive final checklist provide most checkpoints. Not 5 because there is no explicit post-implementation verification feedback loop (build/test/fix-and-retry) and validateConfig guidance lacks an error-recovery path. | 4 / 5 |
Progressive Disclosure | Sections are well-organized and point to real codebase files (connectors/types.ts, hooks/selectors/registry.ts, reference implementations), but the skill is a single ~525-line monolith with no bundle files. The selector-key table and the canonical-pair pattern examples clearly belong in references/ files the body could point to, matching the anchor where content that should be separate is inline. | 3 / 5 |
Total | 15 / 20 Passed |