paper-know-journal

Input and Output

Input: Journal name; optional additional inputs include output directory, workspace, focus areas, target article types (e.g., Article, Original Research, Review, Brief Communication, Case Report, Letter) or target manuscript types.

Output:

KnowJournal-{journal name}.md

, saved by default in the root directory of the user's current working directory; saved to the specified location if the user designates an output path. Path-dangerous characters such as

/\:*?"<>|

in the file name are replaced with

Intermediate Files: By default, all intermediate files are stored in

.bensz-api/task-{yyyymmdd-hhmm}-{brief description}/paper-know-journal/{yyyy-mm-dd-hh-mm}/

. Except for the final Markdown file and outputs explicitly specified by the user, retrieval logs, web excerpts, screenshots, drafts, JSON files, temporary downloads or runtime caches must not be written outside the hidden workspace.

Test Area: Use

./tests/paper-know-journal/

for lightweight verification; test evidence must not be mixed into the final report.

Workflow

Input

Provide necessary inputs according to user requests and configuration files; if information is missing, clearly list it and stop steps that depend on the missing input.

Execution Steps

For bugs caused by design flaws of this skill, first use
```
bensz-collect-bugs
```
to record them in
```
~/.bensz-skills/bugs/
```
in a standardized manner, do not directly modify the skill source code installed locally by the user; if there is a workaround, record the bug first, then continue to complete the task.
Only when the user explicitly requests actions like "report bensz skills bugs" for public submission, use the local
```
gh
```
tool to upload new bugs to
```
huangwb8/bensz-bugs
```
; do not pull / clone the entire repository.

Initialization

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

bash

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 products are written to

workspace_dir

. If prompted

output_path already exists

, confirm with the user before overwriting or use a new path.

If the user specifies an output directory or workspace:

bash

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 mandatory, 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 instructions, author experience posts, etc. Third-party sources are only used as experience clues and cannot replace official policies.

Prioritize verifying the following information:

Full journal name, publisher/society, ISSN, official website, submission portal.
Scope, article types, word count/abstract/figure/reference limits.
Specific requirements for target article types: When the user specifies an article type, it must be fully covered; if not specified, first list official article types, then select 2-3 most common or relevant types (usually including original research and reviews) to expand. For each type, verify its name, word count or page limit for main text/abstract, abstract type, number of keywords, section titles and order, limits on figures/supplementary materials/references, checklist of reporting standards and special submission materials.
Submission format requirements: Title page, author information, abstract type and word count, keywords, main text structure, section titles, file composition, templates, line spacing/page numbering, figure file format and resolution, supplementary materials, reference format, cover letter, checklist of reporting standards.
OA/subscription model, APC, license, whether there are member discounts or waivers.
Review method, first decision time, time from acceptance to online publication, acceptance rate; if no official data is available, indicate the source type and uncertainty.
Format requirements: Title page, abstract, keywords, main text structure, image resolution, supplementary materials, reference format, declaration sections, policies on data/code/AI usage.
Recent article formats: Sample 2-3 similar articles published in recent years, summarize abstract, main text structure, number of figures, declaration and reference styles.
Community reviews: Speed, communication, experience of rejection/major revision, fee disputes, transparency, common complaints; separate from official information.

Maintain

sources.json

during research:

```
official
```
: Official web pages, author guidelines, fee pages, submission systems, publication ethics pages.
```
community
```
: SciRev, LetPub, forums, author experience posts, institutional instructions, etc.
```
article_samples
```
: Representative recently published articles.

For each source, at least record

title

url

source_type

accessed_at

key_facts

. Web excerpts, retrieval logs and drafts can only be stored in

workspace_dir

Refer to

references/source-policy.md

for data processing rules. See

references/report-template.md

for report structure.

Final Report Compilation

Output in Chinese Markdown, with a style similar to JITC / Cancer Cell research samples: Start with key conclusions and journal overview, then write submission requirements, submission format requirements, actual article formats, community reviews and submission suggestions.

The report must include:

Research date.
Journal name and verifiable official website link.
Clear distinction between "official information" and "community reviews/third-party information" sources.
An independent chapter "Submission Format Requirements and Checklist"; do not replace official submission format requirements with only recent article samples.
An independent subsection "Specific Requirements for Target Article Types" within "Submission Format Requirements and Checklist"; for each target article type, clearly write official section titles/order, word count or page limit, abstract, keywords, figures, references and special file requirements. If the official adopts format-free / free format for initial submission, also clarify which items still need to be met and which items only apply during revision or after acceptance.
An actionable checklist for submission preparation, covering at least title page, abstract/keywords, main text structure, figures, supplementary materials, references, declarations/ethics/data/code/AI, submission files or cover letter; write "Not confirmed on official pages" for each item not disclosed by the official.
Explicit labels for missing, conflicting or suspected outdated information.
Source list with links and access dates.

Do not output unverified assertions.易变信息 such as impact factor, partition, fees, review duration must include the source year or access date.

Verification

After compiling the report, run:

bash

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

After verification passes, inform the user of: final file path, number of main sources, unconfirmable information and residual risks.

Output

Deliver the output promised in the Skill description, and clearly specify the format, path and failure return form.

Output Management

Intermediate files for new tasks of this Skill are uniformly written to

./.bensz-api/task-{yyyymmdd-hhmm}-{brief description}/{skill name}/input|output|log/

. Reuse a single task root directory for the same task; create

shared/

only for multi-Skill collaboration. Official deliverables are not written to this directory; historical hidden directories only allow explicit compatible reading, migration or cleaning.

Check

After completion, perform existing static checks, script verification or manual review of the Skill, and record the passing standards.

Failure and Recovery

Official website not found: First cross-locate using publisher, ISSN, NLM Catalog, DOAJ, Crossref, journal submission system; if still unconfirmable, stop report compilation and explain that user confirmation of the target journal is required.
Conflict with journals of the same name: List candidate journals, publishers and ISSN, and ask the user to confirm first.
Insufficient community reviews: Clearly write "Insufficient community reviews found", do not fabricate experiences.
Conflict between official information and community information: Prioritize official policies, treat community information as experience clues, and mark conflict points.
Website inaccessible: Record access failure, try alternative official pages or cached summaries; if key policies cannot be verified, list them as to-be-confirmed in the report.

Constraints

Comply with the following public constraints and implement the exclusive boundaries of this Skill.

Public Hard Constraints

When tasks require disk storage, use a unique
```
./.bensz-api/task-{yyyymmdd-hhmm}-{brief description}/
```
root directory; shared materials are stored in
```
shared/
```
, and Skill-specific materials are stored in
```
input/
```
,
```
output/
```
,
```
log/
```
of the Skill.
Official deliverables, source code and official plans are saved according to project agreements, not written to the task workspace; do not overwrite, delete, migrate or remotely write without authorization.
For project maintenance changes, check BAC availability and record requirements, AI outputs, tool results, file changes and verification summaries; BAC only performs process audits and does not replace signature, 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-volume raw data.
File paths must be standardized and limited to authorized project scopes; external URLs, subprocesses and network access follow the principle of least privilege to prevent path traversal, SSRF and command injection.
Skill versions are uniquely recorded in its own
```
config.yaml:skill_info.version
```
; changes to public APIs, protocols, directories or configurations are synchronized with documents and
```
CHANGELOG.md
```
.
Only design defects of the Skill or Bensz infrastructure itself are submitted to
```
bensz-collect-bugs
```
; first desensitize and write to
```
~/.bensz-skills/bugs/
```
, do not interrupt the current task, only submit publicly if the user explicitly requests, and prohibit direct modification of the Skill source code installed by the user.

Skill Exclusive Constraints

Do not exceed the scope stated in this Skill description and the workflow above; do not disguise unverified information as definitive conclusions.

paper-know-journal

NPX Install

Tags

SKILL.md Content (Chinese)

paper-know-journal

Input and Output

Workflow

Input

Execution Steps

Initialization

Research

Final Report Compilation

Verification

Output

Output Management

Check

Failure and Recovery

Constraints

Public Hard Constraints

Skill Exclusive Constraints