proposal
VerifiedCreate, revise, or audit commercial proposals as editable PowerPoint, interactive HTML, or PDF, with proposal logic, case evidence, scope and pricing, presenter scripts, and format-specific validation. Use for client proposals, pitches, tenders, and proposal revisions, rather than general marketing websites.
references/runtime-compatibility.md
View on GitHub# Runtime Compatibility
Use this file to decide whether the current agent/runtime can complete the full proposal package or must downgrade to a blueprint/script-only delivery.
## Compatibility Status
`tested` means the workflow has been exercised in that runtime or by the maintainer/user with this repository. `expected` means the skill is structurally compatible because the runtime can read local skill folders or `SKILL.md`, but full PPTX generation still depends on available presentation tooling.
| Runtime / Agent | Status | Notes |
|---|---|---|
| Claude Code | tested | User-tested with local proposal-generation flow in June 2026. PPTX output still depends on the host's available file and presentation-generation tools. |
| Codex / OpenAI coding agent | tested for repository maintenance and local PPTX demo generation | This repository was edited, validated, and pushed from Codex. Local style-demo PPTX generation was tested with the available presentation runtime, but other Codex installations may differ. |
| Generic `SKILL.md` readers | expected | Should work when the agent can read `SKILL.md` and referenced files. PPTX generation requires a separate presentation backend. |
| Cursor / Windsurf / Trae / Qoder / Antigravity / OpenClaw / Hermes | expected, not maintainer-verified | Expected to work as instruction packs when installed in a readable local skill folder. Verify invocation, file access, and PPTX tooling in the target runtime before relying on auto mode. |
Do not mark a runtime as `tested` unless someone has actually installed or loaded the skill there and run at least a guided or auto proposal workflow.
## Minimum Runtime Capabilities
Required for any mode:
- Can read `SKILL.md` and files under `references/`.
- Can access the user's brief/source files and write output files.
- Can preserve unknowns as `待确认`, `暂无公开数据`, or equivalent.
Required for full `.pptx` delivery:
- One of:
- a native presentation/PPTX generation skill or tool,
- `python-pptx`,
- `pptxgenjs`,
- an Office-compatible exporter,
- PowerPoint/Keynote/LibreOffice automation,
- another runtime-specific presentation backend that can create editable `.pptx` files.
- Ability to save binary `.pptx` files.
- Ability to validate at least ZIP/XML integrity, and preferably render or open the file.
Recommended for visual QA:
- PPTX-to-PNG/PDF rendering, LibreOffice, PowerPoint, Keynote, or a local preview pipeline.
- Screenshot/contact-sheet review for rhythm and layout.
- Full-size slide review for style-critical pages.
Optional:
- Image generation provider such as OpenAI image APIs, Seedream-style APIs, Flux, Midjourney, or another user-configured provider.
- HTML/SVG rendering for style assets such as ink, glass, pixel, collage, or paper texture.
- PDF extraction / image inspection tools for existing decks and source material.
## Dependency Declaration
This skill is not itself a PPTX rendering engine. It is a proposal strategy, writing, visual-system, and QA instruction pack with a fallback PPTX template.
When the user requests a finished `.pptx`, the agent must explicitly identify the available PPTX backend before building:
```markdown
PPTX backend:
Preview/render backend:
Image-generation backend:
Fallback if unavailable:
```
Do not silently claim a PPTX was produced if the runtime only produced an outline, markdown, HTML, screenshots, or a non-editable PDF.
## Fallback Modes
If full PPTX generation is unavailable, use the highest safe fallback:
| Fallback | Deliverables | When To Use |
|---|---|---|
| `blueprint-only` | brief audit, winning thesis, chapters, slide plan, proof objects, visual system, missing info | Runtime cannot create PPTX or user only wants planning. |
| `copy-and-script` | slide-by-slide copy deck plan plus presenter script `.md` | Runtime can write text files but not PPTX. |
| `template-spec` | visual system, layout recipes, palette, typography, page specs | User will build manually or in another tool. |
| `html-demo` | optional visual prototype plus `.md` script | Runtime can render HTML/SVG but cannot create editable PPTX. Clearly mark as non-PPTX prototype. |
| `repair-needed` | generated PPTX plus warning and repair notes | PPTX exists but fails compatibility checks; do not call it final. |
## HTML Demo Stage Contract
Use this when a visual prototype, style sampler, or HTML-to-PPT design reference is created before an editable PPTX.
- Author each slide on a fixed 16:9 stage, preferably `1920x1080`, and scale the whole stage to the viewport. Do not let slide content reflow independently at different browser widths.
- Keep the stage dimensions, slide chrome, folio, title zones, gutters, and lower-third usage consistent across the sample set.
- Use responsive CSS only for fitting the whole stage into the browser window, not for changing the slide composition.
- Render full-size PNG screenshots for QA. Contact sheets are useful for rhythm, but cannot approve text safety distance, overlap, connector continuity, or image hierarchy.
- Do not rely on `scrollHeight`, DOM bounding boxes, or no-console-error checks alone. A slide can pass DOM checks while still looking cramped, visually collided, or unbalanced.
- If the HTML demo will later become PPTX, keep core business text, tables, budgets, KPI, risk registers, and page numbers as editable PPTX elements in the final deck. HTML/SVG/raster layers should mainly carry background texture, hero imagery, collage, device/interface mockups, or style atmosphere.
- If a slide fails full-size visual review, simplify the layout before adding more decorative style. A clean grid is preferable to a distinctive but confusing page.
## Runtime QA
Before final delivery, state:
- runtime/agent used,
- PPTX backend used,
- preview/render method used,
- whether `.pptx` was opened/rendered or only structurally checked,
- any downgraded deliverables,
- unresolved environment limitations.
## Responsive HTML branch
HTML authoring needs file-writing capability; behavioral/visual acceptance needs a supported browser runtime. PDF needs a print/export backend. Responsive HTML is not constrained to the fixed-stage demo engine. If a requested PPTX backend is absent, disclose this and agree an alternative; only unspecified formats may default to HTML. See web-proposals.md for deployed/real-device evidence boundaries.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |