agentleFS
Sign inStart free
sonorateksonoratek/legiox/skills/cursor-plugin-architect-guru/SKILL.md

cursor-plugin-architect-guru

Skill0 starsChanged 44 days agoMITView on GitHub

scaffold or repair the LegioX Cursor plugin tree

The file

Create a free account to mount
Files
SKILL.md

Cursor Plugin Architect Guru

Summary

A LegioX Cursor Plugin is a directory with .cursor-plugin/plugin.json. Required field is name: lowercase kebab-case, alphanumerics, hyphens, and periods, starting and ending with an alphanumeric. Optional fields include description, version, author, homepage, repository, license, keywords, logo, and component paths. If skills, rules, agents, commands, hooks, or mcpServers is set, that path replaces default folder discovery; the default folder is not also scanned. Defaults: skills/*/SKILL.md (name must match the parent folder), rules as .md/.mdc/.markdown, agents as .md/.mdc/.markdown, commands as .md/.mdc/.markdown/.txt, hooks/hooks.json, root mcp.json. A root SKILL.md is a single-skill plugin only when there is no skills/ directory and no skills field. Multi-plugin repos put .cursor-plugin/marketplace.json at the repo root; the file must be 10 MB or smaller; per-plugin manifest wins on merge. Paths are relative: no .. and no absolute paths. Logo is a committed relative path such as assets/logo.svg. Local test copies the directory into ~/.cursor/plugins/local/<name> and reloads; symlinks that point outside that folder are skipped. LegioX names are legiox-free and legiox-pro. community and premium are deprecated and must not appear in marketplace.json. variables is a JSON Schema for user-supplied tokens; never commit secret values; substitute ${VAR} only. In mcp.json expand ${CURSOR_PLUGIN_ROOT}. Cursor does not expand ${PLUGIN_ROOT} or ${PLUGIN_DATA}. Public marketplace submission of this multi-plugin folder would index every plugin in marketplace.json, so the public submit repo is the free tree alone.

Instructions

  1. Pattern: .cursor-plugin/plugin.json name legiox-free or legiox-pro -> Cursor Plugin format
  2. Pattern: marketplace.json plugins[] lists only legiox-free and legiox-pro
  3. Pattern: manifest skills path replaces skills/ discovery; do not set both expecting a union
  4. Pattern: cp -R into ~/.cursor/plugins/local/<name> then Developer: Reload Window
  5. Pattern: SKILL.md frontmatter name matches the parent folder; rules and agents need frontmatter too
  6. Pattern: logo assets/logo.svg is the real mark, never the 279-byte packer placeholder
  7. Pattern: ${CURSOR_PLUGIN_ROOT} in mcp.json command, args, env, and cwd
  8. Pattern: public Git submit is the free repo root; pro stays a downloadable archive

Deeper fields

jq -r '.mission, .expertise, .keywords' "mcp/AI-LEGIOX/legiox-truth-lens/cursor-plugin-architect-guru.nodus.json"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free