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

# AI assistants (MCP)

> Use Skillsail from an AI assistant: connect it, ask it to build and edit modules for you, and publish or export the result.

Skillsail can be used directly from an AI assistant — Claude, Cursor, or another MCP-compatible tool. Once you connect Skillsail to your assistant, you can ask it to create modules, add slides, generate images, translate content, publish a module, and export it for your LMS, all from the assistant's chat.

This is useful when you want to:

* Build a module while you are already chatting with your assistant about the topic.
* Keep editing a Skillsail module without switching tabs.
* Have the assistant handle bulk tasks like translating into several languages or rewriting a series of slides at once.

<CardGroup cols={2}>
  <Card title="Connect an assistant" icon="link" href="/mcp/connect">
    Add Skillsail to Claude, Cursor, or another MCP-compatible assistant.
  </Card>

  <Card title="What the assistant can do" icon="list-check" href="/mcp/tool-reference">
    See what your assistant can help with in Skillsail.
  </Card>

  <Card title="Recipes" icon="book" href="/mcp/recipes">
    Ready-made prompts for common authoring jobs.
  </Card>

  <Card title="Templates" icon="rectangle-list" href="/templates">
    Share a module as a reusable template once it's ready.
  </Card>
</CardGroup>

## How it works

When you connect an AI assistant to Skillsail, you can ask it to work with your Skillsail content — for example *create a module*, *add a slide*, *translate into German*, *publish as a template*, or *export as SCORM*. You ask in plain language; the assistant handles the matching Skillsail step for you.

The assistant only sees content in **your** Skillsail workspace, scoped to the account you sign in with. It cannot see other people's modules.

## What you can ask the assistant to do

* **Create a module from a description** — "Build a 5-slide onboarding course for new hires with a 3-question quiz at the end."
* **Add or change a single piece** — "Add a slide on fire extinguisher classes after slide 3." / "Rewrite slide 2 to be more concise."
* **Generate or replace media** — "Add an image of an evacuation route to the first slide." / "Tighten the contrast on the image in slide 4."
* **Translate** — "Add German and Spanish to this module."
* **Publish and share** — "Make this module a template." / "Add the passphrase 'team-2026'."
* **Export to your LMS** — "Export this module as a SCORM 2004 package."
* **Roll back** — "Show me the previous versions of this module and restore the one from this morning."

## Safety

* The assistant always acts as you. Whatever you can do in the Skillsail UI, it can do — and nothing more.
* Through this connection, the assistant only works inside Skillsail. It cannot browse the web or change anything outside your Skillsail workspace.
* Some changes, such as deleting a module, restoring an older version, or removing a passphrase, take effect immediately. Most assistants will summarize the change before making it; if yours does not, ask it to confirm first.

## Good practices

* Be specific about which module you mean. "The onboarding module I created yesterday" or pasting the module's link both work well.
* Ask for a summary before bulk changes ("Show me a plan first, don't apply yet").
* Review the result. The assistant will report what it did; open Skillsail and skim the changes for anything that needs a human touch.

## Related

* [Connect an assistant](/mcp/connect)
* [What the assistant can do](/mcp/tool-reference)
* [Recipes](/mcp/recipes)