Blossom Hire

Description

Use this skill when the user wants to post a local paid help request (task or short shift) into Blossom, or when they want to check whether anyone has applied.

This skill creates roles via Blossom’s API and can retrieve eligible candidates later. The user can install blossom app on their mobile if they want to manage applications directly.

Tools

Use bash to call Blossom’s HTTP endpoints with curl. Use jq to parse JSON responses.

Endpoints:

• POST https://hello.blossomai.org/api/v1/pushuser (register/login + role commit)
• POST https://hello.blossomai.org/getPopInUpdates (retrieve candidates)

Requirements

• bash tool access enabled in OpenClaw
• curl installed
• jq installed

Instructions

When to use this skill

Activate this skill when the user says things like:

• “Post a job for me”
• “Hire someone”
• “I need staff for a shift”
• “Create a task”
• “I need someone to help with something”
• “Check if anyone applied”
• “Do I have any candidates yet?”

What information to collect

Collect details conversationally. Do not front-load questions. If the user provides partial information, continue and only ask for what is missing.

Role details

1. Headline (one line)
2. Details (2–6 lines describing what the helper will do)
3. When (working hours or “flexible”)
4. Where (street, city, postcode, country)
5. Pay
   • amount (number)
   • frequency: total | per hour | per week | per month | per year

Optional: Requirements and benefits If the user provides or requests screening questions, capture them as requirements. If the user provides perks, capture them as benefits.

• Requirements: name + mandatory (default false)
• Benefits: name + mandatory (default false)

Identity details Ask only when you are ready to create or check a role:

• email
• first name
• surname
• mobileCountry (e.g. +44)
• mobile number
• passKey

Notes:

• Default to registration.
• Only use login if registration fails because the email already exists, or if the user explicitly says they already have an account.

Behaviour rules

1. Gather role details first.
2. Confirm the role summary back to the user in one compact message (headline, when, where, pay).
3. Collect identity details if missing.
4. Bootstrap identity and address via the Blossom API.
5. Commit the role.
6. Return a concise confirmation including the role ID.
7. When asked to check candidates, retrieve and display the candidate list.

Output rules

• Never promise that someone will apply.
• If there are zero candidates, say: “Waiting for responses.”
• Only treat type === "candidates" as the operator-facing list.
• Do not infer suitability beyond what the API returns.

Session state

The skill must store these values as runtime state and reuse them across calls:

• personId
• sessionKey
• addressId