Agentry

agentry/report-designer

built-inv1.2.0

Designs a report design from a brief, a logo and references, and writes a custom cover page in Typst, looking at each render.

Built into Agentry. The application runs this package itself; it is published here so you can read how it works. Its README says what Agentry gives it beyond its manifest.

Declared capabilities

data: filesknowledge: ships 1

Ships knowledge: design-guide (40.9 KB), in the release archive under knowledge/<name>/, scanned with the version.

Capabilities are the author's declaration and the basis for policy and scanning. The registry cannot enforce them at run time. Your runtime should.

MCP servers & tools

agentry run serves exactly the tools this contract declares, through a per-run MCP gateway. An undeclared capability is a tool that does not exist at run time.

Tools the runner grants

Manifest declarationTool(s) granted
(always)write_report — reports → the run's output folder
(always)list_inputs, read_input, search_inputs — operator-provided input files, read-only

MCP servers involved

  • QuickAgent Tools — the runner's companion server, served through a per-run Docker MCP Gateway; its tool surface is exactly the table above.
  • Operator-cataloged MCP servers may be attached for the declared dataAccess category (files); undeclared categories are never wired in.

In an embedded install

Installed into an existing coding agent (agentry install), the same contract maps to the host's built-in tools — enforcement there is the host's. Allowed tools: none declared (host defaults apply).

Install

agentry install agentry/report-designer@1.2.0
git clone https://secureagentry.net/agentry/report-designer.git
git clone ssh://git@git.secureagentry.net/agentry/report-designer.git

claude-skill is this agent's default target, so the flag is not needed.

README.md

The Report Designer

The Report Designer is the QuickAgent that designs how your PDF reports look. It has two jobs:

  • Design writes a whole report design from your brief: colours checked for contrast, the faces, the title block and headings, a running header and footer, the brand block, and a cover style. You can give it a design to start from, your logo, up to four reference images, up to two web addresses, such as your own site, and one document of yours, a PDF or a Word document, to build the design around: it takes the document's logo, its cover page's artwork, its header and footer, and can write a custom cover modelled on its cover page.
  • Cover writes a custom cover page for one of your designs, in Typst code. It renders the cover, looks at it and refines it, up to twelve renders, and can draw images you give it.

What it makes is a new design. It is never your default and never replaces one of your designs: you pick it for a run, or make it your default, when you want it. Read more at https://docs.secureagentry.net/runner/.

This is the package that runs

The Report Designer is built into the Agentry CLI, and it runs from there: on your computer when you run agentry report-design design or agentry report-design cover. This release has the same bytes. The registry built its archive from the package the CLI carries, and the archive's digest is the one the CLI reports. Run agentry builtins to print it and compare it with the digest on this page.

Installing this release does not give you the Report Designer. The application runs it as a built-in, with the steps and tools listed below. If you install this release, it runs as an ordinary QuickAgent with only what its manifest declares.

What the application does around it

The manifest declares no network access, no file access and no commands, and one data category, files. When Agentry runs the Report Designer:

  • Before the run, the CLI stages what you gave it as inputs: the design to start from, without its images; the design's own images and yours, each re-encoded from its pixels; and your reference images. A document goes through the decode step like any input (its type checked, scanned for malware, its text extracted); then, in the same decode image with no network, a PDF's first twelve pages are rendered as images by poppler's page renderer with the pictures those pages draw, or a Word document's theme, header, footer and pictures are read (no Word layout is rendered). The CLI re-encodes every image from its pixels and stages what was read, never the document itself. Pages from web addresses are fetched and read by AI Review, with your own TypeSafe key, as the Voice Writer's are; a page drawn by scripts is read during the run with web_read, held to the addresses you gave.
  • During the run, the application grants it six tools of its own, and no other package gets them. render_preview lays out a fixed sample report in a design with the same renderer and confinement as a PDF export, and shows the model one page as an image. check_design holds a design to the rules every design is held to. view_reference shows the model one of your reference images. document_pages shows the model a page or a picture of your document, with its text, fonts and colours; crop_logo takes a picture or a box of a page as the design's logo; and take_picture takes one as the design's cover image or as an image of a custom cover modelled on your document's cover page. It writes its files with write_report.
  • Its guide. The release ships a knowledge pack, knowledge/design-guide: the design document and its closed lists, choosing a look, designing from a document, a custom cover's conventions, a short course in cover design, a worked example, and the checks before finishing. The application attaches it to every run.
  • After the run, the CLI checks what it wrote: the design against the same rules the registry applies, and a custom cover against its bounds. It attaches only the design's own images and yours, re-encoded, and refuses an image that is neither. A logo or a picture taken from your document is taken again by the CLI from its own copy of the page or the picture; no whole page of the document and none of its text is kept. With --save it adds the result to your account's designs under a new name; without it, it leaves the files in the run's output folder.

A custom cover's code

A custom cover is Typst code that the report template calls to draw the first page. When a PDF is exported, it is compiled with the rest of the report, offline, with the fonts in the runner image, and it can read only the report, the design and the images copied beside them. It cannot import a package, fetch anything or write a file. A cover that fails to compile, tries to draw more than one page, leaves an image without alt text, or runs past the render's limits is passed over for the built-in band cover. The export never fails for its cover, and the run's receipt says the cover was passed over and what kind of failure it had.

INSTRUCTION.md is the instruction the model follows.

Agentry uses only strictly necessary cookies — they sign you in and keep the site secure. Nothing here tracks you, and there are no advertising or analytics cookies. Privacy policy