Using Fonts in Skills
Fonts can be bundled directly into a Skill so that they are applied consistently whenever the Skill generates Word documents or templates. The requirements below determine whether a font is detected and embedded correctly, and they explain what happens when a font does not qualify.Folder Structure
Font files are detected when they are placed in the assets/fonts/ folder inside the Skill. The following paths are also recognized: fonts/, images/, logos/, and img/. Fonts placed at the Skill root are not detected.Supported Formats
TTF and OTF are the recommended formats. WOFF and WOFF2 are supported as well. Variable fonts cannot be embedded in Office documents and are therefore not accepted.Font Faces per Family
Word supports four faces per font family: regular, bold, italic, and bold italic. Additional weights such as Light, SemiBold, or Black are folded into the base family, and only one weight per slot is used. To make a specific weight selectable in Word, ship it under its own distinct family name.Naming Convention
Use the format FamilyName-Style.ttf, for example Montserrat-Bold.ttf. Numeric suffixes in the filename are also handled.License Requirements
Fonts with an embedding restriction in the OS/2 fsType field are refused by design. When a font cannot be embedded, the document is generated with a fallback font instead. Verify that the font license permits document embedding before adding the font to a Skill.Orchestrator Skill Access
The Orchestrator coordinates Agents, tools, models, and context to determine which AI capabilities are used, when they are used, and how they work together. It has access to the broadest range of Skills across all tiers.Skill Availability
The following table shows which Skill types the Orchestrator can access:
The Orchestrator draws on all System Skills automatically, plus any workspace or personal Skills that are active at the time of the interaction.