Community

Contribute in public

Diversio Engineering builds these tools in the open: 19 plugins, 21 plugin skills, and 5 pi packages, all reviewed through standard GitHub issues and pull requests.

19 Plugins
21 Plugin Skills
5 Pi Packages
PR Default contribution path
Get Involved

Where the work happens

Use GitHub for bugs, proposals, reviews, and contribution docs.

Repository

Source, catalog, and release history

Browse plugin and pi-package source, inspect manifests, and review recent changes directly in the repository.

Open GitHub → Issues

Bugs, proposals, and docs drift

Open issues when command behavior, install docs, or repo metadata drift from the actual codebase.

View issues → Pull Requests

Reviewable changes only

Skills, manifests, docs, and pi packages all flow through normal PR review. Keep changes scoped and version bumps synchronized.

Browse PRs → Contributor Guide

The repo’s working agreement

Use the contribution guide for plugin shape, pi-package rules, validation commands, and doc-sync expectations.

Read CONTRIBUTING.md →
Open Source

More from Diversio Engineering

Beyond Agentic Tools, we maintain a few other open source repos worth exploring.

MCP

clickup-mcp

Connect ClickUp tasks and workspace context to MCP-enabled tools.

DiversioTeam/clickup-mcp Open GitHub → MCP

gemini-cli-mcp

Expose Gemini CLI workflows through MCP for research and automation.

DiversioTeam/gemini-cli-mcp Open GitHub → Shared runtime

pi-cmux

Shared cmux utilities used in Pi-powered terminal workflows.

DiversioTeam/pi-cmux Open GitHub →
Contributors

People behind the work

5 contributors in repository history, excluding bots, with 279 authored commits represented here.

Workflow

How a good contribution moves

This repo is configuration-heavy, so a strong contribution is mostly about shape, sync, and guardrails.

01

Pick the right layer

Decide whether the change belongs in a skill, a Claude Code plugin wrapper/manifest, a pi package, or repo docs.

02

Edit the canonical files

Update SKILL.md first, keep wrappers thin, and sync plugin or package manifests with the user-facing docs.

03

Run local guardrails

Validate skill size, JSON, and pi-package command discovery before asking anyone else to review the change.

04

Open a clean PR

Use standard GitHub review, link the motivating issue when relevant, and keep the diff narrow enough to audit quickly.

Quality Gates

What to check before review

Most repeated failures in this repo are sync failures: versions, docs, wrappers, and package metadata drifting apart.

  • Version sync : Plugin changes should update both the plugin manifest and the top-level registry manifest in `.claude-plugin/marketplace.json`.
  • Wrapper coverage : Every changed Claude Code skill should still have at least one command wrapper.
  • Skill size budget : Changed SKILL.md files stay at or below 500 lines.
  • Doc accuracy : README, catalog, and distribution docs should stay aligned with install and invoke behavior.
  • Pi package checks : When a pi package changes, validate its package.json and smoke-test command discovery.
bash 
bash scripts/validate-skills.sh
jq -e . .claude-plugin/marketplace.json >/dev/null
jq -e . plugins/<plugin>/.claude-plugin/plugin.json >/dev/null
jq -e . pi-packages/<package>/package.json >/dev/null
Support

Questions, security issues, or unclear docs?

Route feedback to the channel that matches the problem so it can turn into docs, scripts, or CI instead of staying tribal knowledge.

General Help

tech@diversio.com

Use email when GitHub alone is not the right path.

Security

Security policy

Follow the security page for responsible disclosure instead of filing a public issue.

Read policy → Documentation

Authoring and distribution guide

The docs section explains directory shape, SKILL.md conventions, runtime distribution, and validation commands.

Open docs →