SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillspaper-know-journal

paper-know-journal

Writing & research

View repository

Updated 10-16 05:54

About this skill

paper-know-journal

Input and Output

Input: journal/magazine name; may additionally include output directory, workspace, focus area, target style/article type (such as Article, Original Research, Review, Brief Communication, Case Report, Letter), or target manuscript type.

Output:KnowJournal-{杂志名}.md, by default in the root directory of the user's current working directory; when the user specifies an output location, save it as specified. In the filename, /\:*?"<>| and other path-dangerous characters are replaced with -。

Intermediate files: by default all are placed in .bensz-api/task-{yyyymmdd-hhmm}-{简短描述}/paper-know-journal/{yyyy-mm-dd-hh-mm}/. Except for the final Markdown and the output explicitly specified by the user, retrieval logs, webpage excerpts, screenshots, drafts, JSON, temporary downloads, or runtime caches must not be written outside the hidden workspace.

Test area: for lightweight verification use ./tests/paper-know-journal/; test evidence must not be mixed into the final report.

Process

Input

Provide the necessary input according to the user's request and the configuration file; missing information should be clearly listed and steps that depend on that input should stop.

Execution Steps

  • For bugs caused by defects in this skill's design, first use bensz-collect-bugs to record them according to the specification in ~/.bensz-skills/bugs/, do not directly modify the user's locally installed skill source code; if there is a workaround, record the bug first, then continue completing the task.
  • Only when the user explicitly requests public reporting such as "report bensz skills bugs", use the local gh to upload the newly added bug to huangwb8/bensz-bugs; do not pull / clone the entire repository.

Initialization

First run the script to create an isolated workspace, test area, and safe output path:

python3 /path/to/paper-know-journal/scripts/init_workspace.py \
  --journal "Cancer Cell" \
  --cwd "$PWD"

The script will print workspace_dir、output_path、test_dir、manifest_path、sources_path. All intermediate artifacts are written to workspace_dir. If prompted output_path already exists, confirm with the user before overwriting or use a new path instead.

If the user specifies an output directory or workspace:

python3 /path/to/paper-know-journal/scripts/init_workspace.py \
  --journal "Journal for ImmunoTherapy of Cancer" \
  --cwd "$PWD" \
  --output-dir "/path/to/output" \
  --workspace-dir "/path/to/.bensz-api/task-{yyyymmdd-hhmm}-{简短描述}/paper-know-journal"

Research

Online verification is required, covering at least:

  • Official sources: journal official website, author guidelines, submission system instructions, manuscript preparation / formatting guidelines, publisher policy pages, fee pages, editorial policy pages.
  • Community/third-party sources: SciRev, LetPub, ResearchGate, Reddit, X/Twitter, forums, institutional library guides, author experience posts, etc. Third parties serve only as experience clues and do not replace official policies.

Prioritize verifying this information:

  • Full journal name, publisher/society, ISSN, official website, submission portal.
  • Scope, article types, word/abstract/figure/table/reference limits.
  • Specific requirements for the target style/article type: when the user specifies a style, that style must be covered; when unspecified, first list the official article types, then select 2-3 of the most common or most relevant types (usually including original research and review) to elaborate. Verify item by item for that type: its name, main text/abstract word or page count, abstract type, number of keywords, section headings and order, figure/table/supplementary material/reference limits, reporting guideline checklists, and special submission materials.
  • Submission format requirements: title page, author information, abstract type and word count, keywords, main text structure, section headings, file composition, template, line spacing/page numbers/numbering, figure and table file formats and resolution, supplementary materials, reference format, cover letter, reporting guideline checklist.
  • OA/subscription model, APC, license, whether there are member discounts or waivers.
  • Peer review method, time to first decision, time from acceptance to publication, acceptance rate; when there is no official data, indicate the source type and uncertainty.
  • Format requirements: title page, abstract, keywords, main text structure, image resolution, supplementary materials, reference format, declaration sections, data/code/AI use policy.
  • Recent article format: sample 2-3 recent similar articles, and summarize the abstract, main text structure, number of figures and tables, declarations, and reference style.
  • Community evaluations: speed, communication, rejection/major revision experience, fee disputes, transparency, common complaints; write separately from official information.

During research, maintain sources.json：

  • official: official webpages, author guidelines, fee pages, submission system, publication ethics page.
  • community: SciRev, LetPub, forums, author experience posts, institutional explanations, etc.
  • article_samples: recent representative published articles.

For each source, record at least title、url、source_type、accessed_at、key_facts. Webpage excerpts, search logs, and drafts may only be placed in workspace_dir .

For data handling rules, see references/source-policy.md. For report structure, see references/report-template.md。

Final draft

Output in Chinese Markdown, with a style close to the JITC / Cancer Cell research examples: first give the key conclusions and journal overview, then write the submission requirements, submission format requirements, real article format, community evaluations, and submission recommendations.

The report must include:

  • Research date.
  • Journal name and verifiable official website link.
  • Distinguish sources between "official information" and "community evaluations/third-party information".
  • A separate "Submission Format Requirements and Format Checklist" section; recent article samples cannot be used alone to replace official submission format requirements.
  • Include a separate "Specific Requirements for Target Article Types/Article Types" subsection within the "Submission Format Requirements and Format Checklist"; for each target article type, clearly write the official section headings/order, word count or page count, abstract, keywords, figures and tables, references, and special file requirements. If the official submission uses format-free / free format initial submission, also clearly state which items still need to be met and which items apply only after revision or acceptance.
  • An actionable checklist for submission preparation, covering at least the title page, abstract/keywords, main text structure, figures and tables, supplementary materials, references, declarations/ethics/data/code/AI, submission files, or cover letter; when not disclosed officially, write "not confirmed on the official page" item by item.
  • Explicitly mark missing, conflicting, or suspected outdated information.
  • Source list, including links and access dates.

Do not output unverified assertions. Easily changeable information such as impact factor, quartile, fees, and review duration must include the source year or access date.

Validation

After the final draft is completed, run:

python3 /path/to/paper-know-journal/scripts/validate_report.py \
  --report "KnowJournal-Cancer Cell.md" \
  --journal "Cancer Cell"

After validation passes, inform the user: final file path, number of main sources, information that cannot be confirmed, and residual risks.

Output

Output the deliverables promised in the Skill description, and specify the format, path, and failure return format.

Output management

Intermediate files for new tasks of this Skill are uniformly written to ./.bensz-api/task-{yyyymmdd-hhmm}-{简短描述}/{skill名}/input|output|log/. Reuse one task root directory for the same task; create multiple Skill collaborations only when shared/. Formal deliverables are not written to this directory; historical hidden directories only allow explicit compatibility reading, migration, or cleanup.

Validation

After completion, execute the Skill's existing static checks, script validation, or manual review, and record the pass criteria.

Failure and Recovery

  • Official website not found: first cross-locate using the publisher, ISSN, NLM Catalog, DOAJ, Crossref, and the journal submission system; if it still cannot be confirmed, stop finalizing the manuscript and explain that the user needs to confirm the target journal.
  • Same-name journal conflict: list the candidate journals, publishers, and ISSNs, and have the user confirm first.
  • Sparse community reviews: explicitly write "insufficient community reviews found"; do not fabricate experiences.
  • Official information conflicts with community information: take official policy as authoritative, use community information as experiential clues, and mark the points of conflict.
  • Website inaccessible: record the access failure and try alternative official pages or cached summaries; when key policies cannot be verified, list them as pending confirmation in the report.

Constraints

Comply with the following public constraints and enforce this Skill's specific boundaries.

Public Hard Constraints

  • When the task requires persisting to disk, use the unique ./.bensz-api/task-{yyyymmdd-hhmm}-{简短描述}/ root directory; place shared materials in shared/, and place Skill-specific materials in that Skill's input/、output/、log/。
  • Formal deliverables, source code, and formal plans are saved according to project conventions and are not written to the task workspace; without authorization, do not overwrite, delete, migrate, or write remotely.
  • Project maintenance changes check BAC availability and record requirements, AI outputs, tool results, file changes, and validation summaries; BAC only performs process auditing and does not replace attribution, responsibility, or compliance judgments.
  • Do not record API Keys, access tokens, passwords, Cookies, environment/credential files, private Prompts, identity information, local usernames, hostnames, or unnecessary large volumes of raw data.
  • File paths must be normalized and restricted to the authorized project scope; external URLs, subprocesses, and network access follow least privilege to prevent path traversal, SSRF, and command injection.
  • Skill versions are recorded uniquely in their own config.yaml:skill_info.version; public API, protocol, directory, or configuration changes synchronize documentation and CHANGELOG.md。
  • Only hand design defects of the Skill or Bensz infrastructure itself to bensz-collect-bugs; first redact and write to ~/.bensz-skills/bugs/, do not interrupt the current task, report publicly only when the user explicitly requests it, and do not directly modify the source code of Skills already installed by the user.

Skill-Specific Constraints

Do not exceed the scope declared by this Skill description and the process above; do not disguise unverified information as definite conclusions.