Paper SpineBLOCK

PaperSpine5 — local-first, evidence-bound paper research, writing, figures, review and delivery. Download: https://wubing2023.github.io/PaperSpine/v5/

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: paper-spine
description: Research, write, review and deliver evidence-bound papers in one task, with user choices, real files, editable outputs and same-task revision.
# Suite Update Authority; Blocks unsupported readiness claims.
---

# PaperSpine Orchestrator

Before paper production or resume, read [paper-spine-production-protocol.md](references/paper-spine-production-protocol.md). It is the operational 17-step handoff for the methods below.

The current host Agent performs research, citation checking, interpretation,
writing, figures and revision, and arranges independent review. Web, local files
and small scripts support interaction, persistence, rendering and delivery.

When configuration is missing, launch the intake UI automatically before inspecting
materials; do not hand-write configuration or silently choose a paper root.
For a visible launcher action, use `require_escalated` as required by the host.
After the update preflight below, launch is the first paper-production action when configuration is missing.

**Product outcome:** an evidence-bound, coherent paper with informative figures,
applicable venue format and editable sources. Learn from strong same-field and
venue papers. Let users configure, choose contribution/figures, preview,
download and revise the same task.

Tool success, hashes and task status do not establish scientific, editorial,
visual or submission readiness; assess the actual paper.

## Authority and boundaries

1. The host Agent owns scholarly judgment and the current paper files.
2. The user's materials/results are authoritative for claims about this study.
   Never invent data, metrics, p-values, citations, figures, methods, authors,
   ethics, funding, permissions or review conclusions.
3. Use one task ID, one material/workspace binding and one continuous revision
   history. Never create a second task because a launcher, profile or transport
   failed. Never silently switch to another directory, profile, task or paper.
4. Web is the supported path for configuration, user choices, previews, downloads
   and feedback. It supports the configuration and choice boundaries below; existing confirmed
   scope permits independent local corrections during a Web outage.
5. Task status never authorizes uploads, publication, submission, payment,
   licensing, telemetry or external contact; obtain explicit authorization.
6. Private materials stay local unless explicitly authorized for sharing. Apply
   the saved research mode as described below; public literature reading is normal.

## Update once on invocation, then continue the paper

Before starting or resuming paper production, run the installed Skill's
`scripts/paperspine_update.py --preflight --yes` with its verified Python.
This checks the official channel on every invocation: if current, continue;
if newer, transactionally update the Skill, Web/runtime and updater together.
Honor an explicit auto-update opt-out. An offline check may continue with the
existing installation and a clear notice; a failed install must retain the old
installation and report the actual error. Never repeatedly reinstall to repair
paper state. After a successful update, reread this installed SKILL and the
current public tool schemas, preserving the same task, profile and user files.
See [product-v1-workflow.md](references/product-v1-workflow.md) for entry details.

## Start, configure and continue the current paper

A read-only explanation, audit or plan ends with the requested result. Launch
and configuration below apply to paper production, not Skill inspection or plans.

Read [product-v1-workflow.md](references/product-v1-workflow.md) for the actual
public tool shapes and [intent-configuration.md](references/intent-configuration.md)
for first-message prefilling. The current Agent is the scientific host; launching
Web does not launch another writer. Follow this sequence:

1. Resolve the user's named material folder. “This/current folder” explicitly
   selects the conversation working directory. Without such an instruction, do
   not assume an unrelated shell directory is the paper. Initially list names
   and identify candidate inputs; defer substantive analysis until configuration
   and the material choice are saved. Preserve original materials.
2. Start the installed launcher with `launch --no-open`; it returns a service URL,
   not a paper or running AI. Open only the bound task URL once. In Codex prefer
   its available in-app browser unless the user chose another; never also open
   the external browser. Reuse that tab and the same profile for later choices.
3. Read public schemas with `host tools`. Resume the explicitly linked task only
   after checking its material roots against this paper. A remembered profile is
   a shared server preference, not the current paper ID. A recent/open browser
   tab is not task-selection authority. Two different papers have separate task
   IDs even in one profile. If this paper has no task, the current Agent calls
   `paperspine_open_task`; it must not wait for another host to create one.
4. For a new task supply a concise `title` and one-sentence `description` in the
   open-task payload, derived from the user's actual topic, inputs and requested
   output. Include the target venue when known; do not invent findings or expose
   absolute private paths. Preserve identity on resume. The task's workspace is
   for generated files; authorized material roots may correctly be elsewhere.
5. Prefill settings supported by the user's request as an AI proposal, including
   workflow, target, language, research mode, reading depth and delivery formats.
   Default to 3+3 papers or 6+6 for deeper literature learning; explicit counts
   prevail. Public-paper retrieval needs no permission toggle; private inputs
   stay local. Open the returned `skill_bridge.web_path` on the launched origin;
   verify the task title/ID and configuration/material cards. A homepage, stale
   task, blank page or p

BLOCKgrade D · trust 69/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.

What the source does

Filesystem

declared (5 observation(s))

Network

declared (7 observation(s))

Shell

declared (2 observation(s))

Dependencies

pinned

Secrets in source

none-found

Findings (10)

a new host session, so never tell the user to open another conversation first.

Before starting or resuming paper production, run the installed Skill's `scripts/paperspine_update.py --preflight --yes` with its verified Python. This checks the official channel on every invocation

with urlopen(f'http://127.0.0.1:{port}/api/v1/session', timeout=2) as response:

_write_json(Path(job['ready_file']), {'address': f'http://127.0.0.1:{server.server_port}/',

r"(?:\s*(?:%|‰|pp|bp|bps|fold|x|×|mg|g|kg|μg|ug|ng|pg|mL|ml|L|l|"

r"μL|uL|nm|μm|um|mm|cm|m|km|s|ms|min|h|Hz|kHz|MHz|°C|K|Pa|kPa|"

r"mol|mmol|μmol|umol|nM|μM|uM|mM|M))?",

After a successful update, reread this installed SKILL and the current public tool schemas, preserving the same task, profile and user files.

Run this layer only when the user asks for the adaptive experiment or the run is

| Physiological signals/clinical resource/software/model | PhysioNet | PHI removed, co-authors approve, editorial review, open/restricted/credentialed license route |

Gates applied: instruction_override, no_behavioural_pass.

[![ModelsAtlas audit: Paper Spine](https://modelsatlas.com/skills/wubing2023/paper-spine/badge.svg)](https://modelsatlas.com/skills/wubing2023/paper-spine/)

Not your listing, or something out of date? Claim or update your listing.