Skills and plugins

A skill supplies reusable instructions and supporting files. A plugin connects tools that can read information or perform actions. A Knowledgebase connector synchronizes source documents; it is not the same as an AI plugin.

Find and install resources

1. Open Skills or Plugins & Tools.
2. Switch between the installed library and the store. Search by name and check the personal/organization filter.
3. Review the resource, its origin and any requested access before installing or connecting.
4. A personally created or imported skill appears in your personal installed library. Organization resources appear in the organization library when you have access.
5. Select installed resources for the chat with @, or in the resource selection dialog for the agent or automation. Installation alone is not the same as selection for every task.

Create or import a skill

Use Create or import skill. The dialog accepts .skill, .zip, .md, or a skill folder. Give it a meaningful name and task-focused instructions. For packaged skills, preserve the main SKILL.md with its name/description header and relative supporting files. A .skill package is handled as an archive, not assumed to be plain Markdown; renaming arbitrary content does not convert it. Imported scripts are not executed during import.

A skill imported from another assistant may mention tools or permissions unavailable in CogLake. Review those instructions and perform a small test before enabling it for an unattended task. Never include passwords, API keys or an instruction to ignore approval rules.

Organization release and role access

1. 1Install or connect
2. 2Release for the organization
3. 3Choose allowed roles and tools
4. 4Select for a task

In the organization's plugin library, the prominent switch controls general availability. Expand the role/tool section to limit use to selected roles and tools. A released plugin is still subject to normal resource access and action approvals.

CogLake Knowledge is an integrated plugin, available by default unless restricted by an administrator. It uses the current user's knowledge permissions, not a shared administrator account. Releasing it cannot make another person's private documents visible.

Use with an automation

Open the automation's skill or plugin selection button. In the modal, turn the required installed resources on and save the automation. Do not assume that a plugin selected as a trigger source is also selected as an action tool; these are separate choices.

Updates and removal

Review changed instructions, tool descriptions and permissions when updating a resource. Removing or restricting a resource can prevent future agent or automation runs that depend on it. Check affected tasks before removing it.

If an installed item is missing, clear library filters, confirm the current organization and check the release switch and allowed roles. More help: permissions.