Back to catalogue

Cross-Provider Technical Review

Content Creator Official v1.0.17

Draft with one AI model, critique with another, revise until the reviewer passes — better output through model diversity

by skrptiq

adversarial-review cross-provider loops technical-writing writing
workflow Updated 18 July 2026 5 nodes 1 download

Sign in to import this skrpt into your workspace.

Sign in
What's included 5 nodes
1 workflow 2 skills 2 prompts
workflow (1)

Cross-Provider Technical Review

Draft with one AI model, critique with another, revise until the reviewer passes — better output through model diversity

skills (2)

Adversarial Review

Critiques technical content from a different perspective — the review side of the cross-provider loop

Technical Drafting

Drafts or revises technical content — the generation side of the cross-provider review loop

prompts (2)

Draft Technical Content

Generates or revises a technical blog post — first pass creates from scratch, subsequent passes incorporate review feedback

Review Adversarially

Critiques a technical draft from an adversarial perspective — finds weak arguments, gaps, and unclear explanations

Requirements 1 service
Services
  • LLM Service
Security Passed
All checks passed v1.0.17 · scanner v3.3.0

Detected

  • Services: llm-service
  • Permissions:
  • Data Handling:
Version history 15 releases
v1.0.17 latest 18 July 2026

GH#863 Wave 3 (Tier-3 tail) — the output_step (language-polish) was polishing its positional-previous step (a validation/review), not the deliverable, because polish-language was pinned pre-`source`-slot. Repinned polish-language 1.0.1→1.0.6 and bound language-polish `source` ← "Technical Drafting" (the real deliverable producer). No new steps; no other change.

v1.0.16 3 July 2026

GH#745 — declare per-step `output: {name, type}` on every execution step (draft/text, adversarial_review/text, polished_content/text, consistency_verdict/decision). Lights up the #744 rich flow-map. Content-only; no bindings or logic changes.

v1.0.15 7 June 2026

Fix-forward after Row 3b v1.0.14 publish failure. The v1.0.14 per-skrpt CI's "Register version with Hub API" step failed because the consumer's source `manifest.id` (822b4944…) did not match the D1 catalogue row's id (14310d87…) — a legacy drift from before Action 6 (`0bcc5ae0`) made publish-skrpt.mjs Step 2 INSERT use `manifest.id` for the D1 id column. v1.0.15 reconciles the source `manifest.id` to the catalogue authoritative value (Row-5-equivalent for consumers) and republishes. Per Adj-1: no re-tag of v1.0.14; the orphaned GitHub release artefact stays inert (no D1 versions row, no consumer pinned it).

v1.0.13 22 May 2026

Wave 2: re-signed with canonical engine signing pipeline.

v1.0.10 19 May 2026

Signature fix — RELEASE_NOTES.md now included in integrity checksum.

v1.0.9 19 May 2026

Initial catalogue release with full structural and content-quality validation. All scanner checks pass.

v1.0.8 18 May 2026

Release notes unavailable for this version.

v1.0.7 14 May 2026

Release notes unavailable for this version.

v1.0.6 14 May 2026

Release notes unavailable for this version.

v1.0.5 13 May 2026

Release notes unavailable for this version.

v1.0.4 11 May 2026

Release notes unavailable for this version.

v1.0.3 27 April 2026

Release notes unavailable for this version.

v1.0.2 25 April 2026

Release notes unavailable for this version.

v1.0.1 19 April 2026

Release notes unavailable for this version.

v1.0.0 19 April 2026

Release notes unavailable for this version.

More from Content Creator

View all →

Send feedback

Sign in to send feedback — it lets us follow up and keeps the tracker free of spam.