Agent skill · Design & Presentation

immigration-document-checklist

Organise the document pile for a visa, work-permit, or residency application — what to gather, in what order, and the common rejection triggers to avoid. Use when asked to help with a visa application, build an immigration document checklist, prepare paperwork for a work permit or green card, or organise what an application needs. Produces the categorised document checklist, the gather-in-this-order plan, the common-mistake/rejection-trigger list, and the professional-help flags. Organises the paperwork; complements the visa-interview simulator.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill immigration-document-checklist --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/immigration-document-checklist/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Immigration Document Checklist Immigration applications are rejected more often for a missing translation or an inconsistent date than for the actual merits — and the sheer document pile is where people freeze. This turns it into an ordered, categorised checklist: what's required, what proves each thing, the order that avoids expiry problems, and the small mistakes that trigger rejections — so the paperwork stops being the obstacle. > Not legal advice. Immigration rules are country- and case-specific and change often — this organises the process and flags where an immigration lawyer is needed; always verify requirements against the official source for your case. ## What This Skill Produces - **The categorised checklist** — identity, financial, employment, relationship, medical, legal — with what document satisfies each - **The gather order** — what to request first (slow items like police certificates, apostilles, translations) so nothing expires waiting - **The rejection-trigger list** — the common avoidable mistakes (inconsistent names/dates, expired docs, missing translations, wrong format) - **Professional-help flags** — where a lawyer is worth it (prior refusals, complex his

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: Paperwork That Doesn't Get Rejected
  4. Output Format
  5. [Visa/permit] Document Checklist — [destination] · citizen of [country]
  6. Documents by category
  7. Gather in this order
  8. Common rejection triggers — check before submitting
  9. See an immigration lawyer if
  10. Quality Checks
  11. Anti-Patterns
  12. Example Trigger Phrases
More from pm-claude-skills
All skills →
About this skill
What does the immigration-document-checklist skill do?

Organise the document pile for a visa, work-permit, or residency application — what to gather, in what order, and the common rejection triggers to avoid. Use when asked to help with a visa application, build an immigration document checklist, prepare paperwork for a work permit or green card, or organise what an application needs. Produces the categorised document checklist, the gather-in-this-order plan, the common-mistake/rejection-trigger list, and the professional-help flags. Organises the paperwork; complements the visa-interview simulator.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill immigration-document-checklist --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going