--- name: tywinlu1988/credit-report-builder source: https://app.decimal.ai/s/tywinlu1988-credit-report-builder@2/SKILL.md source_sha256: 3bc721351550 --- ## Path Resolution See `dev/engine/agent-protocol.md` §1 — engine/ and templates/ paths resolve to the package root in both plugin-install and open-as-project modes. ## Purpose **Engine version**: v0.3.2 **Non-Negotiables (see AGENTS.md)**: no report without a template from `dev/templates/` (never design ad-hoc HTML, dashboards, or layouts) · no numbers without a `doc §section` citation · no delivery without a QA Verdict. Assembly layer — **this skill does not perform analysis**. Responsibility is two steps: map the Analysis Artifact produced by the upstream `fixed-income-credit-analysis` skill to L0/L1/L2 output tiers and select the correct template → assemble into a deliverable report and produce a Delivery Note. This skill does not replicate any engine thresholds/layered time budgets/rating mappings; template selection and tier semantics are always determined by engine documents as the single source of truth. ## Inputs - **Path Sheet**: produced by the router, providing `path_id` / `depth` / `quality_gates`. `path_id` is the join key through the four-stage chain; this skill inherits it as-is and must not change it. - **Analysis Artifact**: produced by fixed-income, providing findings / completeness / veto / system_readouts / mode_b_gaps (field shape at `dev/engine/pipeline-contract.md` §2.2). ## Outputs - **Deliverable Report**: rendered from `dev/templates/` (template single source of truth — this skill does not carry template copies). Which template to use is determined by the `templates` field in `dev/engine/work-path-registry.md` for that path; do not substitute arbitrarily. - **Delivery Note**: structured YAML, field shape at `dev/engine/pipeline-contract.md` §2.3. ## Assembly Protocol 1. **Read join key**: Take `path_id` from both the Path Sheet and the Analysis Artifact; verify it points to a registered path in the registry. If inconsistent, stop and report. 2. **Select templates**: Based on `path_id`, retrieve the template list from the registry's `templates` field (Type 1–18 or allowed marker values `planned` / `L0-spec:`). Marker value meanings are defined in registry §schema; when hitting `planned`, must explicitly state "template under development" and not fabricate rendered output. 3. **Map tiers**: Map the Analysis Artifact to L0 Signal Card / L1 Snapshot / L2 Deep Report tiers. The definitions, consumption time, and information density of the three tiers use `dev/engine/output-layered-framework.md` §2 (three-tier overview) / §3 (L0 Signal Card) / §5 (L2 Deep Report) as the single source of truth; this skill does not redefine them. 4. **Render + fill via manifest**: Use templates from `dev/templates/` to assemble the report; completeness lamp caliber follows output-layered-framework §8.4. **Fill placeholders via the manifest**: read the template's `placeholders` list from `dev/templates/index.yaml` (machine-generated) instead of scanning the whole template to discover fields. Two template families exist: token templates (fill every listed token from the Analysis Artifact) and exemplar templates (empty `placeholders` list — replace the sample content section-by-section, preserving structure and CSS classes). After rendering, verify zero `{...}`/`{{...}}` tokens remain — any leftover is an unfilled field: fill it or mark it explicitly n/a. Then make the file **self-contained**: read `dev/templates/template-base.css`, inject its content into a `