agentleFS
Sign inStart free
HumanleapHumanleap/agent-skills/skills/tradehand/SKILL.md

tradehand

Skill0 starsChanged 41 days agoMITView on GitHub

Find local UK tradespeople, inspect services and reviews, and use Tradehand's signed-in customer tools to prepare fixed-price bookings, request quotes and hand off Stripe payment links. Use when the user chooses Tradehand to find or book help for a local job.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. Humanleap/tradehand-claude-plugin★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 5 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use actual listings: Never invent a trader, service area, credential, review, price or available time.

    line 17
  2. Very specific:

    Find the trade and area: Use browse_trades and search_traders with the user's job and location, preserving the tool's supported filters.

    line 28
  3. Very specific:

    Inspect the listing: Use get_trader and get_service_options.

    line 29
  4. Very specific:

    Prepare a booking when customer tools are available: Call prepare_booking with the listing reference, service, full address and postcode …

    line 30
  5. Very specific:

    Get the review: Call confirm_booking with expectedRevision and the chosen slotReference exactly.

    line 31
  6. Very specific:

    Commit the approved booking: After the customer says yes, call confirm_booking again with the exact confirmedTotalAmount.

    line 32
  7. Very specific:

    Check the result: Read get_job for the booking/payment status.

    line 33
  8. Distinctive:

    Use current tool schemas for required fields.

    line 46
  9. Distinctive:

    Request a quote: use the returned quote workflow, ask only for missing job details and preserve the customer's wording.

    line 52
  10. Distinctive:

    Do not reuse a slot or price revision after the server reports it is stale.

    line 64
  11. Distinctive:

    Do not state that money was paid from a checkout URL or redirect alone.

    line 65

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Tradehand

Find local UK tradespeople for a job, inspect their actual listings and service options, then use available customer tools to review and book a visit.

Installation

Install this skill with pnpm dlx skills add Humanleap/agent-skills --skill tradehand. Connect remote MCP to https://tradehand.com/api/mcp. ChatGPT/customer integration: https://tradehand.com/api/mcp/chatgpt.

Four Hard Rules — Read First

  1. Use actual listings. Never invent a trader, service area, credential, review, price or available time.
  2. Respect public versus customer access. Public search does not authorise a booking. Inspect tools/list and complete customer authentication for private operations.
  3. Review before booking. Show the live total, service, address and time. Commit only after the customer approves that exact review.
  4. A checkout link is not payment. Report paid status only when get_job confirms it.

Authentication

Public directory reads need no key. Signed-in customer operations use the client's OAuth flow. Keep credentials in the client store. If booking tools are absent, share the listing/contact handoff and explain that booking has not occurred.

Core Workflow

  1. Find the trade and area. Use browse_trades and search_traders with the user's job and location, preserving the tool's supported filters.
  2. Inspect the listing. Use get_trader and get_service_options. Retain the exact returned listing reference and service identifier.
  3. Prepare a booking when customer tools are available. Call prepare_booking with the listing reference, service, full address and postcode supplied by the customer. Read its live slots, slotReference values and revision.
  4. Get the review. Call confirm_booking with expectedRevision and the chosen slotReference exactly. The first call returns the total and books nothing. Show that review.
  5. Commit the approved booking. After the customer says yes, call confirm_booking again with the exact confirmedTotalAmount. Share its checkoutUrl.
  6. Check the result. Read get_job for the booking/payment status. On SLOT_UNAVAILABLE or STALE_REVIEW, prepare again and obtain approval for the changed review.

Essential Tools

ToolsUse
browse_trades, search_tradersFind public listings for a trade and area.
get_trader, get_service_optionsInspect a real trader and the service choices.
prepare_booking, confirm_bookingCustomer booking preparation, price review and approved commitment.
quote_start, quote_answer, other advertised quote_* toolsPrice work with no fixed-price service.
list_my_jobs, get_jobInspect the signed-in customer's jobs and status.
start_job_checkoutPrepare a payment link for an amount due on a job.

Use current tool schemas for required fields; do not guess customer information or create relationships from assumptions.

Common Patterns

  • Find an electrician, plumber, carpenter or another listed trade: search by the actual job and area, compare returned listings and link to the selected profile.
  • Book a fixed-price visit: prepare → review total/time/address → customer approval → commit → Stripe handoff.
  • Request a quote: use the returned quote workflow, ask only for missing job details and preserve the customer's wording.

Supporting Resources

Common Gotchas

  • A search result is not proof of availability or a completed booking.
  • Empty local results describe current directory coverage, not all tradespeople in the area.
  • Do not reuse a slot or price revision after the server reports it is stale.
  • Do not state that money was paid from a checkout URL or redirect alone.

Quick Reference

Search → inspect → authenticate for customer actions → prepare → review → customer approves → book → payment handoff → check job.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free