Step by Step Tutorial to Setting Up Skilljar SCORM and xAPI Content

If you’re here, you probably need to get SCORM or xAPI content up and running in Skilljar for your learners, and you want it to just work. Maybe you’re new to this, or maybe you’re tired of vague documentation and just want the real steps (and the pitfalls). This guide is for you.

Everything here is based on real-world Skilljar experience—not marketing hype. I’ll walk you through exactly how to upload, configure, and troubleshoot SCORM and xAPI files in Skilljar. You’ll get tips for what actually matters, what’s just noise, and where most people trip up.

Who This Guide Is For

  • You manage online training or learning content and need to use Skilljar
  • You have SCORM (1.2 or 2004) or xAPI (Tin Can) packages to upload
  • You want clear steps, not a sales pitch

If you’re not sure what SCORM or xAPI is, here’s the 10-second version: they’re standards for e-learning content. If your content comes as a .zip file from Articulate, Captivate, or similar, it’s probably SCORM or xAPI.

Step 1: Prep Your Content

Let’s start with your course files. Don’t skip this—most headaches come from the wrong file type or a bad export.

Checklist:

  • File format: SCORM 1.2, SCORM 2004 (2nd, 3rd, or 4th edition), or xAPI (aka Tin Can). Skilljar doesn’t support AICC, older course formats, or raw HTML zips.
  • Zipped package: You need a .zip file. Don’t unzip it.
  • Index file: Your package must have index.html, story.html, or equivalent at the root, not buried in subfolders.
  • File size: Skilljar’s limit is 1 GB per package, but keep it smaller if possible. Big files = slow load times.
  • Export settings: For SCORM, always check “report completion and success” in your authoring tool. For xAPI, make sure statements are being sent (see your tool’s docs).
  • Test locally: Open the zip in SCORM Cloud or similar to make sure it launches. If it doesn’t, Skilljar won’t magically fix it.

Pro tip: If you’re using Articulate Storyline or Rise, don’t include extra tracking or navigation—Skilljar will handle that.

Step 2: Upload Your SCORM or xAPI Package

Ready? Here’s how to actually get your content into Skilljar.

  1. Login to Skilljar Dashboard.
  2. Go to “Course Management.” Click into the course you want, or create a new one.
  3. Add a Lesson.
  4. Click “Add Lesson.”
  5. Choose "SCORM/xAPI."
  6. Upload Your Package.
  7. Click “Upload a new SCORM/xAPI package.”
  8. Select your zip file.
  9. Give it a clear name—what learners will see.
  10. Wait for Processing. Skilljar will process your file. This usually takes a couple minutes. If it fails, double-check your zip structure.

What not to worry about: You don’t need to manually enter launch URLs or mess with manifest files—Skilljar handles that if your zip is packaged right.

Step 3: Configure Lesson Settings

Now, set up how your content behaves for learners.

Completion Criteria

  • SCORM: Skilljar reads the completion status your SCORM sends. Choose “Mark lesson complete when the SCORM/xAPI package is completed.”
  • xAPI: Same deal—completion is sent by your package to Skilljar.

Caution: If you don’t configure reporting in your authoring tool, learners might get stuck at "In Progress" forever. Double-check your export settings.

Attempts & Retakes

  • Attempts allowed: Set how many times a learner can launch the content. Most people leave this unlimited, unless you need strict compliance tracking.
  • Retake behavior: Decide if you want progress reset on retake. (Usually “No”—it’s safer.)

Display Options

  • Inline vs. New Window: Inline keeps learners in Skilljar; “New Window” can fix some display bugs or let content go fullscreen. Try both, but inline is less confusing for most users.
  • Size: Don’t mess with custom sizing unless your content really needs it. Default works for 99% of courses.

Pro tip: If your content opens to a blank page, it’s almost always a mismatch between your zip structure and the SCORM/xAPI manifest.

Step 4: Test as a Learner

Never trust a course upload until you see it work as a real learner.

  1. Preview the course. Use Skilljar’s “Preview as Learner” feature.
  2. Launch your SCORM/xAPI lesson.
  3. Complete the lesson. Trigger completion in your content (e.g., finish the quiz, reach the last slide).
  4. Check status. Go back to the course outline and see if the lesson shows as “Completed.”

If completion doesn’t trigger:

  • Re-export your package with explicit “report completion” settings.
  • Make sure you’re not using unsupported triggers (like custom JavaScript).
  • Test in SCORM Cloud. If it fails there, fix it before retrying in Skilljar.

Step 5: Handle Common Issues

You will hit snags. Here’s what usually goes wrong—and how to fix it fast.

1. Lesson Never Completes

  • Symptom: Learner finishes the content, but Skilljar won’t mark it complete.
  • Fixes:
  • Re-check your authoring tool export settings: set “Track using quiz result” or “Track using number of slides viewed.”
  • For SCORM, use “Passed/Completed” or “Completed/Passed” reporting.
  • For xAPI, make sure “completed” and “passed” statements are sent.
  • Avoid multiple SCORM files in one zip—Skilljar only launches the first one.

2. Content Won’t Launch

  • Symptom: Clicking the lesson does nothing, or you see an error.
  • Fixes:
  • Your zip is missing index.html at the root.
  • The manifest file is corrupt or missing.
  • File size is too large (>1GB).
  • Try uploading a fresh export.

3. Data Not Tracking

  • Symptom: Completion works, but quiz scores or question-level data isn’t showing up in Skilljar reports.
  • Reality check: Skilljar only stores SCORM completion, pass/fail, and score at a high level. If you need detailed question-level analytics, you’ll need an external tool—Skilljar isn’t a full-blown SCORM analytics platform.

Step 6: Go Live and Support Learners

Once your content works, publish the course.

  • Enroll a test user: Make sure everything works for a real account.
  • Monitor support tickets: Most issues are browser-related (pop-up blockers, cache problems), not platform bugs.
  • Keep a backup: Always save your source files and original exports—re-uploading is faster than troubleshooting a broken package.

What Actually Matters (And What Doesn’t)

Matters:

  • Export settings in your authoring tool
  • Clean zip structure with the right manifest and launch file
  • Checking completion and score reporting

Doesn’t matter:

  • Fancy SCORM “features” most learners never see
  • Over-customizing display settings
  • Obsessing over minor launch window tweaks—if the content works, stop tweaking

Ignore: Anyone telling you SCORM/xAPI setup is “plug and play.” It almost never is, especially with custom content.

Wrapping Up: Keep It Simple, Iterate Fast

Don’t overthink this. Most SCORM and xAPI headaches come from the original export, not Skilljar itself. Start with a simple, clean package. Test it as a real learner. When something breaks, fix the source and re-upload. If you hit a wall, SCORM Cloud is your best friend for debugging.

Skilljar does a decent job with SCORM and xAPI, but it’s not magic. The less you tinker, the fewer problems you’ll have.

Good luck—and remember, done beats perfect.