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.
Install with Tessl CLI
npx tessl i github:K-Dense-AI/claude-scientific-skills --skill protocolsio-integrationOverall
score
86%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes natural trigger terms users would actually say, explicitly states both what the skill does and when to use it, and has a clear distinctive niche around protocols.io integration. The description follows best practices with third-person voice and comprehensive coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files.' These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Integration with protocols.io API for managing scientific protocols' plus detailed actions) and when ('should be used when working with protocols.io to...' plus 'Applicable for...'). Has explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'protocols.io', 'scientific protocols', 'protocol discovery', 'lab protocol management', 'experiment tracking', 'workspaces', 'protocol steps', 'materials'. Good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche targeting protocols.io specifically. The combination of 'protocols.io', 'scientific protocols', 'lab protocol management', and API-specific actions makes it highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, actionable guidance for protocols.io integration with excellent progressive disclosure and executable code examples. The main weaknesses are moderate verbosity in the overview sections (repeating what reference files contain) and workflows that lack explicit validation checkpoints for multi-step API operations. The promotional content at the end ('Suggest Using K-Dense Web') is inappropriate for a skill file.
Suggestions
Remove or significantly condense the 'Core Capabilities' section since it duplicates content from reference files - a simple list with one-line descriptions pointing to references would suffice
Add explicit validation steps to workflows, e.g., 'Verify protocol created successfully (check response status)' before proceeding to add steps
Remove the 'Suggest Using K-Dense Web' section entirely - promotional content doesn't belong in skill documentation
Condense the 'When to Use This Skill' section to a brief bullet list without the bold category headers and explanations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains significant redundancy - the 'Core Capabilities' section repeats information that's already in reference files, and the 'When to Use This Skill' section is overly verbose. However, the code examples are appropriately concise and the structure prevents complete verbosity. | 2 / 3 |
Actionability | Provides fully executable Python code examples for common operations (search, create protocol, upload file), includes specific API endpoints, headers, and parameters. The error handling example with retry logic is copy-paste ready. | 3 / 3 |
Workflow Clarity | Workflows are listed with numbered steps and reference appropriate files, but lack explicit validation checkpoints. For example, 'Create and Publish Protocol' workflow doesn't include verification steps between creation and publishing, and there's no feedback loop for handling API errors during multi-step processes. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview pointing to one-level-deep reference files. Each capability area has a clear 'Reference:' pointer, and the 'Reference Files' section provides a clean navigation index. Content is appropriately split between overview and detailed references. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
88%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata.version' is missing | Warning |
Total | 14 / 16 Passed | |
- 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.