@laitszkin/apollo-toolkit 2.0.0

package/video-production/references/roles-json.md

@@ -0,0 +1,41 @@
+# `roles.json` Definition
+
+Use this schema when preparing recurring-role prompts:
+
+- `<project_dir>/roles/roles.json`
+
+## JSON Shape
+
+```json
+{
+  "characters": [
+    {
+      "id": "lin_xia",
+      "name": "Lin Xia",
+      "appearance": "short black hair, amber eyes, slim build",
+      "outfit": "dark trench coat, silver pendant, leather boots",
+      "description": "standing calmly, observant expression"
+    }
+  ]
+}
+```
+
+## Rules
+
+- Top-level key must be `characters` (array).
+- If the file does not exist, create `roles.json` first with this schema before prompt generation.
+- Each character entry must include:
+  - `id`
+  - `name`
+  - `appearance`
+  - `outfit`
+  - `description`
+- Reuse existing role entries first; add only missing roles.
+- Keep role `id` stable so prompts can reference the same character across scenes.
+- If there are no recurring roles, use:
+
+```json
+{"characters": []}
+```
+
+Use this shared file so long-video workflows can reuse the same role definitions across runs within one project.

package/weekly-financial-event-report/SKILL.md

@@ -0,0 +1,195 @@
+---
+name: weekly-financial-event-report
+description: Read a user-specified PDF that marks the week's key financial events, deeply research each marked event with current sources, capture any additional breaking financial developments, and produce a concise Chinese-capable PDF briefing that explains what happened and why it matters.
+---
+
+# Weekly Financial Event Report
+
+## Dependencies
+
+- Required: `pdf` to read the source PDF and render the final report.
+- Conditional: none.
+- Optional: none.
+- Fallback: If `pdf` is unavailable, stop and report the missing dependency instead of improvising another PDF workflow.
+
+## Standards
+
+- Evidence: Research only events explicitly marked in the source PDF plus clearly material breaking developments, and verify claims with current authoritative sources.
+- Execution: Read the PDF first, lock the research window, research each marked event, then hand the final briefing to `pdf` for rendering and QA.
+- Quality: Keep the report concise, Chinese-compatible, and explicit about source-versus-breaking events, conflicts, uncertainty, and PDF font safety.
+- Output: Save only the final standardized PDF under the month folder using the financial-event-report naming scheme.
+
+## Overview
+
+Turn a marked weekly finance PDF into a short, evidence-based report that a user can read in a few minutes. The workflow starts from the user's source PDF, extracts the explicitly marked key events, validates each event with current reporting and primary sources, adds any material breaking financial developments, and delivers the final briefing as a Chinese-compatible PDF.
+
+## Behavior Contract
+
+GIVEN the user provides a PDF that marks weekly key financial events  
+WHEN the agent uses this skill  
+THEN the agent must read the PDF first  
+AND identify only the events that are explicitly marked or clearly designated in the document  
+AND research each marked event with current sources  
+AND capture any additional breaking financial events that materially changed the week's interpretation  
+AND produce a concise, standardized PDF report that explains the event timeline, market impact, and why the events matter  
+AND default the report language to Chinese unless the user explicitly requests another language.
+
+## Required Inputs
+
+Before writing, confirm these facts from the PDF, user context, or current sources:
+
+- Path to the source PDF
+- The week or date range covered by the source PDF
+- Any user-specified geography, market, sector, or asset-class focus
+- Output directory if the user specified one
+- Language preference if different from the Chinese default
+
+Do not guess any input that materially changes the research window or report scope.
+
+## Source Rules
+
+- Use current web research for time-sensitive claims.
+- Prefer primary or authoritative sources first:
+  - central banks
+  - government statistical agencies
+  - regulators
+  - exchanges
+  - company filings or official releases
+- Use high-quality financial reporting to triangulate facts, surface timelines, or explain market reactions.
+- Record the event date or publication date for every material claim.
+- Separate confirmed facts from interpretation.
+- Distinguish between:
+  - events explicitly marked in the source PDF
+  - additional breaking events added during research
+
+## Workflow
+
+### 1) Read the source PDF and extract the marked events
+
+- Use the `pdf` skill to open and extract the source PDF.
+- Identify the document's explicit markers, such as highlights, comments, callouts, boxed sections, bookmarks, or clearly labeled weekly key-event sections.
+- Build a source-event table before searching. For each marked event capture:
+  - page number
+  - event label in the source PDF
+  - date or date range if present
+  - short note about why the source document highlighted it
+- If the PDF does not expose machine-readable annotations, fall back to clearly visible marked sections or headings.
+- If the document still does not make the marked events unambiguous, stop and report the ambiguity rather than inventing events.
+
+### 2) Lock the research window
+
+- Prefer the exact week or date range stated in the source PDF.
+- If the PDF lacks an explicit range, infer the window only from unambiguous document evidence such as the title, cover date, or repeated date markers.
+- If the research window remains unclear, report the ambiguity instead of assuming one.
+- State exact calendar dates and timezone in the report.
+
+### 3) Research each marked event deeply
+
+- For every marked event, gather:
+  - what happened
+  - when it happened
+  - the direct trigger or official announcement
+  - market or macro channels affected
+  - the immediate reaction
+  - why the event matters after the initial headline
+- Prefer direct evidence over commentary.
+- When multiple sources disagree, explain the conflict instead of forcing a single narrative.
+
+### 4) Capture additional breaking financial events
+
+- Search for material financial or macro developments that occurred within the report window or after the source PDF was prepared but before report finalization.
+- Add an event only when it materially changes the user's understanding of the week, such as:
+  - surprise central-bank communication
+  - emergency policy action
+  - major bank, fund, or exchange stress
+  - sharp cross-asset repricing
+  - geopolitical shocks with direct market spillovers
+  - unexpected company events with broad market consequences
+- Label these clearly as newly added breaking events rather than source-PDF items.
+
+### 5) Write the standardized report
+
+- Start from `assets/financial_event_report_template.md`.
+- Keep the report short enough for a fast read; default target is roughly 2-5 pages unless the user asks otherwise.
+- Default to Chinese if the user does not specify another language.
+- Explain both the sequence of events and the practical market impact.
+- For each marked event, answer:
+  - what happened
+  - why it mattered
+  - what markets or sectors moved
+  - what remains unresolved
+- Include a dedicated section for additional breaking events.
+- Include a final section on implications and watchpoints.
+
+### 6) Prepare PDF requirements for the `pdf` skill
+
+- The final PDF must support Chinese text cleanly.
+- Pass the font and rendering requirements to the `pdf` skill instead of implementing a separate export path here.
+- On macOS, require the `pdf` skill to verify the font path before rendering.
+- When the PDF workflow allows explicit font selection, ask the `pdf` skill to prefer a locally verified CJK font in this order:
+  - `/System/Library/Fonts/Hiragino Sans GB.ttc`
+  - `/System/Library/Fonts/Supplemental/Songti.ttc`
+  - `/Library/Fonts/Arial Unicode.ttf`
+  - `/System/Library/Fonts/STHeiti Medium.ttc`
+  - `/System/Library/Fonts/STHeiti Light.ttc`
+- Do not assume `PingFang` is available on every macOS host.
+- If the active `pdf` workflow already has a verified Chinese-safe default on the current machine, reuse that verified default instead of overriding it.
+- Avoid emoji and uncommon glyphs that often break during rendering.
+
+### 7) Delegate rendering and PDF QA to the `pdf` skill
+
+- Hand the completed report content and font requirements to the `pdf` skill for rendering.
+- Require the `pdf` skill to open the rendered PDF locally before finishing.
+- Require the `pdf` skill to capture temporary screenshots from the rendered PDF before considering the report complete.
+- Require the `pdf` skill to inspect at least:
+  - the first page
+  - one page with a table or timeline
+  - one page with dense paragraph text
+- Require the `pdf` skill to verify:
+  - Chinese glyphs render correctly
+  - no tofu boxes or missing characters
+  - headings and body text are visually balanced
+  - line wrapping is readable
+  - tables remain legible
+- Treat those screenshots as temporary QA artifacts only.
+- If the output fails visual QA, revise the content or PDF requirements and call the `pdf` skill again.
+- After the final PDF passes QA, require the `pdf` skill to delete all temporary screenshots before finishing.
+
+## Standard Report Requirements
+
+The report must contain these sections in order:
+
+1. Report title and source document
+2. Generated time and research window
+3. Executive summary
+4. Source PDF marked-event overview
+5. Key marked events and deep analysis
+6. Additional breaking financial events
+7. Cross-market impact and implications
+8. Watchpoints for the coming days
+9. Risks, uncertainty, and source limitations
+
+## File Layout Rules
+
+- Store reports inside a month-based folder named `YYYY-MM`.
+- If the user gives a base output directory, create or reuse `YYYY-MM` beneath it.
+- If the user does not give a base output directory, use the current working directory as the base.
+- Keep only the final PDF as the persistent deliverable.
+- Remove temporary working files after rendering.
+- Do not keep QA screenshots unless the user explicitly asks to preserve them.
+
+## Report Naming Rules
+
+- The visible report title must use this exact pattern:
+  - `[YYYY/M/D-YYYY/M/D]-financial-event-report`
+- Build the date range from the exact research window start and end dates.
+- Because `/` is not safe in macOS filenames, the PDF filename must use:
+  - `[YYYY-M-D-YYYY-M-D]-financial-event-report.pdf`
+
+## Output Rules
+
+- The default deliverable is a PDF.
+- Save the final file at `YYYY-MM/[YYYY-M-D-YYYY-M-D]-financial-event-report.pdf`.
+- The default language is Chinese unless the user explicitly requests another language.
+- Keep the report evidence-based, concise, and decision-useful.
+- Make it easy for a user to understand the week's important financial developments within a few minutes.

package/weekly-financial-event-report/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Weekly Financial Event Report"
+  short_description: "Turn a marked finance PDF into a concise Chinese-capable PDF briefing"
+  default_prompt: "Use $weekly-financial-event-report to read the user's marked weekly finance PDF, extract the explicitly marked events, research each one with current sources, add any material breaking financial developments, prepare the report content, and then delegate final PDF generation and PDF QA to $pdf."

package/weekly-financial-event-report/assets/financial_event_report_template.md

@@ -0,0 +1,53 @@
+# {{report_title}}
+
+- Source PDF: {{source_pdf}}
+- Generated at: {{generated_at}}
+- Research window: {{window_start}} to {{window_end}} ({{timezone}})
+- Output file: {{report_filename}}
+- Verified font: {{font_name_or_path}}
+- Scope: {{scope}}
+- Language: {{language}}
+
+## {{executive_summary_heading}}
+
+{{executive_summary}}
+
+## {{source_event_overview_heading}}
+
+| Page | Marked event | Source note | Why it was highlighted |
+| --- | --- | --- | --- |
+| {{page_1}} | {{source_event_1}} | {{source_note_1}} | {{source_reason_1}} |
+
+## {{key_events_analysis_heading}}
+
+### {{event_heading_1}}
+
+- What happened: {{what_happened_1}}
+- Why it mattered: {{why_it_mattered_1}}
+- Immediate market reaction: {{market_reaction_1}}
+- What still matters now: {{follow_through_1}}
+- Sources: {{sources_1}}
+
+## {{breaking_events_heading}}
+
+| Date | Event | Why it changed the picture | Most affected assets |
+| --- | --- | --- | --- |
+| {{breaking_date_1}} | {{breaking_event_1}} | {{breaking_impact_1}} | {{breaking_assets_1}} |
+
+## {{cross_market_impact_heading}}
+
+- Rates: {{rates_impact}}
+- Equities: {{equities_impact}}
+- Foreign exchange: {{fx_impact}}
+- Commodities: {{commodities_impact}}
+- Credit or liquidity: {{credit_liquidity_impact}}
+
+## {{watchpoints_heading}}
+
+| Date | Watchpoint | Why it matters | Related events or assets |
+| --- | --- | --- | --- |
+| {{watch_date_1}} | {{watchpoint_1}} | {{watch_impact_1}} | {{watch_assets_1}} |
+
+## {{risks_and_limitations_heading}}
+
+{{risks_and_limitations}}