| name | haipipe-paper-venue |
| description | Recommend the best-fit venue for a paper or topic, then pin it. Analyzes the paper's contribution/method/topic against every venue pack in _venue/playbook-*, ranks a shortlist with per-venue rationale, and writes the choice into STATUS.md venue (which makes every later stage couple to it). This is the venue-first front door: run it before claims. Also owns the venue-label -> pack resolution map. Trigger: venue, which journal, where to submit, venue fit, recommend journal, journal selection, pick venue, 投哪个期刊, 选刊, 期刊推荐, /haipipe-paper-venue. |
| argument-hint | [paper-path | free-text topic/abstract] [--no-pin] |
| allowed-tools | Bash, Read, Write, Edit, Grep, Glob, Skill |
| metadata | {"version":"1.1.0","last_updated":"2026-06-22","summary":"Analyze a topic/paper and recommend + pin the best-fit venue, using the _venue packs as the knowledge base.","changelog":["1.1.0 (2026-06-22): added --no-pin advisory mode + topic-only worked example (from fresh-agent validation); resolution map updated for the utd-is merge and jama-portfolio rename.","1.0.0 (2026-06-22): new venue-selection front door; reads _venue/playbook-* packs, ranks fit, pins STATUS venue, owns label->pack resolution."]} |
Paper Venue: recommend + pin the best-fit venue
Overview
Venue selection is the FIRST design decision (venue-first). Claims, displays, the
minimap, and prose all couple to the venue, so the venue must be chosen before
2-claims. This skill analyzes a paper or a bare topic against every venue pack in
../../_venue/playbook-* and recommends a ranked shortlist, then pins the choice in
STATUS.md.
The venue packs are knowledge, not skills; this skill is the READER that turns them
into a recommendation. It never edits a pack.
Modes
default recommend a shortlist, then ASK before writing STATUS venue (you confirm the pin)
--no-pin advisory only: recommend and stop; never write any file
(for "just tell me which journal" / a bare topic with no folder)
When to use
- "Which journal for this?", "where should I submit?", venue fit, before claims.
- A new paper whose venue is undecided, or a topic with no folder yet.
- Reconsidering venue after a reject, a scope change, or a reviewer signal.
Inputs
paper root reads 0-lifecycle/{0-seed,1-pitch,2-claims} for the contribution profile
or topic text a free-text topic / abstract when there is no folder yet
venue packs ../../_venue/playbook-*/README.md ("-> Claims" rewards + fit signals)
venue index ../../_venue/README.md (family map + IS selection table)
Procedure
- Build the paper's contribution profile. From the seed/pitch/claims (or the
topic text), extract: the central contribution, the method, the topic/domain, the
evidence strength, and the intended audience. If these are unclear, ask one round
of questions before scoring.
- Read the candidate packs. For each
../../_venue/playbook-<venue>/README.md,
read the -> Claims mapping (what it rewards, contribution vs enabler) and the fit
signals; read ../../_venue/README.md for the family map and IS selection table.
- Score each venue on five dimensions, each High/Med/Low with a one-line reason:
contribution-type match, method match, topic/domain match, evidence-bar match,
audience match. Record any hard disqualifier (e.g. "design science -> not ISR").
- Rank and shortlist the top 3. For each: a fit rationale, what to emphasize for
that venue, and the main why-not / risk.
- Recommend ONE primary + 1-2 backups. The primary is the one whose rewards the
paper's strongest claim most directly satisfies.
- Pin it (unless
--no-pin). In default mode, ASK the user, then write
venue: <pack-slug> (plus an optional venue_outlet: for the concrete journal)
into STATUS.md. With --no-pin, stop after step 5 and write nothing. Pinning is
the handoff to 2-claims, which re-runs its venue-coupled primary-claim designation.
Output contract
A recommendation table, then the STATUS write on confirm:
venue fit why (one line) emphasize / why-not
playbook-jama-portfolio HIGH patient-safety opioid outcome, obs. Table1+STROBE; assoc-not-causal
playbook-utd-is LOW thin IS theory contribution would need a theory pivot
...
PRIMARY: playbook-jama-portfolio (outlet: JAMA Internal Medicine) BACKUP: playbook-clinical-medicine
-> write STATUS.md: venue: jama / venue_outlet: JAMA Internal Medicine ?
Topic-only example (no paper folder yet)
/haipipe-paper-venue "physician agreeableness, scored by an LLM from online reviews, predicts higher opioid prescribing; observational, CMS Medicare 2015-2020" --no-pin
- Build the profile from the text (no seed/pitch to read): contribution = a clinical
prescribing-safety association; method = the LLM trait measure (an enabler);
design = observational; audience = clinical / policy.
2-5. Score the packs, shortlist, recommend (here:
playbook-jama-portfolio ->
JAMA Internal Medicine primary, playbook-clinical-medicine backup).
--no-pin, so report only and stop; offer to scaffold a paper folder and pin if
the user then wants one.
Venue label -> pack resolution
A human venue name maps to one pack (family granularity; the concrete outlet is a
delta inside the pack). This skill owns the map:
MISQ / ISR / Management Science (IS) [UTD-IS]-> playbook-utd-is (pick the outlet via the in-pack delta)
Nature / Nature Methods / Nature Biotech -> playbook-nature-portfolio
PNAS -> playbook-pnas
JAMA / JAMA Internal Medicine / JAMA Netw Open-> playbook-jama-portfolio
NEJM / Lancet / Annals / BMJ (clinical) -> playbook-clinical-medicine
grant (NSF / NSFC / KAKENHI / ERC / ...) -> playbook-grant
patent (CNIPA / USPTO / EPO) -> playbook-patent
When STATUS.md venue: is a human label, every stage resolves it through this map to
find ../../_venue/playbook-<slug>. Prefer writing the pack slug into STATUS directly.
Boundaries
this skill recommends a venue and PINS it (STATUS venue); owns label->pack resolution
2-claims couples claims to the pinned venue (does not choose it)
_venue/* knowledge packs, read-only here
It recommends and pins; it does not write claims, displays, or prose. Venue-first.
Gate
Ask before overwriting an existing STATUS.md venue: (a venue change re-runs the
claims designation and can reshape displays and the minimap).
