Project Instructions
Problems with a kendex-owned skill go through kendex report; check ownership in the file first.
YouTube publish
Use Python 3.8 or newer. The executable is scripts/youtube-publish under this installed skill.
Consumer setup
- The consumer supplies
YOUTUBE_CHANNEL_IDandYOUTUBE_APPROVER_EMAILin the command environment. The email identifies the user who can approve a request on Linear. - The consumer supplies
YOUTUBE_ACCESS_TOKENthrough a private credential route. Keep the OAuth client, its secret, refresh token and access token outside the package and version control. An API key does not authorize uploads or comments. - Use the consumer's OAuth client with
youtube.uploadandyoutube.readonlyfor uploads and their channel check. Useyoutube.force-sslfor comments and replies. The consumer's authorization tool owns token acquisition, renewal and revocation. The script checks the token's channel withchannels.listbefore a write. See authorization and channel lookup. - The installed Linear skill supplies live tracker reads. Its configured credentials must be able to read the consumer's tracker item and comment authors.
Draft and approval
To draft an upload, comment or reply, or to send a draft after its recorded approval, follow workflows/publish.md.
- Each draft prints an
approval_recordobject. The user records their explicit yes by posting that object as the entire comment body on the named Linear item. The comment must come fromYOUTUBE_APPROVER_EMAIL. A caller's assertion or an agent-authored approval is insufficient. - Run
publish --draft PATHonly after that yes. The sending path reads the tracker item and comments live. It checks the author, decision, item and digest before any YouTube request. A changed draft or changed video needs a new approval. - A failed or interrupted write can have an uncertain result. Stop and check the channel with the user before any new attempt. Do not repeat a successful request or reuse its approval for another send.
Consent and spam
- YouTube requires specific express consent before uploads, comments and other actions. Identify the channel and visibility settings before consent. OAuth permission alone does not approve a particular send. Follow Developer Policies III.E.3 and III.I.2.
- YouTube prohibits spam, harassment and disruptive commercial messages. Approval does not permit those actions. Draft a relevant comment or reply for its named recipient. Do not use repeated unsolicited promotion or bulk comment campaigns. Follow Developer Policies III.I.11 and III.I.20.
- Report the returned visibility. Do not claim that a video became public from the requested setting alone. See upload response.


