Studio AI Skills

Skills are text files which allow AI agents to discover helpful context about a project or additional advice for how to carry out a particular task.

Skills are loaded by agents only when needed, to avoid using extra tokens and confusion. Each skill has a description and dependencies which help the agent decide if the skill is useful for its current task, and if so it will load the skill into its working context.

Siteglide Skills in the IDE (Code Editor)

Currently the best way to get the most of Siteglide skills is to work in a Code Editor with Siteglide CLI.

1. Check you have a version of Siteglide-CLI > 1.1.11.0, see CLI - Changelog and run siteglide-cli -v

2. Make sure you have no unsynced changes and run the siteglide-cli pull <env command once. This will:

   1. Create an .agents folder, as well as complementary folders for common AI agents to help them recognise the skills without prompting.

   2. It will also create a settings folder in /.siteglide/ai-agent-preferences.json where you can exclude AI agents you don’t use, so you can delete those folders and skip on future pulls automatically.

   3. There is no additional step to “enable” skills, like there is for MCP. They are just text files.

3. When a module updates, newly updated skills relevant to that module will be pulled.

The resulting folders may look a little like this:

Adding custom skills

1. Read about how skills should be structured here: https://agentskills.io/home The simplest skills are just text files and anyone can write them. Your AI agent can also write them for you if you want it to learn from a mistake or remember something for future sessions.

Adding skills to a custom module - which others can then pull to sites where your module is included

Skills are stored in a special module with ID 984. Inside your module repo, you can create a folder for the skills module alongside your own module’s folder which contains skills for your module. Within that it’s important to namespace so you don’t conflict with other modules.

1. Add skills for your marketplace module in the following folder structure:

├── marketplace_builder/
│
└── modules/
    │
    ├── module_<module_id>/                         # Your own module (host module)
    │
    └── module_984/                                  # Example skills module plugin
        │
        ├── private/
        │   └── views/
        │       └── partials/
        │           └── module_<module_id>.liquid    # Registers your module has skills
        │
        └── public/
            └── assets/
                └── agents/
                    └── skills/
                        └── module_<module_id>/
                            └── studio_kit/
                                └── build-page/
                                    ├── SKILL.md
                                    └── references/
                                        └── settings.md

The private Liquid file is needed but is safe to leave empty. It should be named with your module’s vanity ID, rather than the skills module’s ID.

Skills should describe things people may be able to do in a code editor with your module e.g adding your module features to a page?