Skills

A skill packages instructions and optional supporting files for a concrete task. The agent reads a matching skill when it needs that procedure. Skill availability does not itself grant cloud access: operations still use the selected credentials and the provider’s permissions.

​

Built-in, team and personal skills

Built-ins are supplied by Nuphos. Open the team’s Settings → Skills to review team skills, switch to personal scope, or use the local import menu. Team skills are shared in that team. Personal skills belong to their member; loading support can differ by runtime. The current personal-skill UI describes loading on the member’s own Claude Code turns, so do not assume identical personal-skill behavior on every runtime. You can ask the agent to write a team skill after completing a repeatable task. Review what will be saved and its scope. Keep runnable commands, prerequisites, validation and recovery together; refer to configured credentials rather than putting secret values in the files.

​

Import and maintain

Use the import menu to bring in a local skill available on the selected device. Inspect its instructions and supporting files before sharing it. A skill can execute powerful operations, so do not import an unreviewed procedure merely because its name matches your task. Edit the skill when its commands or assumptions change. Check the runtime’s available skill registry after saving; loading and synchronization can take place at the next turn. Team sharing does not copy a computer’s private CLI sign-ins or repository files.

​

Instructions, skills and memory

Use instructions for standing preferences and team rules, a skill for a procedure, and memory for durable facts and verified findings. A skill’s operations follow permission modes; significant cloud work may use plans. Not every skill invocation creates a plan.