> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/tools/service-commissioning-file-skill.md).

# Service Commissioning File Skill

Install the Agent Skill for service commissioning files in any AI coding agent that supports the Agent Skills format.

The service commissioning file skill lets your AI coding agent create and edit service commissioning files. It downloads the [schema](/2-6-1/reference/schema-files.md) for your Connectware version and reads the documentation for that version before writing any YAML, so property names, required fields, and allowed values come from the version you run.

{% hint style="warning" %}

## Always verify the service commissioning file

The skill checks the service commissioning file against the schema, not against a running Connectware instance. Install it on a development instance first, and see [Validate the Output](/2-6-1/guides/operations/writing-service-commissioning-files-with-ai-assistance.md#validate-the-output) for the full check.
{% endhint %}

## Requirements

To use the skill, you need the following:

* An AI coding agent that supports [Agent Skills](https://agentskills.io), can run shell commands, and can connect to Model Context Protocol (MCP) servers.
* The `jq` command line tool, which the skill uses to query the schema.
* Connectware 2.0.0 or later. Cybus publishes [schema downloads](/2-6-1/reference/schema-files.md) from that version onward. For older Connectware versions, the skill falls back to the `latest` schema, which does not match the version you run.

### Network Requirements

The skill needs outbound HTTPS on port 443 to:

* **download.cybus.io** for the schema.
* **docs.cybus.io** for the documentation MCP server.

## Installing the Skill

1. Download the skill and add it to your AI coding agent in the way it expects.

{% file src="/files/cUIlKlHNM1IV1dUzc7bb" %}

2. Connect your AI coding agent to the Cybus documentation MCP server, using transport `http` and URL `https://docs.cybus.io/~gitbook/mcp`. Doing it now avoids the skill asking for the server mid-task. Without the MCP server, the skill works from the schema alone. The command depends on which one you use:

{% tabs %}
{% tab title="Claude Code" %}
{% code lineNumbers="true" %}

```bash
claude mcp add --transport http cybus-docs https://docs.cybus.io/~gitbook/mcp
```

{% endcode %}
{% endtab %}

{% tab title="GitHub Copilot in VS Code" %}
{% code lineNumbers="true" %}

```bash
code --add-mcp '{"name":"cybus-docs","type":"http","url":"https://docs.cybus.io/~gitbook/mcp"}'
```

{% endcode %}
{% endtab %}
{% endtabs %}

## Using the Skill

Ask your AI coding agent to create or edit a service commissioning file:

> Create a service commissioning file for a Modbus/TCP PLC at 192.168.1.100. Read holding registers 0 to 9 every second and publish each value under factory/line-1/press-01.

> Add a Rule Engine transform to the temperature endpoint in this file that converts the value from Celsius to Fahrenheit.

## Data Privacy

The skill runs inside your AI coding agent on your own machine and fetches public files from `download.cybus.io` and `docs.cybus.io`. Cybus does not receive your prompts, your service commissioning files, or your machine data. Your prompts and the generated service commissioning file do reach the model provider your AI coding agent uses, under that provider's terms.

## What the Skill Does Not Do

* It does not install the service commissioning file or check it against a running Connectware instance.
* It does not know your project conventions, such as topic naming or which values belong in parameters. Record those in a [context file](/2-6-1/guides/operations/writing-service-commissioning-files-with-ai-assistance.md#write-a-context-file).
* It does not cover [custom connectors](/2-6-1/connectors/custom-connectors.md). The schema lists only the protocols shipped with a Connectware version, so the skill reports a custom connector protocol as unavailable, even though Connectware installs the service commissioning file.

## Next Steps

Read [Writing Service Commissioning Files with AI Assistance](/2-6-1/guides/operations/writing-service-commissioning-files-with-ai-assistance.md) alongside this page. It covers the project conventions the skill cannot know, and the checks to run before you install what it generates.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cybus.io/2-6-1/tools/service-commissioning-file-skill.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.