Use expert suites and skills

Find the right extension

Open Plugins from the Home sidebar. In the current interface, Expert suites and Skills are separate categories. Use the OpenDesign official and Personal filters to distinguish supplied capabilities from your own additions; a team collection can appear in a team workspace.

Open a card and read its purpose, required inputs and usage instructions. An expert suite packages a workflow; a skill provides task-specific instructions. Neither replaces a connected model or the credentials required by another service.

Import from a link

1. Choose Add, then select Plugin or Skill in the dialog to match the material you have.
2. Under Import from link, enter the repository or supported source link. Check that it points to the extension you intend to add.
3. Read the upload and workspace notice, then choose Import and upload. Wait for a successful result and find the resource in the appropriate collection.

Upload a local folder

1. In Add, choose Plugin or Skill, then find Upload local folder.
2. Choose folder and select the extension’s root directory. For a skill, include SKILL.md; the expert-suite dialog identifies open-design.json / SKILL.md as expected material. Keep referenced supporting files in their relative locations.
3. Check the selected files and destination, then choose the upload action shown for the selected kind, such as Upload Expert suites. Wait for completion before trying to invoke it.

Choosing a folder and uploading it are separate steps. If the upload control is unavailable, check that you have selected files, the workspace has finished loading and another import is not still running.

Create an expert suite from a prompt

For Plugin, Start from a prompt opens an authoring workflow. Describe the repeated task, expected inputs, output files and quality checks. Review the generated instructions and supporting files before reusing or sharing the suite. This starts creation; it does not instantly turn a short description into a verified extension.

Use a skill in a task

1. Open the project where the work belongs. Type @ in the composer and choose the Skills tab.
2. Select the intended skill and add the task requirements and required files. For a framework skill, name the framework and component constraints.
3. Send the request, then inspect the produced files and test the requested behavior. Keep the conversation in the same project for follow-up changes.

Use the card’s own entry action for an expert suite and supply its requested inputs. Attaching an extension is different from attaching a reference file with +. For setup, see AI connections; for interface checks, see prototypes.

If an imported capability does not appear or work

Check category, source filter and active workspace first. A skill can be absent from Expert suites while present under Skills. Open the import error to check the source link, expected manifest and folder structure; do not repeatedly upload an unrelated folder.

Read the extension’s instructions for any external service or model requirements. If a task fails, keep the error and the extension name with your app version for troubleshooting. Importing a capability does not guarantee that every agent supports every tool it requests.

Older versions may show Import a plugin with GitHub, ZIP and folder choices instead of the Add dialog pictured here. Follow the controls in your installed version. If sharing, syncing or uninstalling is offered, check which personal or team resource the action affects before confirming.