protocolsio-integration

Reads, validates, and safely exports protocols.io data with current official REST/MCP contracts, or creates non-executing mutation plans. The bundled client makes bounded official-host GET requests only with explicit --execute. Use only for tasks explicitly targeting protocols.io or an exact protocols.io protocol version.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%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.

Highly actionable, security-conscious content with concrete executable commands, explicit validation gates, and well-organized one-level-deep references. The only cost is minor verbosity — repeated provenance dates and citation boilerplate — that slightly inflates token usage without adding guidance.

Dimension	Reasoning	Score
Conciseness	The body is dense with non-obvious operational constraints and explains nothing Claude already knows; deprecated endpoints are correctly quarantined in a 'Do not restore the old patterns…' callout per the time-sensitivity guideline. Minor trimming opportunities remain: the 2026-09-30 review date is stated three times and the citation section carries boilerplate fetch instructions, keeping it just below the leanest anchor.	4 / 5
Actionability	Fully executable, copy-paste-ready commands with real flags cover the common cases: validate auth ('validate_auth_config.py --require read'), read ('protocols_read.py list --query …', '--execute … --page-size 10 --max-pages 2 --max-items 20'), pagination validation, JSON validation, and mutation planning ('plan_write_request.py --operation update-protocol --target … --payload …'), plus a concrete endpoint map.	5 / 5
Workflow Clarity	Multi-step workflows are clearly sequenced with explicit validation checkpoints: plan-before-execute gating, a numbered 10-point operating contract, a 5-step mutation re-confirmation checklist (snapshot, comparison, token-scope check, irreversibility review, fresh human confirmation), and bounded retry rules for error recovery.	5 / 5
Progressive Disclosure	Clear sectioned overview with well-signaled one-level-deep references; all six referenced files, the asset schema, and the scripts exist, each reference has a content description, and bulk API detail is appropriately split into references/ rather than inlined.	5 / 5
	Total	19 / 20 Passed

Description

92%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 description: concrete third-person action verbs, an explicit 'Use only for' scope restriction, and a distinct niche. The only weakness is slightly jargon-leaning keyword coverage that misses a few natural user phrasings.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete third-person actions — 'Reads, validates, and safely exports protocols.io data', 'creates non-executing mutation plans', 'makes bounded official-host GET requests only with explicit --execute' — covering the skill's function comprehensively with no real gaps.	5 / 5
Completeness	It explicitly answers both what (read, validate, export, create non-executing mutation plans) and when ('Use only for tasks explicitly targeting protocols.io or an exact protocols.io protocol version') with a concrete trigger clause.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('protocols.io', 'protocol version', 'export', 'mutation plans', 'REST/MCP') that a user targeting this service would say, but a few natural variations such as 'search protocols', 'DOI', or 'protocol PDF' are missing, so it falls just short of the comprehensive-synonyms anchor.	4 / 5
Distinctiveness Conflict Risk	Clear niche (protocols.io integration) with a self-restricting trigger clause; the domain-specific naming makes conflict with other skills minimal.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: K-Dense-AI/scientific-agent-skills
Path: skills/protocolsio-integration/SKILL.md
Commit: 1549884

Reviewed: 4 days 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.