Skip to content
Back to skills

Immersive Field Doc

ASecurity

Immersive first-person field documentary: embedded reporting, handheld/gimbal on-the-move, reporter as protagonist, hidden camera, subtitled foreign dialogue. Use for field reporting, conflict/access documentaries and immersive reportage.

  • 5 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
businessgo

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned November 7, 2026

npx -y skills add Wanfeng1028/muse --skill immersive-field-doc --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Immersive Field Doc?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Immersive Field Doc
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wanfeng1028-immersive-field-doc/badge)](https://www.skillsdirectory.com/skills/wanfeng1028-immersive-field-doc)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: immersive-field-doc
description: "Immersive first-person field documentary: embedded reporting, handheld/gimbal on-the-move, reporter as protagonist, hidden camera, subtitled foreign dialogue. Use for field reporting, conflict/access documentaries and immersive reportage."
---

# Runtime entry

This is a routing layer, not a requirement to execute every technique in the full guide.

## Load policy
- Load this short entry when the skill is selected.
- Read `HARNESS.md` for the quality-first workflow.
- Open [the detailed guide](references/legacy-full-guide.md) only for the relevant shot, technique, or implementation detail. Do not ingest it all by default.
- Load no other skill unless the task has a concrete need for it.

## Execution rules
1. Translate the brief into one clear viewer outcome and a concise timecoded beat/shot plan.
2. Pick only the techniques that directly support the story, audience, platform, and available source material.
3. Build and render one representative shot or short vertical slice before scaling the style.
4. Inspect actual frames and audio, fix the largest quality defects first, and preserve editable sources.
5. Validate the rendered result against the brief; text mentions and source code are not proof of quality.
6. Record output paths, tool/model versions, evidence, known defects, and any checks that could not be performed.

## Feature discipline
The detailed guide is a toolbox, not a quota. Never add effects, transitions, 3D, tracking, captions, or generated assets merely to satisfy a list. Prefer clarity, continuity, intentional pacing, legibility, and sound over visual density.

## Completion
Deliver the output and concise evidence-based QA notes. Never claim an action or inspection occurred without evidence.

Files in this skill

  • LICENSE1.1 KB
  • SKILL.md1.7 KB
  • references/legacy-full-guide.md28.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.