Migrate To Rslint logo

Migrate To Rslint

Organization
rstackjs
migrate-to-rslint

Migrate ESLint or other linters to Rslint. Use when asked to replace ESLint flat config, lint scripts, VS Code ESLint settings, inline directives, rules, presets, plugins, or lint dependencies with Rslint equivalents.

Overview

Publisherrstackjs
Repositoryagent-skills
Skill namemigrate-to-rslint
Stars
93
Forks
4
Bundled files
1
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.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by rstackjs on GitHub. Read the source before you install it.

Installation

Install the Migrate To Rslint 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/rstackjs/agent-skills.git /tmp/agent-skills
mkdir -p .claude/skills
cp -r /tmp/agent-skills/skills/migrate-to-rslint .claude/skills/migrate-to-rslint
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Migrate To Rslint 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 Migrate To Rslint 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 Migrate To Rslint 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.

Migrate to Rslint

Goal

Migrate lint tooling to Rslint with minimal behavior changes and clear validation.

Supported source linters

  • ESLint flat config

Migration principles (must follow)

  1. Official docs first: treat Rslint docs as source of truth for CLI, config, inline directives, VS Code settings, rules, and presets.
  2. Smallest-change-first: migrate package, command, config, and editor wiring before changing source files.
  3. Preserve lint intent: keep supported rule severities/options where Rslint supports them; call out unsupported rules/plugins instead of silently dropping behavior.
  4. Do not rewrite inline directives by default: Rslint supports eslint-disable and rslint-disable; replace prefixes only when the user asks.
  5. Validate before cleanup: keep old linter dependencies/config until the Rslint command passes for the migrated scope, then remove obsolete linter-only artifacts.

Workflow

  1. Detect source linter

    • ESLint flat config: eslint.config.*, eslint dependency, or package scripts that run eslint.
    • If the source linter is not covered by a reference yet, inventory the current behavior and explain that no dedicated migration reference exists.
  2. Apply source-specific migration guide

    • ESLint flat config: references/eslint-flat-config.md
  3. Validate behavior

    • Run the migrated lint command.
    • If the project had a fix command, run the migrated fix command only when appropriate for the task.
    • Resolve config, rule, and editor-setting issues before removing legacy files.
  4. Cleanup and summarize

    • Remove obsolete linter dependencies/config after Rslint is green.
    • Summarize changed files, migrated presets/plugins, unsupported gaps, and remaining manual follow-ups.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Migrate To Rslint AI skill do?

Migrate ESLint or other linters to Rslint. Use when asked to replace ESLint flat config, lint scripts, VS Code ESLint settings, inline directives, rules, presets, plugins, or lint dependencies with Rslint equivalents.

Why use Migrate To Rslint on TypingMind?

Because you install it once and use it with any model. Migrate To Rslint 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 Migrate To Rslint in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/rstackjs/agent-skills/tree/main/skills/migrate-to-rslint. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Migrate To Rslint?

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 Migrate To Rslint?

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

Is the Migrate To Rslint AI skill free?

Yes. It is published on GitHub by rstackjs 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 👇