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 the platform (protocols.io), lists specific capabilities (search, create, update, publish, manage steps/materials, handle discussions, organize workspaces, upload files), and provides explicit trigger guidance for when to use it. The description covers both the 'what' and 'when' thoroughly, and the domain-specific terminology makes it highly distinctive from other skills.
| 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...'). Explicit trigger guidance is present. | 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 | Highly distinctive due to the specific platform (protocols.io) and domain (scientific protocols, lab protocol management). Very unlikely to conflict with other skills given the narrow, well-defined niche. | 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.
This skill provides good actionable content with executable Python examples and clear API integration patterns, but is severely bloated with unnecessary explanations, generic best practices, and content that should be delegated to reference files. The workflows are well-structured but lack validation checkpoints and error recovery loops. The progressive disclosure structure is partially effective but undermined by the excessive inline content.
Suggestions
Cut the 'When to Use This Skill' section entirely and reduce 'Core Capabilities' to a brief table mapping tasks to reference files - Claude can infer when to use this skill from context.
Move Python code examples, error handling, troubleshooting, and best practices into a reference file (e.g., references/examples.md) to keep the main skill lean.
Add explicit validation checkpoints to workflows, e.g., after creating a protocol, verify the response contains the expected ID; after publishing, confirm DOI was issued by checking the response.
Remove generic best practices (items 1-4, 6, 8-10) that Claude already knows and keep only protocols.io-specific guidance.
| 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. Concrete API endpoints and parameters are given throughout. | 3 / 3 |
Workflow Clarity | Five workflows are clearly sequenced with numbered steps and reference file pointers, but they lack explicit validation checkpoints. For example, the 'Create and Publish Protocol' workflow says 'Review: Verify all content is complete' but doesn't specify how to validate, and there are no error recovery feedback loops within the workflows themselves. The error handling code is separate from the workflows. | 2 / 3 |
Progressive Disclosure | Good use of reference files with clear one-level-deep pointers to 6 reference documents, and a helpful decision tree in 'Step 2: Identify Your Use Case'. 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 be in separate files). The overview doesn't stay lean enough. | 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
25e1c0f
- 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.