7Pun/codex-campus-recruitment-video-skill

Producing Campus Recruitment Videos

Core principle

Build each video from current evidence, then verify the exported artifact. Reuse the workflow and visual system; never reuse stale facts, mismatched companies, or a previous video's material filters.

Mandatory start gate

Copy and track this checklist:

Production progress:
- [ ] Preflight local dependencies and session capabilities
- [ ] Define today's topic, audience, evidence window, and output target
- [ ] Analyze the benchmark or established project style
- [ ] Approve the script and material mapping
- [ ] Collect and visually inspect official materials
- [ ] Inspect product recording requirements or received footage
- [ ] Generate/receive narration and align captions
- [ ] Build and visually check the Remotion edit
- [ ] Render and verify the export plus contact sheet
- [ ] Publish only when explicitly authorized

Run before scripting, collecting materials, generating TTS, or editing:

First resolve <skill-dir> as the directory containing this SKILL.md, then run:

"<skill-dir>/scripts/preflight.sh"

Add --strict-tts when this run must generate narration. Add --project PATH when checking an existing Remotion project.

Stop on any FAIL. Report the exact missing dependency and remediation. Do not continue with old materials, silent substitutions, unknown voices, or placeholder footage.

In addition to the script, confirm the current Codex session has:

• A benchmark download path when a public Douyin link is provided.
• A current campus-search source such as UPCV or official links supplied by the user.
• Browser/Chrome/Playwright control for opening official pages and taking screenshots.
• Local image inspection for screenshot QA and contact-sheet review.

Route to supporting capabilities

• Benchmark download: Use download-douyin-video when available.
• Campus announcement discovery: Use campus-search when available.
• Web screenshots: Use the available browser-control or Playwright capability.
• Video implementation: REQUIRED SUB-SKILL: Use remotion-best-practices and its relevant caption/render references.
• Final claims: REQUIRED SUB-SKILL: Use verification-before-completion.

If a named Skill is unavailable, use an equivalent capability only after stating the substitution. Never treat absence of a tool as proof that the capability is impossible.

Execute the workflow

1. Read references/workflow.md completely.
2. Read references/script-patterns.md before writing or revising a script.
3. Read references/material-standards.md before searching or screenshotting.
4. Read references/recording-standards.md before requesting or accepting screen recordings.
5. Read references/editing-standards.md before changing the Remotion timeline.
6. Read references/portability.md when installing, moving machines, choosing fallbacks, handling private data, or publishing.

For a new video workspace, run:

"<skill-dir>/scripts/init-video-project.sh" \
  --root "/path/to/workspace" \
  --slug "YYYY-MM-DD_topic" \
  --install

The script creates a standard videos/<slug>/ layout and copies the bundled Remotion starter. Replace all fictional demo content before producing a real export.

Non-negotiable production rules

• Derive company type, date window, industries, cities, degrees, and majors from the current script.
• Use official recruitment pages or official announcements for factual claims.
• Keep company name and official-source context visible in screenshots.
• Inspect every collected image; reject screenshots that cannot identify the company or useful fact.
• Request computer landscape recording. Do not assume mobile portrait footage for this style.
• Keep narration understandable; do not compress speech merely to hit a target duration.
• Align scenes to sentence meaning. Do not cut images at a fixed mechanical interval.
• Keep the product segment restrained: default to at most two text annotations.
• Keep at most one primary sticker on screen; frame only specific buttons or facts.
• Preserve earlier exports. Render revisions as new versions.
• Never operate Jianying/CapCut unless the user explicitly authorizes it.
• Never publish, send messages, or access an account without explicit authorization.

Verify before delivery

Render key frames first. Inspect filter targets, captions, labels, privacy, and product controls. Then render the full video and run:

"<skill-dir>/scripts/verify-export.sh" \
  "/path/to/export.mp4" \
  "/path/to/contact-sheet.jpg"

Deliver only after tests/type checks pass, the verifier reports no FAIL, and the contact sheet shows no placeholder section, unreadable rapid cuts, repeated decorative transition, or excessive annotation.

Common mistakes

Mistake	Required correction
Reusing the same UPCV filters every day	Recompute filters from the current script and target audience.
Showing old openings in a “recent jobs” video	Tighten the evidence window and replace stale companies.
Screenshot hides the company name	Re-open the official page and capture identifying context.
Product recording does not perform the narrated action	Recut to an available truthful action or request the missing recording.
Every cut uses a page-turn effect	Reserve paragraph transitions; use direct cuts elsewhere.
Stickers repeat captions	Delete them; retain only navigation-critical annotations.
Export exists, so work is declared complete	Run tests, artifact verification, and visual contact-sheet review first.

Bundled resources

• scripts/preflight.sh: Check local dependencies and discoverable Skills.
• scripts/init-video-project.sh: Create the standard project structure.
• scripts/verify-export.sh: Validate codec, audio, resolution, frame rate, black frames, volume, and contact sheet.
• scripts/test-scripts.sh: Run script syntax and smoke checks.
• assets/remotion-template/: Portable fictional-data starter project.