From twi-jobworld
Interact with TWI Jobworld server API. Trigger with "jobworld api", "jobworld endpoints", "jobworld server".
How this skill is triggered — by the user, by Claude, or both
Slash command
/twi-jobworld:jobworld-apiThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Skill for interacting with TWI Jobworld server API.
Skill for interacting with TWI Jobworld server API.
http://localhost:{PORT}/api
Where PORT is the jobworld server port (e.g., 3848).
GET /api/health
Returns server status.
GET /api/departments
POST /api/departments
GET: List all departmentsPOST: Create department
{ "name": "content", "description": "Newsletter creation" }
GET /api/agents
POST /api/agents
GET /api/agents/:id
DELETE /api/agents/:id
GET /api/agents: List all agentsPOST /api/agents: Register agent
{
"name": "content-lead",
"dept_id": "dept_xxx",
"agent_file_path": "/path/to/agent.md"
}
DELETE /api/agents/:id: Remove agent (Task #4 - DELETE endpoint exists)GET /api/stats
Returns company statistics.
GET /api/events
POST /api/events
GET /api/events: Recent eventsPOST /api/events: Emit event
{ "type": "task_completed", "data": { "agent": "content-lead", "task": "newsletter_001" } }
# List agents
curl http://localhost:3848/api/agents
# Create department
curl -X POST http://localhost:3848/api/departments \
-H "Content-Type: application/json" \
-d '{"name": "content", "description": "Newsletter"}'
# Register agent
curl -X POST http://localhost:3848/api/agents \
-H "Content-Type: application/json" \
-d '{"name": "content-lead", "dept_id": "dept_xxx", "agent_file_path": "/path/to/content-lead.md"}'
npx claudepluginhub sancovp/twi-jobworldGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.