Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when turning a completed fixed-income credit analysis into a deliverable report — selecting the correct report template (Type 1–18), mapping findings to the L0/L1/L2 output tiers, rendering a multi-stakeholder dashboard, or assembling a layered credit report from an analysis artifact. Triggers on 'generate report', 'produce a credit approval report', 'build a dashboard', 'L0 signal card', or when a work-path sheet's templates must be produced. Requires an upstream analysis artifact; does not
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-02 | ✗→✓ | ▲ Improved | 38% | 0% |
| case-06 | ✗→✓ | ▲ Improved | 142% | 0% |
| case-08 | ✗→✓ | ▲ Improved | 97% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 38% | 0% |
| case-12 | ✗→✓ | ▲ Improved | 109% | 0% |
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.
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.
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.dev/engine/pipeline-contract.md §2.2).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.dev/engine/pipeline-contract.md §2.3.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.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.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.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 <style> block in the report's <head>, and remove the <link rel="stylesheet"> tag. This ensures reports render correctly when copied or forwarded — no missing CSS dependency.<issuer-slug>-type<NN>.html where <issuer-slug> is a lowercase-hyphenated issuer name (e.g., andritz-ag) and <NN> is the two-digit template type number (e.g., type01, type06). This makes reports sortable and identifiable without opening them.rendered. If the count (excluding report-index.html itself if already present) exceeds 1, generate a report-index.html navigation page from dev/templates/report-index.html. The index must:rendered with: its file name, a relative-path link (e.g., ./andritz-ag-type01.html), and a one-sentence description/summary of that report's contentreport-index.html to the rendered list (NOT to templates_used — templates_used is reserved for per-path registry templates); use a relative path for portabilitypath_id — in multi-path engagements, write a separate note file per path (e.g., ad01-delivery-note.yaml); never merge paths into one note (pipeline-contract §2.3). All paths in rendered and source_analysis MUST be relative paths (no absolute paths) — the Delivery Note travels with the report files.Template (schema single source of truth is dev/engine/pipeline-contract.md §2.3):
yamlpath_id: "" # join key (inherited from Path Sheet, must not change) depth: "" # L0|L1|L2|special (inherited from Path Sheet) templates_used: [] # templates selected from the path's registry templates field rendered: [] # actual report files produced (relative paths); includes report-index.html when >1 reports tier_mapping: # Analysis Artifact → L0/L1/L2 tiers L0: "" L1: "" L2: "" completeness_lamp: "" # completeness lamp status source_analysis: "" # upstream analysis artifact reference (traceability)
Example (Credit Selector single target L2 Deep Report, path WP-CS-01 with Type 1 + Type 6):
yamlpath_id: WP-CS-01 depth: L2 templates_used: - dev/templates/template-type1.html - dev/templates/template-type6.html rendered: - ./issuer-name-type01.html - ./issuer-name-type06.html - ./report-index.html tier_mapping: L0: Signal card (rating + outlook + key signals today + completeness lamp) L1: Snapshot (four-dimension radar + key anomalies + rating comparison) L2: Deep Report (pyramid layer-by-layer + dual-track cross-comparison + completeness report) completeness_lamp: yellow (medium confidence, caliber per output-layered-framework §8.4) source_analysis: ./analysis-artifact.yaml
fixed-income-credit-analysis skill — consumes its Analysis Artifact. Without an Analysis Artifact, this skill does not start (it does not perform analysis itself; go back upstream to complete analysis first).credit-qa-verifier — after the Delivery Note is produced, hand off to the QA verification skill for pre-delivery final review (quality gates + mandatory checks); deliver only after QA passes.dev/engine/output-layered-framework.md; template lists are based on dev/engine/work-path-registry.md.insufficient information to evaluate) must retain that annotation in the report; do not fabricate values to make the report look complete.planned, must explicitly state "this template is under development" and provide alternative deliverable items available for that path; do not fabricate rendered output.report-index.html must be generated from dev/templates/report-index.html, linking to all reports with relative paths and descriptions. The index is appended to rendered only, not to templates_used.dev/templates/template-base.css and inline its content into each report's <style> block, replacing the <link> tag. Reports must render correctly when copied to any location or forwarded to others.{...}/{{...}} token is incomplete — fill every field from the template's placeholders manifest entry or mark it explicitly n/a.rendered, source_analysis) must be relative paths. No absolute paths (e.g., a full Windows or Unix path starting with a drive letter or root slash). Reports travel together in one directory — use ./filename not absolute paths.<issuer-slug>-type<NN>.html. The index is report-index.html.references/report-mapping.md — Path → template → tier mapping view (pointer only, no copied values)dev/engine/pipeline-contract.md — Four-stage chain I/O contract (artifact schema single source of truth)dev/engine/work-path-registry.md — Work path registry (templates field single source of truth)dev/engine/output-layered-framework.md — L0/L1/L2 tiered output (tier semantics single source of truth)Other measured skills in the registry, with their headline benchmark lift.