Skip to content

Skills for AI agents ​

Rangka skills teach an AI agent how Rangka OS works and how to change a Rangka site safely. They are written in the open Agent Skills format: one folder per skill with a SKILL.md (frontmatter name and description, then instructions) and optional reference files. The model reads only the names and descriptions until a task needs a skill, then loads its instructions.

The same library serves every harness:

  • Raka, the agent in Juragan and in the app, loads them from the running kernel.
  • Claude Code, Codex, Cursor and other harnesses install them into the folder they read (see Install).

Contract: 0035 Rangka skills.

The skills ​

SkillFromUse it for
rangka-changesetsrangka-osHow to change a running Rangka site safely: write a change set, validate and preview it, read its risk, and tell the owner what happens next without claiming it is done.
rangka-composerangka-osFind out what Rangka can do for a business and add or remove apps on a site: read the live catalogue (installed, available, not in the plan), explain which data a new app shares with the apps already there, and propose the config.rk change.
rangka-conceptsrangka-osHow Rangka OS is put together: apps built from shared modules, one business with one set of data, the company layer, change sets, and what an AI agent may and may not do.
rangka-consultrangka-osRun the studio interview as a business consultant: explore how the business runs, build the peta alur (contract 0042), turn owner files into guesses to confirm, and design the solution from catalogue modules, custom pieces, connectors, edge and Cloud services.
rangka-app-kasirapp:kasirRangka Kasir (app kasir): the browser cashier for shops and F&B outlets, with shifts per outlet, numbered receipts, cash and QRIS, stock and recipes taken out automatically.
rangka-app-sewa-alatapp:sewa_alatRangka Sewa Alat (app sewa_alat): rental of equipment or vehicles with a schedule without double booking, handover out and back per unit, deposit, late fee, rent invoices.

Platform skills live in rangka-os/skills. App and module skills live next to their app or module in rangka-apps (<unit>/skills/), and connector skills in rangka-connectors (skills/). Each skill changes in the same pull request as the capability it describes.

What every skill relies on ​

  • The live catalogue. rangka catalogue --json (or the MCP tool rangka_catalogue) lists every app, module and connector with its state for the site (installed, available, not_in_plan). For each app it also gives the installed modules it shares and the modules it adds. Skills tell agents to read it first and never to name an app from memory.
  • Change sets. Every change to a site is a change set that a person approves. Skills never tell an agent to approve, apply or read secrets, and rangka skills check refuses one that does.
  • Proof before claim. An agent says what it proposed, never that something is done. The app shows completion from the change set's status.

Use them with a connected kernel (MCP) ​

An MCP client connected to a kernel (POST /mcp) gets the skills that match that kernel's version and catalogue without installing anything:

ToolReturns
rangka_skillsname, description and source of every skill
rangka_skill {name}one skill's instructions and its other files
rangka_skill_file {name, path}one reference file
rangka_cataloguethe catalogue above

See MCP tools.

Rangka OS is source-available under the Elastic License 2.0 (ELv2). Free to self-host.