Skills

Skills package reusable agent capabilities (typically a SKILL.md file plus optional supporting files) so multiple agents can share the same workflow definition where their adapters allow.

Supported format

• Primary document: SKILL.md with name/description frontmatter and a markdown body
• Optional supporting files nested with the skill
• Library editor fields cover description, skill markdown content, tags, and supporting files

Prefer skill packages over deprecated per-agent prompt files when an agent (for example Codex) has moved to skills.

Create or import

1. Library → Skills → New, or import via sync review when an agent already has a skill Visu can read.
2. Keep names stable; many agents key skills by folder/name.
3. Save, then assign to Global or Workspace for compatible agents.

Compatibility

Skills are supported widely but not universally:

• Strong coverage includes Claude Code, Codex, Cursor, Kiro, OpenCode, Roo Code, GitHub Copilot family, and others.
• Some agents gate skills or support only one scope (see matrix).
• Cline experimental multi-location skills are unsupported until source-aware update/delete is safe.
• Aider and Zed do not manage skills through Visu.

Linking, enablement, and sync

• Skills are assignable and synchronizable.
• They do not use a separate MCP-style enabled flag in the Library registry; presence is controlled by assignment and sync.
• Live updates and full sync both participate subject to agent support.
• When both Library and agent copies change, resolve the conflict in review before apply.

Limitations

• Supporting files must remain within the skill package Visu manages.
• Agents may load additional compatible skill roots that Visu intentionally does not rewrite.
• Do not hand-edit agent skill folders and Library copies in parallel without a review pass.

Related pages

• Supported agents
• Configuration item lifecycle
• Blog deep-dives for native-only workflows: Claude Code skills, Codex skills