Skip to content

Skill Management

A Skill usually starts with SKILL.md and may depend on scripts, references, assets, and other files. Preserve the complete directory when importing, updating, or distributing it. Copying only the instructions can leave a broken Skill.

Source What to check
Built-in or external store Review its instructions and source before installation
Local directory Scan existing Skills and inspect package files
Git repository Select the relevant Skill directory and import its complete package
Agent or project Confirm the root before importing existing Skills into your library

Version 0.6.2 supports nested GitLab groups and internal HTTP, HTTPS, and SSH sources. Private repositories require access from your device; not every repository directory is a valid Skill.

  1. Read SKILL.md for the task, inputs, outputs, and supported tools.
  2. Verify referenced scripts, documents, and images exist.
  3. Replace unsuitable paths or environment assumptions and save your version.
  4. Organize with tags; create named versions and inspect differences when needed.
  5. Review safety scan results and the actual contents before installation.

Select targets, apply changes, and inspect each result. Confirm the target tool actually loads the Skill.

Mode Behavior
Copy An independent target copy; library edits require redistribution
Link A reference to the source directory; source edits can affect targets immediately and paths must remain stable

Apply changes adds or removes targets. Redistribute updates existing copies. Resolve external edits before overwriting a target.

Check for source updates, review differences, and confirm before updating. Consider local edits alongside upstream changes. History provides comparison and rollback; full 0.6.2 backups preserve package files and history. See Backups.

Keep project-specific content in project workspaces and reusable Skills in your library. Read and adapt community Skills before installation. Remove secrets and private material before publishing.

Skills bundled in Plugins can be imported through available child-resource actions; see Plugin Management.