[PR #4451] docs(skill): list kimi and workbuddy client IDs in the connection-and-recovery reference #6249

Open
opened 2026-10-31 01:13:01 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4451
Author: @devloper961-maker
Created: 10/16/2026
Status: 🔄 Open

Base: main ← Head: docs/skill-reference-missing-client-ids


📝 Commits (1)

  • 350112b docs(skill): list kimi and workbuddy client IDs in the connection-and-recovery reference

📊 Changes

1 file changed (+4 additions, -3 deletions)

View changed files

📝 .agents/skills/reverse-engineer-anything/references/connection-and-recovery.md (+4 -3)

📄 Description

Summary

The bundled skill's connection-and-recovery reference omitted the kimi and workbuddy setup client IDs from its supported-client list, even though both are documented clients (see docs/installation.md client table and docs/client-configuration.md). An agent recovering a Kimi Code or WorkBuddy registration through the skill would not have found the matching client ID in its instructions.

This carries over the Kimi Code skill-reference addition from #1806 as requested at that PR's closure, and extends it to workbuddy after re-checking current main.

Problem and expected behavior

Smallest trigger: a Kimi Code or WorkBuddy registration is missing/stale, an agent reads the skill's connection-and-recovery reference, and the client-ID list does not contain kimi or workbuddy.

Expected: the reference's ID list matches the supported-clients table in docs/installation.md.

Change and scope

One-line list update in the skill reference (4 insertions / 3 deletions from reflowed wrapping). Documentation-only; no contract, tool-catalog, or provider change.

Follow the contribution scope: not applicable (ordinary documentation fix within existing boundaries).

Contract and boundary impact

  • Semantic owner and earliest changed stage: skill instruction content only.
  • Contribution scope fit and linked maintainer decision: not applicable.
  • CLI and MCP/tool-catalog contract: none.
  • Provider/bridge/target-format/platform compatibility: none.
  • Evidence/artifact/provenance/reconstruction contract: none.
  • Target selection/authority/upstream/cleanup: not applicable.
  • Generated metadata impact: none; sourced from the existing documented client set.

Expected effects:

  • Documentation or usability only; no target interaction.

Evidence and regression coverage

  • Tests added or updated: none needed (documentation-only).
  • Base reproduction: current main's list omits both IDs (git show upstream/main before the patch).
  • Remaining proof gaps: none identified for the doc-only scope.

Validation performed

  • npx turbo run docs:check:built — 6/6 tasks passed 47s (includes generate-skill-metadata --check, generate-product-catalog --check, check-doc-facts, licenses check) on this Windows host with Node 24.14.1
  • npm run test:local -- tests/conformance/readmeConsistency.test.ts — 5/5 passed

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra/browser/OS coverage: not applicable.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: none.

Author readiness

Human owner: @devloper961-maker

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem (maintainer request at #1806 closure).
  • Material scope and authority questions are resolved: none; documentation-only.
  • One focused outcome; title follows type(scope): outcome.
  • Related issue linked: #1806 (carry-over request in closure comment).
  • Tests cover changed observable behavior — not applicable beyond the doc-consistency checks above.
  • Owning docs updated where needed.
  • User-visible CLI/MCP changes — none.
  • Checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/4451 **Author:** [@devloper961-maker](https://github.com/devloper961-maker) **Created:** 10/16/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `docs/skill-reference-missing-client-ids` --- ### 📝 Commits (1) - [`350112b`](https://github.com/morluto/rea/commit/350112b1d1e97e6c69b2e1be90f695e798a6985e) docs(skill): list kimi and workbuddy client IDs in the connection-and-recovery reference ### 📊 Changes **1 file changed** (+4 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md` (+4 -3) </details> ### 📄 Description ## Summary The bundled skill's [connection-and-recovery reference](../blob/main/.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md) omitted the `kimi` and `workbuddy` setup client IDs from its supported-client list, even though both are documented clients (see `docs/installation.md` client table and `docs/client-configuration.md`). An agent recovering a Kimi Code or WorkBuddy registration through the skill would not have found the matching client ID in its instructions. This carries over the Kimi Code skill-reference addition from #1806 as requested at that PR's closure, and extends it to `workbuddy` after re-checking current main. ## Problem and expected behavior Smallest trigger: a Kimi Code or WorkBuddy registration is missing/stale, an agent reads the skill's connection-and-recovery reference, and the client-ID list does not contain `kimi` or `workbuddy`. Expected: the reference's ID list matches the supported-clients table in `docs/installation.md`. ## Change and scope One-line list update in the skill reference (4 insertions / 3 deletions from reflowed wrapping). Documentation-only; no contract, tool-catalog, or provider change. Follow the contribution scope: not applicable (ordinary documentation fix within existing boundaries). ## Contract and boundary impact - Semantic owner and earliest changed stage: skill instruction content only. - Contribution scope fit and linked maintainer decision: not applicable. - CLI and MCP/tool-catalog contract: none. - Provider/bridge/target-format/platform compatibility: none. - Evidence/artifact/provenance/reconstruction contract: none. - Target selection/authority/upstream/cleanup: not applicable. - Generated metadata impact: none; sourced from the existing documented client set. Expected effects: - [x] Documentation or usability only; no target interaction. ## Evidence and regression coverage - Tests added or updated: none needed (documentation-only). - Base reproduction: current main's list omits both IDs (`git show upstream/main` before the patch). - Remaining proof gaps: none identified for the doc-only scope. ## Validation performed - `npx turbo run docs:check:built` — 6/6 tasks passed 47s (includes `generate-skill-metadata --check`, `generate-product-catalog --check`, `check-doc-facts`, licenses check) on this Windows host with Node 24.14.1 - `npm run test:local -- tests/conformance/readmeConsistency.test.ts` — 5/5 passed ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra/browser/OS coverage: not applicable. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none. ## Author readiness Human owner: @devloper961-maker <!-- AI-assisted work; human owner to complete declarations below before marking ready for review. --> - [ ] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [ ] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [ ] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem (maintainer request at #1806 closure). - [x] Material scope and authority questions are resolved: none; documentation-only. - [x] One focused outcome; title follows `type(scope): outcome`. - [x] Related issue linked: #1806 (carry-over request in closure comment). - [ ] Tests cover changed observable behavior — not applicable beyond the doc-consistency checks above. - [x] Owning docs updated where needed. - [ ] User-visible CLI/MCP changes — none. - [x] Checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#6249
No description provided.