hs-classification-workflow
Guides the HS Classification Specialist through GRI-ordered Harmonized System classification, customs valuation basis determination, and tariff rate lookup. Ensures classification reasoning is reproducible and defensible under a customs post-clearance audit.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-14
- Stars
- ★ 25
- Forks
- 9
01 前言 Front Matter
- name
- hs-classification-workflow
- owner
- hs-classification-specialist
- scope
- co-export
- status
- active
- version
- 1.0.1
- relates_to
- [ { "type": "follows", "skill": "roo-qualification-worksheet" }, { "type": "follows", "skill": "fta-origin-determination" }, { "type": "composes_with", "skill": "trade-documentation-checklist" }, { "type": "composes_with", "skill": "logistics-coordination" }, { "type": "composes_with", "skill": "market-entry-strategy" }, { "type": "composes_with", "skill": "landed-cost-calculation" } ]
- description
- Guides the HS Classification Specialist through GRI-ordered Harmonized System classification, customs valuation basis determination, and tariff rate lookup. Ensures classification reasoning is reproducible and defensible under a customs post-clearance audit.
- last_reviewed
- 1787616000000
- prerequisites
- none
03 SKILL.md 正文
Context
Use at the start of Phase 1 whenever a shipment's HS code is not already confirmed. Every downstream compliance step (FTA origin analysis, export control screening, tariff cost calculation) depends on this classification, so treat it as the engagement's foundational input.
When to Use
- New product or product variant requiring HS classification
- Existing classification needs re-verification after a product spec change
- Client disputes a prior classification or a customs authority raises a query
- Customs valuation basis needs to be established alongside classification
Prerequisites
- Confirmed product description and technical specifications from the client
- Access to the home jurisdiction's HS nomenclature at tariff-line depth (KR: Korea Customs Service HSK)
- Prior customs ruling database access (if available for precedent research)
- A tariff-dataset snapshot conforming to
docs/tariff-dataset-schema.jsonfor the home jurisdiction (or portal access as fallback; see the schema doc's Consumption section)
Execution Steps
- Gather Product Facts: Collect full product description, materials/composition, function, how it is marketed/sold, and packaging — classification depends on objective characteristics, not the client's preferred outcome.
- Apply GRI in Strict Order:
- GRI 1: Match against heading text and section/chapter notes first
- GRI 2: Consider incomplete/unassembled goods and mixtures if GRI 1 doesn't resolve it
- GRI 3(a)/3(b)/3(c): Apply only if multiple headings appear equally applicable
- GRI 4–6: Apply only for genuinely novel goods or subheading-level disputes
- Never skip ahead to a later GRI rule without documenting why the earlier rule didn't resolve the classification
- Search Ruling Precedent: Check prior customs-authority advance rulings (KR: Korea Customs Service) and authoritative interpretations for materially similar products before finalizing.
- Determine Customs Valuation Basis: Identify the applicable valuation method (transaction value, or fallback methods in the Customs Act Article 30 order) and flag related-party pricing.
- Confidence Rating: Classify the result as confirmed / probable (recommend advance ruling) / contested — never present a probable classification as certain.
- Tariff Rate Lookup: Identify the applicable home-jurisdiction tariff rate and, if relevant, the
destination-country rate (cross-reference
foreign-regulatory-intelligence-analystfindings). Consult the home jurisdiction's tariff-dataset snapshot (schema:docs/tariff-dataset-schema.json) before portal lookup; recordcaptured_atandsource_refof the rate used in the output for audit reproducibility. - Handoff: Pass the confirmed HS code to
fta-origin-analyst(origin rules are HS-specific) and toexport-control-compliance-specialistif the classification falls in a strategic-items-adjacent chapter.
Output Format
- Classification report: candidate HS headings considered, GRI reasoning chain, final HS code code, confidence level, customs valuation basis, applicable tariff rate(s), cited prior rulings
Quality Criteria
- [ ] HS heading and subheading cited with exact text from the nomenclature
- [ ] GRI reasoning chain documented in order (GRI 1 → 2 → 3 → ... as applicable)
- [ ] Confidence level stated explicitly (confirmed / probable / contested)
- [ ] Prior ruling precedent checked and referenced (or noted as unavailable)
- [ ] Ambiguity escalation recommended when multiple plausible headings exist
Related Skills
- fta-origin-determination
- export-control-screening
04 同仓库更多 Skills
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.