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.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./backend/cli/skills/biology/protocolsio-integration/SKILL.md

The canonical home for this skill is protocolsio-integration in K-Dense-AI/scientific-agent-skills

Quality

Content

53%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is well-structured for progressive disclosure and offers concrete executable examples, but it is notably verbose with redundant restatements of capabilities and reference pointers, and its workflows lack explicit validation checkpoints for destructive and batch operations.

Suggestions

Collapse the duplicated capability/reference listings across 'When to Use', 'Core Capabilities', 'Getting Started', and 'Reference Files' into a single canonical map to cut hundreds of redundant tokens.

Add explicit validation/verification checkpoints to destructive and batch workflows (e.g., verify protocol completeness before 'POST /protocols/{id}/publish'; confirm upload checksums before linking files; verify deletion intent before delete/restore).

Trim restated rate-limit and authentication guidance to a single authoritative section and reference it once, removing the repetitions in 'Base URL', 'Rate Limiting', 'Getting Started', and 'Troubleshooting'.

Dimension	Reasoning	Score
Conciseness	The 400-line body is noticeably verbose and padded: it restates capability lists across 'When to Use', 'Core Capabilities', 'Getting Started', 'Common Workflows', and 'Reference Files' sections with heavy repetition of the same reference pointers, and reiterates rate-limit/auth guidance multiple times.	2 / 5
Actionability	Provides several concrete, copy-paste-ready Python examples (protocol search, create, file upload, retry-with-backoff) plus explicit endpoints, base URL, headers, and parameters, with only minor gaps around response/error shape details.	4 / 5
Workflow Clarity	Five workflows are clearly sequenced and reference the right files, but several involve destructive/batch operations (publish with DOI, delete/restore files, workspace permission changes) with no explicit validation or verification checkpoints, which caps the score at 3 per the rubric.	3 / 5
Progressive Disclosure	Good one-level-deep structure: the body is an overview pointing to six real reference files (all present in references/) that are consistently signaled and organized by capability area, with only minor inlining/repetition gaps.	4 / 5
	Total	13 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-rounded description that concretely enumerates capabilities and provides explicit 'use when' trigger guidance tied to the protocols.io domain. Minor gains are possible from tighter, more natural synonyms and explicit file/extension cues.

Suggestions

Add natural synonyms and concrete file/extension cues users might say (e.g., '.protocols', protocols.io URL, DOI, protocol JSON) to broaden trigger coverage.

Tighten the 'Applicable for...' list to a few high-signal scenarios to reduce mild verbosity while preserving triggers.

Confirm all listed actions map to genuinely distinct capabilities to avoid overlap phrasing with generic documentation skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files') covering the domain well, though a few are phrased at a moderate level of abstraction rather than as crisp discrete operations.	4 / 5
Completeness	Explicitly answers both 'what' (integration with protocols.io API for the listed operations) and 'when' via a clear 'This skill should be used when working with protocols.io to...' trigger clause plus an 'Applicable for...' list of concrete scenarios.	5 / 5
Trigger Term Quality	Strong natural terms ('protocol discovery', 'experiment tracking', 'lab protocol management', 'scientific documentation') that users would plausibly say, though it leans slightly on domain phrasing and lacks a few common synonyms or file/extension markers.	4 / 5
Distinctiveness Conflict Risk	The protocols.io niche is clearly delimited with domain-specific triggers (protocol discovery, lab protocol management), giving low conflict risk with only minor overlap against generic biology or documentation skills.	4 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: synthetic-sciences/openscience
Path: backend/cli/skills/biology/protocolsio-integration/SKILL.md
Commit: 3a6c3a9

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.