Contribution Guide
Build and publish AI-powered clinical Skills and MCP Servers to the Medisolv platform. Open to Medisolv teams and approved partner contributors.
How It Works
Fork & Clone the Registry
Start by forking the Medisolv Skills Registry on GitHub. Clone your fork locally and install dependencies with your package manager of choice.
git clone https://github.com/your-org/medisolv-registry cd medisolv-registry npm install
Scaffold Your Contribution
Use the Auggie CLI to scaffold a new Skill or MCP Server. This generates the required directory structure, manifest, and test harness.
# For a Skill auggie scaffold skill @your-org/skill-name # For an MCP Server auggie scaffold mcp @your-org/server-name
Implement & Test
Implement your tool definition, add unit tests, and run the full compliance test suite. All contributions must pass HIPAA-safe data handling checks before review.
auggie test --compliance auggie lint
Open a Pull Request
Push your branch and open a PR against the main registry repository. Fill out the PR template in full — incomplete submissions will be returned.
git push origin feat/your-skill-name
Requirements
HIPAA Compliance
No PHI may be logged, stored, or transmitted outside the defined API boundary.
Manifest Required
Every contribution needs a valid skill.json or mcp.json manifest with all required fields.
Test Coverage ≥ 80%
Unit tests must cover all tool inputs, error states, and edge cases.
Security Review
Submissions undergo an automated security scan and manual review for data handling issues.
Maintainer Commitment
Contributors agree to triage issues and ship patch releases within 30 days of a critical bug report.
Tool Schema
Must include a valid Anthropic-compatible JSON tool definition with input_schema and description.
Review Process
Automated Checks
Lint, compliance scan, and test suite run immediately on PR open. Failures block review.
Security Review
A member of the Medisolv Security team audits data handling within 5 business days.
Clinical Review
For Skills touching patient data, a clinician on the platform team validates use-case accuracy.
Publication
Approved PRs are merged and the package is published to the registry within 24 hours.
Have questions?
Reach out to the platform team on Slack at #medisolv-dev or open a discussion on GitHub.