본문으로 건너뛰기
cccskills
무료GitHub에 공개

validate-plugin

Check a Claude Code plugin before publishing. Inspect file placement, required configuration fields, metadata at the start of skill and agent files, and MCP tool references, then report failures with practical suggestions for fixing them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Validate a Claude Code plugin structure, frontmatter, and MCP tool references

설치 방법 보기

이럴 때 유용합니다

  • Check a newly created plugin before publishing
  • Review structure after adding skills or agents
  • Find missing fields and misplaced files
  • Detect misspelled or nonexistent MCP tool references

포함된 파일(1)

  • SKILL.md2.5 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Validate Plugin

Validate that a plugin follows the correct Claude Code plugin format.

When to use

After creating or modifying a plugin, run validation to catch structural issues before publishing.

Checks performed

  1. Directory structure — .claude-plugin/plugin.json exists at plugin root
  2. plugin.json schema — required fields present (name, description, version, non-empty keywords array); name equals the directory name; version is semver
  3. Skills auto-discovery — every skills/<name>/SKILL.md is a valid skill (Claude Code auto-discovers from directory; plugin.json MUST NOT list a skills array)
  4. Commands auto-discovery — every commands/<name>.md is a valid command (auto-discovered; no commands array in plugin.json)
  5. Agents auto-discovery — every agents/<name>.md is a valid agent (auto-discovered; no agents array in plugin.json)
  6. No legacy arrays in plugin.json — presence of skills, commands, or agents arrays in plugin.json is a validation error (they cause Claude Code to reject the plugin)
  7. SKILL.md frontmatter — each skill has name, description, and allowed-tools (no wildcards)
  8. Agent frontmatter — each agent has name, description, and model
  9. No files in wrong locations — skills/commands/agents not inside .claude-plugin/
  10. MCP tool references — tools in allowed-tools use the mcp__plugin_ruflo-core_ruflo__* prefix AND exist: list the real tools with npx @claude-flow/cli@latest mcp tools and flag any name not in it (typos such as hooks_post_task for hooks_post-task, or agentdb_pattern_search for agentdb_pattern-search, are format-valid but do not exist). Also run the repo gates when inside the ruflo repo: node scripts/audit-skill-frontmatter.mjs, audit-plugin-manifest.mjs, audit-plugin-mcp-prefix.mjs

Steps

  1. Read the plugin's plugin.json and assert no skills / commands / agents arrays present
  2. Glob skills/*/SKILL.md, commands/*.md, agents/*.md and validate each frontmatter
  3. For each SKILL.md, verify frontmatter has required fields and allowed-tools has no wildcards
  4. For each agent .md, verify frontmatter has required fields
  5. Report pass/fail for each check with actionable fix suggestions

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Adding newly available router models to chat-ui
  • Writing concise descriptions of model capabilities
  • Updating production and development model entries together
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Record the reasoning behind adopting a technology
  • Start an ADR for an API or data model change
  • Document an infrastructure decision
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

adr-index

무료

Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Index ADRs imported from another project
  • Refresh a graph that differs from files on disk
  • Set up ADR tracking in an existing codebase
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Rebuild the index after deleting an ADR file
  • Remove stale relationships after editing an ADR
  • Reconcile the ADR index on a schedule
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Check a pull request before merging
  • Review major code changes against agreed design decisions
  • Find references to superseded ADRs
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking ADR integrity after import
  • Blocking CI when ADR issues are found
  • Reviewing ADR data before a release
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

ruvnet의 스킬 모두 보기

이 스킬의 문제 신고