agentleFS
davidmatousekdavidmatousek/tachi/.claude/skills/tachi-infographics/SKILL.md

tachi-infographics

Skill95 starsChanged 38 days agoApache-2.0View on GitHub

Domain knowledge for threat infographic generation — infographic specification formats, template-specific section layouts (Baseball Card, System Architecture, Risk Funnel), Gemini API prompt construction rules, and visual design system tokens. Consumed by the threat-infographic agent during specification and image generation.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When the infographic command receives maestro as the template value, it expands to ["maestro-stack", "maestro-heatmap"] and generates both …

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

tachi-infographics

Domain knowledge for generating visual threat infographic specifications and images from tachi pipeline output. This skill provides the section format definitions, template-specific rendering rules, Gemini prompt construction guidelines, and visual design tokens that the threat-infographic agent uses to produce presentation-ready infographic specifications.

Domain Overview

The infographic generation pipeline transforms structured threat model output into two deliverables per template:

  1. Infographic Specification (threat-{template-name}-spec.md) -- A 6-section structured document containing all data points, color coding, layout instructions, and text content needed to render a presentation-ready infographic. This is the primary deliverable.
  2. Infographic Image (threat-{template-name}.jpg) -- A JPEG image rendered from the specification via Gemini API. This is a best-effort deliverable, conditional on API key availability.

The pipeline supports six templates:

TemplatePurposeAudience
Baseball CardCompact risk summary dashboard with donut chart, heat map, and finding cardsExecutive overview
System ArchitectureAnnotated architecture diagram with trust zones, attack surface badges, and data flowsSecurity architects
Risk Funnel4-tier vertical funnel showing progressive risk reduction through the pipelineRisk management
MAESTRO StackVertical seven-layer stack diagram showing finding counts and highest severities per MAESTRO layer (L1-L7)CISO / security management
MAESTRO HeatmapComponent-by-layer grid with severity coloring at each intersectionSecurity engineers
Executive ArchitecturePortrait layered architecture diagram with Critical/High threat callouts, positioned immediately after the Executive Summary in the compiled PDFCISO / board / executive sponsors

The first five templates share the same Sections 1-4 format (metadata, risk distribution, coverage heat map, top findings) but have a unique Section 5 (Architecture Threat Overlay) layout. Executive Architecture uses a distinct six-section structure (Metadata, Architecture Layers, Threat Callouts, Severity Distribution, Visual Layout Directives, Gemini Prompt Construction Notes) and is the only template rendered in portrait orientation — see references/executive-architecture.md for the full specification.

Template Shorthands

ShorthandExpands ToDescription
allbaseball-card, system-architecture, risk-funnel, executive-architectureGenerate all four core templates (conditionally extends with MAESTRO templates when MAESTRO data is present)
maestromaestro-stack, maestro-heatmapGenerate both MAESTRO templates sequentially
execexecutive-architectureSingle-template alias (not a compound expansion)
corporate-whitebaseball-cardLegacy alias

When the infographic command receives maestro as the template value, it expands to ["maestro-stack", "maestro-heatmap"] and generates both sequentially. The MAESTRO templates require MAESTRO layer data in threats.md (Feature 084); when MAESTRO data is absent, a graceful empty state is rendered.

The executive-architecture template (and its exec alias) is distinct from the other templates in two ways: it is rendered in portrait orientation rather than 16:9 landscape, and it uses a six-section structure instead of the shared Sections 1-5 format. When no Critical or High severity findings exist in the threat model, the spec file is still produced but the image is not — see references/executive-architecture.md for the full skip behavior specification.

Data Source Types

The infographic agent consumes one of three data source types, auto-detected by richness:

Data SourceRisk LabelScore TypePipeline Stage
compensating-controlsResidual RiskPost-control residual scoresAfter control analysis
risk-scoresInherent RiskQuantitative composite scoresAfter risk scoring
threatsSeverityQualitative severity levelsAfter threat modeling

Loading Table

Reference files are loaded on-demand by the threat-infographic agent at specific workflow phases using the Read tool.

ReferenceFileLoad When
Infographic Specificationsreferences/infographic-specifications.mdGenerating Sections 1-4 of any shared-format template (Baseball Card, System Architecture, Risk Funnel, MAESTRO Stack, MAESTRO Heatmap)
Template-Specific Formatsreferences/template-specific-formats.mdGenerating Section 5 for any shared-format template
Executive Architecturereferences/executive-architecture.mdGenerating the full six-section spec for the executive-architecture template (or its exec alias) — distinct section structure, portrait orientation, and PDF positioning rules
Gemini Prompt Constructionreferences/gemini-prompt-construction.mdConstructing the Gemini API image generation prompt after specification is complete
Visual Design Systemreferences/visual-design-system.mdGenerating Section 6 (Visual Design Directives) and populating template styling for the shared-format templates

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.