Immutable. This exact content is served forever at /api/v1/blob/f6baad12d2c5d7e4.
--- name: submission_ready description: Screens Dealum applications in the Application or Under review stage for completeness and SICTIC initial eligibility, then drafts an internal proposed action for Ops. Use for one or more named startups or an overnight batch of all in-scope submissions. --- # Submission Ready Review only the startup's Dealum application and documents submitted through Dealum. Do not use separately scraped website or LinkedIn content as evidence. ## Workflow 1. Retrieve Dealum applications and keep only `Application` and `Under review`. A named out-of-scope startup produces no artifacts. 2. With named startups, force a fresh Dealum import. Without names, process all in-scope applications sequentially using the six-hour per-startup gate. 3. Replace the Dealum snapshot only after all attachments download. 4. Reuse the freshness-tracked JSON audit when substantive submission content is unchanged. A stage-only change creates a new response without rerunning the audit checks. 5. Load the policy, structured Markdown checklist, output instructions, and JSON response schema from `config/submission_ready/`. Constrain the proposed actions in the schema to those permitted for the current Dealum stage. 6. Run every checklist item through `batch_audit` with the `Pass`, `Fail`, and `Unclear` status scale, then render the common Markdown table through `json_to_markdown_table`. 7. Use `Unclear` whenever the submitted evidence is missing, ambiguous, conflicting, or not retrievable. Never infer a pass or fail. 8. Save the canonical JSON audit plus a timestamped rendered checklist and internal proposed action through `InsightFile`. Humans decide whether to contact the startup or change its Dealum stage; the skill does neither. Use `config_cache_key()` over the complete submission-ready configuration, stage, and canonical audit when evaluating artifact freshness. 9. Return a flat `list[InsightFile]` containing checklist then response for each successful startup. The canonical JSON audits remain internal; any generated failure report is appended to the returned list. The result is an Ops screening report, not a jury assessment. Do not evaluate business attractiveness, pitch quality, or investment readiness. ## Usage ```bash conda run -n sictic-env python -m skills.harness /submission_ready conda run -n sictic-env python -m skills.harness /submission_ready "<STARTUP_NAME>" ```