Prompts

Refining the "Ask" Function: GPT Prompts

In the InSkill ecosystem, Prompts act as the "house rules" for the GPT engine. While the Ask function pulls information from your manuals, the Prompt configuration dictates exactly how that information is processed, formatted, and delivered to the user.

Think of a prompt as a persistent set of instructions that the AI follows during every interaction within that specific copilot.

What Can a Prompt Control?

A well-crafted prompt gives you granular control over the AI's output. You can use the "Prompt" field to:

Enforce Formatting: Request that all technical data be presented in tables or bulleted lists.
Standardize Units: Ensure all measurements are automatically displayed in a specific unit (e.g., "Always display torque in Newton-meters").
Filter Content: Explicitly exclude outdated procedures or irrelevant model variations.
Highlight Priorities: Instruct the AI to always lead with safety warnings when discussing high-voltage components.

Guidelines for High-Performance Prompts

To get the most out of the GPT engine, follow these "Pro-Tips" for prompt engineering:

Principle	Advice	Example
Density Over Length	Be descriptive but concise. Avoid "fluff" words.	Instead of "Please try to show the user the part number," use "Always lead with Part Number."
Use Strict Language	Use absolute terms like "Always" or "Never." Avoid "maybe" or "if possible," which create logic gaps.	"Never recommend a restart before a hard reset."
Markdown is King	GPT understands Markdown natively. Use it to specify output styles.	"Format all specs in a Markdown table."
Direct Syntax	Use logical operators like `=` or `->` to define relationships.	"Model X = High Voltage; Model Y = Low Voltage."

What to Avoid (The "Noise" Filter)

Because InSkill already handles the foundational context of your copilot, you should skip the following to save space and prevent logic confusion:

Persona Building: Do not include "You are an AI assistant" or "You are a technician." The system already defines the agent's role.
Product Redundancy: Do not include "The product is a [Model Name]." If the copilot is already tied to that product, repeating it only wastes processing power.
Politeness: While being nice is great for humans, words like "please" and "thank you" are ignored by the engine. Stick to direct commands.

Pro Tip: If you find yourself writing a prompt longer than a paragraph, consider whether that information should actually be a Variable or an Asset Definition instead. Prompts are for behavior; Variables are for data.