Context file or skill?
Use context files for facts
Brand voice, ICPs, claims, product info, competitor lists, legal rules, testimonials, and past learnings.
Use skills for workflows
Step-by-step methods, recurring analyses, report formats, creative formulas, approval rules, or campaign playbooks.
Good skill examples
- “Run our weekly Meta health check and return pause/scale/test actions.”
- “Analyze competitor ads using our hook taxonomy.”
- “Create native-ad concepts using our copywriting method.”
- “Review every output for healthcare claim compliance before generation.”
- “Turn a customer review into five UGC hooks using this structure.”
How to write a skill
Name the outcome
Say what the skill should produce: report, concepts, QA checklist, briefs, or decisions.
How skills are used
| Capability | How it works |
|---|---|
| Kebab-case name | Skills use names like brand-voice-review or weekly-meta-health-check. |
| Slash attach | After creation, attach a skill to a chat with /skill-name. |
| Markdown instructions | The skill body is written as structured markdown instructions the agent should follow. |
| Workspace, brand, or product scope | Skills can be organization-wide or scoped to the brands/products where they apply. |
| Markdown import | Existing playbooks can be uploaded/imported as skills when they are already written down. |
| Scheduled reuse | A scheduled run can carry selected skills so the same method repeats every time. |
If the information is a durable fact, put it in context. If it is a repeatable way of working, make it a skill.
Context vs skills
The full comparison, and when to use each.