技能化
- 作者仓库星标 34,677
- 作者仓库 oh-my-claudecode
- 领域
- 通用
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @Yeachan-Heo · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# Skillify
Use this skill when the current session uncovered a repeatable workflow that should become a reusable OMC skill.
> Compatibility: `/oh-my-claudecode:learner` is a deprecated alias for this skill. Prefer `/oh-my-claudecode:skillify` in docs, prompts, and new workflows. Internal implementation modules may still use the learner name.
## Goal
Capture a successful multi-step workflow as a concrete skill draft instead of rediscovering it later.
## Quality Gate
Before extracting a skill, all three should be true:
- "Could someone Google this in 5 minutes?" → No.
- "Is this specific to this codebase, project, or workflow?" → Yes.
- "Did this take real debugging, design, or operational effort to discover?" → Yes.
Prefer skills that encode decision-making heuristics, constraints, pitfalls, and verification steps. Avoid generic snippets, boilerplate, or library usage examples that belong in normal documentation.
## Workflow
1. Identify the repeatable task the session accomplished.
2. Extract:
- inputs
- ordered steps
- success criteria
- constraints / pitfalls
- verification evidence
- best target location for the skill
3. Decide whether the workflow belongs as:
- a repo built-in skill
- a user/project learned skill
- documentation only
4. When drafting a learned skill file, output a complete skill file that starts with YAML frontmatter.
- Never emit plain markdown-only skill files.
- Do **not** write plain markdown without frontmatter.
- Minimum frontmatter:
```yaml
---
name: <skill-name>
description: <one-line description>
triggers:
- <trigger-1>
- <trigger-2>
---
```
- Write learned/user/project skills to flat file-backed paths:
- `${CLAUDE_CONFIG_DIR:-~/.claude}/skills/omc-learned/<skill-name>.md`
- `.omc/skills/<skill-name>.md`
- Remember that uncommitted skills are still worktree-local until committed or copied to a user-level directory.
5. Draft the rest of the skill file with clear triggers, steps, success criteria, and pitfalls.
6. Point out anything still too fuzzy to encode safely.
## Rules
- Only capture workflows that are actually repeatable.
- Keep the skill practical and scoped.
- Prefer explicit success criteria over vague prose.
- If the workflow still has unresolved branching decisions, note them before drafting.
- Keep `omc-learned` as the storage directory name for compatibility; do not present it as the public invocation name.
## Output
- Proposed skill name
- Target location
- Draft workflow structure or complete skill file
- Verification or quality-gate notes
- Open questions, if any
章节与文件索引
按说明文件中的顺序排列。
质量门
工作流程
规则
输出
文件/命令 -> /oh-my-claudecode:learner · /oh-my-claudecode:skillify · ${CLAUDE_CONFIG_DIR:-~/.claude}/skills/omc-learned/<skill-name>.md · .omc/skills/<skill-name>.md · omc-learned
内容校验值 -> cf34f4387470
当前原文的自动摘译,尚未人工审校。
质量门
在提取一项技能之前,这三个条件都应该为真:“有人可以在 5 分钟内用 Google 搜索一下吗?” → 否。“这是特定于该代码库、项目或工作流程的吗?” → 是的。 “这是否需要真正的调试、设计或操作努力才能发现?” → 是的。优先考虑编码决策启发法、约束、陷阱和验证步骤的技能。避免使用普通文档中的通用片段、样板文件或库使用示例。
工作流程
确定会话完成的可重复任务。提取:输入有序步骤成功标准
规则
仅捕获实际上可重复的工作流程。保持技能的实用性和范围。比起模糊的散文,更喜欢明确的成功标准。如果工作流程仍有未解决的分支决策,请在起草之前记下它们。为了兼容,保留
omc-learned作为存储目录名称;不要将其作为公共调用名称呈现。输出
建议的技能名称 目标位置 工作流程结构草案或完整的技能文件 验证或质量门说明 未解决的问题(如果有)