← StateCourse AICONTENT HISTORY

Update to StateCourse AI

Snapshot Oct 31, 2026 · 01:14 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save StateCourse AI and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Assess an NMLS course-provider application or renewal package for completeness, evidence support, current-source alignment, contradictions, expirations, and human-action gates. Use for provider readiness, provider application checklists, renewal preparation, provider-policy packages, or questions about whether a provider submission is ready.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 563
    }
  ],
  "name": "nmls-provider-readiness",
  "skill_md_contents": "---\nname: nmls-provider-readiness\ndescription: Assess an NMLS course-provider application or renewal package for completeness, evidence support, current-source alignment, contradictions, expirations, and human-action gates. Use for provider readiness, provider application checklists, renewal preparation, provider-policy packages, or questions about whether a provider submission is ready.\n---\n\n# NMLS Provider Readiness\n\nAssess readiness; do not predict approval.\n\n1. Establish the applicant, application type, education category, delivery format, target date, and controlling checklist version. Ask only for missing facts that change the assessment.\n2. Call `get_entitlements` for `nmls_provider_readiness`. This server capability requires Provider. If unavailable, return the safe upgrade-required response without protected findings.\n3. Call `get_current_requirement_set` for NMLS provider standards and the target date. Use `search_official_sources` when the controlling document is missing or potentially superseded.\n4. Inventory every submitted document. Treat a filename or user assertion as an inventory fact, not proof of content.\n5. Call `assess_provider_readiness` with the pinned requirement set and authorized document references.\n6. Classify each item as `READY`, `NEEDS DOCUMENT`, `NEEDS HUMAN EVIDENCE`, `NEEDS CURRENT SOURCE`, `REVIEW REQUIRED`, `BLOCKED`, or `NOT APPLICABLE`.\n7. Return a readiness table, top blockers, source/effective-date list, contradictions, expirations, and the exact next human actions.\n8. Offer a controlled export only when the plan permits it.\n\nNever:\n\n- claim or imply NMLS approval;\n- sign, attest, submit, email, upload, or pay;\n- treat coaching, mentoring, curriculum work, or supervision as direct classroom or virtual instructor-led teaching evidence;\n- expose another project, reviewer-only material, credentials, or private StateCourse evidence;\n- mark an item READY without evidence and a current controlling source.\n\nIf the user asks to submit or sign, prepare a handoff checklist and state that an authorized human must perform the external action.\n"
}

SHA-256 of public snapshot: 1b8410cf17e0547911a9defd274629f1031e666b2e01f65a71eb99a690f51751