SkillhabitDocs

Imported Package (SCORM, Tin Can & cmi5)

Import SCORM 1.2/2004, Tin Can (xAPI), or cmi5 packages as an Imported Package and publish them in Create. Progress is saved in Skillhabit Learn like other packages.

What This Is For

Upload a zip package from an external authoring tool and run it in Skillhabit Learn, with the same visibility, certificate, and Academy options as other Create items.

Supported package kinds:

FormatTypical manifest
SCORM 1.2imsmanifest.xml
SCORM 2004imsmanifest.xml
Tin Can / xAPItincan.xml
cmi5cmi5.xml

Package size is up to about 2.5 GB.

In Create these all use the same Imported Package content item. Learners open them in Learn; progress is saved in Skillhabit the same way for every package format. On public Academy (anonymous), all four formats also keep progress in the browser — details under Public Academy (anonymous).

Who This Is For

Authors who produce packages in tools such as Articulate Storyline/Rise, Adobe Captivate, or similar, and administrators who publish them in Create.

Before You Start

  • You have the Create app.
  • The zip is SCORM 1.2/2004, Tin Can (xAPI), or cmi5 (max 2.5 GB).

Steps

  1. Open Create → create or open an Imported Package-type item.
  2. Upload the package zip and wait until processing finishes (see Uploading and Processing).
  3. Configure title, Visibility and targets, certificates, and Academy as needed.
  4. Publish.

Uploading and Processing

  1. Upload (TUS) — Packages upload with TUS (resumable). If the connection drops, the transfer continues from where it stopped instead of starting over. Max size 2.5 GB.
  2. Waiting in queue… — Another package may be unpacking first; yours starts when a slot is free.
  3. Processing package… — Unpacking shows a percent as work proceeds.
  4. Retry processing — If unpacking fails, retry without choosing the zip again. Retry stays available when you replace a package on a published Imported Package-type item.

Formats and other ceilings: Supported File Types and Sizes.

What the package reports — and what Skillhabit uses

Packages send different learning signals while the learner plays. Skillhabit acts on the signals in the table below for Learn completion, resume, scores, and Analyze. For Tin Can / xAPI and cmi5, every statement the package posts is still kept on the attempt transcript — including common “noise” verbs such as experienced, attempted, or initialized. Those do not change Learn status and do not appear under Review answers; only statements with answer/response data show there.

Legend: Yes = this format can report it and Skillhabit uses it · When reported = used only if the package actually sends that data · No = Skillhabit does not use this signal · — = not part of that format.

Learning signalSCORM 1.2SCORM 2004Tin Can (xAPI)cmi5What Skillhabit does with it
Resume / bookmark (continue later)YesYesYesYesSaved and restored on the next attempt
CompletedYesYesYesYesMarks the item completed in Learn
PassedYesYesYesYesMarks completed / passed in Learn
FailedYesYesYesYesMarks failed in Learn
ScoreWhen reportedWhen reportedWhen reportedWhen reportedStored on the attempt; shown in Analyze when present
Time spent (session / total)When reportedWhen reportedWhen reportedWhen reportedStored on the attempt; shown in Analyze when present
Quiz answers / interactionsWhen reportedWhen reportedWhen reportedWhen reportedStored as a transcript; Analyze → Result details → Review answers
Progress fraction (e.g. 0–100% measure)—When reportedWhen reportedWhen reportedStored when present; not required for completion
Other xAPI verbs (e.g. experienced, attempted)——StoredStoredKept on the transcript; not used for completion or Review answers
cmi5 completion rule (moveOn)———YesControls which pass/complete signals count for that unit
Learning objectives (separate objective records)NoNoNoNoNot used by Skillhabit
Multi-unit / multi-AU sequencingPartialPartial—PartialFirst launchable unit only — prefer a program so you can update modules independently

How to read this

  • Inside the package the authoring tool may track more (slides, branching, local quizzes). Skillhabit only receives what the package chooses to report through SCORM or xAPI.
  • Completion in Learn comes from completed / passed / failed signals (course-level / primary activity) — not from score, progress, or noisy mid-module verbs alone.
  • Review answers in Analyze shows whatever answer-level data was reported (questions, responses, scores when included). If the package never sent answers, that tab is empty. This is the same Review answers place as for other results; it is not identical to built-in course chapter questions.
  • For cmi5, the unit’s moveOn setting decides whether “completed”, “passed”, or both are enough to finish.

Also available for all four formats

These are Skillhabit product features for the Imported Package-type item — not signals from the package itself:

  • Certificates, Academy (sell, price, public link), visibility & targets, programs, restart/cancel participation, Analyze progression counts
  • Not available: Follow Up reflections, built-in-course Export details answer spreadsheets, attempt limits in Create/Learn

Public Academy (anonymous)

SCORM, Tin Can / xAPI, and cmi5 all work on public Academy product links. Resume and in-player progress are stored in the learner’s browser on that device. Skillhabit records general analytics only for the workspace (starts, completions, failures in Analyze → Content statistics) — no named user results for anonymous traffic. Signed-in learners on the same item still get normal Learn progress and detailed Analyze where applicable.

Limits to know

  • cmi5 packages with several assignable units (AUs): Skillhabit launches the first AU only. Prefer publishing each module as its own Imported Package in Create, then grouping them in a program (order, schedule, or journey). You can then update one module without replacing the whole curriculum, and learners get sequencing in Skillhabit without multi-AU logic inside one zip.

Updating a Published Package

When you publish a new package for an existing item, progression for users who have not completed it is reset. Plan communications before replacing a live package.

Imported Package Publish changes supports revision notes and email notify; it does not use the built-in course patch vs Increment revision number dialog.