name: venue-adapt description: adapt stable writing choices while forcing current-year official checks
venue-adapt
Purpose: adapt stable writing choices while forcing current-year official checks.
Source capability: .agent/capabilities/venue-adapt.yaml. Read this file first and treat it as the contract for this run.
Inputs
state/ccfa.yamlstate/conference-template.yamlstate/venue-profile.yamlpaper/venue_preamble.texpaper/style/compat.styscripts/export-venue-template.sh
Declared Outputs
state/venue-profile.yamlstate/conference-template.yamlstate/ccfa.yamlrelease/venue/
Validators
scripts/check-capability-parity.pyscripts/check-conference-template.pyscripts/check-anonymity.pyscripts/check-latex.sh
Venue Conversion (compat.sty shim)
paper/style/compat.sty reimplements the paper/style/ccfa-paper.sty Class
API (\parahead, \headbf, \figref/\tabref/\algref/\eqnref,
\tablestyle, \cmark/\xmark, compact column types) on packages an
official venue class already loads, so paper/sections/*.tex compiles
unmodified under CVPR/ICCV/NeurIPS/etc.
scripts/export-venue-template.sh --mode anonymous|camera-ready [--raw-template <local-kit-path>] copies paper/ sources plus
compat.sty and the user-supplied official kit (never fetched from the
network) into release/venue/<venue>-<year>-<mode>/, generates a
main.tex bound to the official class, and independently compiles it.
It never edits paper/, paper/refs.bib, or the official kit files.
release/venue/ is gitignored — regenerate it, do not hand-edit or
commit it. In anonymous mode, run scripts/check-anonymity.py after
export; it scans generated *-anonymous/ venue exports for leaked
author names and emails in addition to the three release surfaces.
Real-kit compile receipt (#17)
Compiling against the real kit is a hard gate, not something to remember:
a crash under the official class (missing package, macro conflict,
undefined command) fails export-venue-template.sh immediately; a
missing TeX toolchain prints an explicit UNVERIFIED line and records no
receipt (never a silent false pass). On a successful compile, a receipt
is appended to state/conference-template.yaml under realkit_receipts:
venue/year/mode, the kit's checksum, a combined compat.sty + paper/
source fingerprint, the verifying commit, and a timestamp. The
camera-ready-check gate (via scripts/check-conference-template.py,
run inside check-writing-harness.py) refuses to pass once a real
raw_template is configured and the paper is populated unless a
matching, fresh receipt exists for the venue/year/mode currently
declared in state/ccfa.yaml — editing compat.sty or paper/ sources
after the receipt was recorded makes it stale and re-blocks until
export-venue-template.sh is rerun.
Human Gates
current-year-official-rules: required when Recording or changing current-year venue, anonymity, page-limit, or template rules. Record instate/conference-template.yaml.scope-change: required when A needed edit is outside allowed_paths, a forbidden_path must change, or facts are missing from repository sources. Record inhuman/decisions/README.md.
Operating Steps
- Read
.agent/capabilities/venue-adapt.yamland confirm the requested work matches this capability, its read_only_paths, allowed_paths, and forbidden_paths. - Read the declared inputs from the repository. Never infer paper facts from chat, memory, or prior conversation when the repo lacks evidence.
- If a required input, evidence item, result, citation, venue rule, or human approval is missing, stop and record the blocker in
memory/current-status.mdorhuman/inbox/README.md. - Update declared outputs only. Do not edit capability specs, adapters, registry files, or unrelated paper state while executing this workflow.
- Run the declared validators that match the touched outputs. Capture each command and whether it passed.
- Finish only when the completion contract is met: changed files are declared outputs, validators passed or blockers are recorded, and the handoff names every remaining risk.
Completion Contract
- Source capability reviewed:
.agent/capabilities/venue-adapt.yaml - Output contract: all successful edits are limited to the declared outputs above.
- Validator contract: run at least one declared validator and every validator relevant to touched outputs.
- Blocker contract: missing evidence, approvals, or path authority is recorded before handoff.
- Fact contract: never infer paper facts from chat; cite repository paths instead.
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.