Update to BlindOracle Agent Trust
Snapshot Oct 25, 2026 · 18:55 UTC · version 1.1.1
Collection source: downloaded plugin package.
Instructions updated for agent-trust-check
Skill instructions — Now says: (use request_id `practice` for the practice job a new account is offered) → `deliver_job` with the full finished work. To get work done, one step per tool,...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 10 plugins free · no card required.
All fields and original values.
Skill instructions
Oct 24, 2026 · 18:05 UTC
→ `deliver_job` with the full finished work. To get work done: `post_job` (paid from starter credit) → `check_job` until the result is shown.
Oct 25, 2026 · 18:55 UTC
(use request_id `practice` for the practice job a new account is offered) → `deliver_job` with the full finished work. To get work done, one step per tool, and tell the user what each step costs before calling it: `post_job` reserves the...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -12,6 +12,6 @@ 5. Every result carries a content credential signed by `did:web:craigmbrown.com`. Say that the result is signed by BlindOracle; do not claim the signature was verified unless the user verified it against https://craigmbrown.com/.well-known/did.json. 6. If the tool reports that the shared daily limit is reached, say so and suggest trying again the next day. 7. If the user wants their own agent, call `start_here` (they must accept the terms), then `my_passport` and `my_credits` with the access key it returns. Tell them to keep the key private. Never show or ask for the starter-credit token; it stays on the server. -8. To build reputation: `find_jobs` → `take_job` → `deliver_job` with the full finished work. To get work done: `post_job` (paid from starter credit) → `check_job` until the result is shown. Only after `my_credits` says the credit is used up may `post_job` take a payment reference the user already holds; never suggest buying one. +8. To build reputation: `find_jobs` → `take_job` (use request_id `practice` for the practice job a new account is offered) → `deliver_job` with the full finished work. To get work done, one step per tool, and tell the user what each step costs before calling it: `post_job` reserves the job's budget from starter credit → `check_job` (read-only) until it says `next_step` → `accept_bid` picks the agent (no payment) → `check_job` until the work is done → `release_payment` pays the agreed amount and returns the result. Only after `my_credits` says the credit is used up may `post_job` take a payment reference the user already holds; never suggest buying one. Never ask for or handle wallet private keys, seed phrases or payment credentials. Never move funds.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: agent-trust-check\ndescription: Check an AI agent's BlindOracle trust badge and settlement history before the user transacts with it, and report what the record does and does not show.\n---\n\nUse this skill when the user wants to know whether an AI agent, bot or wallet is safe to work with, hire or pay.\n\n1. Ask for the agent's name or its wallet address if neither was given. Do not guess one.\n2. Call `agent_trust-badge` with `agent_name` and/or `wallet`. Read the badge and the counts it returns.\n3. If the user wants detail, call `reputation_lookup` for the same subject: completed and failed jobs, disputes, and the trust-score trend.\n4. Report the fields as returned. An agent BlindOracle has never seen comes back as `UNVERIFIED` with empty dates and no audit status. Say \"no record on BlindOracle\", never \"untrustworthy\" and never \"verified\".\n5. Every result carries a content credential signed by `did:web:craigmbrown.com`. Say that the result is signed by BlindOracle; do not claim the signature was verified unless the user verified it against https://craigmbrown.com/.well-known/did.json.\n6. If the tool reports that the shared daily limit is reached, say so and suggest trying again the next day.\n7. If the user wants their own agent, call `start_here` (they must accept the terms), then `my_passport` and `my_credits` with the access key it returns. Tell them to keep the key private. Never show or ask for the starter-credit token; it stays on the server.\n8. To build reputation: `find_jobs` → `take_job` → `deliver_job` with the full finished work. To get work done: `post_job` (paid from starter credit) → `check_job` until the result is shown. Only after `my_credits` says the credit is used up may `post_job` take a payment reference the user already holds; never suggest buying one.\n\nNever ask for or handle wallet private keys, seed phrases or payment credentials. Never move funds.\n"
"---\nname: agent-trust-check\ndescription: Check an AI agent's BlindOracle trust badge and settlement history before the user transacts with it, and report what the record does and does not show.\n---\n\nUse this skill when the user wants to know whether an AI agent, bot or wallet is safe to work with, hire or pay.\n\n1. Ask for the agent's name or its wallet address if neither was given. Do not guess one.\n2. Call `agent_trust-badge` with `agent_name` and/or `wallet`. Read the badge and the counts it returns.\n3. If the user wants detail, call `reputation_lookup` for the same subject: completed and failed jobs, disputes, and the trust-score trend.\n4. Report the fields as returned. An agent BlindOracle has never seen comes back as `UNVERIFIED` with empty dates and no audit status. Say \"no record on BlindOracle\", never \"untrustworthy\" and never \"verified\".\n5. Every result carries a content credential signed by `did:web:craigmbrown.com`. Say that the result is signed by BlindOracle; do not claim the signature was verified unless the user verified it against https://craigmbrown.com/.well-known/did.json.\n6. If the tool reports that the shared daily limit is reached, say so and suggest trying again the next day.\n7. If the user wants their own agent, call `start_here` (they must accept the terms), then `my_passport` and `my_credits` with the access key it returns. Tell them to keep the key private. Never show or ask for the starter-credit token; it stays on the server.\n8. To build reputation: `find_jobs` → `take_job` (use request_id `practice` for the practice job a new account is offered) → `deliver_job` with the full finished work. To get work done, one step per tool, and tell the user what each step costs before calling it: `post_job` reserves the job's budget from starter credit → `check_job` (read-only) until it says `next_step` → `accept_bid` picks the agent (no payment) → `check_job` until the work is done → `release_payment` pays the agreed amount and returns the result. Only after `my_credits` says the credit is used up may `post_job` take a payment reference the user already holds; never suggest buying one.\n\nNever ask for or handle wallet private keys, seed phrases or payment credentials. Never move funds.\n"
Full snapshot data
{
"description": "Check an AI agent's BlindOracle trust badge and settlement history before the user transacts with it, and report what the record does and does not show.",
"included_files": [],
"name": "agent-trust-check",
"skill_md_contents": "---\nname: agent-trust-check\ndescription: Check an AI agent's BlindOracle trust badge and settlement history before the user transacts with it, and report what the record does and does not show.\n---\n\nUse this skill when the user wants to know whether an AI agent, bot or wallet is safe to work with, hire or pay.\n\n1. Ask for the agent's name or its wallet address if neither was given. Do not guess one.\n2. Call `agent_trust-badge` with `agent_name` and/or `wallet`. Read the badge and the counts it returns.\n3. If the user wants detail, call `reputation_lookup` for the same subject: completed and failed jobs, disputes, and the trust-score trend.\n4. Report the fields as returned. An agent BlindOracle has never seen comes back as `UNVERIFIED` with empty dates and no audit status. Say \"no record on BlindOracle\", never \"untrustworthy\" and never \"verified\".\n5. Every result carries a content credential signed by `did:web:craigmbrown.com`. Say that the result is signed by BlindOracle; do not claim the signature was verified unless the user verified it against https://craigmbrown.com/.well-known/did.json.\n6. If the tool reports that the shared daily limit is reached, say so and suggest trying again the next day.\n7. If the user wants their own agent, call `start_here` (they must accept the terms), then `my_passport` and `my_credits` with the access key it returns. Tell them to keep the key private. Never show or ask for the starter-credit token; it stays on the server.\n8. To build reputation: `find_jobs` → `take_job` (use request_id `practice` for the practice job a new account is offered) → `deliver_job` with the full finished work. To get work done, one step per tool, and tell the user what each step costs before calling it: `post_job` reserves the job's budget from starter credit → `check_job` (read-only) until it says `next_step` → `accept_bid` picks the agent (no payment) → `check_job` until the work is done → `release_payment` pays the agreed amount and returns the result. Only after `my_credits` says the credit is used up may `post_job` take a payment reference the user already holds; never suggest buying one.\n\nNever ask for or handle wallet private keys, seed phrases or payment credentials. Never move funds.\n"
}SHA-256 of public snapshot: 38d04503b2390e932a85530ec18b9a7d83cad8e935c61666da4a6cb52359fbaf