You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs(kiro): document power installation on the portable package - #67
Document Kiro IDE power installation using the current portable Agent Plugins package. The branch is rebased onto one-off/agent-plugin, commit 014d855.
The Kiro-specific diff against that branch is README-only:
Explain GitHub and local-folder power installation.
Document the confirmed import failure for branch names containing / and the workarounds.
Use the current ~/.dataiku/stdio-config.json profile path, with a link to configuration overrides.
Explain that ambient environment inheritance is not guaranteed and verify setup with the MCP panel, get_current_instance, and a read-only Dataiku call.
The base package already has the narrow dataiku / cobuild activation keywords. The old top-level displayName addition is omitted because the current portable manifest schema rejects it. The obsolete tests/test_agent_plugins.py remains deleted; current packaging coverage lives in tests/test_plugin_packaging.py.
This PR targets one-off/agent-plugin, so its diff contains only the Kiro README instructions. The Codex, Cursor, and other portable-package migration changes belong to that base branch and are outside this PR. Merge the portable package separately before retargeting this PR to a release branch. The old dependency on closed PR #91 is superseded by one-off/agent-plugin.
Confirmed Kiro GitHub import failure
Importing https://github.com/dataiku/dataiku-headless/tree/one-off/agent-plugin fails in Kiro. Local Powers logs from November 12, 2026 show repeated attempts interpreting the URL as:
branch: one-off
subdirectory: agent-plugin
Failed to clone repository: Could not find one-off.
The actual branch is one-off/agent-plugin. Kiro splits it at the slash and fails during cloning, before reading the manifest or starting MCP. feat/kiro-support has the same branch-name limitation.
Workarounds:
Publish the desired commit under a stable branch without a slash, such as kiro-submission, and import that branch URL. No such branch was created during this work.
Clone the desired branch locally and choose Powers → Add Custom Power → Import power from a folder. For the portable package branch:
Select /tmp/dataiku-kiro-power in Kiro. Folder import is an officially documented workflow; a successful import and live connection have not yet been verified for the rebased candidate.
Registry submission gaps
Against the current Kiro registry submission requirements, the portable package has the required root plugin.json metadata, mcp.json, and skills. Remaining work, also tracked in #158:
Add a Privacy Policy link to the repository README.
Add support contact information (direct link or email) to the repository README.
Verify the exact candidate in current Kiro: successful import, keyword activation, MCP startup, saved-profile setup, and a read-only Dataiku call.
Confirm the candidate is complete and working and its MCP server is generally available rather than beta/preview; uniqueness and registry inclusion remain subject to Kiro's curated review.
Privacy and support links currently exist only in OpenAI-specific manifest metadata, which does not satisfy Kiro's explicit README requirements. Those gaps did not cause the clone failure.
The submission form's client-side URL validation accepts GitHub /tree/<branch> URLs. Public documentation does not promise that registry review or installation preserves that branch. For a branch-based application, use a stable public branch without a slash, identify its name and reviewed commit in the optional description, and obtain confirmation of the target from the Kiro reviewer. No application has been submitted as part of this work.
Validation
On the rebased branch:
uv sync --locked — passed.
uv run pre-commit run --all-files --show-diff-on-failure — passed.
uv run pytest — 827 passed; two Linux/OpenSSL-specific certificate tests skipped on macOS.
uv build — source distribution and wheel built.
CI-style wheel import smoke in a separate Python 3.12 environment, outside the repository — passed.
uv run cz check --rev-range origin/one-off/agent-plugin..HEAD — passed.
git diff --check — passed.
No MCP implementation, tool, or skill changes were made beyond the inherited portable package. Live Kiro/Dataiku verification remains outstanding.
The branch has the required root plugin.json metadata ($schema, name, version, description, author, activation keywords, and license), root mcp.json, and skills. It is not yet ready for submission:
Add a Privacy Policy link to the repository README. extensions.com.openai.interface.privacyPolicyURL in plugin.json does not satisfy Kiro's explicit README requirement.
Add support contact information (a direct link or email) to the repository README. The OpenAI-specific supportURL and the README's indirect link to CONTRIBUTING.md do not clearly supply the required contact information.
Verify this exact package in current Kiro: import, keyword activation, MCP startup, saved-profile setup, and a read-only Dataiku call. The earlier screenshots in this PR do not verify branch commit 014d855.
Resolve the branch URL import concern before distributing it. This PR reports that branch names containing / are misparsed; one-off/agent-plugin has that shape. Re-test current Kiro or use a branch without a slash for the candidate.
Validation completed in an isolated archive of the reviewed commit:
uv run --locked pytest tests/test_plugin_packaging.py tests/test_cursor_plugin.py tests/test_pep723_launcher.py -q
17 passed
No live Kiro/Dataiku verification or full repository gates were run for this packaging review. Kiro also requires a complete, working power, a unique use case, and generally available MCP servers rather than beta/preview servers; the publisher must confirm readiness, and registry inclusion remains curated.
Can the application point at a specific branch?
The current form has one Public GitHub repository URL field and no separate branch selector. Its client-side URL validation accepts a GitHub /tree/<branch> URL, so a branch URL can be supplied in the application. This does not establish that the backend, registry review, or eventual registry installation will honor that branch; the public documentation does not promise branch pinning.
For a branch-based application, use a stable public candidate branch without a slash, identify the branch and reviewed commit in the optional description, and ask the Kiro reviewer to confirm the target. For the most straightforward published install, land the package and required README links on the default branch first. No application was submitted as part of this review.
ludwigehlert-gif
changed the title
feat(kiro): add Kiro MCP auto-discovery and skill install docs
docs(kiro): document power installation on the portable package
Nov 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Document Kiro IDE power installation using the current portable Agent Plugins package. The branch is rebased onto
one-off/agent-plugin, commit014d855.The Kiro-specific diff against that branch is README-only:
/and the workarounds.~/.dataiku/stdio-config.jsonprofile path, with a link to configuration overrides.get_current_instance, and a read-only Dataiku call.The base package already has the narrow
dataiku/cobuildactivation keywords. The old top-leveldisplayNameaddition is omitted because the current portable manifest schema rejects it. The obsoletetests/test_agent_plugins.pyremains deleted; current packaging coverage lives intests/test_plugin_packaging.py.This PR targets
one-off/agent-plugin, so its diff contains only the Kiro README instructions. The Codex, Cursor, and other portable-package migration changes belong to that base branch and are outside this PR. Merge the portable package separately before retargeting this PR to a release branch. The old dependency on closed PR #91 is superseded byone-off/agent-plugin.Confirmed Kiro GitHub import failure
Importing
https://github.com/dataiku/dataiku-headless/tree/one-off/agent-pluginfails in Kiro. Local Powers logs from November 12, 2026 show repeated attempts interpreting the URL as:The actual branch is
one-off/agent-plugin. Kiro splits it at the slash and fails during cloning, before reading the manifest or starting MCP.feat/kiro-supporthas the same branch-name limitation.Workarounds:
kiro-submission, and import that branch URL. No such branch was created during this work.Select
/tmp/dataiku-kiro-powerin Kiro. Folder import is an officially documented workflow; a successful import and live connection have not yet been verified for the rebased candidate.Registry submission gaps
Against the current Kiro registry submission requirements, the portable package has the required root
plugin.jsonmetadata,mcp.json, and skills. Remaining work, also tracked in #158:Privacy and support links currently exist only in OpenAI-specific manifest metadata, which does not satisfy Kiro's explicit README requirements. Those gaps did not cause the clone failure.
The submission form's client-side URL validation accepts GitHub
/tree/<branch>URLs. Public documentation does not promise that registry review or installation preserves that branch. For a branch-based application, use a stable public branch without a slash, identify its name and reviewed commit in the optional description, and obtain confirmation of the target from the Kiro reviewer. No application has been submitted as part of this work.Validation
On the rebased branch:
uv sync --locked— passed.uv run pre-commit run --all-files --show-diff-on-failure— passed.uv run pytest— 827 passed; two Linux/OpenSSL-specific certificate tests skipped on macOS.uv build— source distribution and wheel built.uv run cz check --rev-range origin/one-off/agent-plugin..HEAD— passed.git diff --check— passed.No MCP implementation, tool, or skill changes were made beyond the inherited portable package. Live Kiro/Dataiku verification remains outstanding.