poteto/plugins

create-plugin-scaffold

Create a new Cursor plugin scaffold with a valid manifest, component directories, and marketplace wiring.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/poteto/plugins --skill create-plugin-scaffold

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Create plugin scaffold

Trigger

You need to create a new Cursor plugin from scratch and make it ready for local use or marketplace submission.

Required Inputs

  • Plugin name (lowercase kebab-case)
  • Plugin purpose and target users
  • Component set to include (rules, skills, agents, commands, hooks, mcpServers)
  • Repository style (single-plugin or multi-plugin marketplace)

Output Location

By default, create the plugin inside the user's local plugin directory:

~/.cursor/plugins/local/<plugin-name>/

This path makes the plugin immediately available to Cursor without any install step. If the user explicitly asks to create the plugin elsewhere (e.g. inside an existing repo or a specific directory), respect that choice instead.

Workflow

  1. Validate plugin name format: lowercase kebab-case, starts and ends with an alphanumeric character.
  2. Determine the target directory:
  • Default: ~/.cursor/plugins/local/<plugin-name>/
  • Override: use the path the user specifies, if any.
  • Create the directory (and parents) if it does not exist.
  1. Create base files inside the target directory:
  • .cursor-plugin/plugin.json
  • README.md
  • LICENSE
  • optional CHANGELOG.md
  1. Populate plugin.json:
  • Required: name
  • Recommended: version, description, author, license, keywords
  • Add explicit component paths only when non-default discovery is needed.
  1. Create component files with valid frontmatter:
  • Rules: .mdc with description, alwaysApply, optional globs
  • Skills: skills/<skill-name>/SKILL.md with name, description
  • Agents: agents/*.md with name, description
  • Commands: commands/*.(md|txt) with name, description
  1. If repository uses .cursor-plugin/marketplace.json, add plugin entry:
  • name
  • source
  • optional metadata (description, keywords, category, tags)
  1. Ensure all manifest paths are relative, valid, and do not use absolute paths or parent traversal.

Guardrails

  • Keep the plugin focused on one use case.
  • Prefer concise, actionable skill and rule text over long prose.
  • Do not reference files that do not exist.
  • Use folder discovery defaults unless custom paths are required.
  • Always save to ~/.cursor/plugins/local/<plugin-name>/ unless the user provides a different path.

Output

  • Created file tree for the plugin (with full path to the output directory)
  • Final plugin.json
  • Marketplace entry (if applicable)
  • Short validation report of required fields and component metadata
  • Confirmation that the plugin is saved under ~/.cursor/plugins/local/ and ready for use
같은 저장소의 Skills

더 많은 Skills

모든 Skills