CLI commands for resources and workflows

Use these commands to publish events, courses, content, quests and jobs, and to run what happens around them: RSVPs, enrollments, attendance, quest evidence and job applications. All of them print JSON. Conventions such as exit codes, --file merging and --account are on the main CLI command reference.

These commands also exist in CLI version 0.3, so nothing on this page carries the (0.4+) marker.

#Common actions

posts, events, courses, content, quests and jobs share the same five actions. Replace <kind> with the family name.

For an item owned by a community, add communities:write to the write scopes and communities:read to reads on other accounts, and you need a current role there.

--account is not supported on these commands; use --owner-type community --community-id <account-id> to create for an account you help run, after hive3 capabilities shows it.

Things to know before you create:

• Events need RSVP approval by default. Put "autoEnroll": true in the file to accept attendees automatically. eventSlots entries need ISO 8601 startsAt and endsAt with a Z or offset, and each end must come after its start.
• Quests need questCreditPlan (single for quests up to 7 days, bundle for up to 30) and spend one quest credit of the owning account. A credited quest needs a valid startsAt.
• Once an event or quest has started, update and archive return 409 conflict.
• Plan rules apply as in the app. A Worker Bee account publishes publicly only and cannot attach subscriptions.

{
  "title": "Portfolio night",
  "description": "Bring two projects for feedback.",
  "visibility": "public",
  "autoEnroll": true,
  "location": "Online",
  "eventSlots": [
    { "startsAt": "2026-12-12T18:00:00Z", "endsAt": "2026-12-12T20:00:00Z" }
  ]
}

hive3 events create --file event.json --idempotency-key portfolio-night-2026
hive3 events list --limit 5
hive3 events archive "<event-id>"

hive3 capabilities
hive3 posts create --body "Moderator update" --owner-type community --community-id "<account-id>"

#Events

RSVPs share the app's limits of 10 per minute and 100 per day. Attendance needs an approved RSVP on an event that is not archived; the first recorded time is kept, the attendee is notified, and clearing attendance (--attended false) is refused with 409 conflict. Treat approving, denying and recording attendance as decisions that need a human check.

#Courses

{
  "title": "Intro to critique",
  "description": "Four short lessons.",
  "visibility": "public",
  "lessons": [
    { "id": "lesson-1", "title": "Give useful feedback" },
    { "id": "lesson-2", "title": "Receive feedback" }
  ]
}

#Content

hive3 content has only the common actions, with --content-type <type> choosing the kind of content (the default is article).

{
  "title": "Welcome guide",
  "description": "How this community works.",
  "contentType": "article",
  "visibility": "public"
}

#Quests

{
  "title": "Ship a portfolio page",
  "description": "Publish a page and share the link.",
  "questCreditPlan": "single",
  "startsAt": "2026-12-01T00:00:00Z",
  "endsAt": "2026-12-05T00:00:00Z",
  "objectives": [
    { "id": "objective-1", "type": "custom", "completionCriteria": "Submit a link", "evidenceType": "link" }
  ]
}

To attach a file as evidence, upload it first and reference the returned upload ID. Use the byteSize and contentType of the file you uploaded.

{
  "attachments": [
    { "storageId": "<upload-id>", "fileName": "proof.pdf", "contentType": "application/pdf", "byteSize": 100000 }
  ]
}

hive3 upload ./proof.pdf --purpose document
hive3 quests evidence submit "<quest-id>" --objective-id objective-1 --content "https://proof.example" --file evidence.json
hive3 quests evidence list "<quest-id>" --status pending
hive3 quests evidence approve "<quest-id>" "<evidence-id>"

#Jobs

resume and the optional coverLetter each need fileName, contentType and a positive byteSize, plus a storageId from hive3 upload --purpose document.

{
  "resume": { "storageId": "<upload-id>", "fileName": "resume.pdf", "contentType": "application/pdf", "byteSize": 124000 },
  "coverLetter": { "storageId": "<upload-id>", "fileName": "cover-letter.pdf", "contentType": "application/pdf", "byteSize": 84000 }
}

{
  "title": "Community manager",
  "description": "Run weekly events and welcome new members.",
  "employerName": "Design Guild",
  "location": "Remote",
  "visibility": "public"
}

Participant, enrollment and application lists include each person's primary email address when you manage the resource. Keep that output out of logs, chats and prompts.