Install
$ agentstack add skill-jasp-nerd-courseforge-imscc-editor ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ● Filesystem access Used
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
IMSCC editor
A .imscc is a ZIP with imsmanifest.xml plus Canvas extension XMLs. The @courseforge/imscc library understands both; the full format anatomy is in [references/imscc-format.md](references/imscc-format.md) — consult it whenever a field is ambiguous.
Inspect
npx -y @courseforge/imscc inspect course.imscc # structure as JSON
npx -y @courseforge/imscc validate course.imscc # cross-reference invariants (the #1 import-failure cause)
Modify (export → modify → re-import loop)
Use the library in a small Node script (pnpm add @courseforge/imscc or run inside the CourseForge repo):
import { readFileSync, writeFileSync } from 'node:fs';
import { CartridgeEditor, validateCartridge } from '@courseforge/imscc';
const ed = CartridgeEditor.fromBytes(readFileSync('export.imscc'));
console.log(ed.listModules());
ed.addItem('Week 1', { type: 'page', title: 'Office hours', body: 'Tue 14:00' });
ed.addModule('Week 9 — Review');
ed.removeItem('Week 2', 'Old quiz');
const bytes = ed.toBytes();
console.log(validateCartridge(bytes)); // must have zero errors before shipping
writeFileSync('export-modified.imscc', bytes);
Item inputs are CourseSpec module items (see the canvas-course-builder skill's course-spec reference): page, assignment, quiz (+questions), discussion, link, file, header.
Key rules the editor enforces for you — don't work around them by hand-editing XML:
- identifiers stay stable across edits, so Canvas updates instead of duplicating on re-import
- manifest organization ↔
module_meta.xmlstay consistent - removing an item removes its resources and files only when nothing else references them
Repair a failing import
validate— every error names the dangling reference or missing file.- Typical causes: an
identifierrefpointing at a deleted resource, a `missing from the zip,imsmanifest.xml` not at the zip root, ids starting with a digit. - Fix via
CartridgeEditor(or parse withreadCartridge, adjust, re-serialize), re-validate, then re-import. - If Canvas imported but content is missing: check the migration issues (MCP tool
list_migration_issues) and whether the cartridge lacked the Canvas flag file (course_settings/canvas_export.txt) — without it Canvas ignores all module/assignment settings.
Push back into Canvas
With courseforge-mcp connected: import_course_package (course_id + file path). Manually: Canvas → Settings → Import Course Content → Common Cartridge 1.x Package.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jasp-nerd
- Source: jasp-nerd/courseforge
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.