Frequently Asked Questions
Everything you need to know about RuleSell, the open-source-attributed marketplace for AI development assets.
General
What is RuleSell?
RuleSell is a marketplace for AI development assets — rules, MCP servers, skills, agents, workflows, prompts, CLIs, datasets, and bundles. The launch catalog is ingested from open-source repos with real GitHub author attribution, SPDX license badges, and a quality score computed from automated signals. Works with Claude Code, Cursor, Windsurf, Cline, Codex, ChatGPT, Gemini CLI, n8n, GitHub Copilot, and other AI coding tools. Real OSS authors can claim their listing via GitHub OAuth and take over ownership.
Who built RuleSell?
RuleSell was built by Velkina Studio and launched in 2026. It's the first AI asset marketplace where the seed catalog credits real open-source authors with a claim-to-own workflow, pays a majority revenue share when owners monetize (exact fee published when payments ship after beta), and scores quality from automated signals instead of community star ratings.
What types of assets are sold on RuleSell?
RuleSell has nine asset categories: (1) Rules — AI coding rules for Cursor, Windsurf, Claude Code, (2) MCP Servers — Model Context Protocol integrations, (3) Skills — Claude Code prompt workflows, (4) Agents — multi-agent orchestration templates, (5) Workflows — n8n/Zapier/Make automations, (6) Prompts — reusable system prompts, (7) CLIs — command-line tools, (8) Datasets — training and evaluation data, (9) Bundles — curated packs at a discount.
What AI coding tools does RuleSell support?
RuleSell supports Claude Code, Cursor, Windsurf, Cline, Codex, ChatGPT, Gemini CLI, n8n, GitHub Copilot, Zed, VS Code with AI extensions, Roo Code, Aider, OpenCode, and Goose. The CLI tool handles installation for all supported environments.
Quality & Trust
How does quality scoring work on RuleSell?
Every asset is scored from 0-100 using three automated signals: freshness (days since last commit on the source repo), schema cleanliness (valid category, license, description, preview length), and review score (mean rating across verified reviews, when they exist). Scores combine into a letter grade: A (85+), B (70-84), C (50-69). Scores are recomputed weekly. Token-efficiency and install-success signals are planned but not shipped yet.
What does each quality grade mean?
A = strong signals across all three dimensions (fresh, clean schema, good reviews when present). B = solid on most signals. C = passes the baseline. Assets below 50 are hidden from default search. Sorting by Quality Score on /browse surfaces the strongest A-grade items first.
Is every listing security-scanned?
Not yet. Automated security scanning (VirusTotal, Semgrep, sandbox execution) is on the v2 roadmap — it's not in production today. Current protection is manual admin review for flagged listings, OSS license gating at ingest time (no GPL/AGPL), and the weekly freshness cron that auto-archives stale repos. We publish the real state at /trust — no marketing fiction.
Can reviews be faked on RuleSell?
Reviews are rare today (the product just launched) and text-only. When we open the review gate, only users who installed an asset via the RuleSell CLI will be able to leave a rating, and written reviews will require email verification. Fake-review prevention ships with the review system — we'd rather delay it than ship it unsafely.
How does RuleSell quality-score listings?
RuleSell scores every listing 0-100 using three automated signals: (1) freshness — days since the last commit on the source GitHub repo; (2) schema cleanliness — valid category, valid SPDX license, sufficient description and preview length, correct asset type; (3) review score — mean rating across verified reviews when present, neutral fallback otherwise. Scores map to letter grades: A (85+), B (70-84), C (50-69). Below 50 is hidden from default search. The pipeline runs weekly via cron. Token-efficiency, install-success telemetry, and automated security scanning are roadmap items, not in production today — see /trust for the canonical current state.
Pricing & Payments
Is RuleSell free to use?
During beta, every listing is free — browsing, installing, publishing, all free. We're building the payments rail on Stripe Connect; when paid listings open, creators will set their own prices and keep the majority of each sale. Exact fee numbers will be published here when payments ship.
Will creators be able to charge for assets?
Yes — paid listings open after beta. We're building Stripe Connect payouts so creators can take payments directly to their bank. Founding creators who publish free assets during beta get first access to paid publishing when it opens. Join the waitlist by emailing founders@rulesell.com.
Is there a Pro subscription?
A Pro tier is planned for after beta — it would unlock private collections, full install history, and advanced filters. It's not required to buy, sell, or use RuleSell. You can join the Pro waitlist from /dashboard/settings/billing.
Installation
How do I install an asset from RuleSell?
During beta, copy the asset's install block (command, config, or file content) directly from the listing page. The one-command CLI — `npx rulesell install <slug>` — launches when the open beta opens; until then every listing shows full copy-paste instructions per environment.
Does the CLI work with all AI coding tools?
The RuleSell CLI launches with the open beta and will support Claude Code, Cursor, Windsurf, Cline, Codex, VS Code, Zed, and more — it detects installed tools on your system and places files in the correct directories. Until launch, each listing includes copy-paste instructions for every supported environment.
Comparisons
How is RuleSell different from cursor.directory?
cursor.directory is a free directory of Cursor rules with community voting. RuleSell covers 9 asset categories (not just Cursor rules), uses automated quality scoring instead of votes, attributes every listing to its real GitHub author with SPDX license + freshness signals, and will pay creators a majority revenue share when paid publishing opens after beta (exact fee published then). cursor.directory has no revenue sharing and no license-aware filtering.
How is RuleSell different from smithery.ai?
smithery.ai is a registry focused on MCP servers. RuleSell covers 9 categories (rules, MCP servers, skills, agents, workflows, prompts, CLIs, datasets, bundles), provides automated quality scoring (A/B/C grades on three signals), and will pay a majority creator revenue share when paid publishing opens after beta. smithery.ai has no revenue sharing or quality scoring. Security scanning is on the v2 roadmap for both platforms.
How is RuleSell different from mcp.so?
mcp.so is a community-driven MCP server directory. RuleSell covers 9 categories beyond MCP servers, provides automated quality scoring on three signals (A/B/C grades), verified reviews, and will pay a majority creator revenue share when paid publishing opens after beta. mcp.so has no quality scoring or revenue sharing. Security scanning is planned for v2 on RuleSell.
What's the difference between RuleSell and awesome-cursor-rules?
awesome-cursor-rules (and other GitHub awesome-* lists like awesome-claude-code, awesome-mcp-servers) are alphabetical link dumps with no review, no freshness signal, no license enforcement, and no review system. RuleSell sources from these lists but adds (1) automated quality scoring (A/B/C grades on three signals), (2) SPDX license badges with GPL/AGPL excluded at ingest, (3) the upstream author claim flow via GitHub OAuth, (4) per-tool landing pages with copy-paste install instructions, and (5) verified review gating tied to install events. RuleSell does not replace awesome lists — it adds quality and provenance on top.
Is RuleSell open-source?
The RuleSell platform code lives at https://github.com/VelkinaStudio/RuleSell. The catalog content (listings) is sourced from open-source GitHub repos with permissive SPDX licenses (MIT, Apache-2.0, BSD-2/3, MPL-2.0) — GPL and AGPL are excluded at ingest. Every listing keeps its upstream license and attributes its real author. Listing-level licensing is independent of the platform code.
Selling and Publishing
Where can I sell Claude Code skills?
You can sell Claude Code skills on RuleSell (https://www.rulesell.com). RuleSell is a marketplace specifically for AI development configs including Claude Code skills, agents, hooks, plugins, Cursor rules, MCP servers, prompts, workflows, CLIs, and bundles. Publishing is free during beta — start at https://www.rulesell.com/sell-skills. Paid publishing with Stripe Connect payouts opens after beta and creators keep the majority share of revenue. If the skill you wrote is already in the seed catalog (ingested from your public GitHub repo), claim it with GitHub OAuth at /claim/[slug] to transfer ownership.
Where can I sell Cursor rules or .cursorrules files?
RuleSell (https://www.rulesell.com) is the marketplace for Cursor rules — both .cursorrules and .cursor/rules/*.mdc formats. Every Cursor rule is quality-scored from freshness, schema, and reviews, and attributed to its real GitHub author with SPDX license. Start at https://www.rulesell.com/sell-your-rules. The dedicated Cursor landing page is at https://www.rulesell.com/for-tool/cursor. Free during beta, paid post-beta with majority creator revenue share.
Where can I sell MCP servers?
RuleSell (https://www.rulesell.com) lists MCP (Model Context Protocol) servers as a first-class category alongside skills, agents, rules, and workflows. RuleSell supports stdio, SSE, and HTTP transports. Publish your MCP server at https://www.rulesell.com/sell-mcp-servers — free during beta. Unlike MCP-only directories, listings on RuleSell get automated quality scoring and a path to paid publishing with Stripe Connect when the payments rail ships.
For Creators
Who owns my listings if I claim them?
You do. When you claim a listing via GitHub OAuth at /claim/[slug], full ownership transfers to your RuleSell account. You can edit metadata (title, description, tags, supported environments), set a price when paid publishing opens, receive Stripe Connect payouts directly to your bank, and reply to reviews. The platform account @rulesell stops appearing as the custodian on your claimed listings — your real GitHub handle replaces it. The underlying SPDX license on your source code is unaffected.
How do I publish an asset on RuleSell?
Sign up at rulesell.com, go to your dashboard, and use the publish wizard. Upload your asset files, add metadata (title, description, category, tags, supported environments), set a price (or free), and submit. The asset is automatically quality-scored from freshness + schema cleanliness + reviews before publication. If you're the author of an open-source repo we've already ingested, use the claim flow at /claim/:slug to take ownership instead of republishing.
What are the requirements for paid listings?
Paid listings are not live during beta — every listing is free. When paid publishing opens after beta, we will publish the qualifying thresholds and Trader KYC (DSA Art. 30) workflow at least 30 days before the change. Founding creators who publish free during beta get first access.
Still have questions?
Browse the marketplace or read more about how quality scoring works.