> ## Documentation Index
> Fetch the complete documentation index at: https://docs.longoz.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Skills

> Save reusable Agent instructions, attach them to work, and manage their versions.

A Skill is a versioned set of instructions for your Agents. Use one when the same procedure should apply to several Issues, a Project, or a [Routine](https://docs.longoz.ai/routines.md).

Workspace owners and admins can create and manage Skills. Members and viewers can read them.

## Create a reporting Skill

This example defines how an Agent should summarize CSV exports already available in its Project. It gives your configured CLI instructions; it does not install a tool or connect Longoz to a reporting service.

1. Open **Skills** and select **New skill**.

2. Set **Canonical name** to `operations-summary`. Names use lowercase letters, numbers, and single hyphens, with a maximum of 64 characters.

3. Set **Description** to `Summarize local operations exports when asked for an operations report.`

4. Select **Create skill**. Longoz opens a valid `SKILL.md` template in the editor.

5. Replace the source with:

   ```markdown theme={null}
   ---
   name: operations-summary
   description: Summarize local operations exports when asked for an operations report.
   ---

   # Operations summary

   Use this procedure for operations reports from local CSV exports.

   Read the input filenames and reporting period from the task.
   Check that the files exist and identify their date and value columns.
   Do not modify the source files.

   Count records and calculate totals only where the columns support them.
   State the reporting period, source filenames, and any missing data.
   If a required file or column is missing, explain the gap instead of
   estimating a value.

   Put the findings in the final response. Create a report file only when
   the task asks for one. Do not send data to an external service.
   ```

6. Wait for **Document is valid**. Optionally enter a change summary, then select **Save version**.

Keep the frontmatter `name` identical to the Skill's canonical name. Both `name` and a nonempty `description` are required. Validation errors must be fixed before saving. **Preview** shows the rendered Markdown.

## Attach it to work

Choose the narrowest useful scope:

* For one Agent, open **Agents**, edit the Agent, and select the Skill in its execution profile's **Skills** picker. Save the Agent changes.
* For a Project, open **Edit project**, select the Skill under **Skills**, and save. New Project work inherits these assignments.
* For one Issue or Routine, open **Agent details**, select the Skill under **Skills**, and save the details. You can also choose it while creating the work after assigning an Agent.

Inherited selections show their source and cannot be removed from the Issue or Routine's picker. Change the assignment at its source when it should no longer apply. The effective set combines Agent, Project, and work-specific assignments; selecting the same Skill from more than one source does not create duplicate copies.

An existing Issue or Routine may show that its captured Project Skills are stale after you change the Project. Save its execution settings to recapture the Project assignments explicitly. A queued or running Run remains pinned to its existing settings.

## Use the Skill in an Issue

1. Ensure the assigned Computer has a working Agent CLI and a Project with readable CSV exports.

2. Attach `operations-summary` to the Agent, Project, or Issue as described above.

3. Create an Issue with the title `Summarize last week's operations` and a description such as:

   ```text theme={null}
   Use the operations-summary procedure to summarize reports/orders.csv
   for the previous Monday through Sunday in Europe/London.
   Include order count and total order value if those columns are present.
   Write the result to weekly-operations-summary.md and include the
   findings in your final response.
   ```

4. Assign the Agent and submit the Issue in **Todo**.

5. Open the Issue to follow the run and review its response and requested report file.

The Skill supplies the reusable procedure. Keep changing details, such as input paths and the reporting period, in the Issue or Routine description.

## Update or restore a version

Open the Skill, edit **Source**, and select **Save version**. Every save creates an immutable version. New Runs resolve the current version of their assigned Skills, then pin the selected content for that Run. Saving a Skill does not replace the content of an existing queued or running Run, or a retry of the same turn.

Open **Version history** to inspect earlier content. Select **Restore as new version** to make earlier content current without deleting later history. Save or discard an unsaved draft before restoring.

If someone saves a newer version while you are editing, Longoz keeps your draft and prevents a stale save. **Keep draft on current base** retains your text against the current version. **Discard draft and reload** replaces your draft with the saved content. Review the result before saving again.

## Archive a Skill

Select **Archive** when a Skill should leave new assignment pickers. Its version and run history remain available. Archived Skills are read-only in the editor. Find one under **Archived** and select **Unarchive** to make it active again.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.