> ## Documentation Index
> Fetch the complete documentation index at: https://klipy.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# How do I teach Klipy a play?

> Build custom skills, add a knowledge base, and let Klipy learn your writing voice from sent email—all from /customize—so its output sounds like you.

Klipy learns how you sell through three tools under **/customize**: skills (a reusable instruction for a situation you handle often), a knowledge base Klipy references when it drafts or answers, and a writing-voice analysis that scans your sent email so replies sound like you. Together they shape the drafts, summaries, and answers Klipy produces for your business.

## Create a custom skill

A skill is a named, reusable instruction—your version of "when X happens, handle it like this." Klipy consults your active skills whenever one is relevant to what it is doing; you do not have to invoke them by name.

<Steps>
  <Step title="Open Skills">
    Go to **/customize/skill** (or **Settings → Skills** in the app). You'll see three sections: **Personal** (only you can see these), **Organization** (shared with your team), and **Built-in** (maintained by Klipy).

    <Frame caption="Screenshot coming soon: /customize/skill page, Personal / Organization / Built-in tabs and the New skill button">
      <div style={{padding:'2.5rem 1rem',textAlign:'center',border:'1px dashed currentColor',borderRadius:'12px',opacity:0.55}}>Screenshot coming soon</div>
    </Frame>
  </Step>

  <Step title="Click New skill">
    Choose one of three ways to start: **Build with Klipy**—describe what you want in chat and Klipy drafts the skill for you to review (recommended); **Choose from library**—browse and install skills built by the community or by Klipy; **Import .md file**—upload an existing skill file to edit here.
  </Step>

  <Step title="Give it a name, slug, and description">
    The name and description are what Klipy reads to decide when the skill is relevant, so make them specific (for example, "Renewal outreach for lapsed clients" rather than "Sales help").
  </Step>

  <Step title="Write the instruction">
    In the editor, write the steps or guidance you want Klipy to follow for this situation. Save when you're done—new skills start **Personal**, visible only to you.

    <Frame caption="Screenshot coming soon: a written skill instruction saved as Personal in the editor">
      <div style={{padding:'2.5rem 1rem',textAlign:'center',border:'1px dashed currentColor',borderRadius:'12px',opacity:0.55}}>Screenshot coming soon</div>
    </Frame>
  </Step>
</Steps>

<Note>
  A skill you build stays **Personal** until you choose to share it. Open the skill and use the **⋯** menu to **Share to org**, which makes it visible to your whole organization. From the same menu you can also **Publish to community**, which makes the skill public to the whole Klipy community and credits it to you.
</Note>

<Note>
  A skill installed from the community library can be **locked**—you can turn it on and use it, but you cannot view or edit its underlying instructions. If the author republishes an update, your installed copy shows an **update available** badge and you choose when to pull it in.
</Note>

## Add your company knowledge

The knowledge base is where you write or paste reference material—pricing details, product specifics, company policy, anything Klipy should know but that would not otherwise appear in an email thread. Klipy pulls from it when a knowledge item is relevant to a draft, summary, or answer; it is not injected into everything Klipy writes.

<Steps>
  <Step title="Open Knowledge">
    Go to **/customize/knowledge** (or **Settings → Knowledge**).
  </Step>

  <Step title="Click New">
    Give the item a **name** and a **slug**—the slug is how the item is referenced internally.
  </Step>

  <Step title="Write the content">
    Type or paste the reference material directly into the rich-text editor. A raw markdown toggle is available if you'd rather write in plain markdown. Save when you're done.
  </Step>
</Steps>

<Note>
  Knowledge items are written or pasted as text—there is currently no file-upload option (no PDF or Word doc attachments). If your material starts as a document, copy the text in.
</Note>

## Match your writing voice

Klipy can learn how you write so email drafts sound like you, not a generic template. This lives alongside your other email-drafting settings, not under /customize.

<Steps>
  <Step title="Connect an email account">
    Writing-voice analysis needs at least one connected email account. If none is connected yet, see [Connecting email and calendar](/docs/guides/connecting-email-calendar).
  </Step>

  <Step title="Open Prepare email drafts settings">
    Go to **/delegation/email-drafts**, scroll to **Settings**, and find the **Analysis** section.
  </Step>

  <Step title="Click Analyze">
    Klipy scans your recently sent emails and learns your tone, typical length, greeting, sign-off, level of formality, and spelling conventions (US, UK, or Australian English, for example). The section then shows the timestamp of your last analysis.
  </Step>

  <Step title="Refresh when your style changes">
    Click **Refresh** at any time to re-run the analysis—useful if your writing has changed or you want Klipy to pick up more recent examples.
  </Step>
</Steps>

<Note>
  The same **Settings** panel shows your **default output language** (used for summaries, tasks, and drafts), with a shortcut back to **/customize** to change it.
</Note>

## Set your timezone, briefing schedule, and languages

The general **/customize** page holds a few more settings that shape how Klipy communicates with you.

<Steps>
  <Step title="Set your timezone">
    Under **Daily briefings**, choose your timezone. This is the timezone Klipy uses for anything scheduled around your day, including the morning brief.
  </Step>

  <Step title="Manage the morning brief">
    Click **Manage your daily brief** to go to the **Daily brief** delegation page, where the schedule and on/off toggle live.
  </Step>

  <Step title="Set your output language">
    Under **Languages**, choose your **default output language**—this is the language Klipy uses for summaries, task labels, and email drafts.
  </Step>

  <Step title="Check supported input languages">
    Click **Check** next to **Input languages** to see the full list of 83 languages Klipy can understand in emails, messages, and meeting recordings, grouped into four accuracy tiers from high (English, Spanish, French, German, and others) down to fair.
  </Step>
</Steps>

<Note>
  **Evening debrief** appears on this page marked **Coming soon**—it is visible in the settings but not yet active, so changing its days or time has no effect yet.
</Note>

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Do I need to tell Klipy when to use a skill or knowledge item?">
    No. Klipy checks your active skills and knowledge items on its own whenever they're relevant to a draft, summary, or answer it's producing—you don't invoke them by name in conversation.
  </Accordion>

  <Accordion title="Will a personal skill I build be visible to my teammates?">
    Not unless you share it. Every new skill starts **Personal**, visible only to you. Open the skill's **⋯** menu and choose **Share to org** to make it visible to your whole organization, or **Unshare** to pull it back to personal.
  </Accordion>

  <Accordion title="Can I install a skill someone else built?">
    Yes. Under **/customize/skill**, choose **New skill → Choose from library** to browse skills built by the Klipy community or by Klipy itself, then click **Install** to add one to your own Personal skills.
  </Accordion>

  <Accordion title="Does Klipy's knowledge base support qualification frameworks like BANT or MEDDIC?">
    Not as a built-in selector today. Klipy's customization currently covers skills, the knowledge base, and writing-voice analysis. A dedicated sales-methodology or qualification-framework picker is not yet available—if your team follows a specific framework, you can describe its criteria as a skill or knowledge item in plain language instead.
  </Accordion>

  <Accordion title="Does the writing-voice analysis read my entire inbox?">
    No. When you click **Analyze**, Klipy scans your recently sent emails only—not incoming mail—to learn your tone, length, greetings, sign-offs, and phrasing.
  </Accordion>

  <Accordion title="What happens to old drafts after I run a new writing-voice analysis?">
    Only future drafts pick up the updated style. Analysis does not rewrite drafts that already exist in your approval queue.
  </Accordion>

  <Accordion title="Can I delete a skill or knowledge item once it's created?">
    Yes. Personal and organization skills can be deleted from the skill's **⋯** menu (built-in skills maintained by Klipy cannot be deleted, only turned off). Knowledge items can be removed the same way from the knowledge list.
  </Accordion>

  <Accordion title="Does changing my output language rewrite past summaries and drafts?">
    No. The output language you set in /customize applies going forward—summaries, tasks, and drafts already created keep the language they were generated in.
  </Accordion>
</AccordionGroup>

## Related guides

<CardGroup cols={2}>
  <Card title="Connecting email and calendar" icon="mail" href="/docs/guides/connecting-email-calendar">
    Connect an email account—required before Klipy can analyze your writing voice or draft on your behalf.
  </Card>

  <Card title="Approve and send drafts" icon="send" href="/docs/guides/follow-ups">
    Where the drafts shaped by your writing voice and skills show up for your review before anything sends.
  </Card>
</CardGroup>