Menu
Debug-only ACP sequence probe step that runs a configurable countdown script before producing a structured result with handoff verification.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Draft a LaTeX literature review section. Use this skill when user wants to create an introduction and/or related work section for a research paper. Ensure you can access to the Zotero library through zotero-bridge CLI.
Dynamic HTML generator for literature deep-reading. Use when the user wants to read a paper in depth. Ensure you can access to the Zotero library through zotero-bridge CLI.
Prepare the context for create topic synthesis workflow. Use this skill when user wants to create a new topic. DO NOT invoke unless you can access to the Zotero library through zotero-bridge CLI.
Draft the topic-level core synthesis and knowledge graph completion based on the analysis context from the prepare phase. Use this skill after create/update-topic-synthesis-prepare. DO NOT invoke this skill directly.
Assess library coverage & evidence reliability, propose collection supplementation, and generate the final summary of a topic. Use this skill after topic-synthesis-core-enrichment. DO NOT invoke this skill directly.
Prepare the context for update topic synthesis workflow. Use this skill when user wants to update an existing topic. DO NOT invoke unless you can access to the Zotero library through zotero-bridge CLI.
| name | debug-sequence-countdown-probe |
| description | Debug-only ACP sequence probe step that runs a configurable countdown script before producing a structured result with handoff verification. |
This skill is only for Zotero Agents debug workflows. Do not write Zotero items, notes, preferences, or external files. Use the current working directory as the ACP run workspace.
Read the provided input and parameter values from the run prompt. Produce a
single JSON object on stdout.
Follow these steps in order:
If input.handoff exists (i.e. this is step bravo or charlie):
input.handoff.step_id is present.input.handoff.marker is present and starts with the expected
previous step id followed by a hyphen (e.g. step bravo expects a marker
starting with alpha-; step charlie expects a marker starting with
bravo-).handoff_checks.If input.handoff is absent (i.e. this is the first step alpha), skip this
phase and set handoff_checks to an empty array.
Read parameter.countdown_seconds (default 120 if absent). Run a countdown
script via bash that prints one line per second in the format
Countdown: Ns remaining where N counts down from the configured value to 1.
Example for 120 seconds:
for i in $(seq 120 -1 1); do echo "Countdown: ${i}s remaining"; sleep 1; done; echo "Countdown complete!"
Replace 120 with the actual value of parameter.countdown_seconds. Wait for
the script to finish before proceeding.
After the countdown completes, generate a single JSON object on stdout with the following fields:
kind: always "debug_countdown_probe_result".step_id: copy from parameter.step_id.status: "ok" if all handoff checks passed (or there were none); otherwise
"failed".marker: a string in the format <step_id>-<unix-timestamp-ms> that uniquely
identifies this step's execution.previous_marker: the marker value received from input.handoff, or null
if this is the first step.countdown_seconds: the value of parameter.countdown_seconds (or 120 if
not provided).countdown_completed: true.handoff_checks: array of check objects from phase 1.checks: array summarising all checks performed in this step.diagnostics: array of diagnostic objects (may be empty).Return JSON matching assets/output.schema.json.