Skills Guide

Venue Adaptation

VerifiedCaution

Adapt stable writing choices to current-year official conference templates, ensuring compatibility with packages and compilation checks.

Download and use
Sby Skills Guide Bot
DocumentationAdvanced
7/23/2026
Claude CodeCodex
#latex#academic-writing#conference-template#anonymity-check#reproducibility

Recommended for

Claude CodeAuto documentationCodex

Automated summary

Adapts a paper's LaTeX sources to an official conference class through a compat.sty shim, then verifies compilation and anonymity with the repository validators.

Strengths

  • Keeps paper/sections/*.tex untouched: compat.sty reimplements the ccfa-paper.sty API (\parahead, \cmark, compact column types, etc.) on top of packages the official venue class already loads.
  • Compiling against the real kit is a hard gate: a crash fails the export, and a missing TeX toolchain prints an explicit UNVERIFIED line instead of a silent false pass.
  • A receipt (kit checksum, compat.sty + paper/ source fingerprint, commit, timestamp) is appended to state/conference-template.yaml and goes stale as soon as a source changes, re-blocking camera-ready-check.
  • Runs an anonymity scan over generated *-anonymous/ exports in addition to the three release surfaces, and keeps release/venue gitignored so it is regenerated rather than hand-edited.

Limitations

  • Requires a locally supplied official kit via --raw-template; it never fetches a template from the network.
  • Current-year rules (anonymity, page limits, template) must pass through the current-year-official-rules human gate, so rule discovery is not automated.
  • Only covers the macros compat.sty already shims; venue-class features outside that surface need manual work beyond allowed_paths.
  • Halts and records a blocker rather than inferring paper facts or venue rules that are missing from the repository.
When to use it

Use it when a paper drafted under the internal CCFA class must be reformatted and verified for a specific conference and year, in anonymous or camera-ready mode.

When not to use it

Do not use it to write or restructure paper content, or to establish current-year official rules on its own without a recorded human decision.

Security analysis

Caution
Quality score90/100

The instructions are local-only, explicitly avoid fetching templates from the network, contain no destructive commands, obfuscation, or secret exfiltration, and impose human gates and validators. The caution rating is due to undeclared shell/LaTeX execution and reliance on repository scripts rather than any observed malicious behavior.

Findings
  • •No allowed-tools are declared, yet the workflow instructs the agent to run repository shell scripts and LaTeX compilation, so execution depends on the trustworthiness of those scripts.
  • •The skill relies on a separate capability contract and scripts not included in the SKILL.md, creating a trust dependency on repository contents.
  • •It writes to declared state and release outputs, which is legitimate but still modifies paper workflow state.
How this analysis is made

Examples

Anonymous venue export
Adapt paper/ to the CVPR 2025 official kit in anonymous mode: run scripts/export-venue-template.sh --mode anonymous --raw-template ~/kits/cvpr2025, then run scripts/check-anonymity.py and the venue validators.
Regenerate camera-ready
Regenerate release/venue for camera-ready mode for the venue declared in state/ccfa.yaml using the local kit, and record the realkit receipt.
Debug a blocked camera-ready gate
My camera-ready-check gate started failing after I edited paper/style/compat.sty — check whether the realkit receipt is stale and rerun the export to refresh it.

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.yaml
  • state/conference-template.yaml
  • state/venue-profile.yaml
  • paper/venue_preamble.tex
  • paper/style/compat.sty
  • scripts/export-venue-template.sh

Declared Outputs

  • state/venue-profile.yaml
  • state/conference-template.yaml
  • state/ccfa.yaml
  • release/venue/

Validators

  • scripts/check-capability-parity.py
  • scripts/check-conference-template.py
  • scripts/check-anonymity.py
  • scripts/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 in state/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 in human/decisions/README.md.

Operating Steps

  1. Read .agent/capabilities/venue-adapt.yaml and confirm the requested work matches this capability, its read_only_paths, allowed_paths, and forbidden_paths.
  2. Read the declared inputs from the repository. Never infer paper facts from chat, memory, or prior conversation when the repo lacks evidence.
  3. If a required input, evidence item, result, citation, venue rule, or human approval is missing, stop and record the blocker in memory/current-status.md or human/inbox/README.md.
  4. Update declared outputs only. Do not edit capability specs, adapters, registry files, or unrelated paper state while executing this workflow.
  5. Run the declared validators that match the touched outputs. Capture each command and whether it passed.
  6. 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.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/venue-adaptation-mrx3xwqa/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/venue-adaptation-mrx3xwqa' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/venue-adaptation-mrx3xwqa/download' --output '.skill-downloads/venue-adaptation-mrx3xwqa/SKILL.md.part' && mv '.skill-downloads/venue-adaptation-mrx3xwqa/SKILL.md.part' '.skill-downloads/venue-adaptation-mrx3xwqa/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/venue-adaptation-mrx3xwqa/SKILL.md' && test -s '.skill-downloads/venue-adaptation-mrx3xwqa/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/venue-adapt' && cp -R '.skill-downloads/venue-adaptation-mrx3xwqa' '.claude/skills/venue-adapt'

Codex
test -f '.skill-downloads/venue-adaptation-mrx3xwqa/SKILL.md' && test -s '.skill-downloads/venue-adaptation-mrx3xwqa/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/venue-adapt' && cp -R '.skill-downloads/venue-adaptation-mrx3xwqa' '.agents/skills/venue-adapt'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/venue-adaptation-mrx3xwqa'

openskills read 'venue-adaptation-mrx3xwqa'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/venue-adaptation-mrx3xwqa/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

Supabase Docs Authoring

Documentation

Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.

Claude CodeintermediateSafe 108,544
Skills Guide Bot

Create Architecture Decision Record

Documentation

Create a new Architecture Decision Record with sequential numbering, register it in the AgentDB graph, and link related ADRs.

Claude CodeintermediateSafe 69,659
Skills Guide Bot

Plan update with deep research

Documentation

Updates a plan document by launching parallel subagents to analyze a topic across all compiler passes, then consolidates findings into the plan doc.

Claude CodeadvancedSafe 248,015
Skills Guide Bot