Menu
Debug-only ACP sequence probe step that emits structured markers and optionally writes a workspace sentinel.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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.
Debug-only ACP sequence probe step that runs a configurable countdown script before producing a structured result with handoff verification.
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.
| name | debug-sequence-probe-emit |
| description | Debug-only ACP sequence probe step that emits structured markers and optionally writes a workspace sentinel. |
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.
Rules:
probe_id from parameter.probe_id.public_marker from parameter.public_marker.secret_marker from parameter.secret_marker.parameter.write_sentinel is true, create the relative file named by
parameter.sentinel_path under the current working directory. Create parent
directories as needed. The file content must be JSON containing probe_id,
public_marker, secret_marker, and sentinel_path.artifact_path to the absolute local path of
that file.parameter.write_sentinel is not true.assets/output.schema.json.Output example:
{
"kind": "debug_sequence_probe_result",
"probe_id": "linear",
"status": "ok",
"public_marker": "linear-public",
"secret_marker": "linear-secret",
"sentinel_path": "",
"checks": [{ "name": "emit", "ok": true }],
"diagnostics": []
}