Skill v1.0.1
currentAutomated scan96/100+5 new
version: "1.0.1" name: context-tree-publish description: Publish a project's local Context Tree as a new private GitHub repository when the user chooses GitHub publication. Connecting an existing GitHub tree uses connect; local creation does not require publication. license: Apache-2.0 compatibility: Requires Node.js 22.13+ and the context-tree CLI with connection schema version 2. metadata: author: first-tree-ai
Context Tree Publish
If context-tree is not found, stop and ask the user to run npm install --global @first-tree-ai/context-tree.
Use the original project's stable absolute path. An explicit request to publish, including choosing a new private GitHub tree during setup, authorizes this step; do not ask again. A vague request to "share" does not choose GitHub or authorize creating a repository: clarify the intended destination first.
Run context-tree publish --project-path "<project>" --tree "<alias>" --json. When the user explicitly supplies an alternative, append the validated OWNER/REPO argument. Never accept a repository URL.
Publication creates one new private repository, and the local connection update that follows is not part of the same atomic step. If it reports PUBLISH_INCOMPLETE, do not inspect, adopt, repair, retry, or delete partial state; report the uncertain outcome. If it reports INVALID_TREE, run context-tree verify --tree-path "<tree-path>" --json and report its findings.
Return success or failure to create/setup so the pending operation resumes only after the requested publication succeeds.
Select the connection alias from context-tree resolve --project-path "<project>" --json. Infer the destination from the user's request, relevant indexes, and task context when clear; ask when several destinations are plausible. A single connection can be selected implicitly. Selecting a destination does not grant write authorization. Keep each operation and commit within one tree. Work spanning trees requires separate operations with individually reported outcomes; there is no cross-tree transaction and no primary tree or implicit precedence.