Use Skills in a Project

A Project binds the Skills the agent can call by name from chat and from a Runbook. This article covers the Skills section inside a Project's Context tab.

Audience: builders

Open the Skills section

Inside a Project, open the Context tab and pick Skills from the left rail. The section header counts the rows and offers a search input.

Each row carries the Skill name, a one-line description, and a scope label: Personal, Project, Team, Workspace, or Built-in.

What the list shows

The section combines three sources into one ordered list:

• Owned. Skills authored locally to this Project (or to your Personal scope from the home Project). You can edit, publish, and delete these in place.
• Available. Published Skills the Project can call: built-in Skills, your Personal Skills, Team Skills you belong to, and Workspace Skills.
• Drafts. In-progress Skill folders sitting in the Project volume that have not been finalized yet.

Call a Skill

The agent picks a Skill on its own when the user's request matches the Skill's when_to_use triggers. You can also call one explicitly:

• From chat. Type @ in the composer and select the Skill. The picker lists every available Skill in the Project.
• From a Runbook. Name the Skill in your Runbook text. The compiler resolves the name against the same picker source the chat composer uses.

If a Skill is in the list but cannot be called, check that it has been finalized: drafts and unfinalized Skills are excluded from the @-mention source.

Edit, publish, or delete an owned Skill

Click any owned row to open the drawer. Two modes:

• View. The rendered SKILL.md, the scope, and the live status.
• Edit. Update the frontmatter and the body, then save. Save writes a new draft snapshot in the Project volume.

The drawer footer carries Publish and Delete. Publish runs the same finalize flow as the create surface: it can land as Published, Proposal submitted, or Blocked. Delete removes the draft folder and every supporting file in it.

Promote a Project Skill to the Team

A Project-scoped Skill that proves useful belongs at the Team level. Open the row, then click Promote to team in the drawer. The platform copies the published snapshot into a new team draft and finalizes it: a team admin lands the publish directly, a team member files a proposal for review.

Where to go next

• Author a Skill for the SKILL.md model, the when_to_use requirement, and the .skill archive import path.
• Shared versus project scope for deciding when a Skill belongs at Project, Team, or Workspace scope.