Docs

---
layout: default
title: "Request a new MSP connector - 90 seconds, no terminal | MSP Skills"
description: "Don't see your PSA, RMM, backup, or M365 tool yet? Request a new MSP Skills connector in about 90 seconds - no code, no terminal, just a web form. The fastest way to move a system up the roadmap and get it co-built live in a free Build Session."
permalink: /requesting-a-skill/
---

# How to request a new MSP Skill (90 seconds, no terminal)

You don't see your PSA, RMM, backup, or M365 tool listed yet? Tell us. This is the fastest way to move a system up the roadmap and to get it co-built live in a Build Session.

No code experience required. No terminal. No GitHub-fu. If you can fill in a web form, you can do this.

## No GitHub account?

You don't need one. **[Use the plain web form instead →](/request-or-report/)** It takes about a minute, a person reads it, and we file the public issue for you. That page also covers the other direction: telling us a connector already worked against your tenant. The rest of this page is the GitHub route.

## What "filing an issue" actually means

A GitHub "issue" is just a public note on the project. Anyone can read it, anyone can vote (👍) it. We use the votes to rank what to build next. Filing one takes about a minute.

## Step 1 - Make sure you have a GitHub account

If you've never used GitHub, you'll need a free account. **[Sign up at github.com →](https://github.com/signup)**

You can use any email. There's nothing to install - it's just a website login. (If you'd rather a teammate file the issue for you, that works too; the votes count the same.)

## Step 2 - Open the request form

**[Click here to open the skill-request form →](https://github.com/servosity/msp-skills/issues/new?template=skill-request.yml)**

The form will ask:

- **System / vendor name** (the product you want a Skill for - e.g. "Autotask", "NinjaOne", "Datto BCDR")
- **Category** (PSA, RMM, Backup, Security, M365, Other)
- **One question you'd ask the AI** if this Skill existed (e.g. "Which clients have open tickets older than 30 days?")
- **Link to the vendor's API docs**, if you know it - or just write "I don't know," that's fine
- **MSP size** (number of techs / clients) - helps us prioritize
- **Would you join a Build Session for this?** - yes/no

That's it. Click **Submit new issue** at the bottom.

## Step 3 - What happens next

1. **You'll see your issue on the public list.** Other MSPs can vote on it.
2. **We comment within a few days** with one of three responses:
   - "Already on the roadmap - here's the ETA."
   - "We need more votes - share with one MSP friend who'd want this."
   - "Bring it to next Thursday's Build Session and we'll co-build it live."
3. **If it gets enough demand**, it goes into the queue. The Servosity skill in this repo got built that way.

## Step 4 - Boost the signal (optional)

If you want this Skill built faster:

- **Vote on related issues** with the 👍 reaction at the top of any issue (not a comment - the 👍 above the title). Issues with more 👍s move up.
- **Share the issue URL** with one MSP friend who'd want the same Skill. One additional vote moves your issue notably up the list.
- **Join a Build Session** at [compoundingteams.com/build-sessions](https://compoundingteams.com/build-sessions) - bring your tenant, your questions, and we co-build with the cohort.

## I have a question, not a Skill request

That's fine too - open a regular issue at [github.com/servosity/msp-skills/issues](https://github.com/servosity/msp-skills/issues) and skip the "skill-request" template. Or email a Build Session host directly via [compoundingteams.com](https://compoundingteams.com).

---

_Last updated: 2026-05-28._