tachi-report-assembly

Assemble Typst security report data from threat artifacts and brand assets.

86|21|Updated Mar 21, 2026

Search Tags:#automation #artifact-detection #typst #brand-assets #report-assembly #pdf-security-report #data-bindings

Ready to run

npx skills add https://github.com/davidmatousek/tachi --skill tachi-report-assembly

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tachi-report-assembly
Source: https://github.com/davidmatousek/tachi/tree/main/.claude/skills/tachi-report-assembly
Command: npx skills add https://github.com/davidmatousek/tachi --skill tachi-report-assembly

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Domain knowledge and contract guidance to assemble a production-grade PDF security report from threat artifacts, ensuring consistent Typst bindings and brand asset handling.

Core Features & Use Cases

Provides artifact detection patterns, Typst template contract coverage, and brand asset guidelines that the report-assembler uses to generate a complete security report from threats, risk scores, compensating controls, and executive narrative.
Enables deterministic data extraction and Typst data generation to populate report-data.typ with type-safe variables for metadata, asset presence, and findings.
Useful for teams building repeatable security reports for multiple projects, ensuring consistent formatting and branding across reports.

Quick Start

Run the report-assembler against your project artifacts to produce report-data.typ and ready Typst bindings.

Frequently Asked Questions about tachi-report-assembly

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a PDF security report from threat artifacts using Typst?▼

To generate a PDF security report from threat artifacts, this Skill applies deterministic extraction to map threats, risk scores, and controls into type-safe Typst data bindings. It populates report-data.typ with variables ensuring consistent formatting and brand asset handling.

What is the Typst template contract for automated report assembly?▼

The Typst template contract is a reference specification ensuring deterministic data extraction maps security findings into type-safe variables. It defines the exact inputs required to populate report-data.typ with metadata, asset presence, and findings for consistent PDF generation.

Can I use this to automate PDF security reports across multiple projects?▼

Yes, you can automate PDF security reports across multiple projects. The Skill provides artifact detection patterns and brand asset guidelines that enable repeatable report assembly, ensuring consistent formatting and branding for teams generating security reports.

What artifact files are required to assemble a Typst-ready security report?▼

Assembling a Typst-ready security report requires artifact detection outputs including threats.md, risk-scores.md, compensating-controls.md, and threat-report.md. These inputs feed the deterministic extraction process to generate the final Typst data bindings.

How do I bind security risk scores and findings into Typst variables?▼

You bind security risk scores and findings into Typst variables through deterministic data extraction. The Skill processes threat artifacts and generates report-data.typ, populating type-safe variables for metadata, asset presence, and findings.

Does this approach require reference material for brand asset guidelines?▼

Yes, brand asset guidelines and typst-template-contract.md reference material are required. They provide the domain knowledge necessary to ensure consistent Typst bindings and proper brand asset handling during automated PDF security report assembly.