Skill names are unique within a workspace. Name a skill for its job, such as
meeting-notes-to-actions, not for its team or author. The same name can exist in another workspace.Skill profile tabs
An empty Usage tab is not a quality result, and Not scanned on Security is not a passed review.
Core offerings
Find and assess skills
Find a skill and check its version, source, scan, and usage.
Choose skill publishing method
Publish from Desktop, a terminal, GitHub, or an agent session.
Release skill version
Release, roll back, or withdraw a version.
How skill security scans work
Read scan decisions and findings, and how they gate a release.
Choose where to start
A skill acts with the permissions of whoever runs it. Review every supporting file in Source, especially scripts and templates, and check Security before an agent uses a version. Never put credentials or customer data in a skill package.
See also
- How skill source works: Package contents and provenance.
- How skill usage works: How runs are attributed to a skill.