科研 Skill
投稿前最终核查
verifying-before-submission
Runs a final submission gate covering argument, citations, terminology, and venue requirements. Use just before a manuscript is submitted or resubmitted.
SKILL.md
Verifying Before Submission
Purpose
Provide the final release gate for a manuscript package. This skill does not repeat every earlier method in full. It verifies that required audits were performed, that their blocking issues were resolved, that the submitted files correspond to the reviewed version, and that no unsupported claim of readiness is made.
A polished PDF is not evidence of scholarly readiness. Submission readiness is a package-level state supported by traceable checks.
Contract
Accepts the final manuscript package, target venue instructions, author and funding information, prior gate reports, revision letter, supplementary files, declarations, and submission metadata.
Requires the exact files intended for submission, current venue requirements, and evidence from citation, terminology, manuscript, and peer-review gates where applicable.
Produces a package inventory, requirement matrix, unresolved-risk register, privacy and metadata check, final GateReport, and a precise PASS, CONDITIONAL PASS, or FAIL decision.
May produce a submission checklist, filename corrections, missing-document list, anonymization actions, or a release manifest with checksums.
Fails when central gate reports are absent, a blocking issue remains, the submitted file differs from the reviewed file, venue requirements cannot be checked, required declarations are missing, or the requester asks for readiness despite unresolved evidence.
Guarantees that the readiness decision is tied to documented checks and that unresolved blocking issues prevent a PASS.
Does not guarantee acceptance, legal compliance in every jurisdiction, factual truth beyond completed audits, successful file upload, or compatibility with an unknown submission system.
When to use
Use immediately before first submission, revised submission, accepted-manuscript delivery, conference upload, book-chapter handoff, repository deposit, or any claim that a manuscript is “submission-ready.”
Run it again whenever the manuscript changes after the gate. Even a small edit can alter page numbers, citations, anonymization, word count, figures, or response-letter references.
Inputs required
Provide:
- Exact final manuscript file and all supplementary files.
- Current venue author instructions or verified requirement summary.
- Author names, affiliations, ORCID information, corresponding-author details, and anonymization status.
- Abstract, keywords, title, running title, and word count where required.
- Citation audit, terminology audit, manuscript review, and peer-review-response reports as applicable.
- Funding, conflict-of-interest, ethics, data, AI-use, copyright, permission, and acknowledgments statements.
- Figures, tables, captions, accessibility text, permissions, and source files where required.
- A declaration of which file version is authoritative.
If the venue instructions are not available or current, the venue-compliance portion cannot pass.
Procedure
1. Freeze and inventory the package
List every intended file with filename, role, version, modification date, and checksum where possible. Identify the authoritative manuscript. Exclude working notes, tracked-change files, personal data, hidden drafts, and unrelated attachments unless required.
2. Verify prior quality gates
Check the latest status and evidence for:
- research question and scope;
- argument and close reading;
- citation audit;
- terminology consistency;
- manuscript review;
- peer-review response for resubmission.
A prior PASS is invalidated if the relevant content changed afterward. Record which checks must be rerun.
3. Verify venue requirements
Create a requirement matrix covering format, genre, length, language, file type, title page, abstract, keywords, headings, notes, references, figures, tables, supplementary material, anonymization, declarations, and submission-system fields.
Use current official instructions. Do not infer requirements from another journal, an old author template, or a third-party blog.
4. Verify manuscript identity and integrity
Check title, author order, affiliations, corresponding author, ORCID, funding, acknowledgments, and version consistency. Ensure abstract, keywords, headings, tables, figures, appendices, notes, and references belong to the same manuscript version.
Confirm that response-letter page and line references match the final revised file.
5. Verify anonymization and privacy
For blinded review, inspect title page, manuscript text, acknowledgments, self-citations, file properties, comments, tracked changes, embedded paths, image metadata, supplementary files, repository links, and filenames. Do not remove information required by the venue; follow its blinding policy.
Check that personal, confidential, student, participant, peer-review, or archival data are not exposed improperly.
6. Verify citations and permissions
Confirm that no blocking citation issue remains and that revisions did not create new orphan references. Check permissions or fair-use documentation for images, tables, long quotations, translated material, archival reproductions, and third-party content as required.
This skill records permission status; it does not provide legal advice.
7. Verify declarations and responsible AI disclosure
Check required statements for funding, conflicts, ethics, consent, data availability, author contributions, originality, prior publication, preprints, and AI assistance. The disclosure must reflect actual use and the venue's policy. Do not invent compliance or conceal prohibited use.
8. Verify technical presentation
Inspect page numbers, line numbers, fonts, margins, headings, cross-references, table and figure numbering, captions, alternative text where required, equation and symbol rendering, hyperlinks, bibliography formatting, and file opening. Check that no placeholder, comment, broken field, or unresolved marker remains.
Search explicitly for markers such as:
TODO
TBD
[CITATION NEEDED]
[AUTHOR DECISION REQUIRED]
XXX
placeholder
Do not remove an unresolved marker merely to pass the gate; resolve or report it.
9. Conduct package-difference check
Compare the final package with the version that passed prior review. Record post-review changes. If substantive claims, quotations, citations, terminology, or structure changed, route back to the relevant skill before deciding readiness.
10. Classify remaining issues
Use:
- blocking: prevents valid submission or makes a material scholarly or ethical claim unreliable;
- non-blocking: does not invalidate submission but should be corrected or disclosed;
- researcher decision required: cannot be decided procedurally;
- external authority required: editor, rights holder, ethics office, legal counsel, or specialist must decide.
11. Issue the final gate
Return PASS only when all mandatory requirements within scope are evidenced, no blocking issue remains, and the exact package has been checked. CONDITIONAL PASS is allowed only when the package may proceed under a clearly stated external condition that does not invalidate the current scholarly claims. Return FAIL for missing audits, unresolved citations, false revision claims, privacy exposure, missing declarations, requirement mismatch, or version inconsistency.
Stop signals
Stop and fail or request action when:
- the exact final files are not available;
- official venue requirements cannot be verified;
- the manuscript changed after its last relevant audit;
- a central citation or quotation remains unverified;
- required author, ethics, funding, permission, or AI-use information is unknown;
- anonymization conflicts with venue policy;
- response-letter claims do not match the manuscript;
- hidden metadata exposes identities or confidential information;
- the requester asks for a
PASSdespite a blocker.
Completion criteria
Completion requires:
- a frozen package inventory;
- a current venue-requirement matrix;
- verified prior gate statuses;
- author, anonymity, privacy, and declaration checks;
- citation, terminology, figure, table, permission, and metadata status;
- no unresolved placeholders;
- package/version consistency;
- explicit blocking and non-blocking lists;
- a final status supported by evidence.
Anti-fabrication rules
Do not claim compliance with instructions that were not checked. Do not invent ethics approval, permission, funding, author consent, ORCID, word count, AI disclosure, or rights status. Do not report a file as inspected when only its filename is known. Do not turn missing information into “not applicable” without researcher confirmation.
A FAIL is correct when evidence is missing. The purpose of this skill is not to make every package pass.
Output format
Use templates/submission-gate.md and include:
- Authoritative package inventory.
- Venue requirement matrix.
- Prior gate status table.
- Scholarly-content checks.
- Citation and terminology checks.
- Author, privacy, anonymization, and metadata checks.
- Ethics, funding, permission, and AI disclosure checks.
- Technical file checks.
- Blocking and non-blocking issue registers.
- Required next actions.
Gate report
Gate: Submission Verification
Status: PASS | CONDITIONAL PASS | FAIL
Evidence checked:
Blocking issues:
Non-blocking risks:
Researcher decisions required:
External authority required:
Required next action:
Verified package identifier:
Next skill:
Good invocation
Verify the exact files in this submission folder against the current journal instructions and prior audit reports. Fail the gate if the manuscript changed after citation audit or if any required disclosure is unknown.
Bad invocation
Mark this submission ready now. I do not have the final files or journal instructions, but the prose looks polished.
The bad invocation mistakes appearance for verified readiness and MUST receive FAIL.
Next skills
auditing-citationswhen references changed or remain unresolved.checking-terminology-consistencyafter late conceptual edits.reviewing-manuscriptafter substantive changes.responding-to-peer-reviewfor mismatch between revision letter and manuscript.using-humanities-superpowersto route any failed gate.
Friction triggers
Create completion friction when polished presentation masks unresolved blockers, open friction, changed dependencies, missing decisions, or stale gate validity.
Friction checks
Reconfirm the exact package, every controlling gate's status and validity, unresolved friction, reopened decisions, ledger conflicts, and post-audit changes.
Judgment boundary
The agent may report readiness evidence and risks but cannot authorize submission, accept scholarly risk, or convert a missing researcher decision into approval.
Evidence ledger updates
Confirm that final claims still point to current ledger entries and that contradicting, qualifying, disputed, or insufficient standing has not been hidden.
Interpretation history impact
Verify that the manuscript uses researcher-accepted versions and that late interpretation changes triggered the required rechecks.
Possible epistemic return
New knowledge discovered at submission may propose a return to an earlier object. Defective files or stale audits use rollback. A return is not a way to evade FAIL.
Productive refusal
If readiness cannot be demonstrated, identify the exact missing evidence, current checked package range, claims that remain blocked, and next gate to run.
Gate impact
Any controlling gate with INVALIDATED or REQUIRES_RECHECK validity, or any unresolved blocking friction, forces submission FAIL. Historical PASS is not permanent certification.
Limitations
Submission systems, policies, legal requirements, and ethical rules vary and can change. This skill depends on current official instructions and accurate researcher-supplied information. It cannot provide legal advice, guarantee upload success, or guarantee editorial acceptance. The final author remains responsible for every submitted file and declaration.
示例提示词
手稿要投出去了,帮我做一次覆盖论证、引文和格式要求的最终核查。
所属插件
安装该插件会一并获得同领域的 62 个 Skill / MCP。
同插件的其他科研 Skill
- 学术文献获取下载Auto-downloads open-access PDFs for graded sources and writes a manual worklist for paywalled items. Use after literature-review, before ingest-source.
- 单篇文献入库管理Adds one verified PDF to a shared bibliography library, computing its citation key and keywords. Use to register a single document outside the full workflow.
- 数字人文计算方法Surveys computational DH methods: text mining, NLP, corpus linguistics, archive standards, GIS, network analysis, and OCR. Use for an overview of available DH tools.
- 考古地理信息系统分析Runs archaeological GIS analysis with GeoPandas: catchment analysis, viewshed, kernel density, spatial statistics. Use for mapping archaeological site locations.
- 论证结构提取可视化Extracts and visualizes argument structure: Toulmin reconstruction, support/attack graphs, circularity detection. Use to diagram an argument’s logical structure.
- 考古遗物类型学分析Performs artifact analysis: typological classification, ceramic attribute coding, lithic reduction analysis. Use when classifying excavated artifacts statistically.
- 引文与出处核查Checks citations, quotations, page numbers, and bibliography entries for accuracy and source fit. Use before submission to verify source-supported claims.
- 研究选题构思设计Explores research intent, field state, methodology, and ethics, then writes an approved design doc. Use before starting a new research question or chapter.
- 术语译名一致性检查Audits a manuscript for terms, translations, abbreviations, and names whose forms must stay stable. Use when terminology drift could undermine an argument.
- 计算语用学分析Runs computational pragmatics: speech act classification, implicature detection, discourse coherence, politeness analysis. Use for language-use-and-meaning studies.
- 文献综述学术对话构建Turns verified sources into a structured scholarly conversation among positions, not a chronological summary. Use when synthesizing literature into a debate narrative.
- 语料库语言学分析Performs corpus analysis with NLTK/spaCy: collocation, keyword analysis, KWIC concordance, word2vec, diachronic trends. Use for quantitative text-corpus research.
- 数字档案馆资源检索Queries digital archive REST APIs: Europeana, Chronicling America, Internet Archive, HathiTrust, DPLA, OAI-PMH. Use when searching or harvesting heritage metadata.
- 学术手稿章节撰写Drafts a chapter or article section by section from synthesized wiki content, agreeing each section’s argument first. Use to turn stable research synthesis into prose.
- 研究项目漂移状态检测Checks a shared source library and registered projects for drift: un-indexed PDFs, unmerged keywords, bibkey collisions. Use to audit a multi-project research setup.
- EMI课堂语料转写分析Segments and annotates classroom transcripts, coding language choice and discourse function with anonymised output. Use to quantify classroom talk or translanguaging.
- 人工智能伦理分析Analyzes AI ethics: algorithmic fairness metrics, bias auditing, value alignment, moral philosophy reasoning. Use to evaluate an AI system’s ethical dimensions.
- 研究计划任务执行Executes a ready research plan task by task, gating acquisition before ingest and dispatching analysis. Use after writing-research-plan to run the planned work.
- 研究项目结项清单Runs the final completion checklist: rendering, bibliography, wiki, data, reproducibility, archiving. Use when a manuscript is finalized and ready to publish.
- 形式逻辑自动推理Applies formal logic tools: Z3 SMT solver, modal logic S5, SAT encoding, Lean4 proof verification. Use to formalize or mechanically check a logical argument.
- 研究问题凝练构建Turns a broad topic or intuition into a precise, contestable, researchable question. Use at the start of a project when no defensible question yet exists.
- 历史地理信息系统分析Performs historical GIS work: georeferencing old maps, digitizing boundaries, temporal territory overlays, population interpolation. Use for historical spatial analysis.
- 历史语言学比较分析Analyzes historical linguistics in Python: sound correspondences, cognate detection, phylogenetic trees, Swadesh lists. Use when reconstructing language relationships.
- 历史社会网络分析Builds historical network analyses: correspondence networks, prosopography, temporal community detection, Gephi export. Use to map relationships among historical actors.
常见问题
投稿前最终核查能做什么?
Runs a final submission gate covering argument, citations, terminology, and venue requirements. Use just before a manuscript is submitted or resubmitted。
如何安装投稿前最终核查?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「投稿前最终核查」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
投稿前最终核查需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
投稿前最终核查经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。