Menu
Configure the local Multica API address, personal access token, and default workspace.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Draft and, after immediate natural-language confirmation, publish a Codex session summary to the linked Multica issue.
Associate the current Codex conversation with a Multica issue and load its context.
Show the configured Multica service, default workspace, and current conversation association.
Clear the Multica issue association from the current Codex conversation.
| name | init |
| description | Configure the local Multica API address, personal access token, and default workspace. |
Configure Multica only when the user explicitly invokes this skill.
Find the plugin root from the absolute path of this SKILL.md: it is two parent directories above this file. Ask for the API address when absent, then invoke node <plugin-root>/scripts/multica.mjs bootstrap --url <api-url>.
The bootstrap result names a private configuration file. Ask the user to add their Multica PAT to its apiToken field themselves; do not ask them to send it in this conversation and never pass a token as a command-line argument. Then invoke node <plugin-root>/scripts/multica.mjs init, adding --workspace-id <id-or-slug> only when the user selected a workspace. The helper accepts HTTPS, plus HTTP only for localhost development addresses.
If the helper reports workspace_selection_required, show only the returned workspace names and identifiers, ask the user to choose one, then rerun init with that selection. The helper stores the API address, token, and selected workspace in ~/.codex/multica/config.json with private permissions.
On success, report the configured API address and workspace without mentioning the token.
