Skip to content

feat: add rh-dataverse plugin with rover-people skill - #44

Merged
cblecker merged 1 commit into
mainfrom
feat/rh-dataverse-plugin
Jun 12, 2026
Merged

feat: add rh-dataverse plugin with rover-people skill#44
cblecker merged 1 commit into
mainfrom
feat/rh-dataverse-plugin

Conversation

@cblecker

@cblecker cblecker commented Jun 12, 2026

Copy link
Copy Markdown
Owner

Summary

  • Add Red Hat Dataverse MCP server plugin (mcp.dataverse.redhat.com)
  • Include rover-people skill for looking up employees, managers, direct reports, and org structure via the RoverPeople data product
  • Register plugin in marketplace manifest and root README

Test plan

  • claude plugin validate . passes
  • claude plugin validate ./rh-dataverse passes
  • npx markdownlint-cli2 passes on rh-dataverse/**/*.md
  • uvx skillsaw --strict passes
  • /rh-dataverse:rover-people triggers and runs the 3-step pipeline successfully

Summary by CodeRabbit

  • New Features
    • Added Red Hat Dataverse MCP server plugin providing capabilities for discovering data products, generating SQL queries, and executing them against Dataverse sources.
    • Included rover-people skill for querying people data with structured result formatting options (person cards, tables, and organizational hierarchies).

Add Red Hat Dataverse MCP server plugin with a skill for looking up
employees, managers, direct reports, and org structure via the
RoverPeople data product.

Assisted-by: Claude:claude-opus-4-6
@coderabbitai

coderabbitai Bot commented Jun 12, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

This PR registers a new MCP server plugin called rh-dataverse in the plugin marketplace. It adds registration entries, metadata, server configuration, and comprehensive documentation describing the Dataverse MCP server, its tools for data querying, and the rover-people skill that implements an enforced 3-step SQL query pipeline for person data retrieval.

Changes

rh-dataverse Plugin Registration

Layer / File(s) Summary
Plugin registration and discovery
.claude-plugin/marketplace.json, README.md
The rh-dataverse plugin is registered in the marketplace with strict: true and added to the main README plugins table with link and description.
Plugin metadata and MCP server configuration
rh-dataverse/.claude-plugin/plugin.json, rh-dataverse/.mcp.json
Plugin metadata (plugin.json) defines name, description, version 1.0.0, author, and keywords. MCP configuration (.mcp.json) defines the HTTP server endpoint at https://mcp.dataverse.redhat.com/mcp/.
Plugin documentation and skills
rh-dataverse/README.md, rh-dataverse/skills/rover-people/SKILL.md
Plugin README documents supported MCP tools (identify_dataproducts, shortlist_tables, get_sql, execute_sql). SKILL.md defines the rover-people skill with its mandatory 3-step pipeline (shortlist → generate SQL → execute), output formatting rules, and constraints on current-employee-only data and ambiguous name handling.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • cblecker/claude-plugins#35: Both PRs edit .claude-plugin/marketplace.json to register plugins in the marketplace manifest.
  • cblecker/claude-plugins#10: Both PRs add a complete new MCP server plugin by updating the marketplace, README, and adding plugin metadata files.

Poem

🐰 A curious rabbit hops to explore,
New data pathways to adore,
Dataverse gleams in structured light,
While rover-people search just right,
Three steps of SQL, pure delight!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely summarizes the main change: adding a new plugin (rh-dataverse) with a specific skill (rover-people), which aligns perfectly with the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/rh-dataverse-plugin

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 and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
rh-dataverse/skills/rover-people/SKILL.md (1)

51-53: ⚡ Quick win

Reduce repetitive sentence structure.

Three consecutive sentences begin with "Present" (lines 51–53). Consider rewording to improve readability and avoid monotonous pacing.

♻️ Proposed fix
 ## Formatting Results
 
-Present single-person results as a card (name, email, title, manager, geo,
-cost center). Present multi-person results as a markdown table. Present org
-chart results as an indented hierarchy.
+For single-person results, use a card format (name, email, title, manager, geo,
+cost center). For multi-person results, use a Markdown table. For org
+chart results, use an indented hierarchy.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@rh-dataverse/skills/rover-people/SKILL.md` around lines 51 - 53, The three
consecutive sentences in SKILL.md that begin with "Present" (the lines
describing single-person, multi-person, and org chart results) are repetitive;
reword them to vary sentence openings and improve flow—e.g., combine into one
sentence or start subsequent sentences with alternatives like "For single-person
results, show...", "For multiple people, render...", and "For org charts,
display..."; update the three result-description sentences in SKILL.md
accordingly to keep the same content but reduce the repeated "Present" wording.

Source: Linters/SAST tools

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@rh-dataverse/skills/rover-people/SKILL.md`:
- Line 52: In SKILL.md update the phrase "Present multi-person results as a
markdown table." to use the capitalized form "Markdown" (i.e., "Present
multi-person results as a Markdown table.") to follow proper noun
capitalization; locate the exact sentence in SKILL.md and replace "markdown"
with "Markdown".

---

Nitpick comments:
In `@rh-dataverse/skills/rover-people/SKILL.md`:
- Around line 51-53: The three consecutive sentences in SKILL.md that begin with
"Present" (the lines describing single-person, multi-person, and org chart
results) are repetitive; reword them to vary sentence openings and improve
flow—e.g., combine into one sentence or start subsequent sentences with
alternatives like "For single-person results, show...", "For multiple people,
render...", and "For org charts, display..."; update the three
result-description sentences in SKILL.md accordingly to keep the same content
but reduce the repeated "Present" wording.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 692ad1d2-59e0-46a1-92fc-c6a6f97cfd23

📥 Commits

Reviewing files that changed from the base of the PR and between 053470f and 99c7b25.

📒 Files selected for processing (6)
  • .claude-plugin/marketplace.json
  • README.md
  • rh-dataverse/.claude-plugin/plugin.json
  • rh-dataverse/.mcp.json
  • rh-dataverse/README.md
  • rh-dataverse/skills/rover-people/SKILL.md

## Formatting Results

Present single-person results as a card (name, email, title, manager, geo,
cost center). Present multi-person results as a markdown table. Present org

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Capitalize "markdown" as a proper noun in technical writing.

Per LanguageTool, the word "Markdown" should be capitalized when used as a language/format name.

✏️ Proposed fix
 Present multi-person results as a markdown table. Present org
+Present multi-person results as a Markdown table. Present org
🧰 Tools
🪛 LanguageTool

[uncategorized] ~52-~52: Did you mean the formatting language “Markdown” (= proper noun)?
Context: ...ter). Present multi-person results as a markdown table. Present org chart results as an ...

(MARKDOWN_NNP)


[style] ~52-~52: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...lti-person results as a markdown table. Present org chart results as an indented hierar...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@rh-dataverse/skills/rover-people/SKILL.md` at line 52, In SKILL.md update the
phrase "Present multi-person results as a markdown table." to use the
capitalized form "Markdown" (i.e., "Present multi-person results as a Markdown
table.") to follow proper noun capitalization; locate the exact sentence in
SKILL.md and replace "markdown" with "Markdown".

Source: Linters/SAST tools

@cblecker
cblecker merged commit 8c333e7 into main Jun 12, 2026
9 checks passed
@cblecker
cblecker deleted the feat/rh-dataverse-plugin branch June 12, 2026 15:50
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