Skill sources
Skills can be built in, stored locally, or downloaded from a published source. Before installation, the product should show which type you are installing.
Use that source label to decide whether the skill can be trusted in the current environment.
What a skill can add
A skill can add prompts, instructions, configuration, scripts, or other packaged behavior. The install screen should make it clear what files are added and whether any executable content is included.
Before enabling a downloaded skill, review:
- the publisher or source
- the files or actions introduced by the package
- whether the skill requires network access or external tools
Update and removal
Keep skill lifecycle operations explicit. Users should be able to see the installed version, apply an update, or remove the skill without affecting unrelated product configuration.
Recommended administration
For managed environments, install new skills on a test machine first. After review, roll them out to production devices that use the same runtime and security policy.