Add readme notes on using the build-plugin skill#76
Conversation
📝 WalkthroughWalkthroughThe README adds a new section describing the Claude Code build-plugin skill, its workflow phases, required tools and tenant access, the ChangesClaude Code build-plugin documentation
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
🧩 Plugin PR Summaryℹ️ No plugins were modified in this PR. |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 `@README.md`:
- Around line 46-65: Update the “Building with Claude Code (build-plugin skill)”
section in README to add the REST-only limitation: the build-plugin skill should
be described as applicable only to web API/REST-based plugins, and readers
should be told to stop or choose another path if the target service does not
expose a usable REST API. Keep the existing flow description, but adjust the
introductory text near the build-plugin mention so it does not imply the skill
works for non-REST integrations.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| ### Building with Claude Code (build-plugin skill) | ||
|
|
||
| If you have access to [Claude Code](https://claude.ai/code), the `build-plugin` skill can guide you through building a plugin from scratch — from exploring the API all the way to a deployed, tested plugin with dashboards. | ||
|
|
||
| **What it does** | ||
|
|
||
| The skill walks you through the full process in structured phases: | ||
|
|
||
| 1. Explores the target API and plans the plugin structure with you | ||
| 2. Scaffolds all the required files | ||
| 3. Deploys a working version of your plugin early, then pauses for you to authenticate it (OAuth, API key, or whatever the service uses) | ||
| 4. Tests imports and indexes objects so real data is flowing before the plugin is finished | ||
| 5. Builds and tests each data stream against live data as it goes | ||
| 6. Authors out-of-the-box dashboards | ||
|
|
||
| **Prerequisites** | ||
|
|
||
| - [Claude Code](https://claude.ai/code) installed | ||
| - The `squaredup` CLI installed and logged in (`npm i -g @squaredup/cli`, then `squaredup login`) | ||
| - A SquaredUp tenant where you can add and authenticate the plugin |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Add the REST-only scope caveat.
The upstream skill is explicitly limited to web API-based plugins and says to stop if the target tool has no usable REST API. Without that note, this README overstates when the skill applies.
Suggested patch
### Building with Claude Code (build-plugin skill)
If you have access to [Claude Code](https://claude.ai/code), the `build-plugin` skill can guide you through building a plugin from scratch — from exploring the API all the way to a deployed, tested plugin with dashboards.
+> [!NOTE]
+> This skill is for web API-based plugins only. If the target tool has no usable REST API, PowerShell may be a better fit.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### Building with Claude Code (build-plugin skill) | |
| If you have access to [Claude Code](https://claude.ai/code), the `build-plugin` skill can guide you through building a plugin from scratch — from exploring the API all the way to a deployed, tested plugin with dashboards. | |
| **What it does** | |
| The skill walks you through the full process in structured phases: | |
| 1. Explores the target API and plans the plugin structure with you | |
| 2. Scaffolds all the required files | |
| 3. Deploys a working version of your plugin early, then pauses for you to authenticate it (OAuth, API key, or whatever the service uses) | |
| 4. Tests imports and indexes objects so real data is flowing before the plugin is finished | |
| 5. Builds and tests each data stream against live data as it goes | |
| 6. Authors out-of-the-box dashboards | |
| **Prerequisites** | |
| - [Claude Code](https://claude.ai/code) installed | |
| - The `squaredup` CLI installed and logged in (`npm i -g @squaredup/cli`, then `squaredup login`) | |
| - A SquaredUp tenant where you can add and authenticate the plugin | |
| ### Building with Claude Code (build-plugin skill) | |
| If you have access to [Claude Code](https://claude.ai/code), the `build-plugin` skill can guide you through building a plugin from scratch — from exploring the API all the way to a deployed, tested plugin with dashboards. | |
| > [!NOTE] | |
| > This skill is for web API-based plugins only. If the target tool has no usable REST API, PowerShell may be a better fit. | |
| **What it does** | |
| The skill walks you through the full process in structured phases: | |
| 1. Explores the target API and plans the plugin structure with you | |
| 2. Scaffolds all the required files | |
| 3. Deploys a working version of your plugin early, then pauses for you to authenticate it (OAuth, API key, or whatever the service uses) | |
| 4. Tests imports and indexes objects so real data is flowing before the plugin is finished | |
| 5. Builds and tests each data stream against live data as it goes | |
| 6. Authors out-of-the-box dashboards | |
| **Prerequisites** | |
| - [Claude Code](https://claude.ai/code) installed | |
| - The `squaredup` CLI installed and logged in (`npm i -g `@squaredup/cli``, then `squaredup login`) | |
| - A SquaredUp tenant where you can add and authenticate the plugin |
🤖 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 `@README.md` around lines 46 - 65, Update the “Building with Claude Code
(build-plugin skill)” section in README to add the REST-only limitation: the
build-plugin skill should be described as applicable only to web API/REST-based
plugins, and readers should be told to stop or choose another path if the target
service does not expose a usable REST API. Keep the existing flow description,
but adjust the introductory text near the build-plugin mention so it does not
imply the skill works for non-REST integrations.
clarkd
left a comment
There was a problem hiding this comment.
I'll add this to the LCP Confluence Docs too - thank you!
📋 Summary
As title suggests
🔍 Scope of change
📚 Checklist
Summary by CodeRabbit