FCP Assistant

This skill appears to implement the advertised FCP/video pipeline, but review and test before trusting it with real projects: - Missing AppleScript files: SKILL.md calls multiple .scpt scripts (check-fcp.scpt, list-projects.scpt, etc.) but those .scpt files are not in the package. Expect to edit the scripts or provide your own .scpt files if you need FCP automation. - Local services required: TTS/ASR calls target local hosts (127.0.0.1:7860 and 127.0.0.1:8000). Ensure you run those services yourself — the skill assumes a local Qwen TTS/ASR stack. It will not contact a remote cloud TTS by default. - Hardcoded developer path: tts/voice scripts default TTS_OUTPUT_DIR to /Users/stevegao/..., which likely does not exist on your machine. Edit script defaults or set appropriate environment variables/directories before running. - Optional API key: media-collector mentions PEXELS_API_KEY (optional). If you supply an API key, it will be used in requests; no explicit secrets are required by the skill, but supplying keys is optional and should be done cautiously. - Network activity: the skill downloads video assets (Pexels) and references public music locations (Pixabay links). If you need an offline or air-gapped workflow, do not run the media-collector or block outbound network calls. - Safety steps before use: run the scripts in a disposable sandbox or inside a throwaway project directory; inspect and, if necessary, edit scripts for paths/ports; verify ffmpeg/osacscript calls on sample files; do not run against sensitive directories. If you rely on the FCP automation, create or supply the missing .scpt files or contact the author for a complete package. Given the above mismatches and surprising defaults, proceed only after addressing missing files and adjusting hardcoded paths; these issues look like sloppy packaging rather than intentionally malicious behavior.