Content Submission Guidelines
The quality and consistency of your content submissions determine how well your catalog integrates into the Skillsoft Platform and how seamlessly learners experience it. The AI Assistant walks you through these requirements on each screen, but the following guidelines summarize what you need to prepare.
1. Supported Content Types
The Skillsoft Platform supports multiple methods for syncing content into the platform:
xAPI – Standards-based integration for detailed learner activity capture.
API-based Metadata Import – Add structured metadata for courses, videos, and documents.
CSV Uploads – Use Skillsoft-provided CSV templates for catalog and completion data.
File-based Content – Videos, PDFs, and similar static learning objects can be onboarded via metadata or CSV.
Alternate Approaches (Fallback) – If no completion tracking is available, you can configure:
Completion on launch
Learner-reported completion
⚠️ Note: SCORM was not listed in the provided documentation. If your integration requires SCORM, please confirm with your Skillsoft Partner Manager.
2. Metadata Standards and Expectations
Every piece of content submitted to the platform requires metadata to ensure discoverability, reporting accuracy, and learner experience consistency.
Mandatory fields (examples): content_id, title, type, URL, language, duration.
Schema adherence: Values must conform to allowed formats (e.g., duration must follow the expected format).
Accuracy: Descriptions and tags should clearly reflect the content.
Consistency: Ensure the same content_id is used across imports, completions, and tracking.
Use the AI Assistant to check acceptable values (e.g., “What values are valid for modality?”) or validate field-level errors.
3. Tips for Naming, Structure, and Compatibility
Titles: Keep clear, concise, and unique. Avoid duplicates.
Descriptions: Up to 500 characters, written for learner clarity.
Logos/Thumbnails: Upload in supported formats (JPG/PNG ≤ 2 MB).
Partner Name: Max 100 characters, no special characters or spaces.
File formats: Videos (MP4), documents (PDF), images (JPG/PNG).
4. SSO and PII Guidelines
Default behavior: If PII = No, the Skillsoft Platform sends the User UUID in the NameID attribute (non-configurable SAML standard).
If PII = Yes: You can enable attribute mapping for First Name, Last Name, Email, and User ID.
Mapping uses a 4-column table (Skillsoft Platform attribute, arrow, provider attribute, toggle).
Use the toggle to enable/disable sending attributes in the SAML response.
SAML 2.0:
Configure Assertion Consumer URL and Entity ID.
Optionally include Authn Statement (Yes/No).
Generate and exchange IDP metadata file if required.
⚠️ Best practice: Avoid using email as the unique identifier; prefer User ID or UUID.
5. Activity & Completion Submissions
The Skillsoft Platform accepts learner activity and completion data through multiple methods:
API / Track API – Submit JSON payloads for learner progress (status, completion %, event date).
xAPI Statements – Post supported verbs/events to the Skillsoft Platform statements endpoint.
CSV-based completions – Upload via SFTP using the Skillsoft completions template.
Fallback – Choose completion on launch or learner-reported completion if no system data is available.
Historical completions: You may import past completions using the same mechanism. Confirm configuration in the AI Assistant.
6. Alternate Approaches & Validation
If you lack a real-time tracking mechanism, configure fallback completion methods (on launch or learner-reported).
Use sandbox to validate every submission:
Ensure metadata renders properly.
Confirm learner completions are captured.
Validate schema adherence (modality, duration, user identifiers).
The AI Assistant will highlight errors such as:
“Invalid field value”
“Unsupported file type”
“Missing mandatory attribute”
Metadata Fields: Mandatory vs Optional
| Field | Mandatory / Optional | Description | Example |
content_id
|
Mandatory | Unique external identifier for the learning object. Must remain consistent across imports, completions, and tracking. | ext-course-001 |
| title | Mandatory | Learner-facing name of the content. Clear, concise, unique. | Cloud Security Fundamentals |
| type | Mandatory | Content type (e.g., video, course, document, PDF). Must align with supported schema values. | video |
| url | Mandatory | Launchable URL for hosted content. | https://partner.com/course123 |
| language | Mandatory | Language code of the content. | en |
| duration | Mandatory | Length of the content in the required format. | PT30M |
| description | Optional (Strongly Recommended) | Short learner-facing description (max 500 chars). | An introduction to cloud security principles. |
| tags / keywords | Optional | Helps with search and discoverability. | security, cloud, fundamentals |
| thumbnail_url / logo | Optional | Link to thumbnail or partner logo for display in the Skillsoft Platform. | https://partner.com/logo.png |
| status | Mandatory at provider level | Governs integration availability: Draft, Active, Inactive. | Active |
| compliance flags | Mandatory at provider level | FedRamp, Accessibility, GDPR (Yes/No). | Yes |
| PII attributes (if applicable) | Conditional (when PII = Yes) | First Name, Last Name, Email ID, User ID mapping via SAML. | john.doe@example.com |
✅ Following these guidelines ensures your content is properly onboarded, searchable in the platform, and compatible with Skillsoft’s reporting and learner experience standards.
AI Assistant Tip: If you’re unsure about a field, ask:
“What format should duration follow?”
“Is description mandatory?”
“How do I map First Name in SAML?”
The Assistant will show the field definition and schema rules inline.
Completion Data Fields: Mandatory vs Optional
| Field | Mandatory / Optional | Description | Example |
content_id
|
Mandatory | Unique identifier of the learning object. Must match the content_id used in metadata import. | ext-course-001 |
| user_id / UUID | Mandatory | Learner identifier. Default is Skillsoft Platform UUID. If PII = Yes, can also include mapped fields (First Name, Last Name, Email). | u12345-xyz |
| status | Mandatory | Current learner progress state. Allowed values: started, in-progress, completed. | completed |
| event_date | Mandatory | Timestamp of the learning event in required format. | 2025-09-12T10:00:00Z |
| completion_percentage | Optional (Recommended) | Numeric value (0–100) showing progress toward completion. | 100 |
| time_spent | Optional | Duration of learner engagement. | PT45M |
| score | Optional | Assessment result, if applicable. | 92 |
| activity_type | Optional | Type of activity (e.g., quiz, video, module). | quiz |
| thumbnail_url / logo | Optional | Link to thumbnail or partner logo for display in the Skillsoft Platform. | https://partner.com/logo.png |
| status |
Mandatory |
Governs integration availability: Draft, Active, Inactive. | Active |
| PII attributes (if applicable) | Conditional (when PII = Yes) | First Name, Last Name, Email ID. These are mapped via SAML and transmitted if toggled. | john.doe@example.com |
ey Notes
Consistency: content_id must always match the value used in your metadata import.
Identifiers: Default is UUID. If PII = No, only UUID is used; if PII = Yes, you can map other identifiers (email, name).
Fallback methods: If no completion data is sent, you may configure:
Completion on launch – marks complete when content opens.
Learner-reported completion – learner manually marks complete.
AI Assistant Tip: Ask for guidance when submitting completions, e.g.,
“What values are allowed for status?”
“Can I import historical completions?”
“Why did my CSV fail validation?”
The Assistant will validate your payloads or CSV files against required fields and highlight errors in real time.