How do I install the Codekiln Beans Rulesync skill?

Run npx skillmds@latest add tomevault-io/codekiln-beans-rulesync in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Codekiln Beans Rulesync skill do?

Rulesync It is listed under Coding & Dev Tools on SkillMD.

Is Codekiln Beans Rulesync safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Codekiln Beans Rulesync?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Codekiln Beans Rulesync free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Codekiln Beans Rulesync?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Codekiln Beans Rulesync by tomevault-io

Name: Codekiln Beans Rulesync
Author: tomevault-io

File contents

Rulesync

Rulesync generates and synchronizes AI rule configuration files across 20+ coding tools (Claude Code, Cursor, Copilot, Windsurf, Cline, Gemini CLI, and more) from a single set of unified rule files in .rulesync/.

Quick Start

# Install
npm install -g rulesync

# New project: initialize config, rules, and directory structure
rulesync init

# Import existing AI tool configs into unified format
rulesync import --targets claudecode    # From CLAUDE.md
rulesync import --targets cursor        # From .cursorrules
rulesync import --targets copilot       # From .github/copilot-instructions.md

# Generate tool-specific configs from unified rules
rulesync generate --targets "*" --features "*"

Core Workflow

Init - rulesync init creates rulesync.jsonc config and .rulesync/ directory with sample rules
Write rules - Add shared AI rules in .rulesync/rules/, MCP configs in .rulesync/mcp/, commands in .rulesync/commands/
Generate - rulesync generate produces tool-specific files (CLAUDE.md, .cursorrules, .github/copilot-instructions.md, etc.)
Verify - rulesync generate --dry-run previews changes; --check validates files are up to date (useful in CI)

Key Commands

Command	Purpose
`rulesync init`	Scaffold project with config and sample rules
`rulesync generate --targets "" --features ""`	Generate all tool configs from unified rules
`rulesync import --targets <tool>`	Import existing tool config into unified format
`rulesync fetch owner/repo --features skills`	Fetch rules or skills from a remote repository
`rulesync install`	Install skill sources declared in rulesync.jsonc
`rulesync generate --check`	CI check that generated files are up to date
`rulesync generate --dry-run`	Preview changes without writing files

Detailed Reference

Source: codekiln/beans — distributed by TomeVault.

---name: codekiln-beans-rulesyncdescription: Rulesync---# RulesyncRulesync generates and synchronizes AI rule configuration files across 20+ coding tools (Claude Code, Cursor, Copilot, Windsurf, Cline, Gemini CLI, and more) from a single set of unified rule files in `.rulesync/`.## Quick Start```bash# Installnpm install -g rulesync# New project: initialize config, rules, and directory structurerulesync init# Import existing AI tool configs into unified formatrulesync import --targets claudecode # From CLAUDE.mdrulesync import --targets cursor # From .cursorrulesrulesync import --targets copilot # From .github/copilot-instructions.md# Generate tool-specific configs from unified rulesrulesync generate --targets "*" --features "*"```## Core Workflow1. **Init** - `rulesync init` creates `rulesync.jsonc` config and `.rulesync/` directory with sample rules2. **Write rules** - Add shared AI rules in `.rulesync/rules/`, MCP configs in `.rulesync/mcp/`, commands in `.rulesync/commands/`3. **Generate** - `rulesync generate` produces tool-specific files (CLAUDE.md, .cursorrules, .github/copilot-instructions.md, etc.)4. **Verify** - `rulesync generate --dry-run` previews changes; `--check` validates files are up to date (useful in CI)## Key Commands| Command | Purpose || ------------------------------------------------ | ------------------------------------------------ || `rulesync init` | Scaffold project with config and sample rules || `rulesync generate --targets "*" --features "*"` | Generate all tool configs from unified rules || `rulesync import --targets <tool>` | Import existing tool config into unified format || `rulesync fetch owner/repo --features skills` | Fetch rules or skills from a remote repository || `rulesync install` | Install skill sources declared in rulesync.jsonc || `rulesync generate --check` | CI check that generated files are up to date || `rulesync generate --dry-run` | Preview changes without writing files |## Detailed Reference- [Installation](./installation.md), [Quick Start](./quick-start.md)- [Why Rulesync?](./why-rulesync.md), [Configuration](./configuration.md), [Global Mode](./global-mode.md), [Simulated Features](./simulated-features.md), [Declarative Sources](./declarative-sources.md), [Official Skills](./official-skills.md), [Dry Run](./dry-run.md), [Case Studies](./case-studies.md)- [Supported Tools](./supported-tools.md), [CLI Commands](./cli-commands.md), [File Formats](./file-formats.md), [MCP Server](./mcp-server.md)- [Programmatic API](./programmatic-api.md)- [FAQ](./faq.md)---> Source: [codekiln/beans](https://github.com/codekiln/beans) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Codekiln Beans Rulesync