Semogram Docs
Reference

Skills

Skill format, triggers, tools, and lifecycle with examples.

Skills are versioned instruction packages. Operator view in Skills and guidance.

Format

PartMeaning
SKILL.mdInstructions; frontmatter carries exactly name + description
references/Background reading the skill draws on
scripts/Executable helpers it may invoke
assets/Images, templates, static material
agents/Sub-agent definitions for delegated work

Missing frontmatter, an unclosed block, or a missing name/description fails validation before anything else runs.

---
name: renewal-review
description: Review renewal-risk forecasts against account history before commit.
---

# Renewal review

1. Open the forecast's evidence chain before reading its score.
2. Confirm the top drivers against the account timeline.
3. Correct stale inputs at the source; do not adjust the score by hand.

A second example — frontmatter for a data-quality skill with triggers and tools:

name: order-hygiene
description: Catch malformed order rows at validation time.
triggers:
  keywords: [orders, refund, duplicate]
  connectors: [crm, erp]
tools: [warehouse-lookup, ticket-search]

Image: skill package layout with SKILL.md, references, and scripts.

Triggers and tools

FieldMeaningRule
KeywordsRequest phrases that wake the skillNarrow beats broad
ConnectorsSystems in play that wake itBind to the systems it knows
ClassificationsWork types that wake itOne job per skill
ToolsExternal capabilities it may callDeclared up front; undeclared reach is a validation failure

Lifecycle

StageMeaning
DraftUnsaved editor state — catalog picks land here, never installed silently
Saved versionsHistory, compare, rollback by activating older
AttachmentWorkflow or node scope in Studio, always shown
RemovalDeletes guidance only — data, runs, history stay

Choosing well

  • One skill, one recurring judgment call.
  • Edit instructions on a schedule; guidance rots as processes change.
  • Judge against the unskilled baseline in a real run.