Skip to content

SKILL.md

Latest commit

 

History

History
235 lines (160 loc) · 5.79 KB

SKILL.md

File metadata and controls

235 lines (160 loc) · 5.79 KB

SKILL.md – TaskBoard Agent Instructions

TaskBoard is a P2P micro-gig marketplace built on the Intercom stack (Trac Network).
Any peer can post tasks, claim them, submit work, and have it accepted or rejected — all recorded on-chain.

This file is the canonical reference for agents and operators running TaskBoard.

1. Prerequisites

Tool Version
git any
node ≥ 18
pear latest

Install Pear globally:

npm install -g pear

2. Installation

git clone https://github.com/theonlysol/intercom
cd intercom
npm install
npm pkg set overrides.trac-wallet=1.0.1
rm -rf node_modules package-lock.json
npm install

3. First Run (Bootstrap / Admin peer)

pear run --tmp-store --no-pre . --peer-store-name admin --msb-store-name admin-msb --subnet-channel taskboard-v1
  1. Wait for startup. Type /exit and press Enter.
  2. Re-run the same command.
  3. When the options prompt appears, copy your Peer Address.
  4. Add yourself as admin:
/add_admin --address <YourPeerAddress>

4. Joining as a Regular Peer

pear run --tmp-store --no-pre . --peer-store-name peer1 --msb-store-name peer1-msb --subnet-channel taskboard-v1

The peer will auto-discover and sync with the bootstrap node.

5. Task Lifecycle

open → claimed → submitted → done
                ↑___reject__|

open → cancelled  (poster cancels before any claim)
Status Meaning
open Posted, not yet claimed
claimed A worker has claimed it; awaiting submission
submitted Worker submitted result; awaiting poster review
done Poster accepted the submission
cancelled Poster cancelled before it was claimed

6. App-Specific Commands

task_post

/tx --command '{ "op": "task_post", "title": "<text>", "description": "<text>", "reward": "<text>", "tags": "<csv>" }'
  • title: string, max 100 chars (required)
  • description: string, max 1000 chars (required)
  • reward: free-text string, e.g. "500 TNK" (optional)
  • tags: comma-separated string, e.g. "writing,seo" (optional)

Returns: { ok, task_id, title, posted_by, created_at }

task_list

/tx --command '{ "op": "task_list", "status": "open" }'
  • status: open | claimed | submitted | done | cancelled | all (default: all)

Returns: { tasks: [...] }

task_get

/tx --command '{ "op": "task_get", "task_id": <id> }'

Returns full task object including submission result if present.

task_claim

/tx --command '{ "op": "task_claim", "task_id": <id> }'
  • Only allowed when task status is open
  • Poster cannot claim their own task
  • First caller wins; subsequent attempts get ALREADY_CLAIMED

Returns: { ok, task_id, claimed_by, claimed_at }

task_submit

/tx --command '{ "op": "task_submit", "task_id": <id>, "result": "<work output>" }'
  • Only the claimant can submit
  • result: string, max 4000 chars (required)
  • Can be called again after a rejection (overwrites previous result)

Returns: { ok, task_id, submitted_at }

task_accept

/tx --command '{ "op": "task_accept", "task_id": <id> }'
  • Only the original poster can call this
  • Task must be in submitted status
  • Marks task as done

Returns: { ok, task_id, done_at, worker: <claimant address> }

task_reject

/tx --command '{ "op": "task_reject", "task_id": <id>, "reason": "<feedback>" }'
  • Only the original poster can call this
  • Task must be in submitted status
  • Returns task to claimed status; worker can resubmit
  • reason: optional feedback string, max 500 chars

Returns: { ok, task_id, reason, status: "claimed" }

task_cancel

/tx --command '{ "op": "task_cancel", "task_id": <id> }'
  • Only the original poster can call this
  • Only allowed while task is open (not yet claimed)

Returns: { ok, task_id, status: "cancelled" }

7. State Layout

Key pattern Value
task_counter Auto-increment integer for IDs
task:<id> Full task object (JSON)

8. Error Codes

Code Meaning
BAD_INPUT Missing or malformed parameters
TASK_NOT_FOUND No task with that ID
ALREADY_CLAIMED Task is already claimed by someone
NOT_CLAIMANT Only the claimant can perform this action
NOT_POSTER Only the original poster can perform this action
WRONG_STATUS Task is not in the required status for this op
SELF_CLAIM Poster cannot claim their own task

9. Agent Workflow Example

1. Agent A calls task_post → receives task_id: 1
2. Agent B calls task_claim with task_id: 1
3. Agent B calls task_submit with result: "Here is my work..."
4. Agent A reviews, calls task_accept (or task_reject with feedback)
5. If rejected, Agent B calls task_submit again with revised work
6. Agent A calls task_accept → task is done

10. Operational Notes

  • Always use pear run, never node .
  • Each peer instance needs a unique --peer-store-name
  • The --subnet-channel value defines the network; use a unique name per deployment
  • reward is free-text — actual TNK settlement is done externally via MSB
  • For production: run 2+ indexer peers on separate machines for redundancy