Use cue skill for two different systems:
  • Local skills: SKILL.md instruction docs on your machine
  • Remote skills: callable server-side actions from the registry

​
Quick Start (Weather)

If you want weather data immediately, use: 
cue weather current '{"location":"San Francisco"}'
cue skill call weather current ... is the remote registry path, not local SKILL.md execution.

​
Command Model

GoalCommandSource
List installed local skillscue skill listLocal
Install local skills from a pathcue skill install ./skills/weatherLocal
Search local skill docscue skill search weather --source localLocal
Read a local skill doccue skill read weather --source localLocal
Search remote registry skillscue skill search weather --source remoteRemote
Read remote skill schema/docscue skill read weather --source remoteRemote
Call a remote skill actioncue skill call weather current '{"location":"San Francisco"}' --source remoteRemote

​
Local Flow (Instruction Skills)

cue skill list
cue skill search weather --source local
cue skill read weather --source local
Then follow the commands written in that SKILL.md (often regular cue <feature> ... commands).

​
Remote Flow (Callable Skills)

cue skill search weather --source remote
cue skill read weather --source remote
cue skill call weather current '{"location":"San Francisco"}' --source remote

​
Environment Keys

cue skill env manages ~/.cue/skills.env. Only set keys when a skill explicitly requires them: 
cue skill env list
cue skill env set <KEY_FROM_SKILL_DOC> <VALUE>
The current first-party weather local skill does not require an env key.

​
Limits and Defaults

  • search, read, and call default to --source remote
  • cue skill call --source local is not supported yet
  • cue skill search --source local does not support --category
  • Skill subcommands support --json output