Pitch Deck

pitch-deck

Triggers

• Investment pitch deck
• investment committee presentation
• buy-side pitch
• sell-side pitch
• investment thesis slides
• executive summary presentation
• financial presentation
• board deck
• investor presentation
• strategy deck

Defaults

Methodology

1. Retrieval Scope

This skill operates with retrieval_scope: structured_only. It performs structured data retrieval only (XBRL facts, financials, earnings calendar) — no unstructured document search. Document-retrieval tools are excluded from allowed_tools.

2. Retrieval Strategy

Follows the retrieval strategy decision tree in contracts/retrieval.md. Primary branch: (a) Structured Data Query. Resolve the canonical ticker first (exact → fuzzy alias → share-class) before any data call.

3. Temporal Scope

Default lookback: 4 fiscal quarter(s); maximum: 8. The default balances recency against the trend window this analysis requires.

4. Tool Allowlist

Per frontmatter allowed_tools:

• search_companies — ticker resolution + company context (entity-alias fuzzy match)
• search_xbrl_facts — primary structured financial facts (is_primary default)
• get_company_financials — consolidated IS/BS/CF highlights
• get_company_profile — sector/industry classification + metadata
• search_earnings_calendar — EPS actual/estimate/surprise + report dates
• list_xbrl_concepts — XBRL concept discovery for non-standard line items (namespace param; default us-gaap — use ifrs-full for foreign filers)

5. Protocol

1. Pre-flight (mandatory): call get_company_fiscal_calendar/{ticker} then get_ticker_coverage/{ticker}; route on coverage.
2. Concept discovery (non-standard concepts only): list_xbrl_concepts(query=<term>, ticker=<T>).
3. Structured retrieval: search_xbrl_facts(ticker, concept=[...], fiscal_year=[...]) (is_primary default) and/or get_company_financials/{ticker}.
4. Batch rule: 3+ same-tool queries → consolidate via batch_search (≤8 sub-queries).
5. Output: write the deliverable per ## Output File, then append to agentii.md.

Deliverable Chain

Inputs → Build → Validate → Output → Next

1. Inputs: resolved ticker + structured facts (search_xbrl_facts, get_company_financials) and any filing pages from the three-layer protocol.
2. Build: write a self-contained Python script using python-pptx that creates the .pptx deck per ## Output Structure. Execute via Bash: python3 script.py. Verify the .pptx file exists at the output path. If python-pptx is absent, fall back to .md slide spec per contracts/office-tooling.md.
3. Validate: run the ## Validation Gates below.
4. Output: write the artifact path per ## Output File.
5. Next: append to agentii.md; hand off to a downstream pitch/review skill if requested.

Disclaimer (Q139/T137) — REQUIRED, template-owned

This output is presentation-shaped, so it MUST carry the canonical disclaimer from scenarios/templates/disclaimer.md — verbatim, not restated or paraphrased. The clause set is the contract; the wording is the workspace's rendering (Q126).

• Rule 1: include the block as authored. Do not write your own.
• Rule 2: [WORKSPACE] / [AS_OF] / [GENERATED] are FILLED, never shipped. An unfilled placeholder fails the output gate.
• Rule 4: the disclaimer states what the document IS; the badges, epistemic_state and coverage-gaps sections state what each claim IS. Do not let the disclaimer carry a burden the body should.

Why this is written here rather than assumed. This skill has no template and no producer (measured 2026-09-18 — scenarios/templates/ holds neither). So there is nothing yet to mount the disclaimer ON, and check_disclaimer.py reports this output as nothing to gate yet rather than as compliant. Recording the requirement in the output contract means it is already binding when a template or producer is written, instead of being rediscovered afterwards — which is how the thesis report's own disclaimer came to be retrofitted rather than designed in.