OkayStudy
EN English 한국어 日本語 中文 हिन्दी বাংলা اردو Español Português Français Deutsch Русский العربية Bahasa Indonesia Tiếng Việt ไทย Türkçe

How to enable notifications

Notifications are unavailable in this browser or on this address. Try a supported browser on the secure BaeumNova site.

If notifications are blocked, allow them in your browser settings.

  1. Open the site controls beside the address bar, or your browser’s site settings. Set Notifications for this site to Allow.
  2. In your device settings, allow notifications for your browser and check Do Not Disturb or Focus.
  3. Return to BaeumNova and reload the page. Once notifications are on, the bell disappears.

On iPhone or iPad, add BaeumNova to your Home Screen, open it there, then allow notifications.

Guest

Sign in to see your lesson schedule.

Getting started

Start English lessons step by step

Tap a step to go there.

Free trial

  1. Pick a free trial teacher

    Tap a teacher with [Free trial] on the photo.

  2. Tap a time with a gift

    Tap a free time with a gift picture in the timetable.

  3. Sign in and book

    Sign in and it is booked right away. No payment.

  4. Camera & Mic Check

    Check your camera and mic before class.

  5. Check your booked lessons

    See the time and tutor of your booked lesson.

  6. Enter the lesson

    Join the video classroom when it’s time.

  7. Check your past lessons

    Look back at the lessons you finished.

  8. Rate your tutor

    Rate your tutor after the lesson.

About me

  1. Add your profile photo

    A photo helps your tutor recognize you.

  2. Introduce yourself

    Write a hello on the introductions board.

Take lessons

  1. Book a lesson

    Pick a time on a tutor’s timetable.

  2. Pay the lesson fee with PayPal

    Pay on PayPal — your lesson is booked as soon as PayPal confirms it.

  3. Check your booked lessons

    See the time and tutor of your booked lesson.

  4. Enter the lesson

    Join the video classroom when it’s time.

  5. Check your past lessons

    Look back at the lessons you finished.

  6. Rate your tutor

    Rate your tutor after the lesson.

Teach your AI agent new skills — in one minute

Free BaeumNova skills for , and other . Install them with one command and ask in plain words, then make your own in the next tabs.

A shelf of colourful binders. One is open, showing a cover with an icon and a few lines, pages of dotted steps, a checklist and a small toolbox clipped inside. A robot reads the covers and pulls out the binder that matches a dice icon in a speech bubble.

Intermediate — make your own skill

Turn a request you keep repeating into a . Make the folder, write a description the can find, write short step-by-step instructions, call it and check it, then decide where it lives — just for you or for the whole team.

Your first skill — turn a repeated request into one

A good first skill is something you have already explained to the three times or more: how to write messages, your test steps, your report format. Put that explanation in a once, and the agent finds and follows it every time.

  1. Pick one job you keep explaining and give it a short name of lowercase letters, numbers and hyphens (commit-message).
  2. Make a folder with that name in your agent's skills folder. init <name> makes the folder and a SKILL.md .
  3. At the top, fill in name (the same as the folder) and description. Below them, write the steps.
  4. Start a new session and ask for that job in plain words. If the agent uses the skill, it works.
# in your project folder
mkdir -p .agents/skills && cd .agents/skills
npx skills init commit-message      # makes commit-message/SKILL.md

# Codex · Gemini CLI · Copilot CLI read   .agents/skills/commit-message/SKILL.md
# Claude Code reads                       .claude/skills/commit-message/SKILL.md
mkdir -p .agents/skills && cd .agents/skills

npx skills init commit-message

You can also ask the agent: "Turn what we just did into a skill." and know the format (Codex has a built-in ).

The description — the only clue the agent has

At the start the agent reads only the name and description of every skill. From those few lines it decides which skill fits your request. A vague description means the skill is never used, or is used at the wrong time.

  • Say what it does and when to use it — both, in one or two sentences.
  • Write in the third person ("Writes commit messages …"), not "I can help you …".
  • Include the words people really type: "commit message", "commit this", "staged changes".
  • Rules: the description is up to 1,024 characters; the name is up to 64 lowercase letters, numbers and hyphens, the same as the folder name.
SKILL.md
# ✗ too vague — the agent cannot tell when to use it
description: Helps with commits.

# ✓ what it does + when to use it + the words people really say
description: Writes a git commit message from the staged changes in the Conventional Commits style. Use when the user asks for a commit message, says "commit this", or wants to describe staged changes.

Claude Code shows at most 1,536 characters of a description in its skill list, so put the main use first.

The instructions — short, in order, with an example

Below the frontmatter is what the agent reads when it uses the skill. The agent is already smart, so write only what it does not know: your rules, your order of steps, your format.

  • Leave out what the agent already knows (what is, how to write ).
  • When order matters, number the steps, and say what to do when something goes wrong ("If nothing is staged, say so and stop").
  • Show the result you want with one or two examples — an example says more than a description.
  • Give one default instead of a list of choices ("Use ; for scanned PDFs use ").
  • Keep SKILL.md under 500 lines. When it grows, split it into files (the [Advanced] tab).
.agents/skills/commit-message/SKILL.md
---
name: commit-message
description: Writes a git commit message from the staged changes in the Conventional Commits style. Use when the user asks for a commit message or says "commit this".
---

1. Run `git diff --staged`. If nothing is staged, say so and stop.
2. Pick one type: feat, fix, docs, refactor, test or chore.
3. Write a subject of 50 characters or less, then a blank line,
   then why the change was made in one or two short lines.

Example:
fix(cart): keep the coupon after a page reload

The coupon code was stored only in memory.

Calling a skill and checking it

A skill is used in two ways: the agent picks it by itself when your request matches the description, or you call it by name.

  • Automatic: just ask in plain words ("write a commit message"). The agent reads the description and loads the skill.
  • Claude Code: /skills shows the list and /<skill-name> calls one. Words after the name go into $ARGUMENTS.
  • Codex: /skills shows the list, and $<skill-name> in your message calls one.
  • Claude Code picks up edits to SKILL.md at once. If you made a new skills folder, run /reload-skills. In other tools, start a new session.
Claude Code · Codex
# Claude Code
/skills                 # list the skills it found
/commit-message         # call one yourself
/fix-issue 123          # "123" goes into $ARGUMENTS in SKILL.md

# Codex
/skills                 # list and pick
$commit-message         # mention one in your message

If the skill is not used when it should be, fix the description first — that is the cause most of the time.

Make a skill in 30 seconds — keep the shape in your head

In the BaeumNova level-3 AI certificate interview, the examiner says "make a skill that …" and you must finish it in 30 seconds. That sounds short, but it is enough if you have memorised the skill format beforehand. Keep the short format below in your head, then fill in just three parts — name, description and instruction — to suit the request.

The example is a webani skill (a web page full of motion and sound) cut to about half its words. A skill this short still works, because the agent reads the description to choose the skill and fills in the details itself.

  1. Type the two --- lines first. The lines between them are the frontmatter.
  2. name: a short name in lowercase letters, numbers and hyphens that hints at the job (webani = web animation). The folder gets the same name.
  3. description: one sentence with what it makes and the words of the request. The agent reads only this to decide when to use the skill.
  4. # Instruction: one or two lines with the most important rule. Leave the details to the AI.
.claude/skills/webani/SKILL.md
---
name: webani
description: Dynamic web page with modern CSS/JS, visual and sound effects.
---
# Instruction
- Use every visual and sound effect in one HTML file.

Do not aim for perfect in 30 seconds. A short skill that works beats a long one you did not finish — you can grow it later.

Prove that the skill works

A skill is proved when the agent finds it and uses it by itself. Save the file where Claude Code looks for skills, start Claude Code in that folder and ask for the job in plain words without naming the skill. In the interview you have 60 seconds for this after the skill is made.

  1. Save the skill as <folder>/.claude/skills/webani/SKILL.md. The folder name webani must be the same as name.
  2. Move into the folder: <folder>
  3. Start Claude Code with claude. If it asks whether you trust this folder, answer yes.
  4. Ask: create a dynamic web. Add a pinky style theme.
  5. Check that Claude Code says it is using the webani skill and makes an file with motion and sound in a pink theme. If it does not, type /skills to see whether the skill was found, then bring the description closer to the request.
Terminal
# 1. save the skill — the folder name is the same as name
<folder>/.claude/skills/webani/SKILL.md

# 2. move into the folder and start Claude Code
cd <folder>
claude

# 3. ask in plain words — do not type /webani
> create a dynamic web. Add a pinky style theme.

Do not type /webani to call it. The point of the proof is that the agent picked the skill from its description alone.

Practise for 10 days — gain confidence

Repeat the whole loop — make a very short skill, save it, use it — on the schedule below, with a new topic each time (a quiz page, a timer, a birthday card …). Then you will become confident about making skills.

Especially for a field you know well, start with a short skill and ask the AI to update it little by little: "add a rule for …", "make the description also catch …".

  1. Day 1: 5 times
  2. Day 2: 2 times
  3. From day 3: once a day — 10 days in total

also has a skill generator called skill-creator (the link is in the official documents below). It is handy for growing a skill you made. In the interview, though, you do not use a generator: you type the skill yourself on the keyboard.

Where to keep it — just for you, or for the team

The same skill can live in your (for all your projects) or in the project (for everyone who works on it).

  • Personal skills: ~/.claude/skills/ for Claude Code, ~/.agents/skills/ for Codex, and .
  • Project skills: or .agents/skills/ in the project. Commit them and the whole team gets the same skill.
  • If two skills have the same name, Claude Code uses the personal one before the project one.
  • Never put passwords or in a skill — its files are read and often shared.
Where
# only me, every project
~/.claude/skills/commit-message/      # Claude Code
~/.agents/skills/commit-message/      # Codex · Gemini CLI · Copilot CLI

# this project — commit it and the whole team gets it
.claude/skills/commit-message/
.agents/skills/commit-message/

git add .agents/skills/commit-message
git commit -m "Add the commit-message skill"

Install someone else's skills — reading the npx skills add options

npx skills add <source> reads the list of skills at that source (a or a website) and installs them. With no options it asks you, one by one, which skills, for which agents and where; each option answers one of those questions ahead of time.

  • -s <skill> (--skill): picks the skills to install by name. For several, repeat it (-s gp -s cowork) or list them after one -s (-s gp cowork). Without it you get the list to choose from.
  • -g (--global): installs once in your home folder, for every project on this computer. Without it the skill goes into the current project only.
  • -a <agent> (--agent): picks the agents to install to, for example -a claude-code or -a codex. Claude Code reads only .claude/skills, so choose claude-code if you use it.
  • -l (--list): only shows the skills at that source and installs nothing — look before you install.
  • -y (--yes): skips the confirmation questions — useful when a or an agent installs for you.
Terminal
# see what is there first — installs nothing
npx skills add https://sonub.com -l

# one skill, only for this project
npx skills add https://sonub.com -s cowork

# one skill, for every project on this computer
npx skills add https://sonub.com -g -s cowork

# several skills — repeat -s, or list them after one -s
npx skills add https://sonub.com -s gp -s cowork
npx skills add https://sonub.com -s gp cowork

# choose the agent too, and skip the questions
npx skills add https://sonub.com -g -s cowork -a claude-code -y
npx skills add https://sonub.com -l

npx skills add https://sonub.com -s cowork

npx skills add https://sonub.com -g -s cowork

npx skills add https://sonub.com -s gp -s cowork

npx skills add https://sonub.com -s gp cowork

npx skills add https://sonub.com -g -s cowork -a claude-code -y

Read the from left to right: npx skills add https://sonub.com -g -s cowork means "from sonub.com, for every project, install only cowork".

Intermediate practice — make one in your project

  1. Write down one request you have made to the AI three times or more.
  2. Make that skill folder with npx skills init and write the name and description.
  3. Write the steps in five lines or fewer, with one example of the result.
  4. In a new session, ask for it in plain words and check that the skill is used. Then call it by name.
  5. Ask for something unrelated and check that the skill is not used.

When all five work, move on to the [Advanced] tab.

Official documentation

Checked against the official documentation on 2026-10-18. These tools change often — if a command fails, see the official docs.

Booking time has passed

Voice chat with Lyen Pick a language and a topic, then talk with Lyen by voice

Lyen speaks aloud in English · 한국어 · 日本語 · हिन्दी. In other languages she answers in text.

Voice chat with Lyen is for members. Sign up first, then start talking.