protocolsio-integration
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
82
75%
Does it follow best practices?
Impact
97%
1.56xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./scientific-skills/protocolsio-integration/SKILL.mdQuality
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 identifies its domain (protocols.io API integration), lists comprehensive concrete actions, and provides explicit guidance on when to use it. The description covers both the 'what' and 'when' thoroughly, includes natural trigger terms spanning protocol management, scientific documentation, and collaboration, and occupies a very distinct niche that minimizes conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: search, create, update, publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files. These are clearly defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (integration with protocols.io API for managing scientific protocols, with specific actions listed) and 'when' ('should be used when working with protocols.io to search, create, update...' and 'Applicable for protocol discovery, collaborative protocol development...'). Has explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'protocols.io', 'scientific protocols', 'protocol steps', 'materials', 'workspaces', 'lab protocol management', 'experiment tracking', 'scientific documentation', 'collaborative protocol development'. Good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche targeting protocols.io specifically. The combination of 'protocols.io', 'scientific protocols', 'lab protocol management', and API-specific actions makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides good actionable code examples and a well-structured reference file system, but is severely undermined by verbosity. It explains too many things Claude already knows (what protocols.io is, generic best practices, when to use the skill), and includes substantial inline content that belongs in reference files. The workflows are reasonable but lack validation checkpoints for operations like publishing protocols with DOIs.
Suggestions
Cut the 'When to Use This Skill' section entirely and reduce the 'Overview' to 1-2 sentences - Claude can infer applicability from the content itself.
Move the Python code examples, error handling code, troubleshooting section, and best practices into a reference file (e.g., references/examples.md) to keep the main skill lean.
Remove the 'Best Practices' list of 10 generic software engineering tips - items like 'store tokens securely' and 'validate input before API calls' are things Claude already knows.
Add explicit validation checkpoints to workflows, especially 'Create and Publish Protocol' - e.g., verify step count, check for required metadata, and confirm draft status before publishing with DOI.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive sections that explain obvious concepts (e.g., 'When to Use This Skill' lists 10 scenarios, 'Best Practices' lists 10 generic software engineering tips Claude already knows). The 'Overview' explains what protocols.io is, and the 'Core Capabilities' section repeats information that's already in the reference files. Much of this content could be cut by 60-70% without losing actionable information. | 1 / 3 |
Actionability | Provides fully executable Python code examples for protocol search, creation, file upload, and error handling with retry logic. The code is copy-paste ready with proper imports, headers, and API endpoints specified. | 3 / 3 |
Workflow Clarity | Five workflows are clearly sequenced with numbered steps and reference file pointers, but they lack explicit validation checkpoints and error recovery loops. For example, the 'Create and Publish Protocol' workflow says 'Review: Verify all content is complete' but doesn't specify how to validate, and there's no feedback loop for fixing issues before publishing. | 2 / 3 |
Progressive Disclosure | Good use of reference files with clear one-level-deep pointers to 6 reference documents, and a helpful routing table in Step 2. However, the main SKILL.md is far too long with inline content that should be in reference files (e.g., the full Python examples, error handling code, troubleshooting section, and best practices could all be in references), undermining the progressive disclosure pattern. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
- Repository
- K-Dense-AI/claude-scientific-skills
- Commit
b58ad7e
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.