putio/sdk-dev
Develop or review put.io SDK repositories, API clients, and client libraries across TypeScript, Swift, Kotlin, and similar packages. Use when adding or changing namespaces, tightening request or error types, aligning SDK behavior with backend and app usage, updating SDK verification flows, or checking how an SDK repo should be documented and released.
75
94%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope around put.io SDK development and review. It provides concrete actions, natural trigger terms across multiple languages and activities, and an explicit 'Use when...' clause with well-defined scenarios. The specificity of the product (put.io) and domain (SDK/API client development) make it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: developing/reviewing SDK repositories, adding/changing namespaces, tightening request/error types, aligning SDK behavior with backend, updating verification flows, and handling documentation/release processes. | 3 / 3 |
Completeness | Clearly answers both 'what' (develop or review put.io SDK repositories, API clients, and client libraries) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios like adding namespaces, tightening types, aligning SDK behavior, updating verification flows, and checking documentation/release. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'SDK', 'API clients', 'client libraries', 'TypeScript', 'Swift', 'Kotlin', 'namespaces', 'request types', 'error types', 'put.io', 'verification flows', 'documented and released'. Good coverage of terms a developer working on SDK repos would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product scope (put.io), the specific languages listed, and the narrow domain of SDK development. Very unlikely to conflict with other skills given the combination of product name and SDK-specific activities. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured SDK development skill with strong actionability and workflow clarity. The endpoint change recipe and verification sections provide concrete, executable guidance with proper validation checkpoints. Minor verbosity in some sections (Source of Truth, Verification) prevents a top conciseness score, but overall the content is effective and well-organized.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient and avoids explaining basic concepts, but some sections are somewhat verbose—e.g., the 'Source Of Truth Order' paragraph and the 'Verification' section repeat ideas that could be tightened. The 'Quick Rules' section is lean and effective, but overall there's room to trim. | 2 / 3 |
Actionability | The skill provides concrete, executable commands (rg searches, verify commands, gradlew), a specific step-by-step endpoint change recipe with exact ordering, and clear bash examples. The guidance is specific enough to be directly followed rather than interpreted. | 3 / 3 |
Workflow Clarity | The Main Workflow is clearly sequenced with 8 explicit steps including validation (step 7: run canonical verify and fix failures before continuing). The Endpoint Change Recipe provides a traceable, ordered process. The Verification section includes feedback loops for missing test layers. Guardrails provide explicit constraints on destructive operations. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled references to three bundled files (sdk-vision.md, patterns.md, language-notes.md), each with a brief description of what to find there. The 'Start Here' section explicitly tells the reader to 'read only what you need' with clear pointers. References are one level deep and clearly organized. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents