Skip to main content 首页 创作者 thomasmoreai legal-skills-open ctpat-security-profile
ctpat-security-profile Drafts a submission-ready C-TPAT Security Profile from verified company records for U.S. CBP enrollment, recertification, or validation prep. Use when preparing security profiles for importers, brokers, freight forwarders, or logistics participants. Trigger keywords: C-TPAT, CTPAT, CBP, security profile, customs compliance, validation visit, revalidation.
跳到安装 Skills Marketplace 发现并探索由社区构建的 Agent Skills
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ThomasMoreAI/legal-skills-open --skill ctpat-security-profile命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
下载 Zip 下载中... 同仓库更多 Skills fetching-arbitration-rules Use when retrieving arbitration institutional rules (ICC, LCIA, SCC, SIAC, HKIAC, VIAC, МКАС/МАК при ТПП України, UNCITRAL) — fetching current version, verifying redaction applicable to the date of arbitration agreement, constructing URLs for official rule texts
determining-pl-request-regime Use when choosing the Polish legal regime for letters, requests, applications, complaints, petitions, public-information requests, KPA filings, PPSA complaints, RODO access requests, registry extracts, court-file access, tax/ZUS/cudzoziemcy/USC procedures, or professional lawyer letters. Prevents mixing UDIP, KPA, PPSA, RODO, registry, special-procedure, and advocate/radca letter regimes.
applying-new-york-convention Use when preparing applications for recognition and enforcement of foreign arbitral awards in Poland, applications for setting aside arbitral awards under KPC art. 1205–1211, or opposing such applications — mapping Article V of the 1958 New York Convention to art. 1214–1215 of the Polish KPC, identifying grounds for refusal, structuring public policy arguments
name ctpat-security-profile title C-TPAT Security Profile description Drafts a submission-ready C-TPAT Security Profile from verified company records for U.S. CBP enrollment, recertification, or validation prep. Use when preparing security profiles for importers, brokers, freight forwarders, or logistics participants. Trigger keywords: C-TPAT, CTPAT, CBP, security profile, customs compliance, validation visit, revalidation. author CaseMark author_url https://github.com/CaseMark/skills/tree/main/skills/legal/ctpat-security-profile license Apache-2.0 version 0.1.0 execution_mode open jurisdiction us practice trade language en tags ["drafting","memo"]
C-TPAT Security Profile
Produces an evidence-based C-TPAT profile draft aligned to U.S. CBP minimum security criteria, mapped directly to company operations and source documents.
Quick Start
Collect governing docs (policies, SOPs, audits, training records, partner questionnaires).
Confirm corporate identifiers (legal name, EIN, DUNS, C-TPAT account number, facility addresses).
Gather operations data (importer role, volumes, countries/lanes, supply chain map).
Gather security evidence per module (physical, personnel, cargo, conveyance, IT, business partner).
Set document version baseline and submission target date.
Core Workflow
Validate inputs — verify each factual claim against source documents.Identify gaps — emit a Gap Register before drafting if required facts are missing.Draft sections — populate all 13 mandatory sections (see below).Crosswalk compliance — map each company control → C-TPAT minimum → supporting evidence.Quality check — scan for accuracy, contradictions, completeness, and CBP-appropriate tone.
Intake Matrix
Domain Evidence Needed Maps To Eligibility Import role, volume, facilities, prior tier Intro + jurisdiction Governance Security leadership, reporting lines, budget Org framework Risk methodology Assessment cadence, criteria, data sources Risk assessment Physical controls Access, surveillance, lighting, alarms, patrols Physical security Personnel Screening, onboarding, training, revocations Personnel security Procedural Partner due diligence, custody chain, inspections Business-partner security Conveyance Carrier vetting, 7-point inspections, seals, transit Conveyance/cargo integrity IT MFA, segmentation, patching, incident response IT security Compliance Self-assessments, corrective actions, validation prep Continuous improvement
Mandatory Sections
Cover Page — company info, title, version, date, preparer
Profile Summary — tier objective, participation status, confidence level
Organizational Framework
Risk Assessment
Physical Security
Personnel Security
Procedural / Business-Partner Security
Conveyance and Cargo Integrity
Information Technology Security
Recordkeeping and Compliance Management
Self-Assessment and Corrective Action Register
Validation Readiness
Appendix Index and Signature Statement
Section Template Each security module section follows this structure:
Current Practice — fact-based descriptionControls in place — specific measuresEvidence references — document name + dateGaps and residual risks Planned improvements — owner assignedStatus : Compliant / Partially Compliant / Non-Compliant
Specialized Records Seven-Point Inspection Log (per container/trailer): Unit ID, date/time, inspector, front wall, left side, right side, floor, ceiling/roof, doors inside/out, undercarriage, anomalies + photos + corrective actions.
Seal Control Register : Seal number, vendor/standard, issuance date, assigned shipment, installation point, receipt verification, discrepancy response, disposition.
Corrective Action Plan : Finding, control owner, corrective action, deadline, verification method, status.
Pitfalls and Checks
Use only verifiable facts from provided records — never invent documents, certifications, or findings.
Every claim requires a source pointer (policy, SOP, log, audit report, contract, training record).
Use exact terms from company records for titles, systems, equipment, and locations.
Mark uncertain regulatory specifics with [VERIFY] for human confirmation.
Enforce 7-point inspection checks and ISO 17712 high-security seal handling.
Default to U.S.-only CBP scope unless user provides multinational authority requirements [VERIFY].
Final output must be validator-ready: consistent cross-references, indexed exhibits, revision control.
