← DelegentCONTENT HISTORY

Update to Delegent

Snapshot Nov 18, 2026 · 06:18 UTC · version 0.3.1

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Delegent and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Get a template. Use when the user asks for one of their Delegent templates, or wants a PowerPoint, Excel or Word file built in a personal or firm-shared template's style.",
  "included_files": [],
  "name": "get-template",
  "skill_md_contents": "---\r\nname: get-template\r\ndescription: Get a template. Use when the user asks for one of their Delegent templates, or wants a PowerPoint, Excel or Word file built in a personal or firm-shared template's style.\r\n---\r\n\r\n# Get a template\r\n\r\nDelegent returns the template's compiled instructions and style, never the template file. You build the new file with your own tools.\r\n\r\n## 1. Find it\r\n\r\n- With a `template_ref`, or a name the user gave, call `delegent_get_template`.\r\n- No match or several matches: show `available_templates` or `matches` and ask which one. `delegent_list_templates` lists everything with readiness.\r\n- **No template of their own?** Delegent still has its own standard for PowerPoint, Excel and Word (scope `built_in`, always ready, in the user's brand colour). Call `delegent_get_template` with `name` set to \"PowerPoint\", \"Excel\" or \"Word\", or with the `built_in` template_ref from `delegent_list_templates`. Use it by default instead of your own plain styling; a template the user uploaded always takes priority.\r\n\r\n## 2. Check it is ready\r\n\r\n- `usable: false` or a file with `ready: false` has a `reason` (still analysing, failed, unsupported type). Tell the user and offer to go without it.\r\n- A file marked `omitted` was left out for size. Call again with `file` set to its name.\r\n- A built-in standard can span several parts (the PowerPoint one does). When the result has `next_part`, call again with `part` set to it and read every part before you build.\r\n\r\n## 3. Build the file\r\n\r\n- Use the template file whose `format` matches what the user wants (pptx, xlsx, docx).\r\n- `generation_instructions` are binding. Apply `design_tokens` (hex colors, fonts, sizes) and `style_profile`:\r\n  - PowerPoint: canvas ratio, palette, typography, density and the `slide_roles` sequence with box positions in percent of the slide.\r\n  - Excel: sheet order, `anchor_cells` addresses for titles and headers, header/body/section styles, column widths, number formats and `formula_examples` logic.\r\n  - Word: structure, headings and wording from the instructions; there are no extracted style tokens.\r\n- Fill it with the user's sourced facts (`delegent_get_context_for_task`, `delegent_get_source`). Never copy example facts from the template.\r\n- For a full client deliverable with evidence checks, follow `draft-the-deliverable`.\r\n\r\n## 4. Save, if asked\r\n\r\nOn the user's request, `delegent_save_file` saves the finished file to a workstream with a summary and its text.\r\n"
}

SHA-256 of public snapshot: d7dbbacba145cb965d9ee2ac2d88be7f835c4b008024c26c056d66578f22fee8