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.

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 →

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 →

The form will ask:

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:

I have a question, not a Skill request

That’s fine too - open a regular issue at github.com/servosity/msp-skills/issues and skip the “skill-request” template. Or email a Build Session host directly via compoundingteams.com.


Last updated: 2026-05-28.