protocolsio-integration

Read, validate, and safely export protocols.io data with current official REST/MCP contracts, or create 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

92%

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.

The content is highly actionable and well-structured with strong validation checkpoints and clean progressive disclosure into the reference bundle. The only restraint is mild repetition of safety constraints across sections that slightly tempers conciseness.

Suggestions

Consolidate the recurring --execute / official-host / untrusted-content safety rules into the Operating Contract and reference it from workflow sections rather than restating each rule inline.

Move the 'Supported plan-only operations' paragraph so the 5-step confirmation checklist immediately follows its 'Re-run with --confirm only after:' lead-in, removing the current sequence break.

Consider moving the 'Do not restore the old patterns' deprecation note and the 2026-07-23 refresh date into a dedicated 'Deprecated patterns / source ledger' section to keep the API map focused.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence (no explanations of REST/OAuth/JSON), but safety constraints such as the --execute gate and official-host rules recur across sections and could be consolidated, keeping it just below the lean score-5 anchor.	4 / 5
Actionability	Copy-paste-ready commands with real flags and arguments cover the common cases — `protocols_read.py list/get/export-pdf`, `validate_auth_config.py`, `pagination_helper.py`, `validate_protocol_json.py`, `plan_write_request.py` — alongside an exact endpoint map.	5 / 5
Workflow Clarity	Multi-step processes are clearly sequenced with explicit validation checkpoints: the offline-first operating contract, the bounds-review-before-execute read flow, and the 5-step mutation confirmation checklist, plus retry guidance for 429/5xx as a feedback loop.	5 / 5
Progressive Disclosure	SKILL.md is a clear overview with well-signaled one-level-deep references — the References section links all six reference files with descriptions, inline links to authentication.md and the schema asset are present, and all referenced bundle files exist on disk.	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: it states concrete capabilities, gives an explicit use-when clause scoped to protocols.io, and is highly distinct. The only minor gap is trigger-term breadth, since the niche domain has few synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Read, validate, and safely export protocols.io data', 'create non-executing mutation plans', 'bounded official-host GET requests only with explicit --execute' — giving comprehensive coverage of the skill's capabilities, matching the score-5 anchor.	5 / 5
Completeness	Explicitly states both what ('Read, validate, and safely export protocols.io data ... or create non-executing mutation plans') and when ('Use only for tasks explicitly targeting protocols.io or an exact protocols.io protocol version') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good keyword coverage with the natural term 'protocols.io' plus 'protocol version' and 'export', but the narrow domain offers few synonyms and no file-extension variants, so a few natural terms are missing relative to the score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	A clear niche (protocols.io integration) with distinct triggers and an explicit scope limit ('Use only for tasks explicitly targeting protocols.io'), giving minimal conflict risk with other skills.	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: 9e8b0cb

Reviewed: 2 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.