deploy

skills/activities/SKILL.md

@@ -11,6 +11,14 @@ Use the generated operation tools to make real API calls. Do not invent API resp
 If a tool reports missing setup, return the exact setup field name to the caller.
 For write, update, or delete operations, state the intended action before calling the tool.
 
+For visible lesson content, prefer `POST /api/v1/activities/` with
+`activity_type=TYPE_DYNAMIC`, `activity_sub_type=SUBTYPE_DYNAMIC_MARKDOWN`,
+markdown stored in `content`/`details`, `lock_type=public`, and `published=true`
+unless the user asks for drafts. Always use the target chapter's own
+`chapter_id`; do not attach every activity to the first chapter. On
+`PUT /api/v1/activities/{activity_uuid}`, do not send `published_version`;
+this LearnHouse backend rejects that field.
+
 ## Operations
 
 ### api_create_activity_api_v1_activities_post

skills/chapters/SKILL.md

@@ -11,6 +11,11 @@ Use the generated operation tools to make real API calls. Do not invent API resp
 If a tool reports missing setup, return the exact setup field name to the caller.
 For write, update, or delete operations, state the intended action before calling the tool.
 
+When creating multiple lesson chapters for a course, keep the returned `id` for
+each chapter. If the user requested course content, create at least one activity
+for every chapter using that specific `chapter_id`; do not reuse the first
+chapter ID for all activities. Verify every chapter has at least one activity.
+
 ## Operations
 
 ### api_create_coursechapter_api_v1_chapters_post

skills/courses/SKILL.md

@@ -20,6 +20,8 @@ Deployment context for this LearnHouse instance:
 - When listing courses and the user does not provide pagination, use `page=1` and `limit=50`.
 - When creating a course, use query parameter `org_id=1` unless the user explicitly provides another org ID.
 - Course creation must send multipart form fields `name`, `description`, `public`, and `about`. If the user only gives a title, use it as `name`, provide short `description` and `about` values, and set `public=false` unless the user asks for a public course.
+- When the user asks for a course with lessons, modules, or activities, do not stop after creating the course and chapters. Create at least one activity per chapter, using each chapter's own returned `chapter_id`.
+- Do not attach all generated activities to the first chapter. Verify the resulting course metadata shows activities distributed under the intended chapters.
 - Course creation and course management require `LEARNHOUSE_AUTH` consumer setup.
 
 ## Operations