SupaKeeper Plain comparisons of AI coding tools

How to organize prompts for support investigations

Learn how technical support specialists can organize reusable prompts for support investigations, what to prepare first, and which tools to compare.

By SupaKeeper ยท

SupaKeeper is published by LunarWerx, the makers of AgentHydra, Copilot AI Productivity Suite, Codex Forecast and Model Odds, which are compared here alongside other tools.

Keep each reusable prompt in one place, group the prompts an investigation needs together, and use a method you can search and insert from quickly during a live case.

OptionWhat it can doWhat to check
Copilot AI Productivity SuiteKeeps saved prompts in folders and groups, and asks for values in placeholders when they are inserted. [1] [1]Check whether your team works in VS Code or a VS Code-family editor, since the extension is built for those. [1]
Existing team documentationStores written prompts in the place your team already keeps notes.Check whether it can be searched quickly during a live investigation.
Shared document or wiki pageGives the team one place to edit prompts together.Check who can edit it and how customer details are kept out of it.
Separate prompt management toolKeeps prompts in a dedicated tool outside your editor.Check which features it offers for grouping and filling in prompts before choosing it.

What you need before you start

Before you organize prompts for support investigations, gather the prompts your team already uses. Include the questions you ask when collecting logs, the steps for narrowing down an issue, and the wording you send to customers when you need more details.

Decide which kinds of investigations the prompts will serve. A prompt for account access problems is different from one for application errors, so note the main case types you handle each week.

Have a clear sense of who will use the prompts. Some may belong to one specialist, while others should be shared across the support group. Knowing this shapes how you name and group them.

Check the tools your team already uses. Know where your current notes, documents or ticketing system store reusable text, and whether you can search it during an investigation. Also note any rules about customer data that the prompts must never include.

Set aside time to review the list before you move anything. Old prompts that no longer match your current products or steps create confusion later.

Step by step

  1. Collect every prompt you use during investigations, including the short ones you type from memory.
  1. Remove duplicates and any prompts that no longer match current products or procedures.
  1. Sort the remaining prompts by case type, such as login problems, slow performance or failed installs.
  1. Give each prompt a short name that says what it does and when to use it.
  1. Replace specific customer details with clear placeholders, such as the customer's name or the product version, so the same prompt works on the next case.
  1. Group prompts that are always used together, such as a set of checks for one kind of issue.
  1. Decide where the library will live and who is allowed to edit it.
  1. Test the library on a recent case by finding the prompts you would have needed, and note any gaps.
  1. Schedule a review each month or after a product change, and update names and groups as needed.

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]

Typing #copilotsuite and a saved prompt's short code into a conversation inserts that prompt's exact text. [1]

You can keep saved prompts in nested folders, and bundle several into a group that can be referenced all at once. [1]

Placeholders written as ${name} or ${name:default} ask you for a value each time the prompt is inserted. [1]

You can pin up to five favorite saved prompts to the VS Code status bar, the strip along the bottom of the window. [1]

Bulk actions let you select several saved prompts and move them, delete them or insert all their references at once. [1]

A bundled local server makes your saved prompts and groups available to Claude Code, Codex CLI and other tools that connect to it. [1]

If you turn on the slash command option, each saved prompt is written out as a slash command file for Claude Code and Codex CLI, and the files stay in sync as you edit. [1]

If you sign in with an account using a one-time code sent by email, your saved prompts, groups and settings sync across your machines. [1]

You can export saved prompts as JSON, a plain text data format, or create a share link, and teammates can import them. [1]

The Free plan costs $0 and allows 20 insertions a week. [1] Premium costs $6.99 a month and has unlimited insertions. [1]

While VS Code telemetry is turned on, the extension sends anonymous usage statistics but never snippet content. [1]

Other approaches include your team's existing documentation or ticketing system, a shared document or wiki page, or a separate prompt management tool. For each, check whether it can be searched during a live investigation, whether prompts can be grouped by case type, and how customer details are kept out of shared text. Compare each option against the job of organizing prompts for support investigations.

Common mistakes to avoid

Avoid putting customer names, account numbers or log excerpts directly into shared prompts. Use placeholders instead, so the prompt stays reusable and private details stay out of the library.

Avoid vague names such as 'check logs' or 'test 2'. A name should say what the prompt does and when to use it, or it will sit unused.

Avoid organizing prompts only by product or team. Grouping by case type, such as login problems or failed installs, matches how you search during an investigation.

Avoid moving every prompt at once. Start with the ones used most often, then add the rest after the first set works well.

Avoid skipping the review. Prompts that refer to old versions or retired steps can send a specialist down the wrong path.

Frequently asked questions

How do technical support specialists organize prompts for support investigations?

Start by collecting the prompts you already use, removing duplicates and outdated ones, and sorting the rest by case type. Give each prompt a name that says what it does, replace customer details with placeholders, and group prompts that are used together. Then choose a place where the library can be searched during a live case, and review it after each product change so the prompts keep matching current steps.

Does Copilot AI Productivity Suite cost money?

The Free plan costs $0 and allows 20 insertions a week. [1] Premium costs $6.99 a month and has unlimited insertions. [1] Before you choose, count how many prompts your team inserts in a typical week, since that count decides whether the Free plan's weekly limit is enough for the work.

Can Copilot AI Productivity Suite share prompts with teammates?

You can export saved prompts as JSON or create a share link, and teammates can import them. [1] You can also select several prompts at once and move, delete or insert them together. [1] Before sharing, review each prompt for customer names or other private details, so those do not reach people who should not see them.

Does Copilot AI Productivity Suite work with Claude Code?

A bundled local server makes saved prompts and groups available to Claude Code, Codex CLI and other tools that connect to it. [1] If you turn on the slash command option, each saved prompt is also written out as a slash command file for Claude Code and Codex CLI, and those files stay in sync as you edit. [1] Check which of these methods fits how your team already runs Claude Code before setting either one up.

Does Copilot AI Productivity Suite send usage statistics?

While VS Code telemetry is turned on, the extension sends anonymous usage statistics but never snippet content. [1] Telemetry is the automatic sending of usage data from software. Review that setting against your team's data rules before you rely on the extension for investigations that involve sensitive customer information.

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

Try Copilot AI Productivity Suite

Sources

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

Related comparisons