Agent skill

Cheat Publish Registration

by XBuilderLAB in XBuilderLAB/cheat-on-content

Records that a piece of content went live by writing its URL, platform and publish time into the prediction file header and state file, leaving the prediction text untouched.

MITAuto-check: notesMarketing & SEO

SKILL.md written in Chinese; this summary is our English description.

Install Cheat Publish Registration

skills CLI

$ npx skills add XBuilderLAB/cheat-on-content --skill cheat-publish -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install XBuilderLAB/cheat-on-content cheat-publish --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/XBuilderLAB/cheat-on-content.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cheat-publish .claude/skills/cheat-publish && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "cheat-publish" agent skill from https://github.com/XBuilderLAB/cheat-on-content/tree/main/skills/cheat-publish into .claude/skills/cheat-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cheat-publish", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/XBuilderLAB/cheat-on-content/tree/main/skills/cheat-publish

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add XBuilderLAB/cheat-on-content --skill cheat-publish -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install XBuilderLAB/cheat-on-content cheat-publish --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/XBuilderLAB/cheat-on-content.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/cheat-publish .agents/skills/cheat-publish && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "cheat-publish" agent skill from https://github.com/XBuilderLAB/cheat-on-content/tree/main/skills/cheat-publish into .agents/skills/cheat-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cheat-publish", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add XBuilderLAB/cheat-on-content --skill cheat-publish -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install XBuilderLAB/cheat-on-content cheat-publish --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/XBuilderLAB/cheat-on-content.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/cheat-publish .cursor/skills/cheat-publish && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "cheat-publish" agent skill from https://github.com/XBuilderLAB/cheat-on-content/tree/main/skills/cheat-publish into .cursor/skills/cheat-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cheat-publish", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/XBuilderLAB/cheat-on-content.git --path skills/cheat-publish

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add XBuilderLAB/cheat-on-content --skill cheat-publish -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install XBuilderLAB/cheat-on-content cheat-publish --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/XBuilderLAB/cheat-on-content.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/cheat-publish .gemini/skills/cheat-publish && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "cheat-publish" agent skill from https://github.com/XBuilderLAB/cheat-on-content/tree/main/skills/cheat-publish into .gemini/skills/cheat-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cheat-publish", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install XBuilderLAB/cheat-on-content cheat-publish

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add XBuilderLAB/cheat-on-content --skill cheat-publish -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/XBuilderLAB/cheat-on-content.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/cheat-publish .github/skills/cheat-publish && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "cheat-publish" agent skill from https://github.com/XBuilderLAB/cheat-on-content/tree/main/skills/cheat-publish into .github/skills/cheat-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cheat-publish", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add XBuilderLAB/cheat-on-content --skill cheat-publish -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install XBuilderLAB/cheat-on-content cheat-publish --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/XBuilderLAB/cheat-on-content.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/cheat-publish .opencode/skills/cheat-publish && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "cheat-publish" agent skill from https://github.com/XBuilderLAB/cheat-on-content/tree/main/skills/cheat-publish into .opencode/skills/cheat-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cheat-publish", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: cheat-publish
GitHub stars: 7.2k
Token cost: ~1.3k tokens
SKILL.md length: 335 words
Files: 1
Skills in repo: 16
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Records that a piece of content went live by writing its URL, platform and publish time into the prediction file header and state file, leaving the prediction text untouched.

Works in 5 steps: 找到对应的预测文件 → 解析平台 → 更新 prediction 文件 header → …
Registering a post's link right after publishing it in a prediction workflow
SKILL.md covers Overview, Constants, Inputs and Workflow, plus 3 more sections
Reaches v.douyin.com

What it does

This is a light step in a workflow where each post is first blind-predicted and later compared with results. The agent finds the matching prediction file, from an explicit path, from the in-progress session in `.cheat-state.json`, or by listing prediction files whose header lacks a publish time, and it warns if the gap between that session and the URL is more than 14 days. It detects the platform from the URL (YouTube, Bilibili, Douyin, Xiaohongshu, WeChat, Substack, Medium or Twitter and X), and asks you for the publish time rather than scraping it.

Only the metadata block above the prediction section is edited, with the Edit tool, adding the publish time, platform, URL and platform-specific IDs such as an aweme ID, BV number, note ID or video ID; short links are marked pending for a later retrospective step. A hook blocks changes to the prediction text and the skill says to report a wrongly triggered hook, not bypass it. It also reminds you that looking at later data breaks the blind claim, and then updates the state file. The text is in Chinese.

When your agent uses it

Registering a post's link right after publishing it in a prediction workflow
Adding the platform and publish time to a prediction file's header
Finding which prediction files are still missing a publish record

Example prompts

“已发布，链接是 https://v.douyin.com/abc123，帮我登记一下。”
“I shipped it, the YouTube link is https://youtu.be/example, register the publish.”
“List the prediction files that have no published time yet.”

Requirements

A project with prediction files and a `.cheat-state.json` state file
Pre-approved tools (allowed-tools): Bash(*), Read, Edit, Glob

Workflow steps

5 steps, taken from the step headings in SKILL.md.

找到对应的预测文件
解析平台
更新 prediction 文件 header
更新 state file
提醒 + 下一步 + buffer 状态

What it can do on your machine

Read from SKILL.md and the folder at commit 2d8211e. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash(*)
- Read
- Edit
- Glob
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- v.douyin.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cheat Publish Registration loads about 1.3k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 335 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~41
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Bash(*), Read, Edit, Glob
```

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from XBuilderLAB/cheat-on-content at commit 2d8211e, republished under its MIT licence (© XBuilderLAB). 335 words, ~1,263 tokens.

Download SKILL.mdSave it as .claude/skills/cheat-publish/SKILL.md (or your agent's skills folder).

name: cheat-publish
description: 登记一篇内容已发布，把 URL/平台 ID/发布时间写入对应预测文件 header 和 state file。这是一个轻量动作——只更新元数据，**不动预测段任何字符**。触发词："已发布"/"I shipped"/"发布链接是 X"/"刚发完 [url]"/"publish registered"。
allowed-tools: Bash(*), Read, Edit, Glob
argument-hint: <prediction-file-or-url> [— platform: youtube|bilibili|douyin|...]

/cheat-publish — 发布登记

把作品的发布元数据（URL、发布时间、平台）补到预测文件 header 与 state file。禁止改预测段——hook 会拦。

Overview

[用户：已发布 https://...]
  ↓
[Phase 0: 找到对应的预测文件]   ← 通过 in_progress_session 或匹配
  ↓
[Phase 1: 解析 URL → 平台/发布时间]
  ↓
[Phase 2: 更新 prediction 文件 header（仅 metadata 段）]
  ↓
[Phase 3: 更新 .cheat-state.json，清除 in_progress_session]

Constants

AUTO_DETECT_PLATFORM = true — 从 URL 模式自动识别平台
VERIFY_BLIND = true — 提醒用户：从此刻起看到任何后续数据都会破坏盲度声明的诚信

Inputs

必填	来源
`<prediction-file>` 或 URL	用户参数；缺失则用 `.cheat-state.json` 的 `in_progress_session.file`
`.cheat-state.json`	用户项目根

Workflow

Phase 0: 找到对应的预测文件

按优先级：

用户参数明确给了 prediction 文件路径 → 用它
用户参数只给了 URL → 读 .cheat-state.json 的 in_progress_session.file
都没有 → 列出 predictions/*.md 中 header 没填 published_at 的文件，让用户选

警告路径：若 in_progress_session.file 与用户给的 URL 时间差超过 14 天 → 提示"这个预测写于很久之前，确认是这篇？"

Phase 1: 解析平台

AUTO_DETECT_PLATFORM=true 时按 URL 模式：

URL 模式	平台
`youtube.com/` `youtu.be/`	youtube
`bilibili.com/` `b23.tv/`	bilibili
`douyin.com/` `iesdouyin.com/` `v.douyin.com/*`	douyin
`xiaohongshu.com/` `xhslink.com/`	xhs
`mp.weixin.qq.com/*`	wechat
`substack.com/` `.substack.com/*`	substack
`medium.com/` `.medium.com/*`	medium
`twitter.com/` `x.com/`	twitter
其他	unknown — 询问用户

发布时间获取：

不强求自动抓——绝大多数平台需要登录态
询问用户："发布时间是？（默认：现在）" → 接受 ISO 8601 或自然语言（"今天 14:30" / "20 分钟前"）
解析失败 → 用 now()

绝不触碰 ## 预测 段及之后。只动文件最顶部的 metadata 块。

读文件，定位到 metadata 块（在第一个 ## 之前的所有行）。检查是否已有这些字段——有则警告"已登记过"并询问是否覆盖；无则追加：

markdown

**Published at**: 2026-05-04T14:32:00+08:00
**Platform**: douyin
**URL**: https://v.douyin.com/abc123
**Video Folder**: videos/2026-05-04_a3f2c1d4_停止期待/
**Aweme ID**: 7234567890123456789  (douyin / 视频号 等需要的 platform-specific ID)

关于 platform-specific ID：

抖音：从 URL 短链 resolve 后提取 aweme_id（v.douyin.com → 重定向后含 modal_id 或 item_id 参数）
B 站：BV 号
小红书：note_id
YouTube：v= 参数后的 video_id

如果用户给的是分享短链（无法立刻 resolve）→ 标 Aweme ID: pending，下次 /cheat-retro 时由 adapter 解析。

video folder 处理：到 cheat-publish 这一步，对应的 videos/<id>/ 目录应该已经由 cheat-shoot 创建（含 script.md）。

如 video folder 不存在 → 警告"你跳过了 cheat-shoot？建议先跑 cheat-shoot 把拍摄稿登记进 video folder 再发"，询问用户是否跳过登记直接发：
- 是 → 自动建一个 video folder（fallback），但不询问稿子一致性，标 ad_hoc_publish: true
- 否 → 让用户先跑 cheat-shoot 再回来 publish

用 Edit 工具（不是 Write 重写整个文件）。

hook 行为预期：因为只动 metadata 段（在 ## 预测 之前），immutability hook 应放行。如果 hook 误拦 → 报告 bug，不要绕过 hook。

Phase 3: 更新 state file

json

{
  "in_progress_session": null,
  "last_published_at": "<ISO timestamp>",
  "last_published_file": "predictions/<filename>",
  "last_published_video_folder": "videos/<...>/",
  "last_published_platform_id": "<aweme_id 或 BV 号 等>",
  "pending_retros": [
    "predictions/<filename>"
  ],
  "shoots": [
    // 移除 video_folder 匹配本次发布的项；buffer -1
  ]
}

shoots 队列处理（buffer 跟踪关键）：

读 state.shoots[]
找 video_folder == 本次发布的 video_folder 的项 → 移除
如果没找到 → 警告"buffer 队列里没有这条视频。是直接发布没经过 /cheat-shoot 吗？"——不阻塞，但提示用户下次走 /cheat-shoot 让 buffer 跟踪准确

last_published_platform_id 是 cheat-retro 调 adapter 时的输入——如 douyin-session 需要 aweme_id 直接抓数据。

pending_retros 是待复盘列表——cheat-status 会基于这个列表 + RETRO_WINDOW_DAYS 显示"今天该复盘哪些"。

Phase 4: 提醒 + 下一步 + buffer 状态

✅ 登记完成：predictions/2026-05-04_a3f2c1d4e5b6_停止期待.md
   - Published at: 2026-05-04 14:32
   - Platform: douyin
   - URL: https://v.douyin.com/abc123

📦 Buffer：N 篇（颜色 + 含义）
   按你的 cadence（X）= N×X 天 buffer
   [如颜色变了，提示"现在该去拍/暂停拍"]

⚠️  从此刻起，你看到任何关于这条作品的播放/点赞/评论数据
    都会破坏盲度声明的诚信。如果不小心看到，告诉我——
    我会在文件里追加一个 integrity warning。

📅 计划复盘：T+3d，约 2026-05-07
   到时间说："复盘 predictions/2026-05-04_..."

Buffer 颜色由 shared-references/cadence-protocol.md 派生。如本次发布让 buffer 跌入红色（断更风险）→ 高亮警告"今天必须再拍 ≥1 条"。

Key Rules

不动预测段。即使是修复笔误，也不允许在 publish 时改预测段
不抓数据。publish 是登记动作，不是数据回收（那是 cheat-retro 的活）
state 字段名固定。pending_retros / last_published_at 是其他子 skill（特别是 cheat-status / cheat-retro）依赖的契约
平台未知不强报。无法识别 → 询问用户，允许 platform: other 作为兜底
重复登记需明示。已有 published_at → 询问"覆盖？"，绝不静默覆盖

Refusals

「我顺手把预测段也改一下」 → 拒绝。请走 _redo.md 路径
「URL 我等会儿补，先把发布时间记上」 → 允许：URL 字段可后续追加；published_at + platform 必填
「跳过 metadata 更新，直接清 in_progress_session」 → 拒绝。元数据是复盘时的关键上下文（特别是 platform 决定数据回收用哪个 adapter）

Integration

上游：/cheat-predict（写出 prediction 文件并设 in_progress_session）
下游：T+RETRO_WINDOW_DAYS 后 → /cheat-retro
cheat-status 用 pending_retros 字段计算"今天该复盘哪些"
平台字段被 cheat-retro 用来路由到对应的 perf-data adapter（manual-paste / youtube-data-api / 等）

Files

Just SKILL.md in skills/cheat-publish of XBuilderLAB/cheat-on-content.

Open the folder on GitHubat commit 2d8211e

Compare with similar skills

Cheat Publish Registration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cheat Publish Registration compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Cheat Publish Registration this skillXBuilderLAB/cheat-on-content	7.2k	—	~1.3k	Automated safety check: Notes	MIT	2 days ago
Ra Video DownloadPluviobyte/rnskill	1.6k	—	~861	Automated safety check: Notes	Custom licence	16 days ago
Schedule Socialindranilbanerjee/digital-marketing-pro	854	1 repos	~3.4k	Automated safety check: Pass	MIT	3 days ago
Social Media Pro Maxcriptogus/agent-evolve-network	288	—	~1.6k	Automated safety check: Pass	Custom licence	27 days ago
Creator Analytics MasterFerroxLabs/wayland	608	—	~3.6k	Automated safety check: Pass	Apache-2.0	yesterday
Agent ReachPanniantong/Agent-Reach	93k	—	~1.4k	Automated safety check: Pass	MIT	22 days ago

Similar skills

Ra Video Download
Pluviobyte/rnskill
Download source video or audio from Douyin, YouTube, Bilibili, Twitter/X, Xiaohongshu, and other yt-dlp-supported URLs into the content-creation workspace.
1.6k GitHub stars~861 tokensUpdated 16 days ago
Media & CreativeAuto-check: notes
Schedule Social
indranilbanerjee/digital-marketing-pro
Schedule social posts to Twitter/X, Instagram, LinkedIn, TikTok, YouTube, and Pinterest through connected platform MCPs — generating per-platform copy variations, hashtag mixes, media-spec…
854 GitHub starsUsed in 1 repo~3.4k tokens
Writing & ContentAuto-check passed
Social Media Pro Max
criptogus/agent-evolve-network
State-of-the-art viral content + social design intelligence.
288 GitHub stars~1.6k tokensUpdated 27 days ago
Writing & ContentAuto-check passed
Creator Analytics Master
FerroxLabs/wayland
Cross-platform analytics mastery for content creators covering YouTube, Instagram, TikTok, Twitter/X, podcast, and newsletter metrics, audience demographic analysis, content performance patterns…
608 GitHub stars~3.6k tokensUpdated yesterday
Writing & ContentAuto-check passed
Agent Reach
Panniantong/Agent-Reach
Routes web research and platform lookups across 16 sites, including Twitter, Reddit, YouTube, Bilibili, Xiaohongshu and GitHub, through one command-line tool.
93k GitHub stars~1.4k tokensUpdated 22 days ago
Productivity & AutomationAuto-check passed
Video Podcast Maker
Agents365-ai/video-podcast-maker
A skill your agent uses when the user gives a topic and wants an automated topic-driven narrated explainer, podcast, or knowledge-summary video (Bilibili / YouTube / Xiaohongshu / Douyin / WeChat…
1.7k GitHub stars~4.9k tokensUpdated 6 days ago
Media & CreativeAuto-check passed

Questions about Cheat Publish Registration

What does Cheat Publish Registration do?

Records that a piece of content went live by writing its URL, platform and publish time into the prediction file header and state file, leaving the prediction text untouched. This is a light step in a workflow where each post is first blind-predicted and later compared with results.json`, or by listing prediction files whose header lacks a publish time, and it warns if the gap between that session and the URL is more than 14 days.

When should I use Cheat Publish Registration?

Cheat Publish Registration fits situations like: registering a post's link right after publishing it in a prediction workflow; adding the platform and publish time to a prediction file's header; finding which prediction files are still missing a publish record.

How do I install Cheat Publish Registration in Claude Code?

Run `npx skills add XBuilderLAB/cheat-on-content --skill cheat-publish -a claude-code`. Or copy the skill folder (skills/cheat-publish in XBuilderLAB/cheat-on-content) into .claude/skills/cheat-publish in your project. Claude Code loads it when a task matches its description.

How do I install Cheat Publish Registration in Codex?

Run `npx skills add XBuilderLAB/cheat-on-content --skill cheat-publish -a codex`. Or copy the skill folder (skills/cheat-publish in XBuilderLAB/cheat-on-content) into .agents/skills/cheat-publish in your project. Codex loads it when a task matches its description.

Can I use Cheat Publish Registration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add XBuilderLAB/cheat-on-content --skill cheat-publish -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cheat-publish, .gemini/skills/cheat-publish, .github/skills/cheat-publish and .opencode/skills/cheat-publish in your project.

What does Cheat Publish Registration need to run?

SKILL.md names no scripts, command-line tools or credentials: Cheat Publish Registration is instructions for the agent only. Our summary lists: A project with prediction files and a `.cheat-state.json` state file. Its frontmatter pre-approves these tools: Bash(*), Read, Edit, Glob.

Does Cheat Publish Registration access the network?

SKILL.md names 1 domain. In commands or code: v.douyin.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Cheat Publish Registration safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Cheat Publish Registration use?

Cheat Publish Registration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cheat Publish Registration use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cheat Publish Registration?

Skills that share tags, products or a category with Cheat Publish Registration: Ra Video Download (Pluviobyte/rnskill, 1.6k stars), Schedule Social (indranilbanerjee/digital-marketing-pro, 854 stars), Social Media Pro Max (criptogus/agent-evolve-network, 288 stars) and Creator Analytics Master (FerroxLabs/wayland, 608 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cheat Publish Registration?

XBuilderLAB (a GitHub organization) maintains it in XBuilderLAB/cheat-on-content, which has 7,225 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 5, 2026.

Source: XBuilderLAB/cheat-on-content on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Cheat Publish Registration

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

/cheat-publish — 发布登记

Overview

Constants

Inputs

Workflow

Phase 0: 找到对应的预测文件

Phase 1: 解析平台

Phase 2: 更新 prediction 文件 header

Phase 3: 更新 state file

Phase 4: 提醒 + 下一步 + buffer 状态

Key Rules

Refusals

Integration

Files

Compare with similar skills

Similar skills

More from XBuilderLAB/cheat-on-content

Related

Questions about Cheat Publish Registration