Skills

Skills are reusable content guidelines for Content Studio generation. They let you store brand voice, content standards, and strategic priorities so they can be reused instead of rewritten for every content task.

What a skill contains

Each skill has:

  • Name -- A descriptive label (e.g., "Brand Voice Guidelines", "SEO Best Practices", "Technical Writing Style")
  • Content -- The guidelines themselves, written in plain text. This can include instructions about tone, structure, required elements, things to avoid, target audience, or any other direction you want to give the AI when generating content.

Skills are freeform -- you can write whatever guidelines make sense for your needs.

Examples of useful skills

  • Brand voice -- "Write in a professional but approachable tone. Avoid jargon. Use active voice. Address the reader as 'you'."
  • Competitive positioning -- "Always position our product as the most innovative option. Acknowledge competitor strengths but highlight our unique advantages."
  • SEO guidelines -- "Include the primary keyword in the first paragraph and at least two H2 headings. Keep paragraphs under 150 words."
  • Technical accuracy -- "Cite specific features and capabilities. Include version numbers where relevant. Don't make claims that can't be verified."
  • Compliance -- "Don't make performance guarantees. Include required disclaimers. Avoid superlatives like 'best' or 'guaranteed'."

Creating a skill

  1. Open the project
  2. Go to Project Settings -> Content Studio
  3. Click Add Skill
  4. Enter a name and the guideline content
  5. Choose whether the skill belongs to this project or the whole organisation
  6. Click Create Skill

Using skills with content briefs

Skills are managed from Project Settings -> Content Studio. The current customer UI does not expose a per-brief skill picker in the brief editor; briefs focus on title, content type, objective, and tone.

Stored skills remain useful as durable guidelines for generation flows that include skill IDs, and as the place to maintain brand voice and content rules for the project or organisation.

Managing skills

  • Edit any skill to update its guidelines as your standards evolve
  • Delete skills you no longer need
  • Upload .md, .markdown, or .txt content into a skill

Skills can be scoped to a specific project or shared across your entire organisation. Project-scoped skills appear only in that project's Content Studio settings.

Tips

  • Start with 2-3 core skills. A brand voice skill and a content structure skill cover most needs. Add more as specific requirements emerge.
  • Keep guidelines specific and actionable. "Write well" is too vague. "Use short sentences, active voice, and explain technical terms on first use" is actionable.
  • Update skills based on results. If generated content consistently needs the same edits, add those patterns to your skills.