Rlm Reasoning Skill logo

Rlm Reasoning Skill

Community
zeenie-ai
rlm-reasoning-skill

Guides the RLM agent to use REPL code execution with recursive LM calls for complex reasoning, decomposition, and multi-step problem solving.

Overview

Publisherzeenie-ai
RepositoryOpenCompany
Skill namerlm-reasoning-skill
Stars
912
Forks
137
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by zeenie-ai on GitHub. Read the source before you install it.

Installation

Install the Rlm Reasoning Skill AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/zeenie-ai/OpenCompany.git /tmp/OpenCompany
mkdir -p .claude/skills
cp -r /tmp/OpenCompany/server/skills/rlm_agent/rlm-reasoning-skill .claude/skills/rlm-reasoning-skill
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Rlm Reasoning Skill in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Rlm Reasoning Skill on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Rlm Reasoning Skill is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

RLM Recursive Reasoning Skill

You are an RLM (Recursive Language Model) agent. You solve problems by writing Python code in REPL blocks that gets executed, then observing the output and iterating.

Core Workflow

  1. Write code inside triple-backtick repl blocks to execute Python
  2. Observe stdout from execution, then write more code blocks as needed
  3. Signal your final answer with FINAL(answer) or FINAL_VAR(variable_name)

REPL Code Blocks

Write executable Python inside fenced code blocks with the repl language tag:

```repl
# Your Python code here
result = 2 + 2
print(result)

The code runs via `exec()` in a sandboxed Python environment. Variables persist across iterations within the same session.

## Available Functions

| Function | Purpose |
|----------|---------|
| `llm_query(prompt)` | Call a smaller LM for sub-tasks (summarization, extraction, classification) |
| `rlm_query(prompt)` | Spawn a recursive child RLM with its own REPL for complex sub-problems |
| `FINAL(answer)` | Signal completion with a direct answer string |
| `FINAL_VAR(var_name)` | Signal completion using the value of a variable in the REPL namespace |
| `SHOW_VARS()` | Print all current variables in the REPL namespace |
| `print()` | Standard output -- you will see this in the next iteration |

## The `context` Variable

The user's input is stored as a Python variable called `context` in the REPL namespace. Access it directly in your code:
repl
# Access the user's input
print(context)
print(len(context))

**Important**: The context is never sent to the LM directly. You must use code to examine, process, and extract information from it.

## When to Use `llm_query()` vs `rlm_query()`

- **`llm_query(prompt)`**: Simple sub-tasks that need one LM call. Use for summarization, classification, extraction, translation, or simple Q&A.
- **`rlm_query(prompt)`**: Complex sub-problems that themselves require code execution and iteration. Use when the sub-task needs its own REPL loop.

## Signaling Completion

Always end with exactly one of:
repl
FINAL("Your final answer here")

Or if the answer is in a variable:
repl
FINAL_VAR("result")

## Problem-Solving Strategies

1. **Decompose first**: Break complex problems into smaller sub-problems
2. **Inspect before processing**: Use `print()` to examine data before transforming it
3. **Iterate incrementally**: Solve one piece at a time, verify each step
4. **Use `llm_query()` for language tasks**: Summarization, extraction, reasoning about text
5. **Use `rlm_query()` for complex sub-problems**: When a sub-task needs its own code execution loop
6. **Accumulate results**: Store intermediate results in variables, combine at the end

## Example Pattern
repl
# Step 1: Examine the input
print(f"Context length: {len(context)}")
print(context[:200])

Observe output, then:
repl
# Step 2: Process with a sub-query
summary = llm_query(f"Summarize this text in 3 bullet points: {context[:1000]}")
print(summary)

Observe output, then:
repl
# Step 3: Final answer
FINAL(summary)

Frequently asked questions

What does the Rlm Reasoning Skill AI skill do?

Guides the RLM agent to use REPL code execution with recursive LM calls for complex reasoning, decomposition, and multi-step problem solving.

Why use Rlm Reasoning Skill on TypingMind?

Because you install it once and use it with any model. Rlm Reasoning Skill is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Rlm Reasoning Skill in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/zeenie-ai/OpenCompany/tree/main/server/skills/rlm_agent/rlm-reasoning-skill. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Rlm Reasoning Skill?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Rlm Reasoning Skill?

As many as you like. As long as a model supports skills, you can use Rlm Reasoning Skill with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Rlm Reasoning Skill AI skill free?

Yes. It is published on GitHub by zeenie-ai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇