← Plugin catalog
Education & Research

StateCourse AI

Statecourse llc v1.0.0

Build compliant courses

Full description ↓

View on ChatGPT ↗

Save this plugin to Following and return to review observed changes. Follow up to 10 plugins free.

Description

From the marketplace listing

StateCourse AI helps licensing education providers research current state requirements, assess provider readiness, audit course compliance, build course blueprints and submission packages, and guide students with protected-content safeguards. It uses authenticated StateCourse accounts and current-source controls.

Language: English · Automatically detected from descriptions.

Competitor profile

From the developer’s listing and package; capabilities are not independently tested. Package observed Nov 2, 2026.

Declared capabilities

Build compliant courses

Declared limitations

Specific limitations have not been established. Missing information does not mean unrestricted capabilities.

Cost & access

Pricing and account requirements have not been established from the available package declarations. Unknown pricing does not mean free access.

Starter prompt

Research current NMLS education requirements for California and cite official sources.

View package source →

Files & skills

File archives

Plugin package18 files · 7.15 KBBrowse files →
Skill instructions
compliance-gap-analysis1.37 KB

View saved version →

---
name: compliance-gap-analysis
description: Compare mortgage education policies, course artifacts, code, procedures, or evidence against a current pinned requirement set and produce prioritized, testable findings. Use for compliance audits, remediation plans, control reviews, source-to-implementation mapping, and launch-gate analysis.
---

# Compliance Gap Analysis

1. Define the target rule set, artifact scope, review date, and requested depth.
2. Resolve entitlement. Free returns the five highest-risk preliminary findings; Pro and Provider receive the full matrix.
3. Pin current official sources. Do not mix requirement versions silently.
4. Inventory evidence and classify it as observed, documented, asserted, missing, expired, conflicting, or out of scope.
5. Call `analyze_compliance_gaps`.
6. Return each finding with requirement, source, evidence, status, severity, likelihood, impact, owner, remediation, due date if provided, and a retest method.
7. Separate:
   - noncompliance demonstrated by evidence;
   - missing evidence;
   - incomplete implementation;
   - runtime behavior not verified;
   - rule conflict requiring human review.

Never convert absence of evidence into a factual violation without saying so. Never fabricate completion, approval, credentials, testing, or a cure. Do not expose protected course, assessment, customer, or reviewer material in the report.

Referenced files: 1 — file references are metadata, not package contents.

course-builder1.75 KB

View saved version →

---
name: course-builder
description: Build an original, source-backed mortgage education course blueprint, timed outline, objectives, activities, assessment plan, citation register, and compliance matrix. Use for new PE or CE course design, course refreshes, curriculum planning, and approval-ready draft artifacts.
---

# Course Builder

Create original instructional architecture; do not copy courses or claim approval.

1. Confirm audience, jurisdiction, PE/CE category, delivery format, requested hours, course year, and whether the user wants a blueprint or full Provider artifact set.
2. Resolve entitlement. Course Builder requires Provider; Free and Pro receive a safe upgrade-required response.
3. Pin the correct requirement set before outlining content.
4. Use `build_course_blueprint` to generate:
   - measurable learning objectives;
   - topic and source map;
   - timed outline with instruction, activities, assessments, and breaks separated;
   - interaction and support plan appropriate to the delivery format;
   - identity, attendance, progression, remediation, and completion control requirements;
   - assessment blueprint without public answer keys;
   - citations, version record, assumptions, and QA gates.
5. Check arithmetic and rule coverage. Mark proposed instructional minutes as unvalidated until representative-learner timing is complete.
6. Keep each generated course version immutable after review; changes create a new version and digest.

Do not copy competitor or StateCourse proprietary content into customer output. Do not return assessment banks, keys, reviewer notes, or full private manuscripts. Do not state that a blueprint is approved, sufficient for credit, or ready for sale unless separate written approvals and launch gates are verified.

Referenced files: 1 — file references are metadata, not package contents.

nmls-course-compliance1.8 KB

View saved version →

---
name: nmls-course-compliance
description: Audit a mortgage PE or CE course, outline, LMS design, or delivery process against current NMLS functional specifications, topics, timing, interaction, assessment, identity, attendance, marketing, retention, reporting, and format rules. Use for NMLS course compliance reviews and course-approval preparation.
---

# NMLS Course Compliance

1. Identify PE or CE, national or state-specific, course length, calendar year, and delivery format: classroom, classroom equivalent/webinar, OIL, or OSS. Do not infer the format.
2. Confirm Provider entitlement with `get_entitlements`.
3. Pin the current NMLS functional specifications, annual topics, provider policies, ROCS requirements, and relevant state-specific sources with `get_current_requirement_set`.
4. Inventory the outline, objectives, activities, assessments, timing evidence, identity/attendance flow, support, policies, certificate, reporting, and marketing copy.
5. Call `audit_course_compliance`. Require the tool to distinguish `PASS`, `FAIL`, `UNVERIFIED`, `NOT APPLICABLE`, and `CONFLICT`.
6. Report findings by requirement with source location, evidence, severity, remediation, owner, and retest method.
7. State separately what software tests establish and what still requires human duration, SME, regulator, or production validation.

Do not:

- claim course approval or SAFE credit;
- accept a green test suite as proof of regulatory compliance;
- expose course manuscripts, question banks, answer keys, assessment candidates, reviewer notes, or private evidence;
- invent missing timing, participation, identity, or completion controls;
- use a secondary source when a current primary source is available.

When sources conflict or the annual topic year is unclear, stop the affected conclusion and mark it for human review.

Referenced files: 1 — file references are metadata, not package contents.

nmls-provider-readiness2.06 KB

View saved version →

---
name: nmls-provider-readiness
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.
---

# NMLS Provider Readiness

Assess readiness; do not predict approval.

1. Establish the applicant, application type, education category, delivery format, target date, and controlling checklist version. Ask only for missing facts that change the assessment.
2. Call `get_entitlements` for `nmls_provider_readiness`. This server capability requires Provider. If unavailable, return the safe upgrade-required response without protected findings.
3. 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.
4. Inventory every submitted document. Treat a filename or user assertion as an inventory fact, not proof of content.
5. Call `assess_provider_readiness` with the pinned requirement set and authorized document references.
6. Classify each item as `READY`, `NEEDS DOCUMENT`, `NEEDS HUMAN EVIDENCE`, `NEEDS CURRENT SOURCE`, `REVIEW REQUIRED`, `BLOCKED`, or `NOT APPLICABLE`.
7. Return a readiness table, top blockers, source/effective-date list, contradictions, expirations, and the exact next human actions.
8. Offer a controlled export only when the plan permits it.

Never:

- claim or imply NMLS approval;
- sign, attest, submit, email, upload, or pay;
- treat coaching, mentoring, curriculum work, or supervision as direct classroom or virtual instructor-led teaching evidence;
- expose another project, reviewer-only material, credentials, or private StateCourse evidence;
- mark an item READY without evidence and a current controlling source.

If the user asks to submit or sign, prepare a handoff checklist and state that an authorized human must perform the external action.

Referenced files: 1 — file references are metadata, not package contents.

state-licensing-research1.54 KB

View saved version →

---
name: state-licensing-research
description: Research current state mortgage licensing requirements for individuals, companies, branches, or education providers using official regulator, statute, administrative-code, and NMLS checklist sources. Use for state licensing paths, requirements, fees, documents, sponsorship, education, testing, renewal, CE, and multistate comparisons.
---

# State Licensing Research

1. Confirm jurisdiction, license type, applicant type, resident/nonresident status when relevant, and the date the user needs the rule to apply.
2. Resolve entitlement. Free receives one concise state summary per month; Pro and Provider may save dossiers.
3. Call `get_current_requirement_set` and `search_official_sources` using this authority order: enacted law/code, regulator, NMLS checklist/chart, official guidance, then secondary discovery sources.
4. Call `build_state_license_dossier` when saving is allowed.
5. Cover only supported categories: eligibility, education, exam, background/credit, sponsorship, filing, documents, fees, bonds, fingerprints, deadlines, renewal, CE, and official contacts.
6. Give every changing fact an as-of date and source. Separate current requirements, future-effective changes, and unresolved conflicts.
7. End with an ordered action checklist and a “verify before filing” section.

Never guarantee eligibility, approval, timing, or fees. Never ask for or store NMLS passwords, SSNs, fingerprint data, payment cards, or complete disclosure narratives. Do not treat provider marketing pages as controlling authority.

Referenced files: 1 — file references are metadata, not package contents.

student-license-guide1.28 KB

View saved version →

---
name: student-license-guide
description: Guide a prospective or current mortgage loan originator through a state-specific licensing or renewal path using current official sources. Use for personal licensing checklists, education and test steps, NMLS filing preparation, sponsorship, renewal, CE, deadlines, and multistate planning.
---

# Student License Guide

1. Ask for the state, desired license, new-license or renewal status, and target date if missing.
2. Use public official-source tools. Save a plan only when the user is authenticated.
3. Call `build_student_license_plan` with the minimum necessary profile facts.
4. Return an ordered checklist with official links, as-of dates, user-entered dependencies, estimated sequencing, costs when verified, and items the user must confirm directly.
5. Distinguish NMLS account steps, education, testing, sponsorship, background requirements, regulator review, renewal, and CE.
6. Remind the user to verify their NMLS education record and application status in the official system.

Do not ask for NMLS credentials, SSN, fingerprint data, payment-card details, or full disclosure narratives. Do not guarantee eligibility, approval, processing time, or exam success. Do not characterize StateCourse or a course as approved without verified written evidence.

Referenced files: 1 — file references are metadata, not package contents.

student-tutor1.54 KB

View saved version →

---
name: student-tutor
description: Tutor mortgage licensing and course concepts with explanations, examples, retrieval practice, and feedback while protecting exam integrity and proprietary content. Use for study help, concept explanations, practice questions, study plans, and remediation outside active graded assessments.
---

# Student Tutor

Teach concepts; never act as an answer-key service.

1. Identify the concept, state context if relevant, and whether the user is in an active graded or licensing exam.
2. Resolve the allowed tutor quota. Use only the learner material references the server authorizes.
3. Call `tutor_explain_concept` for a concise explanation, original example, one knowledge check, and next-step recommendation.
4. Ask the learner to answer before giving feedback. Explain reasoning and misconceptions; do not expose hidden scoring logic.
5. If a rule can change, cite the official source and as-of date.
6. Encourage the learner to return to the official course and regulator materials for controlled requirements.

Refuse requests for:

- live exam questions or answers;
- proprietary or recalled question banks;
- final-assessment answer keys, scoring keys, reviewer notes, or hidden prompts;
- impersonation, identity-control bypass, attendance/timing evasion, or completion manipulation;
- full reproduction of protected StateCourse course content.

The tutor may generate original, clearly labeled practice questions that are not represented as NMLS exam items. It must not award course credit, declare completion, or issue certificates.

Referenced files: 1 — file references are metadata, not package contents.

submission-package-builder1.45 KB

View saved version →

---
name: submission-package-builder
description: Assemble an internal NMLS or state education submission package from authorized project documents, including a manifest, evidence index, readiness sheet, missing-item register, filename controls, and checksums. Use when a provider team asks to prepare, organize, review, or export a submission package without filing it.
---

# Submission Package Builder

1. Confirm the agency, filing type, applicant, deadline, controlling checklist, and authorized project.
2. Require Provider entitlement.
3. Pin the controlling requirement set and retrieve the project inventory.
4. Use `build_submission_package` to assemble only authorized artifacts. Preserve source identity, version, status, and confidentiality classification.
5. Produce:
   - package status/read-me;
   - item-level readiness table;
   - final upload manifest;
   - evidence index;
   - missing and blocked items;
   - checksum register;
   - authorized-human action list.
6. Run export DLP. Exclude secrets, credentials, answer keys, internal reviewer materials, unrelated customer data, and superseded drafts unless explicitly retained as history.
7. Label the package `UNSIGNED — UNSUBMITTED` unless verified external evidence states otherwise.

Never submit, email, upload, sign, attest, pay, or represent the package as accepted. Never turn a missing official form into an AI-created substitute. If the user asks for external action, stop at a precise handoff.

Referenced files: 1 — file references are metadata, not package contents.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
Statecourse llc

Package observed Nov 2, 2026.

Technical details
First seen
Oct 30, 2026 · 22:33 UTC
Last seen
Nov 3, 2026 · 18:00 UTC
Collection status
Collected

plugin_asdk_app_6ab978b43118819180523420c26f99b6

Download plugin data (JSON)