Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Iblai Api Studio Unit

BSecurity

Manage units (vertical blocks) of an Open edX course on Studio — create a unit inside a subsection, list and reorder the components it contains, rename, set staff-only visibility, duplicate, move between subsections, and delete. Use when the user says unit, page, "add a page to the lesson", reorder components, or asks what is inside a unit. Session auth via studio.env; components themselves are added with the html / problem / pdf skills. For the build order and the other Studio skills, see /i...

15 stars
0 votes
0 copies
0 views
Added 9/20/2026
developmentpythongobashnodeapi

Works with

api

Security Analysis

B88/100
criticalDownloads and executes remote scripts — classic supply chain attack

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add iblai/vibe --skill iblai-api-studio-unit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Iblai Api Studio Unit?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Iblai Api Studio Unit
[![Security: B — Skills Directory](https://www.skillsdirectory.com/api/skills/iblai-iblai-api-studio-unit/badge)](https://www.skillsdirectory.com/skills/iblai-iblai-api-studio-unit)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: iblai-api-studio-unit
description: Manage units (vertical blocks) of an Open edX course on Studio — create a unit inside a subsection, list and reorder the components it contains, rename, set staff-only visibility, duplicate, move between subsections, and delete. Use when the user says unit, page, "add a page to the lesson", reorder components, or asks what is inside a unit. Session auth via studio.env; components themselves are added with the html / problem / pdf skills. For the build order and the other Studio skills, see /iblai-api-studio.
metadata:
  kind: api
---

# iblai-api-studio-unit

A **unit** (`vertical`) is one user-facing page inside a subsection; it
holds the components (`html`, `problem`, `pdf`, …). Publishing happens at
unit level or above. This skill is the container; content goes in with
`/iblai-api-studio-html`, `/iblai-api-studio-problem`, `/iblai-api-studio-pdf`.

## Before you start

1. Preflight: `node .claude/skills/iblai-api-studio-auth/scripts/studio-login.mjs --check` prints two `ok`s; otherwise run **`/iblai-api-studio-auth`** first — do not attempt the calls below.
2. A subsection locator from `/iblai-api-studio-subsection` (or `GET /api/v1/ibl/course/{COURSE}/units` from `/iblai-api-studio-outline` for existing units).
3. Plan the unit's rhythm before adding components (overview → content → one problem block → summary; `/iblai-api-studio`).

## Auth & conventions

- **Base URL:** `$STUDIO_URL`; Studio session cookies from `studio.env` (its values are single-quoted — bash strips the quotes; any other parser must strip them too, or Studio answers 500: `/iblai-api-studio-auth`).
- **Snippet:**
  ```bash
  set -a; . ./studio.env; set +a
  S=(-s -b "studio_session_id=$STUDIO_SESSION; csrftoken=$STUDIO_CSRF" -H "X-CSRFToken: $STUDIO_CSRF" \
     -H "Origin: $STUDIO_URL" -H "Referer: $STUDIO_URL/" -H "Accept: application/json" -H "Content-Type: application/json")
  ```
- **Keys:** parent = a subsection locator (`…+type@sequential+block@…`); a unit is `…+type@vertical+block@<hex>`.
- Every edit is a draft until `/iblai-api-studio-publish`. DELETE removes the components inside — confirm with the user first.

## Reads

- **GET** `/api/contentstore/v1/container/vertical/{unit}/children` — the components in order:
  `{ "children": [ { "name", "block_id", "block_type", "actions": {can_copy, can_duplicate, can_move, can_delete, …}, "validation_messages", "render_error", … } ] }`.
  This is the only JSON listing of a unit's components (`GET /xblock/{unit}` and `/xblock/outline/…` stop at the unit).
- **GET** `/xblock/{unit}` — the unit itself: `display_name`, `metadata`, `published`, `has_changes`, `visibility_state`, `released_to_students`, `start`, `graded`, `format`, `lms_url` (user deep link), `studio_url`.
- **GET** `/xblock/container/{unit}` — same plus `ancestor_info.ancestors` (subsection, section, course) and `currently_visible_to_students`.
- **GET** `/xblock/outline/{subsection}` — units of one subsection with publish state.

## Writes

- **POST** `/xblock/` — create:
  ```json
  { "parent_locator": "<subsection>", "category": "vertical", "display_name": "Reading: what is data?" }
  ```
  → `{ "locator": "…+type@vertical+block@<hex>", "courseKey": "…" }`.
- **POST** `/xblock/{unit}` `{ "metadata": { "display_name": "New name" } }` — rename; `{ "metadata": { "visible_to_staff_only": true } }` — hide from users (`false` to show).
- **POST** `/xblock/{unit}` `{ "children": ["<component A>", "<component B>", …] }` — reorder components (send every current component id in the new order).
- **PATCH** `/xblock/` `{ "move_source_locator": "<unit>", "parent_locator": "<other subsection>", "target_index": 0 }` — move a unit (or, with a component id, move a component into another unit).
- **POST** `/xblock/` `{ "duplicate_source_locator": "<unit>", "parent_locator": "<subsection>" }` — duplicate with its components → `{locator, courseKey}`.
- **DELETE** `/xblock/{unit}` → `204`. Confirm with the user first. (Same call deletes a single component by its locator.)
- **POST** `/xblock/{unit}` `{ "publish": "make_public" }` — publish this unit (`/iblai-api-studio-publish` for states and discard).

## Example

```bash
set -a; . ./studio.env; set +a
S=(-s -b "studio_session_id=$STUDIO_SESSION; csrftoken=$STUDIO_CSRF" -H "X-CSRFToken: $STUDIO_CSRF" \
   -H "Origin: $STUDIO_URL" -H "Referer: $STUDIO_URL/" -H "Accept: application/json" -H "Content-Type: application/json")
SUB="block-v1:acme+DATA101+2026-T1+type@sequential+block@8b9148c629c54a46b7404a88fcb528d0"

UNIT=$(curl "${S[@]}" -X POST "$STUDIO_URL/xblock/" \
  -d "{\"parent_locator\":\"$SUB\",\"category\":\"vertical\",\"display_name\":\"Reading\"}" \
  | python3 -c 'import sys,json; print(json.load(sys.stdin)["locator"])')

# …add components with /iblai-api-studio-html, -problem, -pdf… then list them:
curl "${S[@]}" "$STUDIO_URL/api/contentstore/v1/container/vertical/$UNIT/children" \
  | python3 -c 'import sys,json; [print(c["block_type"], c["name"], c["block_id"]) for c in json.load(sys.stdin)["children"]]'
```

## Notes

- Component locators come back from each create call; keep them instead of
  re-listing after every addition.
- A unit with no components publishes fine but renders empty; the LMS app
  still shows it in the outline.
- `lms_url` on the unit is the user deep link on the LMS host; the user
  app equivalent is `$LMS_APP_URL/platform/<org>/course-content/<course_key>/course?unit_id=<unit>`.
- Duplicating a unit also duplicates any problem inside (new problem ids, same OLX).
- Next: `/iblai-api-studio-html`, `/iblai-api-studio-problem`, `/iblai-api-studio-pdf`, then `/iblai-api-studio-publish`.

Attribution

iblaiiblai
View sourceMore from iblai →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Browser Extension Developer

Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.

281612 votes

Seo Optimizer

SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.

2132 votes

Google Official Seo Guide

Official Google SEO guide covering search optimization, best practices, Search Console, crawling, indexing, and improving website search visibility based on official Google documentation

1862 votes

Tanstack Start

Build a full-stack TanStack Start app on Cloudflare Workers from scratch — SSR, file-based routing, server functions, D1+Drizzle, better-auth, Tailwind v4+shadcn/ui. Use whenever the user mentions TanStack Start, asks to scaffold a full-stack Cloudflare app with SSR, wants an SSR dashboard, or asks for a React 19 + Cloudflare Workers app with file-based routing and server functions — even if they don't name TanStack Start specifically. No template repo — Claude generates every file fresh per ...

9881 votes

Pentest

PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.

5491 votes
View all in development →