Creating Custom Skills

This guide covers everything you need to create effective custom Skills. For background, see What Are Skills? and Using Skills.

Creating a New Skill

1. Click the / button below the chat input
2. Click + Add skill
3. Fill in the skill name, description, and content
4. Click Create

Your new skill is saved and appears in your Skills library under the Personal tab.

You can also create skills from the Skills library by clicking the + Add skill button in the top right.

The Skill Format

Every skill has three required parts:

Name

The skill identifier. Rules:

• Lowercase letters, numbers, and hyphens only
• No spaces (use hyphens instead)
• Maximum 255 characters
• Must be unique among your skills

Good names:

• brand-guidelines
• code-review
• blog-post-structure
• api-documentation

Avoid:

• My Skill (no spaces or capitals)
• helper (too vague)
• stuff (not descriptive)

Description

A summary of what the skill does. Maximum 1,024 characters.

The description helps you remember what each skill is for, especially when you have many skills. Write something clear and specific.

Good example:

Blog post style guide for company content. Includes tone, structure, formatting rules, and headline patterns.

Bad example:

Helps with writing.

Content

The actual instructions, written in Markdown. Maximum 50,000 characters.

This is where you provide the guidance, context, examples, and rules the AI should follow when you apply this skill.

Writing Effective Content

Start with the Goal

Begin with a clear statement of what the skill accomplishes:

# Brand Guidelines

Apply these guidelines whenever creating content for Acme Corp.

## Core Principles
- Voice: Professional but approachable
- Tone: Confident, not arrogant
- Language: Clear and jargon-free

Be Specific, Not Generic

The AI already knows how to write. Your skill should add context it doesn’t have.

Too generic:

Write good content that engages readers.

Specific and useful:

## Blog Post Structure

1. Hook (1-2 sentences that create curiosity)
2. Problem statement (what pain point are we addressing?)
3. Solution overview (our approach in 2-3 paragraphs)
4. Practical steps (numbered, actionable)
5. Call to action (link to related resource or next step)

Keep paragraphs under 4 sentences. Use subheadings every 2-3 paragraphs.

Provide Examples

Show the AI what you want with concrete examples:

## Headline Style

**Good:**
- "5 Ways to Improve Your Morning Routine"
- "Why Remote Teams Outperform Office Teams"
- "The Complete Guide to Project Planning"

**Avoid:**
- "Tips" (too vague)
- "You Won't Believe What Happened" (clickbait)
- "Leveraging Synergies for Optimal Outcomes" (jargon)

Use Clear Formatting

Structure content so it’s easy to scan:

• Use headings (##) to separate sections
• Use bullet points for lists
• Use code blocks for templates or examples
• Use bold for emphasis on key terms

Include Decision Logic

Help the AI make choices:

## Image Selection

When choosing images:
- Product features → Use product screenshots
- Conceptual topics → Use abstract illustrations
- Team/culture content → Use team photos
- Technical tutorials → Use annotated screenshots

If no suitable image exists, suggest creating one rather than using a generic stock photo.

Skill Templates

Brand Guidelines Skill

# Brand Guidelines for [Company Name]

Apply these guidelines to all content creation.

## Voice & Tone
- Voice: [e.g., Professional, friendly, authoritative]
- Tone: [e.g., Confident but not arrogant, helpful not pushy]

## Language Rules
- [e.g., Use "we" not "I"]
- [e.g., Avoid jargon, explain technical terms]
- [e.g., Write at an 8th-grade reading level]

## Visual Identity
- Primary color: [hex code]
- Secondary color: [hex code]
- Font preferences: [font names]

## Content Patterns
- Headlines: [style guide]
- CTAs: [preferred phrases]
- Sign-offs: [standard closing]

Code Style Skill

# Code Style Guidelines

Apply when writing or reviewing code.

## General Principles
- Prefer clarity over cleverness
- Functions should do one thing
- Names should be descriptive

## Naming Conventions
- Variables: camelCase
- Functions: camelCase, verb prefix (getUserData, validateInput)
- Components: PascalCase
- Constants: UPPER_SNAKE_CASE

## File Organization
- One component per file
- Group related files in folders
- Index files for public exports

## Patterns to Use
- [specific patterns for your stack]

## Patterns to Avoid
- [anti-patterns in your codebase]

Content Structure Skill

# [Content Type] Structure

Use when creating [content type].

## Required Sections
1. [Section 1] - [purpose]
2. [Section 2] - [purpose]
3. [Section 3] - [purpose]

## Formatting Rules
- [rule 1]
- [rule 2]

## Example

[Complete example of ideal output]

## Common Mistakes
- [mistake to avoid]
- [mistake to avoid]

Best Practices

Keep It Concise

Every instruction competes for the AI’s attention. Include only what adds value.

Before (verbose):

When you are writing content for our blog, it's important to remember that our readers are busy professionals who don't have a lot of time to read lengthy articles, so you should try to keep your writing concise and to the point while still providing valuable information.

After (concise):

## Audience
Busy professionals. Keep content scannable and actionable.

Assume Intelligence

Don’t explain concepts the AI already understands. Focus on what makes your context unique.

Unnecessary:

A headline is the title of an article that appears at the top. It should grab attention and summarize the content.

Useful:

## Headlines
- Max 60 characters
- Include primary keyword
- Use numbers when applicable ("5 Ways to...")
- Never use clickbait

Use Strong Language for Musts

When something is required, say so clearly:

• “Always include…” (required)
• “Never use…” (prohibited)
• “Prefer…” (strong suggestion)
• “Consider…” (optional)

Test and Iterate

After creating a skill:

1. Test it with several relevant requests
2. Note where the AI follows instructions well
3. Note where it misses or misinterprets
4. Refine the skill based on results
5. Test again

The best skills evolve through real usage.

Common Mistakes

Too Much Content

Problem: The AI gets overwhelmed or misses key instructions.

Solution: Prioritize. Put the most important guidance first. Remove anything obvious.

No Examples

Problem: The AI interprets instructions differently than intended.

Solution: Show concrete examples of good and bad output.

Conflicting Instructions

Problem: The skill says to do X in one place and Y in another.

Solution: Review for consistency. Remove or reconcile conflicts.

Assuming Context

Problem: The skill references things the AI doesn’t know (internal terms, undocumented systems).

Solution: Define terms, provide context, or link to explanations.

Skill Limits Reference

Limit	Value
Name	255 characters, slug format
Description	1,024 characters
Content	50,000 characters

Next Steps

Start with one skill for a task you do frequently. Keep it simple, test it, and refine based on results. Once you’re comfortable, add more skills for other workflows.