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.

Master — share, use across tools, design, maintain

Share your skills so anyone can install them with one command, make one work in every , decide when a skill is the right tool, and keep your skills good as you use them.

Share your skills — one GitHub repository

Put your skills in a public and anyone can install them with npx skills add <owner>/<repo>. One repository can hold many skills.

  • Put each skill in its own folder under skills/. The installer finds them.
  • Add a and a with what each skill does and the install .
  • Users can take one skill with -s and install it for all their projects with -g.
  • When you fix a skill and push, users get it with update.
my-skills/
my-skills/                     # a public GitHub repository
├── README.md                  ← what each skill does + the install command
├── LICENSE
└── skills/
    ├── commit-message/SKILL.md
    └── sql-report/SKILL.md

# anyone can install it
npx skills add my-name/my-skills
npx skills add my-name/my-skills -s commit-message -g
npx skills update              # gets your new commits

Share from your own website — like BaeumNova

You can also share skills from your own website. BaeumNova does: npx skills add https://sonub.com reads the list at /.well-known/agent-skills/index.json and downloads each skill as an archive.

  • The list has each skill's name, description and archive address, with the of the archive.
  • When a digest changes, npx skills update downloads that skill again — only changed skills are updated.
  • If name or description breaks the rules (a lowercase name the same as the folder, a description up to 1,024 characters), the installer silently skips the skill.
  • BaeumNova builds the list and archives from the skill folders on each request, so a fix is the new .
sonub.com
# the list the installer reads
https://sonub.com/.well-known/agent-skills/index.json

# one archive per skill, with the sha256 digest of its bytes in the list
https://sonub.com/.well-known/agent-skills/gp.tar.gz

npx skills add https://sonub.com

One skill for every tool

is an , so one folder works in , , , and more. Only the folder each tool reads is different.

  • Make it work with the standard fields (name, description) and plain instructions. Tool-only options are extras.
  • Avoid words tied to one tool ("the tool"). Write "run this in the ".
  • Keep one real folder in .agents/skills/ and link it into . npx skills add can do this for you (recommended), or make copies with --copy.
  • In Claude Code you can also bundle skills with , hooks and into a plugin and share it through a .
Terminal
# one real folder for every tool
.agents/skills/commit-message/

# a link so Claude Code finds the same folder
mkdir -p .claude/skills
ln -s ../../.agents/skills/commit-message .claude/skills/commit-message

If a skill uses MCP tools, write the full name with the (ServerName:tool_name). Without it the agent may not find the tool.

Design — when a skill, and when something else

Agents learn in several ways. Use a skill where a skill fits, and the work gets simpler.

  • Rules to follow in every conversation → AGENTS.md (or CLAUDE.md).
  • A procedure or knowledge needed now and then → a skill.
  • A big job handed off, with only the result coming back → a subagent.
  • Connecting to outside services and → MCP. A skill can teach how to use those tools.
  • Something that must happen every time (formatting after each edit) → a hook.

One skill, one job. When a skill does too much, split it.

Look after your skills — improve them as you use them

A skill gets better from watching it work, not from guessing. Use it on real tasks and fix it where the agent struggles.

  • Watch how the agent uses it: files it never reads, files it reads again and again, rules it misses.
  • Improve the skill in one session and test it in a new one — the fresh session shows what is missing.
  • Instead of dates ("before August …"), write the current way and fold the old way into an "Old way" section.
  • Delete skills nobody uses — every description takes up in every session.
  • Ask your team: Did it start when expected? Were the instructions clear? What was missing?

Master checklist

  • The description says what it does, when to use it, and the words people really use
  • is under 500 lines, and other files are linked one level deep
  • handle their own errors, and it is clear whether to run or read them
  • At least three tests, including one where the skill must not be used
  • No secrets inside, and other people's skills are read before they are installed
  • Checked in the agents and you will use, and shared with an install command

When every box is checked, publish one of your skills on GitHub and share it with npx skills add.

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.