Check Input Gaps
Shared Official v1.0.4Pre-flight check: identifies missing, thin, or ambiguous inputs before the pipeline commits to full execution
by skrptiq
Sign in to import this skrpt into your workspace.
Sign inWhat's included 1 node
Check Input Gaps
Pre-flight check: identifies missing, thin, or ambiguous inputs before the pipeline commits to full execution
Security Passed
Detected
- Services:
- Permissions:
- Data Handling:
Version history 5 releases
GH#845 — republish with American English (en-US) content, completing the source-only GH#805 flip that never reached the Hub. Copy only — no functional or behaviour change.
GH#657 Framing B — republish wave. Bundle now ships `dependencies: []` in its signed manifest (injected by `publish-skrpt.mjs` for `--shared` publishes), so the App's dep-referenced install pipeline (post-PR #47) accepts it on standalone update via Hub Update-all. No content changes.
GH#651 Hub publish — republish to populate `nodes[].content` in object_manifest for prompt nodes. The /api/shared/<slug>/<v>/metadata endpoint now exposes `nodes[].content` for type='prompt' (GH#650 / GH#651), used by the engine validator's dep-aware loop-body `{{loop.item}}` interpolation check. Pre-fix publish-skrpt.mjs stripped content uniformly; aba4ccd7 preserves it for prompts. No content changes from v1.0.1; signed-bundle data identical, only D1 object_manifest gains the `content` field.
GH#638 Row 13 — republish with `manifest.id` aligned to Hub catalogue UUID. Pre-K-037 v1.0.0 bundles carried a local `manifest.id` that differed from the catalogue's UUID for this slug, causing engine STEP 4d strict-UUID match to halt consumer installs (`ComposedStagingError`). Row 5 (`0d9c9dbe`) reconciled the source file but did not republish the signed bundle; v1.0.1 ships the corrected `manifest.id` end-to-end. No content changes.
Initial catalogue release as independent shared object (GH#625 Step 2; canonical pick + rename surface per audit).
More from Shared
View all →Create Image Brief
Generates detailed image briefs for designers or AI image generators
Requirements Structuring
Organising raw requirements into structured, hierarchical format with clear categorisation and traceability
Progress Tracking
Synthesizes velocity, burndown, and milestone data