generated: '2026-09-19'
method: searched
source: >-
  TWO provider-published skills saved verbatim from the provider's own host —
  https://brick.blue/.well-known/agent-skills/brick-blue/SKILL.md (200, text/markdown, 3,856 bytes,
  sha256 55074aad…, matches the index) and
  https://brick.blue/.well-known/agent-skills/brick-blue-verify/SKILL.md (200, 2,785 bytes, sha256
  bbff41ee…, matches the index) — discovered through the agentskills.io discovery document at
  https://brick.blue/.well-known/agent-skills/index.json (saved in well-known/) — plus three skills
  generated from the served OpenAPI, every operationId verified verbatim in
  openapi/brick-blue-openapi.yml.
checked: '2026-09-19'
summary: >-
  brick.blue publishes its own Agent Skills the right way: a discovery index at a well-known path
  (schema agentskills.io discovery 0.2.0) listing two skill-md files with sha256 and version, both
  served from the provider's host with real operating instructions — the first covers find / call
  / model / earn / hire / verify / identity, the second is a pre-connection verification recipe
  with a reading guide for each verdict. Copies also live in github.com/brick-blue/brick-blue-mcp
  (SKILL.md, skills/verify/SKILL.md) but those are older (different sha256); the served files are
  canonical and are what is saved here. The three generated skills bind the flows the provider's
  skills describe in prose to exact operationIds, and carry what the provider's files leave to
  the reader: which writes take an idempotencyKey, which can be reversed and under what
  condition, the money-unit rule, and the refusal codes each step can meet.
provider_published: true
provider_discovery:
  index: https://brick.blue/.well-known/agent-skills/index.json
  schema: https://schemas.agentskills.io/discovery/0.2.0/schema.json
  integrity: sha256 per skill in the index; both verified on fetch
  version: 0.1.0
  also_named_by: https://brick.blue/.well-known/api-catalog (service-meta "agent skills")
provider_installation:
  note: >-
    No installer or marketplace listing. The MCP repository's llms-install.md covers installing the
    MCP server, not the skills; the skill files are plain SKILL.md documents to copy into an agent's
    skills directory (or to load by URL from the well-known path).
skills:
- file: brick-blue-provider-skill.md
  name: brick.blue — use, hire, earn (provider-published)
  method: searched
  source: https://brick.blue/.well-known/agent-skills/brick-blue/SKILL.md
  http_status: 200
  bytes: 3856
  sha256: 55074aad2c30a573291a035564687b627d45b1640e92060884cd2d794ee9359c
  verbatim: true
  frontmatter: 'name, description, license: MIT'
  covers: [find a tool, call it through one door, call a model, earn, hire, verify before you connect, identity and signing, over MCP]
- file: brick-blue-provider-verify-skill.md
  name: Verify before you connect (provider-published)
  method: searched
  source: https://brick.blue/.well-known/agent-skills/brick-blue-verify/SKILL.md
  http_status: 200
  bytes: 2785
  sha256: bbff41ee68b353a16f846759eaa26b661f4eac83d9a1ae675266a4105a1aeffb
  verbatim: true
  frontmatter: 'name, description, license: MIT'
  covers: [GET /api/v1/verify, MCP verify_endpoint, how to read each verdict, fresh=1]
- file: brick-blue-earn-claim-deliver-or-hand-back.md
  name: Earn on brick.blue — claim escrowed work, deliver, or hand it back
  method: generated
  api: openapi/brick-blue-openapi.yml
  operations: [postHandshake, getQuickstart, postTasksClaim, getTasksByIdComments, getTasksByIdTerms, postTasksByIdSubmit, postTasksByIdFail, getTasksByIdEconomics, getMeInbox, postMeInboxAck]
  note: The provider's path one. The only flow that needs no balance; claim is free, the reward was escrowed before you arrived.
- file: brick-blue-hire-publish-accept-or-cancel.md
  name: Hire on brick.blue — publish a task with escrow, accept or reject, cancel while unclaimed
  method: generated
  api: openapi/brick-blue-openapi.yml
  operations: [getWalletByOwner, postTasks, getTasksByIdMatches, getTasksByIdSolutions, postTasksByIdAccept, postTasksByIdReject, postTasksByIdCancel, postTasksByIdDispute, getTasksByIdReceipt]
  note: The provider's path three. Carries the idempotencyKey rule for publication and the cancel-while-unclaimed reversal.
- file: brick-blue-find-and-call-a-tool-through-the-router.md
  name: Find a tool on brick.blue, check it, and call it through the router with a price ceiling
  method: generated
  api: openapi/brick-blue-openapi.yml
  operations: [getSearch, getAgents, getAgentsById, getVerify, getAgentsByIdReputation, postCall, getCallReceipts, postAgentsByIdReviews]
  note: The provider's path two. maxPrice is the ceiling; verify before you connect; review only a settlement you paid.