# Reachai Onboarding

Integrate Java business systems with ReachAI SDK registration, instance heartbeat...

- Repository: https://github.com/w8123/EnterpriseAgentFramework (1017 stars)
- Category: Business
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add w8123/EnterpriseAgentFramework --skill reachai-onboarding -g -a claude-code -y`
Codex: `npx skills add w8123/EnterpriseAgentFramework --skill reachai-onboarding -g -a codex -y`
Cursor: `npx skills add w8123/EnterpriseAgentFramework --skill reachai-onboarding -g -a cursor -y`
Gemini CLI: `npx skills add w8123/EnterpriseAgentFramework --skill reachai-onboarding -g -a gemini-cli -y`

## Description

Integrate Java business systems with ReachAI SDK registration, instance heartbeat, gateway/embed access, and business capability source sync. Use when asked to connect a Spring Boot service to ReachAI, add reachai-capability-sdk or reachai-spring-boot2-starter, configure reachai.registry/reachai.project/reachai.capability, prepare @ReachCapability declarations, or verify SDK onboarding from a ReachAI manifest.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# ReachAI Onboarding

## Operating Rules

Treat the current business repository as the source of truth. Inspect its Maven modules, Java version, Spring Boot version, configuration files, existing controller/service boundaries, and test commands before editing.

凡是写入 ReachAI 或展示给业务用户的名称、标题、描述、说明、System Prompt、节点名称、审计原因、进度和结果，默认使用清晰的简体中文。不要仅因 API、Schema 或字段名为英文就生成英文业务文案。Token、MCP、AI、Agent、Supervisor、Workflow、Tool、API、SDK 等熟知专业术语，以及 keySlug、toolName、代码、路径、枚举值、协议字段和技术标识可保留英文；必要时使用“中文名称（英文术语）”。不要翻译或改写技术标识。

Never paste, print, or commit the registry app secret. Use the environment variable named by the manifest, normally `REACHAI_REGISTRY_APP_SECRET`.

ReachAI task handoffs use a one-time activation code. Activate it once, keep the returned short-lived task token only in the current process, and call `/api/ai-coding/tasks/{taskId}/**` with `Authorization: Bearer <taskToken>`. Never reuse a project-level `aiCodingKey` on task protocol routes.

Separate project/Workflow AI Coding APIs under `/api/ai-coding/projects/**` and `/api/workflows/**/ai-coding/**` can still use the explicit project `aiCodingKey` when the user independently supplies one. Send it as `X-ReachAI-AiCoding-Key`; never put it in a URL, browser bundle, task artifact, or progress event.

The rest: https://github.com/w8123/EnterpriseAgentFramework/blob/HEAD/reachai-control-service/src/main/resources/ai-assist/skills/reachai-onboarding/SKILL.md