light-venue-matching
Build evidence-bound journal or conference shortlists for Light stage 12. Use after typesetting delivers venue-handoff.json/PDF/compliance facts; when an author asks where to submit, journal selection, conference fit, scope or article-type matching, publication strategy, reach/match/safety tiers, transfer order, APC/OA/indexing/deadline constraints, or predatory/hijacked-journal risk. Produces a current-source candidate registry, fit/risk/unknown reports, and an unchosen decision packet; never recompiles the PDF, invents acceptance rates, condemns a venue from soft signals, chooses without a d
npx skills add Light0305/Light-skills --skill light-venue-matching --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Venue matching · stage 12 Turn a delivered paper into an auditable venue decision. Read `venue-resource-map.md` before a real run and `references/workflow_contract.md` before producing or consuming JSON. Use `references.md` to choose current sources. Start from `templates/venue_input.json`; never start from model memory or a bundled venue list. ## Non-negotiable boundaries 1. Consume typesetting's `venue-handoff.json`. Verify its PDF path/hash, `DELIVERED`, pages, page size, profile/source, compliance `PASS`, and zero critical findings. Preserve paper/figure/citation/typesetting provenance. Do not compile, reformat, inspect page boxes again, or treat stage-11 `UNAVAILABLE` as compliance. 2. Consume paper-writing's manuscript/claim profile through `manuscript_profile.claims_delivery` with a safe relative path, schema, and SHA-256. Do not change claims, methods, results, article type, data scale, or evidence strength to make a venue fit. Citation owns reference authenticity; figure owns visual honesty. 3. Treat acceptance rate, review time, APC/OA, indexing, quartile, and CFP deadline as high-velocity fields. Require a source checked on the run date. Otherwise emit `UNKNOWN`, `UNAV
- Non-negotiable boundaries
- Workflow
- 1. Consume the real submission artifact
- 2. Capture the author constraints
- 3. Discover for recall, then verify for precision
- 4. Build field-level evidence
- 5. Prepare the canonical decision packet
- 6. Stop at the user decision
- 7. Apply the user's choice
- Script roles
- Delivery self-check
- Honest capability boundary
What does the light-venue-matching skill do?
Build evidence-bound journal or conference shortlists for Light stage 12. Use after typesetting delivers venue-handoff.json/PDF/compliance facts; when an author asks where to submit, journal selection, conference fit, scope or article-type matching, publication strategy, reach/match/safety tiers, transfer order, APC/OA/indexing/deadline constraints, or predatory/hijacked-journal risk. Produces a current-source candidate registry, fit/risk/unknown reports, and an unchosen decision packet; never recompiles the PDF, invents acceptance rates, condemns a venue from soft signals, chooses without a d
How do I install it?
Run `npx skills add Light0305/Light-skills --skill light-venue-matching --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Light0305/Light-skills, a repository with 505 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.