Skip to main content
Skills work best when you start with outputs your team already produces repeatedly. You do not need to rethink your workflows. You need to capture what already works and make it available automatically. For the full Skills reference, see Skills.

​
The “three outputs” framework

Think about the three outputs your team produces most often. Those are your first three Skills. A good first Skill is:
  • Something your team does at least weekly
  • Something where the output format matters or needs to be consistent
  • Something where writing the same prompt repeatedly wastes time
Once you have those three, expand from there.

​
Worked examples

​
Tone of voice Skill

Use this when your team produces customer-facing content and consistency matters. Name: Company Tone of Voice Description: Use when writing any customer-facing content including emails, proposals, support replies, and marketing copy. Instructions: 
Always write in a warm, direct, and confident tone. Avoid jargon and overly formal language.

Use "you" to address the reader. Keep sentences short. Prefer active voice over passive voice.

Do not use:
- Filler phrases like "As per our conversation" or "Please do not hesitate to contact us"
- Excessive exclamation marks
- Vague language like "various" or "certain"

When in doubt, write as if explaining something clearly to a smart colleague who is not an expert in the topic.

​
Status update Skill

Use this when your team produces regular progress updates that need to follow a consistent format. Name: Status Update Description: Use when asked for a status update, progress summary, or weekly report. Instructions: 
Summarize work in three sections:

**This week**
What was completed. Use bullet points, one line each.

**Blockers**
What is slowing things down. If none, write "None."

**Next week**
What is planned. Use bullet points, one line each.

Keep the total length to under 200 words. Use plain language, no technical jargon unless the audience is technical.

​
Meeting follow-up Skill

Use this for turning meeting notes into structured, shareable summaries. Name: Meeting Follow-Up Description: Use when summarizing a meeting, turning notes into a follow-up, or writing a recap to share with participants. Instructions: 
Structure every meeting follow-up as follows:

**Meeting summary** (2 to 3 sentences maximum)
What the meeting was about and what was decided overall.

**Key decisions**
Bullet list. Each item is one decision that was made.

**Action items**
Bullet list. Each item follows this format: [Owner] - [Action] - [Due date if known]

**Open questions**
Bullet list. Questions raised that were not resolved.

Keep the tone neutral and factual. Do not editorialize. If no notes are provided, ask for them before writing the summary.

​
Client email Skill

Use this for customer-facing teams that need consistent email tone and structure. Name: Client Email Description: Use when drafting an email to a client or external stakeholder. Instructions: 
Structure client emails as follows:

1. Opening: One sentence acknowledging context or thanking the client if appropriate.
2. Body: The main message, broken into short paragraphs. No paragraph longer than 3 sentences.
3. Next step: One clear sentence stating what happens next and who is responsible.
4. Closing: "Best regards" followed by the sender's name placeholder.

Tone: professional, direct, and warm. Avoid corporate clichés.

Never start an email with "I hope this email finds you well" or similar openers.

If the user provides background context, incorporate it. If the user does not specify the purpose, ask before drafting.

​
Document review Skill

Use this when your team reviews drafts against a standard set of criteria. Name: Document Review Description: Use when reviewing a document, checking a draft for issues, or auditing content against guidelines. Instructions: 
Review the provided document and return a structured assessment:

**Summary** (2 sentences)
What the document is and its overall quality.

**Issues found**
Bullet list. Categorize each issue as: [Clarity], [Accuracy], [Completeness], [Tone], or [Format].

**Suggestions**
Bullet list. Specific, actionable improvements.

**Verdict**
One of: Ready to publish / Needs minor revisions / Needs major revisions

Be direct. Do not soften feedback with excessive praise. If the document is good, say so briefly and explain why.

​
Skills vs. Agents

Skills and Agents solve different problems.
SkillsAgents
When to useRecurring instructions that apply across many situationsA dedicated environment for a specific domain or workflow
How they activateAutomatically based on the description, or manually via the @ menuYou navigate to the Agent or tag it
Knowledge and toolsVia attached integrationsConfigured directly on the Agent
Best forTone, format, output standards, integration shortcutsMulti-step workflows, specialized domains, customer-facing bots
If your team has an Agent they open just to get consistent formatting, that behavior belongs in a Skill instead. Agents should stay focused on what makes them specific. Generic instructions like tone of voice or output standards should be Skills.

​
What Skills cannot do

  • No memory across sessions. Instructions are re-read fresh in each conversation.
  • No live data without an integration. A Skill without an attached integration only provides instructions and cannot fetch external information.
  • No version history. Updating a Skill’s instructions replaces the previous version with no rollback.

​
Setting up workspace defaults

Once you have Skills your whole team should use, deploy them as workspace defaults. Every user gets them active from day one without installing anything. See Workspace Skills for the full setup.
Have more questions? See the Skills FAQ.