agentleFS
Colab8Colab8/rosetta-plugin/skills/comply/SKILL.md

comply

Skill0 starsChanged 8 months agoMITView on GitHub

Run full import compliance analysis — classify, duty, PGA, entry type, and declaration readiness in one shot using AskRosetta. Use for end-to-end import analysis.

  • Reads credentials
  • Sends data out
  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the complete AskRosetta pipeline: HTS classification, duty calculation, PGA screening, entry type recommendation, and declaration …

    line 9
  2. Very specific:

    Use the analyze_product MCP tool, or call the quote endpoint:

    line 19

≈ “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

Full Compliance Analysis

Run the complete AskRosetta pipeline: HTS classification, duty calculation, PGA screening, entry type recommendation, and declaration readiness — all in one pass.

When to Use

  • User asks "how much will it cost to import X?"
  • User wants a complete compliance picture
  • User is preparing for a specific shipment

How It Works

Use the analyze_product MCP tool, or call the quote endpoint:

curl -s -X POST "https://api.askrosetta.ai/api/v1/quote" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: ${ASKROSETTA_API_KEY}" \
  -d '{
    "products": [{
      "description": "<description>",
      "country_of_origin": "<country>",
      "unit_value": <number>,
      "quantity": <number>
    }],
    "shipping_method": "<ocean|air|truck>"
  }'

Response Format

Present as a structured compliance report:


COMPLIANCE REPORT

1. Classification

  • HTS: XXXX.XX.XXXX — Description
  • Confidence: XX%

2. Duty & Fees

ComponentAmount
Base Duty$XXX.XX
Section 301$XXX.XX
MPF$XX.XX
HMF$XX.XX
Landed Cost$X,XXX.XX

3. PGA Requirements

  • FDA: Required / Not required
  • EPA: Required / Not required

4. Entry Type

  • Recommended: Type XX — Informal/Formal
  • Bond required: Yes/No
  • Broker required: Yes/No

Important

This is intelligence, not legal advice. For actual customs filing, the user must work with a licensed customs broker.

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.