/skill_name in chat, or the agent can recognize from a skill’s description that it’s relevant to a question and invoke it automatically.
Skills live alongside Memory and the Semantic Catalog in your Context Layer. Where Memory holds durable facts and the Semantic Catalog holds metric and dimension definitions, Skills hold procedures.
What a Skill Contains
A skill can chain to another by mentioning it as
@skill_name in its content — useful for shared sub-procedures like cohort scoping or experiment extraction.
Built-in Skills
ClarityQ ships with skills for building and maintaining your Context Layer. They’re available in the Builder chat to admins and contributors:
Use these when you want guided creation or editing — the agent walks you through the right SQL, naming conventions, and validations.
Custom Skills
You can also write custom skills for the workflows your team runs repeatedly: a weekly retention drilldown, a launch readout template, a product-area QBR. Custom skills are managed on the Skills page. All custom skills are scoped to the product level — once deployed, they’re available to everyone working on the product.Invoking a Skill
There are three ways a skill can be invoked:- Type
/in chat — Type/followed by the skill name, or just/to open the skills picker and filter as you type. - Skills dropdown — Select a skill from the skills dropdown available from the add menu in the chat input box.
- Automatically by the agent — When the agent recognizes from a skill’s description that it matches the user’s question, it imports and follows the skill on its own — no manual invocation needed.
When to Use Skills vs Memory vs Rules
- Use Skills for repeatable procedures with steps (“how we calculate weekly retention”).
- Use Memory for durable facts and conventions that hold across the whole product (“we exclude internal accounts”).
- Use Rules for instructions tied to one specific catalog item (“always filter this metric to paid plans”).