App Publish

What to consider before installing: - Functionally this package does what it claims: it automates Chrome to upload videos and fill forms. That requires access to your local video/cover files and to a Chrome session that is logged in to the target platforms. - High-impact capability: it connects to a Chrome debug port and can reuse a browser profile — if you point user-data-dir at a profile that contains your real accounts the skill will act with those authenticated sessions. Use a dedicated Chrome profile (create a new user-data-dir) to isolate credentials. - The code executes arbitrary JS in pages and can save page HTML to disk (debug helpers). Treat it as able to read page content, DOM, and client-side data; do not run it against sensitive accounts unless you trust the author. - Environment variables: CHROME_BIN and proxy env vars (KBS_PROXY/HTTP[S]_PROXY) are respected though not listed in the registry metadata. Do not set a proxy you don't trust. - Safety steps: review the full source locally, run first with --no-publish to confirm behavior, run in an isolated environment or VM, and point --user-data-dir to a throwaway Chrome profile. If you need higher assurance, have a developer audit the remaining omitted files or run the skill in a sandboxed environment.