connect

Resolves and persists eventmodelers API connection config from inline params or config file.

1|1|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/Powerworks/K9DatingApp --skill connect-powerworks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: connect
Source: https://github.com/Powerworks/K9DatingApp/tree/main/.claude/skills/connect
Command: npx skills add https://github.com/Powerworks/K9DatingApp --skill connect-powerworks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Every skill that talks to the eventmodelers API needs a token, board ID, organization ID, and base URL, and manually re-entering these credentials each session is error-prone. This Skill centralizes credential resolution so all other skills start from a verified, consistent connection config. ## Core Features & Use Cases - Multi-source config resolution: Reads inline parameters (board=, token=, org=, baseUrl=) first, then falls back to .eventmodelers/config.json found by walking up parent directories, then asks the user for anything still missing. - Secure persistence: Writes the resolved config to the repo-root .eventmodelers/config.json and ensures it is added to .gitignore so the API token is never committed. - Connection verification: Validates the token and board with a lightweight API call and handles 401, 403, and 404 responses with targeted re-prompting. - Use Case: Before running load-slice or build-state-change against an eventmodelers board, invoke this skill once to establish and verify the session's API credentials. ## Quick Start Connect to my eventmodelers board and set up the API config for this session.

Frequently Asked Questions about connect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure eventmodelers API credentials for a session?▼

Provide values inline (board=, token=, org=, baseUrl=) or let the skill read .eventmodelers/config.json by walking up parent directories. Missing values are requested interactively, then persisted and verified with a test API call.

Where is the eventmodelers config file stored?▼

The config is written to .eventmodelers/config.json at the repository root so every skill and the Ralph .NET tool find the same file regardless of working directory. It is automatically added to .gitignore because it contains a secret API token.

What happens if my eventmodelers API token is invalid?▼

A 401 response means the token is invalid and the skill re-prompts for it. A 403 means the token's organization does not match the board, and a 404 means the board ID was not found; each case triggers targeted re-entry of the affected fields.

Can I override the config file with inline parameters?▼

Yes, inline parameters like board=<uuid> or token=<uuid> take priority over values in .eventmodelers/config.json. The resolution order is inline param first, then config file, then asking the user.

Is the eventmodelers API token committed to git?▼

No, the skill checks .gitignore for the config path and appends .eventmodelers/config.json if missing. The token is treated as a secret and is never logged or displayed after initial confirmation.