agentleFS
deciqAIdeciqAI/knowledge-skills/customs-reasonable-care-isf-checklist/SKILL.md

customs-reasonable-care-isf-checklist

Skill13 starsChanged 4 months agoMITView on GitHub

Activate when: filing an entry or ISF; onboarding an importer (POA); building the compliance file; 'did we file ISF in time?', 'is our reasonable-care record complete?'. Do NOT activate when: the shipment is exempt and no entry/ISF is required. More: deciqai.com/s/customs-reasonable-care-isf-checklist

The file

Files
SKILL.md

Customs — Reasonable Care & ISF Compliance Checklist

Industry front door for checklist. Adds domain triggers, example, packs only. Parent Process unchanged. Not legal advice. Verify against current 19 CFR and CBP guidance.

Activate when: filing an entry or ISF; onboarding an importer (POA); building the compliance file; "did we file ISF in time?", "is our reasonable-care record complete?" Do NOT activate when: the shipment is exempt and no entry/ISF is required.

Why this variant

The parent checklist is a verifiable gate. Customs entry is a reasonable-care obligation with hard filing clocks (ISF) and 5-year recordkeeping. This maps those duties onto the parent's gate.

Domain inputs → parent's gate

  • ISF (10+2): importer security filing transmitted no later than 24 hours before lading (ocean); update as info changes.
  • Entry data: classification, valuation, origin, quantity — each supported and documented (reasonable care).
  • POA: valid power of attorney + importer identity (KYC) on file.
  • PGA: any FDA/USDA/EPA/other agency data flagged and filed.
  • Recordkeeping: entry records retained 5 years from date of entry.

Worked example

New importer, ocean shipment, mixed goods, one FDA-regulated item. → Gate: ISF must transmit ≥24h pre-lading (late = liquidated damages up to $5k/violation); the FDA item needs prior notice + PGA data; POA + reasonable-care file must exist before entry. Any gap = do not file until cleared.

Compliance anchors

  • 19 CFR 149 (ISF); 19 U.S.C. 1484/1485 reasonable care; 19 CFR 163 recordkeeping (5 yrs); PGA requirements.

Packs

  • Solo broker: per-importer compliance folder template.
  • Brokerage: ISF timing alerts into the deadline engine; PGA triage.

Red flags

  • ISF filed inside the 24-hour window.
  • Valuation/classification with no supporting record.
  • PGA-regulated goods entered without agency data.

Verification

  • ISF transmitted ≥24h before lading; updated on change
  • Entry data supported & documented (reasonable care)
  • Valid POA + importer KYC on file
  • PGA requirements identified and met
  • 5-year recordkeeping started

Part of deciqAI Knowledge Skills. Core method: checklist.


Part of deciqAI Knowledge Skills — 253 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. See it run → https://www.deciqai.com/s/customs-reasonable-care-isf-checklist · Built by deciqAI · github.com/deciqAI · Contributions welcome.

Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/customs-reasonable-care-isf-checklist.json

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.