Agent skill

Cheat Status

by XBuilderLAB in XBuilderLAB/cheat-on-content

cheat-on-content 的状态看板。显示当前模式 / rubric 版本 / 校准进度 / 待复盘 / pool 状态 / 是否该升级 SQLite / 是否该 bump rubric。任何时候都可调，无副作用。触发词："状态"/"看板"/"status"/"我现在该做什么"/"进度怎么样"。

MITAuto-check: notesEducation

Install Cheat Status

skills CLI

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

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

GitHub CLI

$ gh skill install XBuilderLAB/cheat-on-content cheat-status --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-status .claude/skills/cheat-status && 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-status" agent skill from https://github.com/XBuilderLAB/cheat-on-content/tree/main/skills/cheat-status into .claude/skills/cheat-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cheat-status", 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-status

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-status -a codex

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

GitHub CLI

$ gh skill install XBuilderLAB/cheat-on-content cheat-status --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-status .agents/skills/cheat-status && 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-status" agent skill from https://github.com/XBuilderLAB/cheat-on-content/tree/main/skills/cheat-status into .agents/skills/cheat-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cheat-status", 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-status -a cursor

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

GitHub CLI

$ gh skill install XBuilderLAB/cheat-on-content cheat-status --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-status .cursor/skills/cheat-status && 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-status" agent skill from https://github.com/XBuilderLAB/cheat-on-content/tree/main/skills/cheat-status into .cursor/skills/cheat-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cheat-status", 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-status

--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-status -a gemini-cli

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

GitHub CLI

$ gh skill install XBuilderLAB/cheat-on-content cheat-status --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-status .gemini/skills/cheat-status && 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-status" agent skill from https://github.com/XBuilderLAB/cheat-on-content/tree/main/skills/cheat-status into .gemini/skills/cheat-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cheat-status", 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-status

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-status -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-status .github/skills/cheat-status && 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-status" agent skill from https://github.com/XBuilderLAB/cheat-on-content/tree/main/skills/cheat-status into .github/skills/cheat-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cheat-status", 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-status -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-status --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-status .opencode/skills/cheat-status && 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-status" agent skill from https://github.com/XBuilderLAB/cheat-on-content/tree/main/skills/cheat-status into .opencode/skills/cheat-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cheat-status", 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-status
GitHub stars: 7.2k
Token cost: ~1.5k tokens
SKILL.md length: 415 words
Files: 1
Skills in repo: 16
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Works in 4 steps: 读状态 → 派生指标 → 检测建议触发器 → …
Tasks that involve Quizzes and assessments
SKILL.md covers Overview, Constants, Inputs and Workflow, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Cheat Status is an agent skill from XBuilderLAB/cheat-on-content. cheat-on-content 的状态看板。显示当前模式 / rubric 版本 / 校准进度 / 待复盘 / pool 状态 / 是否该升级 SQLite / 是否该 bump rubric。任何时候都可调，无副作用。触发词："状态"/"看板"/"status"/"我现在该做什么"/"进度怎么样"。

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Education, covering Quizzes and assessments. It works with SQLite. The repository describes itself as: You're reading this. The skill predicted it. A workflow that turns every post into a calibrated experiment—score, blind-predict, retro, evolve. The future doesn't reward effort… The licence is MIT.

When your agent uses it

Tasks that involve Quizzes and assessments

Example prompts

“status”
“我现在该做什么”
“/cheat-status”

Requirements

Python 3
Pre-approved tools (allowed-tools): Bash(*), Read, Glob, Grep

Workflow steps

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

读状态
派生指标
检测建议触发器
输出看板

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
- Glob
- Grep
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 python).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 Status loads about 1.5k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 415 words of instructions outside code blocks.

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

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, Glob, Grep
```

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). 415 words, ~1,514 tokens.

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

name: cheat-status
description: cheat-on-content 的状态看板。显示当前模式 / rubric 版本 / 校准进度 / 待复盘 / pool 状态 / 是否该升级 SQLite / 是否该 bump rubric。**任何时候都可调，无副作用**。触发词："状态"/"看板"/"status"/"我现在该做什么"/"进度怎么样"。
allowed-tools: Bash(*), Read, Glob, Grep

/cheat-status — 状态看板

读 state file + 扫描用户项目 → 汇总当前进度 → 输出"今天该做什么"清单。

Overview

[用户：状态]
  ↓
[Phase 1: 读 .cheat-state.json + 扫文件系统]
  ↓
[Phase 2: 计算派生指标]
  ↓
[Phase 3: 检测建议触发器（升级 / bump / 清算）]
  ↓
[Phase 4: 输出看板]

Constants

SQLITE_UPGRADE_THRESHOLD = 30 — calibration_samples 达到 N 时建议升 SQLite
CLEANUP_LINE_THRESHOLD = 600 — rubric_notes.md 行数超 N 时建议清算
STALE_PREDICTION_DAYS = 30 — in_progress prediction 超 N 天未发布提示清理

Inputs

来源	用途
`.cheat-state.json`	主要状态
`predictions/*.md`	校准样本数 / pending retros
`candidates.md`	候选池规模
`rubric_notes.md`	行数 / 当前版本
`.cheat-cache/usage.jsonl`（如有）	meta-logging 数据，用于"距上次 bump 多少次预测"

Workflow

Phase 1: 读状态

python

state = read_json('.cheat-state.json')
if not state:
    return "你还没初始化。请先跑 /cheat-init。"

predictions = glob('predictions/*.md')
candidates_count = parse_candidates_md_entries()
rubric_lines = wc -l rubric_notes.md

Phase 2: 派生指标

指标	算法
Buffer 数	`len(state.shoots)`
Buffer 颜色	按 cadence-protocol.md 派生：`buffer_days = buffer_count × target_publish_cadence_days`，`<1 红 / 1-2 橙 / 3-5 绿 / >5 蓝`。如 `target_publish_cadence_days=null` → 颜色禁用
Confidence 等级	按 state-management.md confidence 表派生：从 `calibration_samples` 整数派生 emoji + 标签
最早一拍至今天数	`now - state.shoots[0].shot_at`，用于警告"拍了 N 天没发"
校准样本数	predictions 中含完整复盘段（实绩数据非空）的文件数
待复盘	state.pending_retros 中已过 RETRO_WINDOW_DAYS 的
池大小	candidates.md 中 tier!=skip 的 entry 数
上次 bump 至今几次预测	predictions 中 published_at > state.last_bump_at 的数量
同向偏差队列	state.consecutive_directional_errors
in_progress 陈旧度	now - state.in_progress_session.started_at（如有）

Phase 3: 检测建议触发器

按优先级（高→低）逐项检查：

Buffer 颜色 = 🔴 红 → 第一行高优先级警戒："buffer 已 0/1 篇，下个发布日可能断更——今天必须拍 ≥1 条。说'推荐选题'我只推 top 1 稳分（不推实验性）"
Buffer 颜色 = 🔵 蓝 → 高优先级提示："buffer 已 N 篇积压。暂停拍摄，先发存货 + 复盘。说'已发布 ...'我帮你出队"
state.shoots 中最早一项 shot_at > 14 天 → "你有视频拍了 N 天还没发——议题时效流失风险，建议尽快发或弃稿"
in_progress 陈旧 (>= STALE_PREDICTION_DAYS) → 高优先级提示"清理或 publish"
待复盘 ≥ 1 → 高优先级"今天该复盘 X 篇"
pool_status=none + calibration_samples=0 + 距 init >24h → "🌱 你 init 完已经 N 天但还没拍——是因为没选题吗？跑 /cheat-seed 5 分钟拿 5 个候选 + 5 个 draft" 高优先级
Claude 判断系统性偏差信号（不是死磕 ≥3 同向） → 提示"建议跑 /cheat-bump"
- 默认参考：连续 ≥3 次同向偏差
- 但 Claude 可以更早：1 次极端偏差（≥10x）或 2 次同向 + 评论区强反向证据
- 也可以更晚：3 次同向但每次幅度都 <25%（可能只是噪声）
- 提示时显式标注："本次是 [default-aligned] / [judgment-driven]"
calibration_samples 跨入新 confidence 等级（0→1, 2→3, 5→6, 10→11, 20→21）→ 提示"🎉 confidence 升级：<旧等级> → <新等级>。bucket 中枢精度从 ±X% 提到 ±Y%"。仅作通知，无任何用户必须确认的操作——所有 skill 都已经按 calibration_samples 自动调整
calibration_samples 跨过 5 → "你的 rubric 形态可以第一次正式 bump 了。回顾 rubric_notes.md 看观察记录段是否有 ≥3 样本支持的 pattern → 跑 /cheat-bump"
calibration_samples 跨过 10 → "可以跑 /cheat-bump --bucket-only --scheme percentile 让 bucket 边界改用 percentile（永远自洽）"
calibration_samples 跨过 SQLITE_UPGRADE_THRESHOLD 且 data_layer=markdown → "建议跑 tools/md-to-sqlite.py"（planned — batch 3, not yet available）
rubric_notes.md 行数 > CLEANUP_LINE_THRESHOLD → "建议清算观察段（手动或下次 bump 触发）"
calibration_samples ≥ 5 + pool_status=none → "可以开始建立选题池了"
calibration_samples ≥ 15 + pool_status=none → "强烈建议建池：/cheat-trends 或手动建 candidates.md"
state.hooks_installed=false → "你的 immutability 是君子协定，建议跑 /cheat-init 装 hook"
state.last_bump_self_audited=true → "上次 bump 是自审。建议配置 mcp__llm-chat__chat 后下次 bump 走外部审"
state.rubric_form_mismatch=true → "你的 content_form 不是 opinion-video，用了内置观点 rubric。前几篇预测会更不准，下次 bump 时建议自行调整权重适配你的形态"
state.benchmark_status=pending → "🎯 你 init 时答应等下找对标账号但还没找。跑 /cheat-learn-from 导入 ≥3 条对标视频，工具就有 anchor 了"
state.benchmark_status=imported + Claude 判断用户数据信号已超过 benchmark → "📊 你的真实数据已经成为主信号，benchmark 影响淡出"

Show full SKILL.md (76 more words)Show less

默认参考：calibration_samples ≥ 10
但 Claude 可以更早：N=5 但用户的 (打分, 实绩) 配对里出现 ≥3 条与 benchmark pattern 不一致的——说明你的账号已经走出对标的路径
也可以更晚：N=15 但用户的样本都很相似，没足够多样性 → benchmark 仍有信号价值
提示是通知不是 gate——benchmark.md 永远保留作 sanity check，cheat-seed 仍可读

Phase 4: 输出看板

🎛️ cheat-on-content 状态（更新于 2026-05-04 15:00）

内容形态：opinion-video / 时长 3-5min / cadence: 隔日更
当前 rubric：v2 (上次 bump: 2026-04-22)
校准样本：18 篇
Confidence: 🟢 较高 (中枢 ±15%，rubric 形态稳定)
Baseline: 4.2w 中位数

📦 Buffer：3 篇（🟢 绿色）
   按你的 cadence (隔日更)= 6 天 buffer，节奏稳定

📊 进度条
  [█████████████░░░░░] 18 / 30 → SQLite 升级建议门槛
  [██████████░░░░░░░░] 18 / 10 → percentile 桶可用（已超过门槛）

🎬 待办（按紧急度）
  🚨 复盘 1 篇（已过 T+3d）
     - predictions/2026-05-01_db063817_你已不在关系里.md（T+3d 到了）
  ⚠️  同向偏差 3 次（high, high, high）→ 建议 /cheat-bump
  💤 in-progress prediction 已陈旧 35 天
     - predictions/2026-04-01_xxx.md → 是已发了忘登记？还是弃稿？

🔥 候选池
  - candidates.md: 27 条（tier1: 12, tier2: 9, tier3: 6）
  - 距上次抓热点: 4 天 — 可以再跑 /cheat-trends

📈 健康度
  - rubric_notes.md: 412 行（健康，<600 警戒线）
  - hooks_installed: ✅
  - external audit configured: ❌ → 建议配 mcp__llm-chat__chat

下一步建议（按推荐优先级）：
1. /cheat-retro predictions/2026-05-01_db063817_你已不在关系里.md  ← 最紧急
2. /cheat-bump  ← 同向偏差 3 次的处理
3. 处理陈旧 in-progress（手动或回 "清理 in-progress"）

完整的命令清单见主 SKILL.md。

输出风格：直白、具体、可点击。每个建议附确切的命令——用户应能 copy-paste 直接执行。

Key Rules

无副作用。读多写零。任何状态修改是其他 skill 的事
不假装数据可用。state file 字段缺失 → 显式标"未知"，不猜
建议带优先级。10 个建议同时显示用户会麻木——按紧急度排
每个建议附命令。不能只说"该 bump 了"——要给 /cheat-bump --propose "..." 的精确入口

Refusals

「顺便帮我自动跑一下 retro」 → 拒绝。status 是只读，retro 是另一个动作（避免一次操作做两件事）
「我不想看 rubric_notes 行数，太琐碎」 → 输出仍包含但折叠到底部"健康度"区——状态信息的存在让用户在出问题前可见

Integration

上游：所有其他 skill 完成时更新 .cheat-state.json，status 是这些更新的可视化
下游：每个建议都路由到具体子 skill
meta-logging hook（如启用） → 写 usage.jsonl，status 用它算"距上次 X 多少次"

Files

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

Open the folder on GitHubat commit 2d8211e

Compare with similar skills

Cheat Status 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 Status compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Cheat Status this skillXBuilderLAB/cheat-on-content	7.2k	—	~1.5k	Automated safety check: Notes	MIT	2 days ago
Signal Scoringgrandamenium/cortextos	100	—	~2.2k	Automated safety check: Pass	MIT	15 days ago
DeepTutor CLIHKUDS/DeepTutor	41k	—	~2.3k	Automated safety check: Pass	Apache-2.0	3 days ago
AI Engineering Placement Quizrohitg00/ai-engineering-from-scratch	65k	—	~2k	Automated safety check: Pass	MIT	yesterday
Codebase to Coursezarazhangrui/codebase-to-course	5.7k	—	~4.4k	Automated safety check: Pass	None	6 mo ago
AI Engineering Phase Quizrohitg00/ai-engineering-from-scratch	65k	—	~2.1k	Automated safety check: Pass	MIT	yesterday

Similar skills

Signal Scoring
grandamenium/cortextos
Score, deduplicate, rank, and select fresh research signals from SQLite using the configured rubric.
100 GitHub stars~2.2k tokensUpdated 15 days ago
EducationAuto-check passed
DeepTutor CLI
HKUDS/DeepTutor
Teaches the agent to set up and run DeepTutor from the command line: chat and capabilities, knowledge bases, partners, memory, sessions, notebooks and the server or Web app.
41k GitHub stars~2.3k tokensUpdated 3 days ago
EducationAuto-check passed
AI Engineering Placement Quiz
rohitg00/ai-engineering-from-scratch
Runs a 10-question quiz across five areas to place a learner in the AI Engineering from Scratch curriculum, so they skip what they already know.
65k GitHub stars~2k tokensUpdated yesterday
EducationAuto-check passed
Codebase to Course
zarazhangrui/codebase-to-course
Turns a codebase into an interactive single-page HTML course for non-technical learners, with scroll modules, animated diagrams, quizzes and plain-English code translations.
5.7k GitHub stars~4.4k tokensUpdated 6 mo ago
EducationAuto-check passed
AI Engineering Phase Quiz
rohitg00/ai-engineering-from-scratch
Quizzes you on a completed phase of the AI Engineering from Scratch course, taking a phase number or name and mapping it to that phase's directory.
65k GitHub stars~2.1k tokensUpdated yesterday
EducationAuto-check passed
Scholar Evaluation
K-Dense-AI/claude-scientific-writer
Provide qualitative-first, evidence-traceable developmental review of scholarly works and audit low-stakes research-assessment rubrics with optional local quality controls.
2.4k GitHub starsUsed in 2 repos~2.9k tokens
EducationAuto-check: notes

Questions about Cheat Status

What does Cheat Status do?

cheat-on-content 的状态看板。显示当前模式 / rubric 版本 / 校准进度 / 待复盘 / pool 状态 / 是否该升级 SQLite / 是否该 bump rubric。任何时候都可调，无副作用。触发词："状态"/"看板"/"status"/"我现在该做什么"/"进度怎么样"。. Cheat Status is an agent skill from XBuilderLAB/cheat-on-content.

When should I use Cheat Status?

Cheat Status fits situations like: tasks that involve Quizzes and assessments.

How do I install Cheat Status in Claude Code?

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

How do I install Cheat Status in Codex?

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

Can I use Cheat Status 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-status -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-status, .gemini/skills/cheat-status, .github/skills/cheat-status and .opencode/skills/cheat-status in your project.

What does Cheat Status need to run?

SKILL.md names no scripts, command-line tools or credentials: Cheat Status is instructions for the agent only. Our summary lists: Python 3. Its frontmatter pre-approves these tools: Bash(*), Read, Glob, Grep.

Does Cheat Status access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cheat Status 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 Status use?

Cheat Status 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 Status use?

About 1.5k tokens (SKILL.md is roughly 6.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 Status?

Skills that share tags, products or a category with Cheat Status: Signal Scoring (grandamenium/cortextos, 100 stars), DeepTutor CLI (HKUDS/DeepTutor, 41k stars), AI Engineering Placement Quiz (rohitg00/ai-engineering-from-scratch, 65k stars) and Codebase to Course (zarazhangrui/codebase-to-course, 5.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cheat Status?

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 Status

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-status — 状态看板

Overview

Constants

Inputs

Workflow

Phase 1: 读状态

Phase 2: 派生指标

Phase 3: 检测建议触发器

Phase 4: 输出看板

Key Rules

Refusals

Integration

Files

Compare with similar skills

Similar skills

More from XBuilderLAB/cheat-on-content

Related

Questions about Cheat Status