Google Antigravity SDK
google-antigravity/antigravity-sdk-python
Design, implement, and debug autonomous AI agents and multi-agent systems using the Google Antigravity (AGY) SDK.
CC 与 Codex（或两个各自独立运行的 CC 会话）之间用 OS 信道留言、查未读、被新消息唤醒。触发：要跨 harness 把结论交给对端、给对端留言或清未读、用户问"能不能让 Claude 和 Codex 互相沟通"。不适用于派子 agent 或 workflow 内部协作——那是 Agent 与 SendMessage，信道对同会话的子 agent 没有意义。
Install Os Channel
$ npx skills add CronusL-1141/AI-company --skill os-channel -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install CronusL-1141/AI-company os-channel --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/CronusL-1141/AI-company.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugin/skills/os-channel .claude/skills/os-channel && rm -rf skills-srcUse ~/.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/
Install the "os-channel" agent skill from https://github.com/CronusL-1141/AI-company/tree/master/plugin/skills/os-channel into .claude/skills/os-channel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "os-channel", 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 install https://github.com/CronusL-1141/AI-company/tree/master/plugin/skills/os-channelType 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.
$ npx skills add CronusL-1141/AI-company --skill os-channel -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install CronusL-1141/AI-company os-channel --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CronusL-1141/AI-company.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugin/skills/os-channel .agents/skills/os-channel && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "os-channel" agent skill from https://github.com/CronusL-1141/AI-company/tree/master/plugin/skills/os-channel into .agents/skills/os-channel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "os-channel", 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.
$ npx skills add CronusL-1141/AI-company --skill os-channel -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install CronusL-1141/AI-company os-channel --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CronusL-1141/AI-company.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugin/skills/os-channel .cursor/skills/os-channel && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "os-channel" agent skill from https://github.com/CronusL-1141/AI-company/tree/master/plugin/skills/os-channel into .cursor/skills/os-channel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "os-channel", 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 https://github.com/CronusL-1141/AI-company.git --path plugin/skills/os-channel--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add CronusL-1141/AI-company --skill os-channel -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install CronusL-1141/AI-company os-channel --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CronusL-1141/AI-company.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugin/skills/os-channel .gemini/skills/os-channel && rm -rf skills-srcUse ~/.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/
Install the "os-channel" agent skill from https://github.com/CronusL-1141/AI-company/tree/master/plugin/skills/os-channel into .gemini/skills/os-channel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "os-channel", 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.
$ gh skill install CronusL-1141/AI-company os-channelInstalls 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).
$ npx skills add CronusL-1141/AI-company --skill os-channel -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/CronusL-1141/AI-company.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugin/skills/os-channel .github/skills/os-channel && rm -rf skills-srcUse ~/.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/
Install the "os-channel" agent skill from https://github.com/CronusL-1141/AI-company/tree/master/plugin/skills/os-channel into .github/skills/os-channel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "os-channel", 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.
$ npx skills add CronusL-1141/AI-company --skill os-channel -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install CronusL-1141/AI-company os-channel --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CronusL-1141/AI-company.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugin/skills/os-channel .opencode/skills/os-channel && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "os-channel" agent skill from https://github.com/CronusL-1141/AI-company/tree/master/plugin/skills/os-channel into .opencode/skills/os-channel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "os-channel", 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
os-channel- GitHub stars
- 371
- Token cost
- ~969 tokens
- SKILL.md length
- 207 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
CC 与 Codex（或两个各自独立运行的 CC 会话）之间用 OS 信道留言、查未读、被新消息唤醒。触发：要跨 harness 把结论交给对端、给对端留言或清未读、用户问"能不能让 Claude 和 Codex 互相沟通"。不适用于派子 agent 或 workflow 内部协作——那是 Agent 与 SendMessage，信道对同会话的子 agent 没有意义。
- Works in 4 steps: 约定身份和频道 → 发信 → 读信与清零 → …
- Agent Workflows work in your project
- SKILL.md covers 三条能力，边界要说准, 1. 约定身份和频道, 2. 发信 and 3. 读信与清零, plus 2 more sections
- Calls bash
What it does
Os Channel is an agent skill from CronusL-1141/AI-company. CC 与 Codex（或两个各自独立运行的 CC 会话）之间用 OS 信道留言、查未读、被新消息唤醒。触发：要跨 harness 把结论交给对端、给对端留言或清未读、用户问"能不能让 Claude 和 Codex 互相沟通"。不适用于派子 agent 或 workflow 内部协作——那是 Agent 与 SendMessage，信道对同会话的子 agent 没有意义。
Its SKILL.md is about 970 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 Agent Workflows. It works with Model Context Protocol. The repository describes itself as: Multi-agent team operating system for Claude Code. 108 MCP tools, 40+ agent templates, 10 lifecycle hooks, 7 pipeline workflows. Persistent teams, structured meetings, task wall… The licence is MIT.
When your agent uses it
- Agent Workflows work in your project
Example prompts
- “能不能让 Claude 和 Codex 互相沟通”
- “/os-channel”
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 3275b8a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bash
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
Os Channel loads about 969 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 207 words of instructions outside code blocks.
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 passed
The automated check found no risky patterns in SKILL.md.
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 CronusL-1141/AI-company at commit 3275b8a, republished under its MIT licence (© CronusL-1141). 207 words, ~969 tokens.
Download SKILL.mdSave it as
.claude/skills/os-channel/SKILL.md (or your agent's skills folder).- name
- os-channel
- description
- CC 与 Codex（或两个各自独立运行的 CC 会话）之间用 OS 信道留言、查未读、被新消息唤醒。触发：要跨 harness 把结论交给对端、给对端留言或清未读、用户问"能不能让 Claude 和 Codex 互相沟通"。不适用于派子 agent 或 workflow 内部协作——那是 Agent 与 SendMessage，信道对同会话的子 agent 没有意义。
OS Channel — 让另一个 AI 找得到你
两个 AI 会话各自独立、互不可见。这个信道让它们能留言、能知道有人叫自己、甚至能被 新消息叫醒。
三条能力，边界要说准
| CC | Codex | |
|---|---|---|
| 发信 / 主动读信 / 标记已读 | ✅ 实测 | ✅ 实测 |
| 开口时自动提示未读 | ✅ 实测 | ✅ 实测（2026-09-09，CLI 与桌面端各一次）：提示在任何工具调用之前进入模型上下文 |
| 没人开口时也能收到消息 | ✅ 实测：事件驱动，武装 watcher 后约 8 秒 | ✅ 实测：显式等待，会话调 channel_wait 挂起，来信即返回；没在等的空闲会话不会被叫醒 |
| 会话已退出后被叫醒 | ❌ | ❌ |
两侧第三行的机制根本不同，不要混为一谈：
- CC 是消息把会话叫醒——watcher 发现有人点名就退出，后台任务退出触发 harness 重新 调起模型。延迟取决于轮询间隔（默认 8 秒）。
- Codex 是会话自己决定等——调
channel_wait后挂在 WS 上，来信即返回，到期则返回末次 补读结果。响应里的delivery_source说明走的是哪条路：replay（一开始就有信）、event（等到推送后补读）、timeout_read（到期补读，可能有信也可能为空）。没有调channel_wait的空闲会话什么都收不到，这一点与 CC 的 watcher 不对等。
（Codex 侧 hook 要让模型看见输出必须走 hookSpecificOutput.additionalContext，纯文本
stdout 不注入——这条属 Codex hook 开发面，见 plugin/harness/codex/。）
失效模式也不同类，排障时先分清是哪一种：
- CC 会整体停摆：进程被环境挤掉、忘了重新武装、会话消亡。特征是从某一刻起完全没 反应，容易发现。
- Codex 是等或不等在模型手里：
channel_wait是它自己决定调的，指令躺在上下文里不等 于会被执行；没调就等于没在收。另有到期返回空页的正常情况（status=timeout），别当 成故障。
所以「对方没回」不能直接推成「对方没收到」，两种形态要用不同办法确认。
三条纪律：
- 最后一行是硬天花板：会话退出后模型不在运行，没有任何东西能接收唤醒。跟用户描述 时不要含糊成"实时通信"。
- 两侧能力不对称，不要按 CC 的结论描述 Codex。上表前三行两侧都有真机背书，但机制 不同：描述 Codex 时说"开口时会被提示、可以显式挂起等信"，不要说"消息会把它叫醒"。
- CC 的 8 秒是检查频率，不是端到端延迟；Codex 的
channel_wait是显式挂起，快慢取决 于它有没有在等。给用户解释时别用这些数去承诺一个确定的延迟，也别说"实时互通"。
1. 约定身份和频道
- reader 是角色标识（
leader-cc/leader-codex），不是 session_id。会话是一次性 的，按会话记已读水位会让每开一个新会话就把全部历史消息重算成未读。 - 用专线频道（如
team:<项目名>-bridge）而不是project:<id>频道——后者是项目级 广播，同项目的其他会话都会读到。频道名只过格式校验，不要求 team 真实存在。
2. 发信
channel_send(
channel="team:aiteam-os-bridge",
message="...",
sender="leader-cc",
mentions=["leader-codex"], # 不写 mentions 对方就不会被提示
project_id="<项目 id>", # 你自己解析不到项目时必须显式传，见下
)mentions里裸名与@名都算数，未读判定两种都认project_id留空时按发送方自己的工作目录自动归属（cwd 最长前缀匹配），与收件方在 哪运行无关。现行纪律下 worktree 一律建在仓库内.worktrees/，属子目录，能正常解析； 只有 cwd 落在所有已注册项目路径之外（例如 worktree 被建到了仓库同级目录）才解析不到。 拿不准就先context_resolve。- 归属为空的消息照发照存，但不进任何人的未读——收件人不会被提示，只能主动读到。 这是刻意的取舍（拒收会打死所有不用未读功能的历史调用方），但代价是漏传 project_id 这件事不会报错，只会让消息静悄悄地谁也不通知。
3. 读信与清零
channel_read(channel="team:aiteam-os-bridge") # 纯读，不清未读
channel_read_ack( # 清零
channel="team:aiteam-os-bridge",
reader="leader-cc",
project_id="<项目 id>", # 同上：你解析不到项目时必须传
last_read_at="<你实际读到的最后一条的 created_at>",
)last_read_at 填你本次实际读到的最后一条的 created_at（工具描述与每轮注入的未读
提示行里都已给出这个口径和拼好的 ack 命令）。
不是你的事，就别清零
水位按 (reader, channel, project_id) 记，而同一端的所有会话共用同一个 reader。所以
你一 ack，同一 harness 的其他会话的徽章一起消失——那条消息对它们从此隐形，除非有人
主动 channel_read 去翻。
这是刻意的取舍：按会话记水位会让每开一个新会话就把全部历史消息重算成未读，那更糟。 代价就落在纪律上：
- 读到明显是发给另一个会话的消息（比如点名的是另一份工作、或内容属于别人手上的 任务），读了就好，不要 ack，把它留给该处理的那个会话
- 只有"这件事归我处理"时才推进水位
- 拿不准就别 ack。重复看到一条消息是噪音，让它对所有人消失是丢消息
4. 被新消息叫醒（可选，需要武装）
默认情况下，对方发的消息要等下次有人跟你说话时你才会看到。要让它主动叫醒你：
bash scripts/os-watch.sh <session_id> <team_id> <reader> # 必须以宿主的后台任务方式起（run_in_background）watcher 每 8 秒问一次 GET /api/wake/actionable，发现有人点名你就退出，而后台任务
退出会让 harness 重新调起你。实测：对端发消息后约 8 秒内自动醒来，用户零输入。
约束：
- 随会话消亡：父进程没了即自判孤儿退出（日志
WATCHER_ORPHANED）；另有 12h 硬超时 兜底（OS_WATCH_MAX=43200）。它不是常驻服务；触发一次即退出， 醒来后要重新武装 - 只能用宿主的后台任务方式起：在前台 shell 里
nohup … &起的，父 shell 一退它就自判 孤儿退出（日志WATCHER_ORPHANED），看起来像"又被杀了" - 第三个参数
reader不传就不把信道点名算作唤醒信号 OS_WATCH_SIGNALS=mentions可只盯信道点名；跑 workflow 时必开，否则每条子 agent 的 进展 memo 都会叫醒你- 判据是"新到达"而非"当前未读"：读了但没清零的消息不会让它反复唤醒你
检查有没有人叫你
channel_unread(reader="leader-cc") # 纯读，不会清掉未读© CronusL-1141, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugin/skills/os-channel of CronusL-1141/AI-company.
Open the folder on GitHubat commit 3275b8a
Compare with similar skills
Os Channel 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Os Channel this skillCronusL-1141/AI-company | 371 | — | ~969 | Automated safety check: Pass | MIT | |
| Google Antigravity SDKgoogle-antigravity/antigravity-sdk-python | 3.7k | — | ~2.1k | Automated safety check: Notes | Apache-2.0 | |
| Chatgpt AppsHaohao-end/openagent | 791 | 1 repos | ~4.9k | Automated safety check: Pass | Apache-2.0 | |
| Autocontext for Hermesgreyhaven-ai/autocontext | 1.3k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| Workflow Schema Tuningbreaking-brake/cc-wf-studio | 5.4k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Documentation Serverandrea9293/mcp-documentation-server | 343 | — | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
Chatgpt Apps
Haohao-end/openagent
Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI.
Autocontext for Hermes
greyhaven-ai/autocontext
Lets a Hermes agent run Autocontext scenarios, inspect Hermes curator state, export reusable knowledge and prepare local MLX or CUDA training data through the autoctx CLI.
Workflow Schema Tuning
breaking-brake/cc-wf-studio
Guides edits to cc-wf-studio's workflow schema so AI agents generate better workflows, treating schema text as prompt engineering rather than validation.
Documentation Server
andrea9293/mcp-documentation-server
A skill your agent uses when you need to store, retrieve, search, or manage documents in a local knowledge base with semantic search and hybrid (vector + full-text) retrieval.
Clawmem
yoloshii/ClawMem
ClawMem operational reference for agents at query time — the 3-rule escalation gate, MCP tool routing, the 4 query-optimization levers, pipeline behavior (query vs intentsearch), composite scoring…
More from CronusL-1141/AI-company
Meeting Facilitate
CronusL-1141/AI-company
用 meeting 工具跑一场多 Agent 会议：创建 → 亲自 spawn 参与者 → 推进轮次 → 签到 → conclude 并把决策上墙。仅当已决定以「开会」形式产出一个需上墙的决策时使用；典型场景是减法类提案：回退既有设计决策、砍工具删表、削弱或删除自动检查——这类结论必须留痕。加法（新增检查、加严判据、新增工具）不需要开会，写清理由直接做。用户只是让你评审代码、复盘、比较方案时不要…
Os Release
CronusL-1141/AI-company
发布 AI Team OS 新版本的完整清单——预检、版本七处锁步、中英双语 CHANGELOG、双份 dist 构建、私有术语扫描、commit/tag、双仓推送、建 GitHub Release 条目并核对 latest 徽章、事后核对。当准备发版、补建漏掉的 Release 条目、或核对已发版本的线上状态时使用。
Os Workflow
CronusL-1141/AI-company
AI Team OS 里用 CC 内置 Workflow 的两件事：产出回写 OS 的标准模板（§1-2、§4），以及审查分级与派工档位纪律（§3/§3.1）。准备调用 Workflow 编排子 agent 时，或要判定一件事该按 L0/L1/L2 哪一档审查（含「这活要不要开 workflow」）时使用。
Meeting Participate
CronusL-1141/AI-company
你被派来参加 AI Team OS 会议（派你的 prompt 里带 meetingid），且要在 Round 2 及之后发言时用：怎么拿到自己的 agentid、怎么引用前人发言、roundnumber 怎么填。Round 1 的材料、发言规则与调用样例已经写在派你的 prompt 里，不必读本技能。
Related
Works with
Categories
Questions about Os Channel
What does Os Channel do?
CC 与 Codex（或两个各自独立运行的 CC 会话）之间用 OS 信道留言、查未读、被新消息唤醒。触发：要跨 harness 把结论交给对端、给对端留言或清未读、用户问"能不能让 Claude 和 Codex 互相沟通"。不适用于派子 agent 或 workflow 内部协作——那是 Agent 与 SendMessage，信道对同会话的子 agent 没有意义。. Os Channel is an agent skill from CronusL-1141/AI-company.
When should I use Os Channel?
Os Channel fits situations like: agent Workflows work in your project.
How do I install Os Channel in Claude Code?
Run `npx skills add CronusL-1141/AI-company --skill os-channel -a claude-code`. Or copy the skill folder (plugin/skills/os-channel in CronusL-1141/AI-company) into .claude/skills/os-channel in your project. Claude Code loads it when a task matches its description.
How do I install Os Channel in Codex?
Run `npx skills add CronusL-1141/AI-company --skill os-channel -a codex`. Or copy the skill folder (plugin/skills/os-channel in CronusL-1141/AI-company) into .agents/skills/os-channel in your project. Codex loads it when a task matches its description.
Can I use Os Channel 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 CronusL-1141/AI-company --skill os-channel -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/os-channel, .gemini/skills/os-channel, .github/skills/os-channel and .opencode/skills/os-channel in your project.
What does Os Channel need to run?
Going by SKILL.md and its folder, Os Channel needs the command-line tools its instructions call (bash).
Does Os Channel 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 Os Channel safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Os Channel use?
Os Channel 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 Os Channel use?
About 969 tokens (SKILL.md is roughly 3.9k 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 Os Channel?
Skills that share tags, products or a category with Os Channel: Google Antigravity SDK (google-antigravity/antigravity-sdk-python, 3.7k stars), Chatgpt Apps (Haohao-end/openagent, 791 stars), Autocontext for Hermes (greyhaven-ai/autocontext, 1.3k stars) and Workflow Schema Tuning (breaking-brake/cc-wf-studio, 5.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Os Channel?
CronusL-1141 (a GitHub user) maintains it in CronusL-1141/AI-company, which has 371 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 10, 2026.
Source: CronusL-1141/AI-company on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.