Agent skill

Oryxos Lesson Dev

by oryx-labs in oryx-labs/oryxos

按课件驱动开发 OryxOS 的一节课模块:输入节号(16~31),自动完成备料 → speckit-specify → clarify → plan → tasks(停等确认)→ implement → 节级验收报告,全程施加硬/软两类门禁, 保证产出严格贴合 docs/TechnicalSolution.md 的 OryxOS 设计。当用户说「开发第 N 节 / 实现第 N 节课的模块 /…

Apache-2.0Auto-check passedDevelopment

Install Oryxos Lesson Dev

skills CLI
$ npx skills add oryx-labs/oryxos --skill oryxos-lesson-dev -a claude-code

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

GitHub CLI
$ gh skill install oryx-labs/oryxos oryxos-lesson-dev --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/oryx-labs/oryxos.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/oryxos-lesson-dev .claude/skills/oryxos-lesson-dev && 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/

Facts

Skill name
oryxos-lesson-dev
GitHub stars
186
Token cost
~1.5k tokens
SKILL.md length
364 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
Apache-2.0

At a glance

按课件驱动开发 OryxOS 的一节课模块:输入节号(16~31),自动完成备料 → speckit-specify → clarify → plan → tasks(停等确认)→ implement → 节级验收报告,全程施加硬/软两类门禁, 保证产出严格贴合 docs/TechnicalSolution.md 的 OryxOS 设计。当用户说「开发第 N 节 / 实现第 N 节课的模块 /…

  • Works in 6 steps: 需要创建"本节交付物"清单之外的任何对外概念(public… → 需要修改任何已定字面量(类名、方法签名、配置键、表列名、端点路径); → 课件与 docs/TechnicalSolution.md 冲突; → …
  • Tasks that involve Spec-driven development
  • SKILL.md covers User Input, 总纪律(贯穿全程), 第 0 步:输入校验与课型分流 and 第 1 步:H0 开工纪律——必读与依赖检查, plus 6 more sections
  • Calls git and mvn

What it does

Oryxos Lesson Dev is an agent skill from oryx-labs/oryxos. 按课件驱动开发 OryxOS 的一节课模块:输入节号(16~31),自动完成备料 → speckit-specify → clarify → plan → tasks(停等确认)→ implement → 节级验收报告,全程施加硬/软两类门禁, 保证产出严格贴合 docs/TechnicalSolution.md 的 OryxOS 设计。当用户说「开发第 N 节 / 实现第 N 节课的模块 / 用 spec kit 做第 N 节」时使用。

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 Development, covering Spec-driven development. The repository describes itself as: OryxOS is an open-source Distributed AI Agent OS. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Spec-driven development

Example prompts

  • “/oryxos-lesson-dev”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. 需要创建"本节交付物"清单之外的任何对外概念(public 类型、配置键、数据表、REST 路径、Profile 字段);
  2. 需要修改任何已定字面量(类名、方法签名、配置键、表列名、端点路径);
  3. 课件与 docs/TechnicalSolution.md 冲突;
  4. 需要修改前序节交付的公共接口(当节课件明确列为"改造点"的除外);
  5. 第三方 API 在本地依赖中核实不到;
  6. 需要新增 plan 未列明的第三方依赖。

What it can do on your machine

Read from SKILL.md and the folder at commit 6f86810. 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:

    • git
    • mvn

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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

Oryxos Lesson Dev loads about 1.5k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 364 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
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 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 oryx-labs/oryxos at commit 6f86810, republished under its Apache-2.0 licence (© oryx-labs). 364 words, ~1,507 tokens.

Download SKILL.mdSave it as .claude/skills/oryxos-lesson-dev/SKILL.md (or your agent's skills folder).
name
oryxos-lesson-dev
description
按课件驱动开发 OryxOS 的一节课模块:输入节号(16~31),自动完成备料 → speckit-specify → clarify → plan → tasks(停等确认)→ implement → 节级验收报告,全程施加硬/软两类门禁, 保证产出严格贴合 docs/TechnicalSolution.md 的 OryxOS 设计。当用户说「开发第 N 节 / 实现第 N 节课的模块 / 用 spec kit 做第 N 节」时使用。
argument-hint
节号(16~31),如:16
user-invocable
true

OryxOS 逐节开发 Skill

User Input

text
$ARGUMENTS

节号来自上面的输入。设计依据见 docs/class/Harness 设计:用门禁保证每个功能符合预期.md,流程原理见 docs/class/Spec-Kit 执行指导:从课件到代码(以第16节为例).md——本 skill 是它们的可执行版本,条款以本文为准执行,不需要复读那两份文档给用户。

总纪律(贯穿全程)

能机器判的绝不留给人,机器判不了的绝不自行发挥。

  • 硬门禁:测试、mvn clean verify、存在性核对——不过不放行,不许绕。
  • 软门禁:遇到下列任一情况,立即停下、向用户报告、等确认后继续,不得自行决定:
    1. 需要创建"本节交付物"清单之外的任何对外概念(public 类型、配置键、数据表、REST 路径、Profile 字段);
    2. 需要修改任何已定字面量(类名、方法签名、配置键、表列名、端点路径);
    3. 课件与 docs/TechnicalSolution.md 冲突;
    4. 需要修改前序节交付的公共接口(当节课件明确列为"改造点"的除外);
    5. 第三方 API 在本地依赖中核实不到;
    6. 需要新增 plan 未列明的第三方依赖。
  • 反作弊:不得删断言、@Disabled、放宽阈值让测试变绿。实现错修实现;认为测试错,停下报告。未全绿不得宣称完成。
  • 全程不自动 commit / push / 运行 package.sh,同步时机由用户决定。

第 0 步:输入校验与课型分流

解析节号 N,按下表分流;表外输入直接报错退出。

N课型处理
16,17,18,19,20,22,24,25,26,29,30代码课走完整流程(第 1~7 步)
21,23评审课拒绝并说明:这节不产码,是下一节(22/24)的 specify 素材
27,28串联课特殊模式:不开新 feature,逐条执行该节课件的对账清单,并把对账固化成课件建议的 @Tag("integration") 测试类(27→HumanTriggerFlowIT;28→SchedulerFlowIT/RestartRecoveryIT),然后出报告
31Demo 课特殊模式:按课件定义 weather-daily(走 30 节 API)与 daily-tech-digest(走手写文件)两个 Agent,完成调试对账与发布清单,不做常规模块开发
其他—报错:仅支持 16~31

第 1 步:H0 开工纪律——必读与依赖检查

  1. 读三样(用 Read 完整读,不凭记忆):
    • 当节课件:docs/class/第{N}节*.md(glob 匹配);
    • docs/TechnicalSolution.md 对应章节(映射表见下);
    • 前序各代码课课件的"本节交付物"小节。
  2. 依赖存在性检查:对前序每节交付物清单里的核心类,在代码库里 grep/Glob 确认存在。任何缺失 → 停下报告"先做第 X 节",不得跳节自造。
  3. 分支:确认当前在该节的 feature 分支上(speckit-specify 的 before_specify hook 会建分支;若 hook 未配置,手动 git checkout -b {NNN}-lesson{N}-<slug>),不在 main/主干上直接开发。

技术方案章节映射表:

节TechnicalSolution 章节
16§3(Provider)、§8.2(Profile)、§9.2(llm_calls)
17§4(ReAct/AgentService/ProfileContext)、§8.3(ContextLoader)、§9.2(tool_invocations)
18§8.4、§8.6(CLI)、§9.2(sessions)
19§6.8(Notify)
20§6.1~6.6(Tool/MCP)
22§5(Memory)
24§6.7(Sandbox)
25§8.5(定时/会话身份)
26§7(Web Service)
29§11.1~11.2(Skill+Profile、运行时注册)
30§11.3~11.4(AgentLifecycleService、/api/v1/agents)
27/28/31§12(关键流程/两个 Demo)

第 2 步:组装并执行 /speckit-specify

用 Skill 工具调用 speckit-specify,参数按此骨架从当节课件的一、二部分提炼(只写 WHAT/WHY,不带类名和技术栈):

text
第{N}节需求:<模块名>——<一句话定位>
背景与价值。<为什么需要,从课件"是什么"部分提炼>
用户场景。<2~3 个具体场景>
功能需求。FR1~FRn <从课件"想清楚"部分提炼,每条可测试>
明确不做(边界)。<课件"有几样先别做"逐项照搬>
验收标准。可自动化部分由课件"验收 harness"测试套件承载(mvn test 全绿即通过),
  关键回归点:<列出课件 harness 里写出代码的那几个测试的守点>;
  人工项见课件"五、做完怎么验"。
依赖与假设。<指向前序节交付物;外部依赖如 BOM/MCP server>

第 3 步:/speckit-clarify

调用 speckit-clarify。有问题答问题(答案只从课件和技术方案找,找不到 → 软门禁停下问用户);无问题继续。

第 4 步:组装并执行 /speckit-plan

参数 = 固定技术栈句 + 本节模块落位 + 测试策略句 + 语法禁区:

固定技术栈句:JDK 21 + Spring Boot 3.x + Spring AI Alibaba(动手前先跑 mvn dependency:tree 确认锁定 BOM 里目标依赖存在)、SQLite + Spring Data JPA。凭证走环境变量占位,不落明文。SQLite 用手工建表脚本,不依赖 hibernate.ddl-auto=update。

模块落位表(照抄本节行,细节以 TechnicalSolution §10 为准):

节落位
16Profile/ProfileLoader/ProfileRegistry→oryxos-core;ProviderService/适配器→oryxos-provider;LlmCall+Repository→oryxos-storage
17ReActLoop/PromptBuilder/ToolExecutor/AgentService/ProfileContext/ContextLoader→oryxos-core;ToolInvocation+Repository→oryxos-storage
18OryxOsCli+12 命令→oryxos-cli;CliChannel→oryxos-channel-cli;SessionManager 接口→oryxos-core,Session 实体+Repository→oryxos-storage
19notify 包(Adapter/Target/Webhook 实现/NotifyTools)→oryxos-tool
20OryxTool/ToolResult→oryxos-core;其余(Registry/内置 Tool/MCP)→oryxos-tool
22全部→oryxos-memory
24sandbox 包→oryxos-tool
25AgentScheduler/ScheduleConfig→oryxos-core
26Controller/异常处理/static-admin→oryxos-web
29运行时注册方法→oryxos-core 既有类;示例 Skill/Profile→.oryxos/
30AgentApiController→oryxos-web;AgentLifecycleService→oryxos-core

测试策略句(从课件"验收 harness"抄):测试策略按课件"验收 harness"执行:<测试类清单>(覆盖 <关键回归点>),单测默认跑、集成冒烟打 @Tag("integration") CI 跳过;实现完成的定义是 mvn clean verify 全绿。

语法禁区句:避开 P3C/ASM 解析不了的 Java 18+ 语法形态(如增强 switch 的 default -> 写法),静态检查是构建门禁。

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

第 5 步:/speckit-tasks + 固定软停点

  1. 调用 speckit-tasks。
  2. 自动比对:任务清单 ↔ 课件"本节交付物"(代码/测试/配置/表逐项),并确认测试任务先于或伴随对应实现任务(harness 先行)。
  3. 输出比对结果(齐 / 缺什么 / 多什么),停下等用户确认后才进入下一步。这是流程中唯一的固定停点,不许跳过。

第 6 步:/speckit-analyze(建议跑)+ /speckit-implement

implement 期间逐任务执行,附加门禁:

  • 写前(H3):涉及第三方 API 的任务,先在本地依赖核实方法存在;核实不到 → 软门禁。
  • 写中(H1/H5):只创建交付物点名的对外概念;已定字面量逐字保真;异常不吞(catch 必落审计/日志或上抛);不建文档外抽象层;注释只写"为什么"。测试方法名必须是英文(驼峰或 snake_case,如 callWithToolSchema_disablesAutoExecution),不得用中文方法名;课件 harness 里若给出中文方法名,翻译成语义等价的英文名落地,并用 @DisplayName 保留课件原文以便对号。
  • 写后(任务级 DoD):实现与测试一起落地,跑该模块测试,红了当场修,不攒到最后。
  • 课件"验收 harness"里写出代码的关键回归测试必须原样落地(断言逻辑逐条保真;方法名按上条规则译成英文,课件原文进 @DisplayName)。

第 7 步:节级收尾——六项证据 DoD

全部满足才可宣布本节完成,逐项把证据写进验收报告:

  1. mvn clean verify 全绿(含 P3C/SpotBugs/FindSecBugs/PMD),贴关键输出;
  2. 课件 harness 映射表的每个测试类存在且非空,关键回归测试逐个对号;
  3. "本节交付物"逐项 ls/grep 存在性核对;
  4. 前序节全部测试回归绿(跨节契约证据);
  5. H4 六条全局不变量逐条自查:①涉外 IO 首行过 Sandbox.enforce(Sandbox 未就位的节:留调用位注明 24 节接线)②LLM 调用成败都落 llm_calls、工具执行成败都落 tool_invocations ③grep 无明文 key ④session_id 只在 SessionManager 内拼接 ⑤无 Reactor/CompletableFuture/自建线程池 ⑥无 Spring AI 自动工具执行路径;
  6. 验收报告收尾:以上证据 + 课件"做完怎么验"的剩余人工项清单(真模型/真 webhook/冒烟等),明确告知用户"harness 已判卷,这几项等你人工过"。
  7. 变更总结(给 reviewer 的导读,直接输出在对话里,不另开文件)——以 git status --short / git diff --stat 实测为准,三段固定结构:
    • 改动点:按模块分组列新增 / 移动(改名)/ 修改 / 删除的文件,每处一句话说明动机;前序节文件被本节触碰的(哪怕只改 import)单独标出;
    • 重点 review 清单:按风险排序 3~6 条——架构决策(依赖方向、契约变化)优先,其次课件骨架同构性(逐行对照点)、跨节契约兼容性、静态门禁妥协点(如为过 P3C 改名);每条给出文件行级定位;
    • 如何验证:可直接复制执行的命令块(全量门禁、只跑本节测试、关键回归单测、依赖方向 grep 等),每条命令注明预期结果;最后重复剩余人工项。

报告完停止——commit/push/package.sh 由用户决定。

© oryx-labs, Apache-2.0. 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 .claude/skills/oryxos-lesson-dev of oryx-labs/oryxos.

Open the folder on GitHubat commit 6f86810

Compare with similar skills

Oryxos Lesson Dev 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.

Oryxos Lesson Dev compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Oryxos Lesson Dev this skilloryx-labs/oryxos186—~1.5kAutomated safety check: PassApache-2.0
OpenSpec Bulk Change ArchiverFission-AI/OpenSpec71k2 repos~5.6kAutomated safety check: PassMIT
Speckit ConstitutionWeihanLi/WeihanLi.Common24211 repos~2.1kAutomated safety check: PassApache-2.0
Speckit Plankunstmusik/blue15418 repos~2.1kAutomated safety check: PassGPL-3.0
Speckit Specifykunstmusik/blue15418 repos~4.7kAutomated safety check: PassGPL-3.0
Review Spdzhu1090093659/spec_driven_develop985—~1.5kAutomated safety check: PassMIT

Similar skills

  • Archives several completed OpenSpec changes in one operation, checking the codebase to resolve spec conflicts rather than archiving blindly.

    71k GitHub starsUsed in 2 repos~5.6k tokens
    DevelopmentAuto-check passed
  • Speckit Constitution

    WeihanLi/WeihanLi.Common

    Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

    242 GitHub starsUsed in 11 repos~2.1k tokens
    DevelopmentAuto-check passed
  • Speckit Plan

    kunstmusik/blue

    Execute the implementation planning workflow using the plan template to generate design artifacts.

    154 GitHub starsUsed in 18 repos~2.1k tokens
    DevelopmentAuto-check passed
  • Speckit Specify

    kunstmusik/blue

    Create or update the feature specification from a natural language feature description.

    154 GitHub starsUsed in 18 repos~4.7k tokens
    DevelopmentAuto-check passed
  • Review Spd

    zhu1090093659/spec_driven_develop

    Findings-first code review workflow for AI coding agents. An agent skill from zhu1090093659/spec_driven_develop.

    985 GitHub stars~1.5k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed
  • Speckit Tasks

    kunstmusik/blue

    Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

    154 GitHub starsUsed in 18 repos~3k tokens
    DevelopmentAuto-check passed

More from oryx-labs/oryxos

  • Oryxos Admin UI

    oryx-labs/oryxos

    生成或扩展 OryxOS 的 Web 管理台(web manager)前端——Vue 3 + Vite 单页应用,视觉与官网首页 (website/,VitePress)完全同源:深色底 + 橙色主色、Inter/JetBrains Mono。内置这套设计 token、 工程约定(base '/admin/'、产物落 oryxos-web static/admin、SPA…

    186 GitHub stars~913 tokensUpdated today
    Auto-check passed
  • Oryxos Init

    oryx-labs/oryxos

    初始化 OryxOS(或同类 JDK 21 + Spring Boot 3.x 企业级单体)的工程地基:Maven 多模块骨架、 结构化日志、Actuator + Prometheus 监控、Spring MVC + 虚拟线程、springdoc OpenAPI、 统一响应体与全局异常/错误码、Google 格式 + 阿里编码规约(Spotless + 阿里 P3C +…

    186 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

Categories

Questions about Oryxos Lesson Dev

What does Oryxos Lesson Dev do?

按课件驱动开发 OryxOS 的一节课模块:输入节号(16~31),自动完成备料 → speckit-specify → clarify → plan → tasks(停等确认)→ implement → 节级验收报告,全程施加硬/软两类门禁, 保证产出严格贴合 docs/TechnicalSolution.md 的 OryxOS 设计。当用户说「开发第 N 节 / 实现第 N 节课的模块 /…. Oryxos Lesson Dev is an agent skill from oryx-labs/oryxos.

When should I use Oryxos Lesson Dev?

Oryxos Lesson Dev fits situations like: tasks that involve Spec-driven development.

How do I install Oryxos Lesson Dev in Claude Code?

Run `npx skills add oryx-labs/oryxos --skill oryxos-lesson-dev -a claude-code`. Or copy the skill folder (.claude/skills/oryxos-lesson-dev in oryx-labs/oryxos) into .claude/skills/oryxos-lesson-dev in your project. Claude Code loads it when a task matches its description.

How do I install Oryxos Lesson Dev in Codex?

Run `npx skills add oryx-labs/oryxos --skill oryxos-lesson-dev -a codex`. Or copy the skill folder (.claude/skills/oryxos-lesson-dev in oryx-labs/oryxos) into .agents/skills/oryxos-lesson-dev in your project. Codex loads it when a task matches its description.

Can I use Oryxos Lesson Dev 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 oryx-labs/oryxos --skill oryxos-lesson-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/oryxos-lesson-dev, .gemini/skills/oryxos-lesson-dev, .github/skills/oryxos-lesson-dev and .opencode/skills/oryxos-lesson-dev in your project.

What does Oryxos Lesson Dev need to run?

Going by SKILL.md and its folder, Oryxos Lesson Dev needs the command-line tools its instructions call (git and mvn).

Does Oryxos Lesson Dev access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Oryxos Lesson Dev 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 Oryxos Lesson Dev use?

Oryxos Lesson Dev is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Oryxos Lesson Dev use?

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

Skills that share tags, products or a category with Oryxos Lesson Dev: OpenSpec Bulk Change Archiver (Fission-AI/OpenSpec, 71k stars), Speckit Constitution (WeihanLi/WeihanLi.Common, 242 stars), Speckit Plan (kunstmusik/blue, 154 stars) and Speckit Specify (kunstmusik/blue, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Oryxos Lesson Dev?

oryx-labs (a GitHub organization) maintains it in oryx-labs/oryxos, which has 186 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 9, 2026.

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