How to reuse prompts for troubleshooting for system administrators in 2026

Reuse troubleshooting prompts as a system administrator, with the steps to save, fill in and insert them, and what to check in tools that help.

By SupaKeeper · 2026-10-26

SupaKeeper is published by LunarWerx, which makes some of the tools compared here.

To reuse prompts for troubleshooting, save the ones that worked on a real fault, mark the parts that change from one case to the next, and insert them again when a similar problem comes up. Store them where the whole team can open them and check them against the systems they cover.

Option	What it does	What to check
Copilot AI Productivity Suite	Saves troubleshooting prompts as snippets and inserts them by typing a short command. ^[1]	Check whether a VS Code setup fits the machines and tools your team uses.
Shared team runbook	Keeps prompts in one shared place that people already read during incidents.	Check how quickly people can find and fill in the right prompt when a fault is live.
Saved-prompt feature in a tool you already use	Stores prompts inside a tool your team already opens every day.	Check which prompts it can insert and whether it can share them with teammates.

What you need before you start

Before you write any prompts down, have a list of the faults you handle most often, such as a service that will not start, a disk that fills up, or a login that fails for one user. For each one, note the first checks you run and the order you run them in.

Keep a short record of the server type, operating system and tool each prompt was written for, so a colleague knows when it applies. Gather one or two prompts that already helped during a real incident.

Remove any passwords, host names or customer details before you keep a prompt, so the set can be shared safely. Decide who will use the set, whether that is one person or the whole team, because that decides where the prompts are stored and how they are named.

Step by step

Pick one recurring fault and write down, in plain words, the prompt that helped the last time you faced it.
Mark each part that changes between cases, such as the service name, the error text or the server group, so you know what to fill in later.
Add the checks the prompt should ask for first, such as the log location and the last change made, so the answer points to something you can verify.
Test the prompt on a non-production system or on a copy of an old case, and compare the answer with what you already know is correct.
Name each prompt by the symptom people will search for, such as 'disk full on log volume', rather than by the tool that produced it.
Store the set in one place the whole team can open, and note the date each prompt was last checked.
Review the set after each major change to the systems it covers, and remove any prompt that no longer matches how those systems work.

A reused prompt is only as good as its last check, so the review step matters as much as the first write-up.

Tools that can do it

Copilot AI Productivity Suite is made by the team that publishes this site.

It is a VS Code extension that needs VS Code 1.116.0 or newer, and it is also on Open VSX for Cursor, Windsurf and VSCodium. ^[1] You install it from the VS Code Marketplace as LunarWerx.copilot-suite. ^[1] Its software is proprietary and confidential to LunarWerx. ^[1]

Typing #copilotsuite /snippet_id inserts the exact saved snippet template into the conversation. ^[1] Placeholders like ${name} or ${name:default} in a snippet ask you for a value when the snippet is inserted. ^[1] Snippets can sit in nested folders, and you can bundle several into a group that is referenced all at once. ^[1] You can select several snippets and move them, delete them or insert all their references at once. ^[1] You can pin up to five favorite snippets to the VS Code status bar. ^[1]

A bundled local server makes your snippets and groups available to Claude Code, Codex CLI and other tools that support MCP, a standard connection method. ^[1] If you turn it on, each snippet is also written out as a slash command file for Claude Code and Codex CLI, and the files stay in sync as you edit. ^[1]

You can export snippets as JSON or make a share link, and teammates can import it. ^[1] If you sign in with an account using an emailed one-time code, your snippets, groups and settings sync across your machines. ^[1] While VS Code telemetry is on, it sends anonymous usage statistics, but never snippet content. ^[1]

There is a Free plan at $0 that allows 20 Copilot insertions a week. ^[1] Premium costs $6.99 a month and has unlimited Copilot insertions. ^[1]

Other options to compare are a shared team runbook and any saved-prompt feature you already have in your tools. Check how each one inserts a prompt, fills in the details that change and shares it with teammates.

Common mistakes to avoid

Avoid storing prompts that contain passwords, host names or customer data, since anyone with access to the list can read them.

Avoid vague prompt names. A name like 'fix server' does not tell a colleague when to use the prompt during an incident.

Avoid running an old prompt on a system that has changed since it was written. Check the prompt's assumptions against the current setup first.

Avoid keeping only one person's copy of the set. When that person is busy or away, the team loses its working prompts.

Avoid assuming a sync or sharing setting applies on every machine. Check the setup on each machine you use for troubleshooting.

Frequently asked questions

How can system administrators reuse prompts for troubleshooting?

System administrators can reuse troubleshooting prompts by saving the ones that worked, marking the parts that change from one problem to the next, and inserting them again when a similar fault appears. A good prompt is one that a colleague could run on a different server and still get a clear, checkable result. Keep the wording plain, record which checks each prompt runs first, and review the set regularly so that old prompts do not send people down the wrong path.

What should be checked before choosing a tool to store troubleshooting prompts?

Check where the prompts will be used, which editors and machines need access, and whether teammates can find and fill in the right prompt during an incident. Also check how the tool handles sharing and whether it can insert prompts into the assistant your team already uses. Copilot AI Productivity Suite needs VS Code 1.116.0 or newer. ^[1] Confirm that your editor meets that requirement before you plan around it.

Does Copilot AI Productivity Suite make troubleshooting prompts available in Claude Code?

Copilot AI Productivity Suite includes a bundled local server that makes your snippets and groups available to Claude Code, Codex CLI and other tools that support MCP, a standard connection method. ^[1] If you turn on the slash command export, each snippet is also written out as a slash command file for Claude Code and Codex CLI, and the files stay in sync as you edit. ^[1] Check that this setup matches the tools your team runs.

Is Copilot AI Productivity Suite free to use for troubleshooting prompts?

There is a Free plan at $0 that allows 20 Copilot insertions a week. ^[1] Premium costs $6.99 a month and has unlimited Copilot insertions. ^[1] Before you choose a plan, count how often your team inserts prompts in a typical week, since the free limit applies to those insertions.

Can Copilot AI Productivity Suite share troubleshooting prompts with teammates?

You can export snippets as JSON or make a share link, and teammates can import it. ^[1] You can also select several snippets and move them, delete them or insert all their references at once. ^[1] If you sign in with an account using an emailed one-time code, your snippets, groups and settings sync across your machines. ^[1]

There is a Free plan at $0 that allows 20 Copilot insertions a week. ^[1]

Try Copilot AI Productivity Suite

Sources

Copilot AI Productivity Suite's own description of itself (the product of this site's publisher)