Skill Introduction

Overview

Turn a repeatable workflow from the current session into a reusable OMC skill draft

Core value

Turns reusable Debugging know-how into an installable skill, helping users complete github, community, claude work faster.

Target users

Developers, testers, and maintainers who handle Debugging tasks in Focus Code.
Teams that already trust workflows or content from Yeachan-Heo.
Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

Read the skill content first to confirm required inputs, expected outputs, and dependencies.
Try it on a small task before relying on it for critical work.
Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

Tasks related to github, community, claude that need a reusable execution flow.
Converting a community repo, team convention, or personal workflow into day-to-day assistance.
Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

Results depend on the quality of the original skill content and may need human correction.
It does not replace code review, tests, security review, or professional judgment.
External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

Structured around Debugging, making it easier to discover and reuse than loose prompt snippets.
Marked as GitHub, which helps users judge trust and maintenance expectations.
Keeps the original source link available for repository, documentation, or discussion follow-up.
Tagged with github, community, claude, so it can be filtered by concrete task intent.

Install and use

Install

Copy Install Command

focus install skillify-fe1f19

View source

Detail Preview

SKILL.md

Primary filemarkdown3 KB

name: skillify aliases: [learner] description: Turn a repeatable workflow from the current session into a reusable OMC skill draft

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

Identify the repeatable task the session accomplished.
Extract:
- inputs
- ordered steps
- success criteria
- constraints / pitfalls
- verification evidence
- best target location for the skill
Decide whether the workflow belongs as:
- a repo built-in skill
- a user/project learned skill
- documentation only
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:
```
---
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.
Draft the rest of the skill file with clear triggers, steps, success criteria, and pitfalls.
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

skillify