A small, growing library of Claude Code skills used at eTop Technology to run an MSP. Published so other MSPs (and curious peers) can lift, fork, or argue with our patterns.
| Skill | What it does |
|---|---|
news |
Pulls a fresh AI + cybersecurity news digest from across the web — model releases, CVEs, practical AI how-to, MSP-relevant vendor news — and tags items for relevance to your stack. Invoke with /news (supports today/week/month/ai/cyber/msp/howto). |
service-manager |
Daily / weekly / monthly / quarterly cadence for running a service desk as a non-technical operator. CFO / Integrator-friendly. |
technical-architect |
Runs a ticket through Claude and returns a structured good / bad / next review with documentation, vendor-doc, and prior-ticket context. Designed so a non-technical operator can carry Tier 3 reviews without bottlenecking senior techs. |
A lot of MSP "ops content" is paywalled coaching, conference slides, or LinkedIn posturing. We figured the actual playbooks — the ones we run on Tuesday mornings — would be more useful in the open.
These are the eTop versions, lightly generalized. Where we name a vendor or rule, that's because we've actually been burned by it. Steal the structure; replace the specifics with yours.
Skills are markdown files with frontmatter. Two ways to use them:
- Drop into Claude Code: copy a
SKILL.mdinto~/.claude/skills/<skill-name>/SKILL.md(user-level) or.claude/skills/<skill-name>/SKILL.md(project-level). Claude Code auto-discovers it. - Read as a doc: they read fine on GitHub. The methodology is the value; the Claude integration is the icing.
Invoke from inside Claude Code with /skill <skill-name> or just describe what you want — the description in the frontmatter is the trigger.
eTop Technology is an MSP. We run on ConnectWise Manage, Hudu, Microsoft 365, and a stack we've curated over years of "that one didn't work, try the other." We use Claude Code heavily across service delivery, sales, and back-office ops.
If any of these patterns spark ideas, or you want to compare notes on running an MSP with AI in the loop, we're hiring conversations welcome.
MIT — use them, modify them, ship them. Attribution appreciated, not required.