protocolsio-integration▌
davila7/claude-code-templates · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Protocols.io is a comprehensive platform for developing, sharing, and managing scientific protocols. This skill provides complete integration with the protocols.io API v3, enabling programmatic access to protocols, workspaces, discussions, file management, and collaboration features.
Protocols.io Integration
Overview
Protocols.io is a comprehensive platform for developing, sharing, and managing scientific protocols. This skill provides complete integration with the protocols.io API v3, enabling programmatic access to protocols, workspaces, discussions, file management, and collaboration features.
When to Use This Skill
Use this skill when working with protocols.io in any of the following scenarios:
- Protocol Discovery: Searching for existing protocols by keywords, DOI, or category
- Protocol Management: Creating, updating, or publishing scientific protocols
- Step Management: Adding, editing, or organizing protocol steps and procedures
- Collaborative Development: Working with team members on shared protocols
- Workspace Organization: Managing lab or institutional protocol repositories
- Discussion & Feedback: Adding or responding to protocol comments
- File Management: Uploading data files, images, or documents to protocols
- Experiment Tracking: Documenting protocol executions and results
- Data Export: Backing up or migrating protocol collections
- Integration Projects: Building tools that interact with protocols.io
Core Capabilities
This skill provides comprehensive guidance across five major capability areas:
1. Authentication & Access
Manage API authentication using access tokens and OAuth flows. Includes both client access tokens (for personal content) and OAuth tokens (for multi-user applications).
Key operations:
- Generate authorization links for OAuth flow
- Exchange authorization codes for access tokens
- Refresh expired tokens
- Manage rate limits and permissions
Reference: Read references/authentication.md for detailed authentication procedures, OAuth implementation, and security best practices.
2. Protocol Operations
Complete protocol lifecycle management from creation to publication.
Key operations:
- Search and discover protocols by keywords, filters, or DOI
- Retrieve detailed protocol information with all steps
- Create new protocols with metadata and tags
- Update protocol information and settings
- Manage protocol steps (create, update, delete, reorder)
- Handle protocol materials and reagents
- Publish protocols with DOI issuance
- Bookmark protocols for quick access
- Generate protocol PDFs
Reference: Read references/protocols_api.md for comprehensive protocol management guidance, including API endpoints, parameters, common workflows, and examples.
3. Discussions & Collaboration
Enable community engagement through comments and discussions.
Key operations:
- View protocol-level and step-level comments
- Create new comments and threaded replies
- Edit or delete your own comments
- Analyze discussion patterns and feedback
- Respond to user questions and issues
Reference: Read references/discussions.md for discussion management, comment threading, and collaboration workflows.
4. Workspace Management
Organize protocols within team workspaces with role-based permissions.
Key operations:
- List and access user workspaces
- Retrieve workspace details and member lists
- Request access or join workspaces
- List workspace-specific protocols
- Create protocols within workspaces
- Manage workspace permissions and collaboration
Reference: Read references/workspaces.md for workspace organization, permission management, and team collaboration patterns.
5. File Operations
Upload, organize, and manage files associated with protocols.
Key operations:
- Search workspace files and folders
- Upload files with metadata and tags
- Download files and verify uploads
- Organize files into folder hierarchies
- Update file metadata
- Delete and restore files
- Manage storage and organization
Reference: Read references/file_manager.md for file upload procedures, organization strategies, and storage management.
6. Additional Features
Supplementary functionality including profiles, notifications, and exports.
Key operations:
- Manage user profiles and settings
- Query recently published protocols
- Create and track experiment records
- Receive and manage notifications
- Export organization data for archival
Reference: Read references/additional_features.md for profile management, publication discovery, experiment tracking, and data export.
Getting Started
Step 1: Authentication Setup
Before using any protocols.io API functionality:
- Obtain an access token (CLIENT_ACCESS_TOKEN or OAUTH_ACCESS_TOKEN)
- Read
references/authentication.mdfor detailed authentication procedures - Store the token securely
- Include in all requests as:
Authorization: Bearer YOUR_TOKEN
Step 2: Identify Your Use Case
Determine which capability area addresses your needs:
- Working with protocols? → Read
references/protocols_api.md - Managing team protocols? → Read
references/workspaces.md - Handling comments/feedback? → Read
references/discussions.md - Uploading files/data? → Read
references/file_manager.md - Tracking experiments or profiles? → Read
references/additional_features.md
Step 3: Implement Integration
Follow the guidance in the relevant reference files:
- Each reference includes detailed endpoint documentation
- API parameters and request/response formats are specified
- Common use cases and workflows are provided with examples
- Best practices and error handling guidance included
Base URL and Request Format
All API requests use the base URL:
https://protocols.io/api/v3
All requests require the Authorization header:
Authorization: Bearer YOUR_ACCESS_TOKEN
Most endpoints support JSON request/response format with Content-Type: application/json.
Content Format Options
Many endpoints support a content_format parameter to control how protocol content is returned:
json: Draft.js JSON format (default)html: HTML formatmarkdown: Markdown format
Include as query parameter: ?content_format=html
Rate Limiting
Be aware of API rate limits:
- Standard endpoints: 100 requests per minute per user
- PDF endpoint: 5 requests/minute (signed-in), 3 requests/minute (unsigned)
Implement exponential backoff for rate limit errors (HTTP 429).
Common Workflows
Workflow 1: Import and Analyze Protocol
To analyze an existing protocol from protocols.io:
- Search: Use
GET /protocolswith keywords to find relevant protocols - Retrieve: Get full details with
GET /protocols/{protocol_id} - Extract: Parse steps, materials, and metadata for analysis
- Review discussions: Check
GET /protocols/{id}/commentsfor user feedback - Export: Generate PDF if needed for offline reference
Reference files: protocols_api.md, discussions.md
Workflow 2: Create and Publish Protocol
To create a new protocol and publish with DOI:
- Authenticate: Ensure you have valid access token (see
authentication.md) - Create: Use
POST /protocolswith title and description - Add steps: For each step, use
POST /protocols/{id}/steps - Add materials: Document reagents in step components
- Review: Verify all content is complete and accurate
- Publish: Issue DOI with
POST /protocols/{id}/publish
Reference files: protocols_api.md, authentication.md
Workflow 3: Collaborative Lab Workspace
To set up team protocol management:
- Create/join workspace: Access or request workspace membership (see
workspaces.md) - Organize structure: Create folder hierarchy for lab protocols (see
file_manager.md) - Create protocols: Use
POST /workspaces/{id}/protocolsfor team protocols - Upload files: Add experimental data and images
- Enable discussions: Team members can comment and provide feedback
- Track experiments: Document protocol executions with experiment records
Reference files: workspaces.md, file_manager.md, protocols_api.md, discussions.md, additional_features.md
Workflow 4: Experiment Documentation
To track protocol executions and results:
- Execute protocol: Perform protocol in laboratory
- Upload data: Use File Manager API to upload results (see
file_manager.md) - Create record: Document execution with
POST /protocols/{id}/runs - Link files: Reference uploaded data files in experiment record
- Note modifications: Document any protocol deviations or optimizations
- Analyze: Review multiple runs for reproducibility assessment
Reference files: additional_features.md, file_manager.md, protocols_api.md
Workflow 5: Protocol Discovery and Citation
To find and cite protocols in research:
- Search: Query published protocols with
GET /publications - Filter: Use category and keyword filters for relevant protocols
- Review: Read protocol details and community comments
- Bookmark: Save useful protocols with
POST /protocols/{id}/bookmarks - Cite: Use protocol DOI in publications (proper attribution)
- Export PDF: Generate formatted PDF for offline reference
Reference files: protocols_api.md, additional_features.md
Python Request Examples
Basic Protocol Search
import requests
token = "YOUR_ACCESS_TOKEN"
headers = {"Authorization": f"Bearer {token}"}
# Search for CRISPR protocols
response = requests.get(
"https://protocols.io/api/v3/protocols",
headers=headers,
params={
"filter": "public",
"key": "CRISPR",
"page_size": 10,
"content_format": "html"
}
)
protocols = response.json()
for protocol in protocols["items"]:
print(f"{protocol['title']} - {protocol['doi']}")
Create New Protocol
import requests
token = "YOUR_ACCESS_TOKEN"
headers = {
"Authorization": f"Bearer {token}",
"Content-Type": "application/json"
}
# Create protocol
data = {
"title": "CRISPR-Cas9 Gene Editing Protocol",
"description": "Comprehensive protocol for CRISPR gene editing",
"tags": ["CRISPR", "gene editing", "molecular biology"]
}
response = requests.post(
"https://protocols.io/api/v3/protocols",
headers=headers,
json=data
)
protocol_id = response.json()["item"]["id"]
print(f"Created protocol: {protocol_id}")
Upload File to Workspace
import requests
token = "YOUR_ACCESS_TOKEN"
headers = {"Authorization": f"Bearer {token}"}
# Upload file
with open("data.csv", "rb") as f:
files = {"file": f}
data = {
"folder_id": "root",
"description": "Experimental results",
"tags": "experiment,data,2025"
}
response = requests.post(
"https://protocols.io/api/v3/workspaces/12345/files/upload",
headers=headers,
files=files,
data=data
)
file_id = response.json()["item"]["id"]
print(f"Uploaded file: {file_id}")
Error Handling
Implement robust error handling for API requests:
how to use protocolsio-integrationHow to use protocolsio-integration on Cursor
AI-first code editor with Composer
1Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add protocolsio-integration
2Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
$npx skills add https://github.com/davila7/claude-code-templates --skill protocolsio-integrationThe skills CLI fetches protocolsio-integration from GitHub repository davila7/claude-code-templates and configures it for Cursor.
3Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
◆ Which agents do you want to install to?││ ── Universal (.agents/skills) ── always included ────│ • Amp│ • Antigravity│ • Cline│ • Codex│ ●Cursor(selected)│ • Cursor│ • Windsurf4Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/protocolsio-integrationReload or restart Cursor to activate protocolsio-integration. Access the skill through slash commands (e.g., /protocolsio-integration) or your agent's skill management interface.
⚠Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
Additional Resources
List & Monetize Your Skill
Submit your Claude Code skill and start earning
GET_STARTED →Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
✓Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
✓Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
✓Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
✓Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
general reviewsRatings
4.6★★★★★62 reviews- ★★★★★Emma Gonzalez· Dec 28, 2024
Registry listing for protocolsio-integration matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Alexander Martin· Dec 20, 2024
protocolsio-integration has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Emma Ramirez· Dec 12, 2024
protocolsio-integration is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Mei Srinivasan· Dec 12, 2024
protocolsio-integration reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Alexander Jackson· Dec 4, 2024
protocolsio-integration fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Rahul Santra· Nov 23, 2024
We added protocolsio-integration from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Lucas Thompson· Nov 19, 2024
Useful defaults in protocolsio-integration — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Tariq Thompson· Nov 11, 2024
We added protocolsio-integration from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★James Robinson· Nov 11, 2024
Keeps context tight: protocolsio-integration is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Mei Patel· Nov 3, 2024
Solid pick for teams standardizing on skills: protocolsio-integration is focused, and the summary matches what you get after install.
showing 1-10 of 62
1 / 7