Plugin

niw-skills

Open-source plugin for U.S. EB-2 National Interest Waiver (NIW) case work. Honest pre-filing legal evaluation of self-petitions under the current USCIS adjudication standard, with the preponderance-of-the-evidence burden applied prong by prong under Matter of Dhanasar. Built for three cohorts: DIY self-petitioners ready to file, prospective applicants 6–24 months out, and master's/PhD students 3–5 years out who want a multi-year roadmap before committing. Key features: • Agentic 5-stage conversation — orient → co-design your proposed endeavor → confirm → full evaluation → follow-ups. Adapts to what you know and what you've provided; produces a clean structured memo, not an engineering trace. • Citation discipline — every legal rule cites authority inline (Dhanasar, Chawathe, Katigbak, USCIS Policy Manual Vol. 6 Pt. F Ch. 5, and curated AAO decisions). • Verdict floor under preponderance — no inflated assessments. No prong is rated "Strong" without documented evidence clearing preponderance. • Hard anti-hallucination rules — no invented citation counts, grant roles, employer facts, or AAO decision IDs. • Achievable case ceiling — beyond the current-state verdict, the plugin produces a roadmap of concrete prerequisite actions and an honest 0–60 month timeline to reach a stronger case. • AC21 framing for India/China nationals — surfaces the practical reason most backlogged-country petitioners file NIW: an approved I-140 unlocks indefinite H-1B extension under AC21 § 104(c) and § 106(a). • Written for international, ESL-primary, highly-educated users — short sentences, technical terms explained on first use, citations in standard form, no idioms. Future skills shipping in this plugin: endeavor-statement drafter, petition-letter drafter, evidence finder, recommendation-letter drafter, RFE/NOID analyzer. Not legal advice. Not a substitute for licensed immigration counsel. See DISCLAIMER.md.

• Published source
• Repository

Analysed

11 October 2026

Last observed

14 October 2026

What the code does

What does this mean?

These are capabilities our static analysis found in the latest published version. They describe what the code can do, not whether it is malicious: many tools need shell access or the network to do their job. Use them to decide what to check before installing.

Static analysis found none of the capabilities we track, such as shell commands, network requests or file writes, in the latest version.

Having a capability is not wrongdoing; many tools need these to do their job. It tells you what to check before you install.

This is public metadata, not a safety certification or complete assessment. Static analysis cannot establish what a tool does at runtime.