As an admin you can create global skills that your entire team can access. You manage these global skills in the settings section of Endgame.
Access your skills in settings
Navigate to https://app.endgame.io/settings/skills

Add a Skill
Click “Add Skill” (top right of the list) -> Write a Skill or Upload a Skill to add a new skill
Write a basic skill: Choose Write a Skill and fill out the skill form, tips below.Anatomy of a Skill:
Remember, any change you make to a skill in settings such as creating,
editing, or deleting applies to your entire organization.

-
Title: The title of your skill, displayed on the skill card.
Example:
Demo Follow-Up -
Description: Used under the hood to determine when your skill is applicable. The AI references this to decide if the skill should be used when generating a response.
Example:
Generates a post-demo follow-up email that thanks the prospect, recaps their key pain points, and outlines a clear next step. -
Example Prompt: The prompt that pre-populates in the chat input when this skill is selected from the skill grid.
Example:
Use the Demo Follow-up skill to write a follow-up email for the demo I just completed. -
Context: The actual instructions that define what your skill does and how it should output content — this is where the real customization lives.
Example:
Write a concise follow-up email after a sales demo. Open by thanking the prospect for their time. Summarize the 2–3 pain points they mentioned during the call. Close with a single, specific next step (e.g., a follow-up call, trial, or proposal). Keep the tone warm but professional. Do not use filler phrases like "Hope this email finds you well."
SKILL.md file in addition to other optional material that will be used to execute your skill. This is often example or template files to inform the output of your skill and other assets like company logos.Skill folders generally contain:- SKILL.md (required): Instructions in Markdown - MUST contain a
nameanddescriptionfield - scripts/ (optional): Executable code (Python, Bash, etc.)
- references/ (optional): Documentation loaded as needed
- assets/ (optional): Templates, fonts, icons used in output
