Skip to content

docs: skill-publishing layout standard (BRO-1561)#80

Merged
broomva merged 1 commit into
mainfrom
fix/bro-1561-publishing-standard
Jun 27, 2026
Merged

docs: skill-publishing layout standard (BRO-1561)#80
broomva merged 1 commit into
mainfrom
fix/bro-1561-publishing-standard

Conversation

@broomva

@broomva broomva commented Jun 27, 2026

Copy link
Copy Markdown
Owner

Adds a Publishing standard section to the skills roster: skills must live in skills/<name>/ (Agent Skills standard) — a top-level SKILL.md + sibling scripts/ at a repo root installs only SKILL.md on remote npx skills add (CLI repo-root special-case), yielding a non-functional skill. Documents the why, the keep-your-repo-name fix (git mv → skills/<name>/), and the validation discipline (--list necessary-not-sufficient; runnable clean-room install is the gate; skillify now machine-enforces it). Doc-only.

Part of BRO-1561. Companion to the merged kg/p9/role-x restructures + the skillify gate.

🤖 Generated with Claude Code

A skill must live in skills/<name>/ — a top-level SKILL.md + sibling scripts/ at
a repo root installs only SKILL.md via remote `npx skills add` (CLI repo-root
special-case), yielding a non-functional skill. Document the standard, the why,
the keep-your-repo-name fix, and the validation discipline (--list is necessary
not sufficient; runnable clean-room install is the gate; skillify enforces it).

BRO-1561

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jun 27, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@broomva, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 33 minutes and 3 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 057e20ed-6191-4c26-be75-c75481fa1f30

📥 Commits

Reviewing files that changed from the base of the PR and between 314a0e6 and 0c6e79e.

📒 Files selected for processing (1)
  • references/skills-roster.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/bro-1561-publishing-standard

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@broomva broomva merged commit e29780e into main Jun 27, 2026
5 checks passed
@broomva broomva deleted the fix/bro-1561-publishing-standard branch June 27, 2026 03:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant