Skip to content

docs(kiro): document power installation on the portable package - #67

Open
ludwigehlert-gif wants to merge 1 commit into
one-off/agent-pluginfrom
feat/kiro-support
Open

ludwigehlert-gif wants to merge 1 commit into
one-off/agent-pluginfrom
feat/kiro-support

Conversation

@ludwigehlert-gif

@ludwigehlert-gif ludwigehlert-gif commented Jul 27, 2026 •

Copy link
Copy Markdown
Contributor

Summary

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:
git clone --branch one-off/agent-plugin --single-branch \
  https://github.com/dataiku/dataiku-headless.git \
  /tmp/dataiku-kiro-power

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.

@ludwigehlert-gif
ludwigehlert-gif marked this pull request as ready for review July 27, 2026 19:58
@ludwigehlert-gif
ludwigehlert-gif force-pushed the feat/kiro-support branch 3 times, most recently from d11d0e6 to 94983f1 Compare September 15, 2026 11:38
@ludwigehlert-gif
ludwigehlert-gif changed the base branch from main to agent/agent-plugins-standard September 15, 2026 11:38
@pmasiphelps
pmasiphelps changed the base branch from agent/agent-plugins-standard to release/0.10.0 November 12, 2026 14:25
@ludwigehlert-gif

Copy link
Copy Markdown
Contributor Author

Registry readiness review of one-off/agent-plugin

Reviewed branch commit 014d855a00513815392bb87c2b4c571d1beead73 against the current Kiro registry submission requirements and power packaging documentation. Related tracking: #158.

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 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
@ludwigehlert-gif
ludwigehlert-gif changed the base branch from release/0.10.0 to one-off/agent-plugin November 12, 2026 16:47
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