pga
Skill0 starsChanged 8 months agoMITView on GitHub
Screen products for FDA, EPA, USDA, CPSC, FCC, and other government agency requirements using AskRosetta. Use when checking regulatory compliance for US imports.
- Reads credentials
- Sends data out
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Very specific: line 19
Use the determine_pga_requirements MCP tool with the product description.
- Distinctive: line 21
If MCP is unavailable:
- Distinctive: line 47
Always include CFR citations — users need them for compliance records.
- Distinctive: line 49
If no agencies are flagged, confirm the product appears exempt but recommend verifying with a licensed customs broker for high-value or …
≈ “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.
Files
PGA Screening
Determine which US Partner Government Agencies (PGA) require clearance for an imported product. Screens FDA, EPA, USDA, CPSC, FCC, ATF, DOT, and others — with specific CFR regulation citations.
When to Use
- User asks "does X need FDA approval?"
- User wants to know regulatory requirements for an import
- User is checking if a product needs special permits or testing
How It Works
Use the determine_pga_requirements MCP tool with the product description.
If MCP is unavailable:
curl -s -X POST "https://api.askrosetta.ai/api/v1/pga" \
-H "Content-Type: application/json" \
-H "X-API-Key: ${ASKROSETTA_API_KEY}" \
-d '{
"product_description": "<description>",
"hts_code": "<if known>",
"intended_use": "<if specified>"
}'Response Format
PGA Screening Result
- Requires PGA clearance: Yes/No
- Agencies:
- FDA — Prior Notice required (21 CFR 1.276), product registration
- EPA — TSCA certification (15 USC 2601)
- CPSC — Testing required (16 CFR 1500)
- (etc.)
- Risk Level: Low / Medium / High / Critical
- Warnings: any holds or flags
Always include CFR citations — users need them for compliance records.
If no agencies are flagged, confirm the product appears exempt but recommend verifying with a licensed customs broker for high-value or novel product shipments.
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
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.

