CC resubmit-pipeline
Workflow 5: orchestrate a text-only resubmit of a polished paper to a different venue under hard constraints (no new experiments, no bib edits, no framework changes, never overwrite prior submissions). Use when user says "resubmit pipeline", "重投流程", "port paper to <new venue>", "resubmit to <venue>", "tighten paper for resubmission", or has a rejected/withdrawn paper to move to a different top venue under tight time budget.
Workflow 5: orchestrate a text-only resubmit of a polished paper to a different venue under hard constraints (no new experiments, no bib edits, no framework…
As a process C 63/100 · Has gaps — References files that are not bundled: ../shared-references/reviewer-backends.md, ../integrity-forensics/SKILL.md, templates/<venue>.tex
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bash(*)allowed-tools: Bash(*) Read Write Edit Grep Glob Skill mcp__codex__codex mcp__codex__codex-reply
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 8338 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../shared-references/reviewer-backends.md - warning
missing-refreference to a missing file: ../integrity-forensics/SKILL.md - warning
missing-refreference to a missing file: templates/<venue>.tex - note
edit-residuethe text marks something as outdated (lines 43, 60): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 63/100
- 0Tools and files. 3 referenced file(s) missing: ../shared-references/reviewer-backends.md, ../integrity-forensics/SKILL.md, templates/<venue>.tex
- 20When it triggers. No condition that starts the skill
- 40Execution cost. Instruction body is 8338 tokens: crowds the task out of the window
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 86 steps, 1 vague phrases
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (25 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 427: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 86 items
- +3Output format is stated explicitly
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.