← SendaCONTENT HISTORY

Update to Senda

Snapshot Oct 24, 2026 · 13:47 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Senda and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Suggest HS codes for a product with Senda's find_hs_codes tool, and present them as suggestions to confirm with a licensed customs broker. Use when the user asks for an HS code, an HTS number, a tariff heading or \"what code does this fall under\", or describes a product they import or export and wants its classification.",
  "included_files": [],
  "name": "hs-code-suggestions",
  "skill_md_contents": "---\nname: hs-code-suggestions\ndescription: Suggest HS codes for a product with Senda's find_hs_codes tool, and present them as suggestions to confirm with a licensed customs broker. Use when the user asks for an HS code, an HTS number, a tariff heading or \"what code does this fall under\", or describes a product they import or export and wants its classification.\n---\n\n# HS code suggestions with Senda\n\n`find_hs_codes` suggests up to eight 6-digit HS subheadings for a product\ndescribed in plain words, most likely first. It names the US tariff schedule\nrevision it checked them against and returns a disclaimer. It reads none of\nthe user's records.\n\n## How to ask\n\n- Describe **what the product is and what it is made of**, in 3 to 200\n  characters: \"kiln-dried white oak lumber\", \"hyaluronic acid serum in glass\n  dropper bottles\". If the user's description is vague (\"wood\", \"parts\"),\n  ask what it is, what it is made of and what it is for before calling.\n- One product per call. For several products, call once for each.\n\n## How to answer\n\n- Show the top few suggestions with their 6-digit code and description, most\n  likely first, and name the tariff schedule revision the tool returned.\n- **Always say these are suggestions, not a classification**, and that the\n  user should confirm the code with a licensed customs broker. Include the\n  disclaimer the tool returned, in your own words if it reads better.\n- Use only codes the tool returned. Never invent a code, extend one to 8 or\n  10 digits, or state a duty rate: the full US HTS number, the duty and any\n  additional duties depend on details only a classification settles.\n- Don't add a confidence score or an accuracy figure. The tool gives none.\n- **No candidates** means no confident match. Say so, ask for more detail\n  (material, use, how it is processed), or suggest asking a broker. Don't\n  guess.\n\n## Binding classifications\n\nIf the user wants a binding or final classification (\"the code to put on my\nentry\", \"a ruling\"), say you can't provide one. Offer the suggestions as a\nstarting point, and point them to a licensed customs broker. In the US, a\nbinding ruling comes from US Customs and Border Protection.\n\n## Example\n\n\"Suggest an HS code for kiln-dried white oak lumber\" → `find_hs_codes` →\n\"Senda suggests **4407.91** (oak, sawn or chipped lengthwise, of a thickness\nexceeding 6 mm) as the most likely subheading, then 4407.99 and other\n4407 subheadings, checked against the US tariff schedule revision it names.\nThese are suggestions to confirm with a licensed customs broker, not a\nclassification.\"\n"
}

SHA-256 of public snapshot: a07ef5db3a3672e8d601d1bb5f0983b73b49a36b943625c795859ef8fff501ed