К основному содержанию
скилл CX Codex

education-cloud-academic-calendar-generate — скилл для Claude Code

Скилл education-cloud-academic-calendar-generate для Claude Code создаёт в Education Cloud учебный год, семестры и другие периоды, а также сессии по датам из текста или документа. Настраивает календарь учебного заведения.

Apache-2.0 124 установок ★ 1 183 обновлён 2026-11-13

Установить в Claude Code · Через Skills CLI (Vercel) Все способы и платформы ↓
npx skills add forcedotcom/sf-skills --skill education-cloud-academic-calendar-generate -a claude-code
Открыть на GitHub

Что делает education-cloud-academic-calendar-generate

Скилл разбирает календарные даты в тексте или файле PDF, CSV либо таблице и готовит записи Academic Year, Academic Term и Academic Session. Он связывает периоды с учебным годом, сессии — с периодами, а также учитывает окна регистрации и сроки добавления или отчисления с курса.

Перед созданием записей скилл проверяет доступ к Education Cloud, объекты и поля Salesforce, затем проверяет диапазоны дат. Для локальной проверки нужен python3 версии >=3.8. До настройки потребуется подтвердить систему календаря и указать даты; если сведений недостаточно, агент попросит их. Существующие записи календаря, расписание курсов и предложения курсов в его задачи не входят.

Какие задачи решает

  • создать учебный год в Education Cloud
  • разбить учебный год на семестры, триместры или четверти
  • извлечь даты периодов и сессий из PDF или таблицы
  • задать окна регистрации и сроки добавления или отчисления
  • проверить диапазоны дат и связи между записями календаря

Примеры запросов агенту

  • Создай календарь Education Cloud на основе этого файла PDF.
  • Настрой учебный год по датам: Fall начинается 25 августа и заканчивается 12 декабря.
  • Добавь семестры и сессии, а также окна регистрации и сроки добавления или отчисления.

Как установить education-cloud-academic-calendar-generate

1Через Skills CLI (Vercel)

npx skills add forcedotcom/sf-skills --skill education-cloud-academic-calendar-generate -a claude-code

2Вручную: положить файлы

~/.claude/skills/education-cloud-academic-calendar-generate/SKILL.md

Папка скилла целиком; для одного проекта — .claude/skills/education-cloud-academic-calendar-generate/

По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов

Вопросы об education-cloud-academic-calendar-generate

Как установить education-cloud-academic-calendar-generate в Claude Code?

Выполните npx skills add forcedotcom/sf-skills --skill education-cloud-academic-calendar-generate -a claude-code. Файл скилла находится по пути ~/.claude/skills/education-cloud-academic-calendar-generate/SKILL.md.

Что делает education-cloud-academic-calendar-generate?

Создаёт записи учебного года, периодов и сессий в Education Cloud по датам из текста или календарного документа. Проверяет даты и связывает записи между собой.

Какие даты нужны для создания календаря?

Нужны даты начала и окончания учебного года, даты начала и окончания каждого периода, а также даты регистрации и добавления или отчисления. Для сессий внутри периода понадобятся даты этих сессий.

Исходный текст

SKILL.md · Apache-2.0
---
name: education-cloud-academic-calendar-generate
description: "Use this skill to set up, create, or generate an academic calendar for Education Cloud orgs. Creates Academic Year, Academic Terms (semester/quarter/trimester), Academic Sessions, registration windows, and add/drop deadlines from natural language or documents. Validates date ranges and handles overlapping sessions, linking terms to the year and sessions to their term. TRIGGER when: user asks to \"create an academic calendar\", \"set up semester dates\", \"generate the academic year\", \"add terms and sessions\", \"configure registration windows\", or \"add/drop deadlines\" — or uploads a calendar document (PDF, CSV, XLSX) containing term or session dates. DO NOT TRIGGER for querying or updating existing calendar records, scheduling courses, or configuring course offerings."
metadata:
  version: "1.0"
  domains:
    - "Education"
  minApiVersion: "68.0"
  accessCheck: "OrgPreferences.EducationCloudEnabled"
  cliTools:
    - tool: ["python3"]
      semver: ">=3.8"
  relatedSkills:
    - "education-cloud-multi-campus-configure"
---

# Education Cloud Academic Calendar Generation

Create the foundational academic calendar infrastructure for Education Cloud orgs, parsing calendar data from documents or natural language and generating validated Academic Year, Term, and Session records with proper date ranges and institutional linkage.

## Scope

- **In scope**: Academic Year records, Academic Term records (semester/quarter/trimester systems), Academic Session records (term subdivisions), registration windows, add/drop deadlines, date validation
- **Out of scope**: Course scheduling (delegate to course offering skills), individual course section dates, financial aid deadlines, exam schedules, institutional hierarchy setup (no dedicated skill exists yet for this — set up Accounts/campuses manually)

---

## Execution Model

All Salesforce operations use relative-path REST calls. Do not use CLI or shell commands to reach Salesforce (`sf`, `sfdx`, `curl`); the execution environment may not provide them. This does not apply to the skill's own local validation script (`scripts/validate_calendar_dates.py`, see step 4) — that runs locally and never touches the org.

- **Record CRUD**: sObject REST — `POST /services/data/<ver>/sobjects/<Object>`, `GET /services/data/<ver>/sobjects/<Object>/<Id>`, `PATCH /services/data/<ver>/sobjects/<Object>/<Id>`
- **Schema checks**: sObject describe — `GET /services/data/<ver>/sobjects/<Object>/describe` (confirm object + field API names exist before writing).
- **SOQL `/query` is routable**: `GET /services/data/<ver>/query` with the SOQL passed as a structured `queryParams: {"q": "..."}`, NOT inlined into the URL as `?q=...` — confirmed by live test: inlining `?q=` 404s (`ROUTE_NOT_FOUND`/`NOT_FOUND`) via headless-360 dispatch, while `queryParams` reliably 200s. Use it to list-scan for existing terms/sessions, or resolve records by the runtime Id captured at create time and read them back with a direct `GET .../sobjects/<Object>/<Id>` — either is valid.
- **All IDs are runtime variables** captured from create-response `body.id` — never hardcode a literal Salesforce Id.
- **Resolve API version dynamically** — see Execution Transport below. Do not hardcode a version.

---

## Required Inputs

Gather or infer before proceeding:

- **Calendar system**: Semester (Fall/Spring/Summer) or Quarter (Fall/Winter/Spring/Summer) or Trimester
- **Academic year span**: Start and end dates for the overall academic year
- **Term dates**: For each term - class start/end, registration open date, add/drop deadline
- **Session subdivisions**: Any sub-sessions within terms (e.g., Summer Session 1 and 2)

If the user provides a calendar document (PDF, CSV, spreadsheet), parse it to extract all dates. If the user provides natural language, ask for specific dates before proceeding.

Note: AcademicYear, AcademicTerm, and AcademicSession have no Account reference field — calendar records are not linked to a Business Account. Linkage is Year → Term (`AcademicYearId`) and Term → Session (`AcademicTermId`) only.

Defaults unless specified:
- Calendar system: **Semester** (Fall, Spring, Summer)
- Academic year naming: **"Academic Year YYYY-YYYY"** format
- Registration windows: **Open 3-4 months before term start**
- Add/drop deadlines: **2 weeks after term start**

---

## Execution Transport

1. **Resolve API version**: `GET /services/data/` (unversioned) via headless-360 dispatch. Response is a map of endpoint paths already resolved to the org's current max version (e.g. `"limits": "/services/data/v69.0/limits"`) — not an array with a `version` field. Extract the version from any returned path (regex `v\d+\.\d+`) and use it as `<ver>` for every call below.
2. **Probe transport health**: `GET /services/data/<ver>/limits` via headless-360 dispatch. 2xx → route all calls through it. On absent/4xx/5xx → probe other available transports (other Salesforce MCP, authenticated `sf` CLI, custom MCP) with the same read, use first healthy, announce it. None healthy → stop, ask user to connect one; never fabricate.

---

## Workflow

All steps are sequential. Do not skip or reorder. If blocked, stop and ask for missing context.

0. **Verify foundation prerequisites** — Follow `references/foundation_prerequisites.md`: org edition, Lightning Experience, Education Cloud license, running user's EDU access, Education Cloud Foundation enabled (self-heal via confirm-then-enable if off). Do not proceed to Step 1 until all checks pass.

1. **Confirm calendar system**
   - Ask user: semester, quarter, or trimester system?
   - Identify expected term names based on system type

2. **Gather calendar data**
   - If user provides document (PDF, CSV, spreadsheet): parse to extract year, term, and session dates
   - If user provides natural language: extract dates from description
   - If insufficient detail: ask for specific dates (term start/end, registration windows, deadlines)

3. **Verify object and field schema**
   - Before writing, confirm each object and every field you will set exists on the org:
     `GET /services/data/<ver>/sobjects/AcademicYear/describe`, `.../AcademicTerm/describe`, `.../AcademicSession/describe`
   - Read the `fields` array; match your intended field API names (`Name`, `AcademicYearId`, `StartDate`, `EndDate`, `RegistrationOpenDate`, `RegistrationCloseDate`, `Season`, `AcademicTermId`, `ClassStartDate`, `ClassEndDate`, `AddDropDeadline`) against it.
   - Note picklist field `Season` (`AcademicTerm.Season`, values `Fall`/`Spring`/`Summer`/`Winter`): only send values present in that field's `picklistValues`. `AcademicSession.Type` is a different picklist (`Semester`/`Trimester`/`Quarter`/etc.) not used by this workflow — do not confuse it with `Season`.
   - If a field is absent: STOP — do not POST with an unverified field name; report the mismatch to the user.

4. **Validate date ranges**
   - Assemble the gathered year/term/session data into the JSON shape documented at the top of `scripts/validate_calendar_dates.py`, then run it once:
     ```bash
     python3 scripts/validate_calendar_dates.py <<'EOF'
     {"academicYear": {...}, "terms": [...], "sessions": [...]}
     EOF
     ```
   - The script checks term end > start, year spans all terms, registration open < term start, add/drop deadline within term bounds, and session containment within parent term — and computes each term's `RegistrationCloseDate`.
   - If `valid` is `false`: stop, report each entry in `errors` to the user, and ask for corrected dates. Do not proceed to step 5.
   - `warnings` (e.g., intentional session overlaps) do not block — surface each one to the user for confirmation in step 6.
   - Carry `computedRegistrationCloseDates` forward — step 8 uses it instead of recalculating.

5. **Detect duplicate terms**
   - AcademicTerm `Name` is not unique-constrained, so a duplicate name will NOT error on insert. List-scan for existing terms with matching names before creating: `GET /services/data/<ver>/query` with `queryParams: {"q": "SELECT Id, Name, StartDate, EndDate FROM AcademicTerm WHERE Name = 'Fall 2025'"}` — pass the SOQL via `queryParams`, not inlined as `?q=` in the URL (inlining 404s) — or, if the user has previously created a calendar for this year in the same session, reuse the Ids captured then instead of re-creating.
   - If a duplicate name is found, compare dates and ask the user whether to update the existing record or skip.
   - If the duplicate-check read itself fails (non-2xx, transport error): STOP — do not proceed to create the term. Report the failure to the user and ask how to proceed; do not silently create a possibly-duplicate record.

6. **Display proposed calendar structure and confirm**
   - Present a summary of what will be created: Academic Year name and dates, then each term's name/dates/registration window/computed `RegistrationCloseDate`, then each session's name and dates grouped under its parent term. See `examples/sample-output.md` for a filled-in rendering.
   - For every session-overlap warning from step 4: state the overlap period and ask the user to confirm it's intentional.
   - Ask user: "Should I create all of these records?"
   - Wait for user confirmation before proceeding to step 7

7. **Create Academic Year record**
   - After user confirms in step 6, insert Academic Year:
     ```http
     POST /services/data/<ver>/sobjects/AcademicYear
     {"Name": "Academic Year 2025-2026"}
     ```
   - Capture `academicYearId` from the response `body.id` for term linkage
   - Report: "Academic Year created: Academic Year 2025-2026"

8. **Create Academic Term records**
   - For each term (Fall, Spring, Summer or Quarter equivalents), insert with `AcademicYearId` set to `academicYearId` from step 7:
     ```http
     POST /services/data/<ver>/sobjects/AcademicTerm
     {"Name": "Fall 2025", "Season": "Fall", "StartDate": "2025-08-18", "EndDate": "2025-12-12",
      "AcademicYearId": "<academicYearId>",
      "RegistrationOpenDate": "2025-04-01", "RegistrationCloseDate": "2025-08-17"}
     ```
     - `RegistrationCloseDate` comes from step 4's `computedRegistrationCloseDates[<term name>]` — do not recompute it by hand.
     - `Season` is a restricted picklist: `Fall`, `Spring`, `Summer`, `Winter`. AcademicTerm has NO add/drop field — add/drop deadlines live on AcademicSession only.
   - Capture each `termId` from the response `body.id` for session linkage
   - Report progress: "Created 3 terms: Fall 2025, Spring 2026, Summer 2026"

9. **Create Academic Session records**
   - For each session subdivision (e.g., Summer Session 1, Summer Session 2), insert with `AcademicTermId` set to the parent `termId` from step 8:
     ```http
     POST /services/data/<ver>/sobjects/AcademicSession
     {"Name": "Summer Session 1", "ClassStartDate": "2026-05-26", "ClassEndDate": "2026-07-03",
      "AddDropDeadline": "2026-06-11", "AcademicTermId": "<termId>"}
     ```
   - Report progress: "Created 2 sessions: Summer Session 1, Summer Session 2"

10. **Generate completion summary**
    - Display a final summary: the created Academic Year with its dates, each created Term with its date range, and each created Session grouped under its parent Term, plus a one-line note on the Year → Term → Session linkage. See `examples/sample-output.md` for a filled-in rendering.
    - If any sessions overlap (per step 4's warnings), note the overlap period and that it was confirmed intentional.
    - If any terms were skipped due to duplicates, list them with reason

---

## On-Demand Verification

Available at any time after step 10, not a required workflow step — use only when the user asks to spot-check a record or view a calendar range.

- **Specific record** (e.g., "show me Fall 2025"): cold-read by its captured Id — `GET /services/data/<ver>/query` with `queryParams: {"q": "SELECT Id,Name,Season,AcademicYearId,StartDate,EndDate,RegistrationOpenDate,RegistrationCloseDate FROM AcademicTerm WHERE Id='<termId>'"}` — or, if the Id was not captured, look it up by name with the same call and `queryParams: {"q": "SELECT Id FROM AcademicTerm WHERE Name = 'Fall 2025'"}` (pass the SOQL via `queryParams`, not inlined as `?q=` in the URL — inlining 404s). Display only the allowlisted fields in table format with parent hierarchy.
- **Calendar view** (e.g., "show all dates for Summer 2026"): cold-read the term and each child session by their captured Ids — `GET /services/data/<ver>/query` with `queryParams: {"q": "SELECT Id,Name,Season,AcademicYearId,StartDate,EndDate,RegistrationOpenDate,RegistrationCloseDate FROM AcademicTerm WHERE Id='<termId>'"}`, and the same call with `queryParams: {"q": "SELECT Id,Name,AcademicTermId,StartDate,EndDate,ClassStartDate,ClassEndDate,AddDropDeadline FROM AcademicSession WHERE Id='<sessionId>'"}` per session (a plain sObject GET with `?fields=` is not supported on headless-360, so select the calendar fields through SOQL) — and display as a table (Record Type, Name, Start Date, End Date, Duration, Registration Open, Registration Close, Add/Drop). Calculate and display overlap periods if applicable. See `examples/sample-output.md` for a filled-in rendering.

---

## Rules / Constraints

| Constraint | Rationale |
|-----------|-----------|
| Verify object + field API names via describe before writing | Prevents a failed POST on an unverified field; `Season` picklist values must match `AcademicTerm.Season`'s `picklistValues` |
| Term end date must be after start date | Platform validation will reject invalid date ranges |
| Registration window must open before term starts | Students cannot register after classes begin |
| Add/drop deadline (on AcademicSession) after or equal to term start | Deadline before classes start is logically invalid; AcademicTerm has no add/drop field |
| Academic Year must span all its child terms | Term dates outside year range cause reporting issues |
| Overlapping sessions within same term are allowed | Common pattern for Summer sessions (e.g., Session 1: May-Jul, Session 2: Jun-Aug) |
| Term names should match calendar system convention | Fall/Spring/Summer for semester, Fall/Winter/Spring/Summer for quarter |
| Resolve API version dynamically, don't hardcode | Org's max API version changes over time; a stale hardcoded version drifts from the org's current one |
| Check for duplicate terms via SOQL `/query` before creating, pass `q` via `queryParams` not inlined in the URL | `/query` is routable via headless-360, but only with `queryParams` — inlining `?q=` 404s (confirmed by live test); term `Name` is not unique-constrained so duplicates do not error on insert; a failed duplicate-check read must block creation, not be skipped |

---

## Gotchas

| Issue | Resolution |
|-------|------------|
| User provides relative dates ("next Fall") | Convert to absolute dates before inserting (e.g., "next Fall" → "Fall 2026" with specific dates) |
| Overlapping sessions flagged as error | Confirm with user — overlaps are intentional in many institutions (e.g., Summer Session 1 and 2 overlap by 1 week) |
| Duplicate term with different dates | Ask user whether to update existing or skip — do not auto-update without confirmation |
| Registration window after term start | This is invalid — ask user to provide correct registration open date |
| Academic Year end date before last term end date | Extend Academic Year to cover all terms, or adjust term dates |
| Input carries a term-level add/drop date but no session subdivisions | AcademicTerm has no add/drop field — surface the term-vs-session placement to the user or propose a session per term to carry the date; never write it onto AcademicTerm and never silently drop it |
| User provides 3-part year range (2025-2026-2027) | Clarify with user — Academic Year spans exactly 2 years (e.g., 2025-2026) |
| Session without parent term | Every session must link to a term — if user provides session dates without term, ask which term it belongs to |

---

## Output Expectations

Deliverables:

- **Academic Year record**: Single year record spanning all terms (e.g., "Academic Year 2025-2026")
- **Academic Term records**: 3-4 term records per year (Fall, Spring, Summer for semester; Fall, Winter, Spring, Summer for quarter)
- **Academic Session records**: 0-N session records (typically 2 Summer sessions for semester systems)
- **Summary report**: Table listing all created records with names, dates, and linkages

Terms link to the parent Academic Year (`AcademicYearId`); sessions link to the parent Term (`AcademicTermId`). These objects have no Account reference field.

---

## Cross-Skill Integration

| Need | Delegate to |
|------|-------------|
| Institutional hierarchy (Accounts, campuses) | No dedicated skill yet — set up manually |
| Course scheduling and offerings | Course offering generation skills |

---

## Reference File Index

| File | When to read |
|------|-------------|
| `references/foundation_prerequisites.md` | Step 0 — org edition, Lightning Experience, EDU license, permission set assignment, Education Cloud Foundation enablement; run before Step 1 on every standalone invocation |
| `references/calendar-systems.md` | When user's calendar system is unclear or non-standard |
| `references/date-validation.md` | When validating complex date overlaps or multi-session terms |
| `examples/semester-calendar.json` | To verify output structure for semester system |
| `examples/quarter-calendar.json` | To verify output structure for quarter system |
| `examples/sample-output.md` | To see filled-in renderings of the proposed-structure display, completion summary, and calendar-view table |
| `scripts/validate_calendar_dates.py` | Invoked in step 4 to validate date ranges and compute `RegistrationCloseDate` deterministically |

© forcedotcom · Apache-2.0 · forcedotcom/sf-skills

Похожие скиллы

Все скиллы по теме «Документы и офис» →
Salesforce Cloud aaronsb MCP-сервер Salesforce Cloud подключает Salesforce к Claude Code, Cursor, Codex и другим агентам через SOQL-запросы и анализ сделок. Агент читает воронку, находит похожие выигранные сделки и генерирует бизнес-кейсы прямо в чате. CX Codex +1 ★ 6звёзд репо Devart MCP Server for Salesforce Marketing Cloud (ADO.NET) devart-ai-connectivity Devart MCP Server for Salesforce Marketing Cloud (ADO.NET) — MCP-сервер для Claude Code, который даёт доступ к данным Salesforce Marketing Cloud: превращает запрос на естественном языке в SQL и возвращает результат. CX Codex +1 generate-leads gtmagents Строит список лидов по критериям ICP: отрасль, размер компании, стек, география. Запускается с флагом --enrich comprehensive, чтобы получить карту комитета по закупкам, технографику и сигналы намерения. CX Codex +1 ★ 450звёзд репо academic-pptx Gabberflast Скилл academic-pptx задаёт правила структуры и оформления академических презентаций для защиты диссертаций, докладов на конференциях и отчётов по грантам. CX Codex +1 1 400установок office-academic-skill zLanqing Скилл office-academic-skill для Claude Code разбирает научные статьи и готовит отчёты Word и презентации PowerPoint. Работает с DOCX/PPTX и проверяет их оформление. CX Codex +1 978установок academic-slides EvoScientist Скилл academic-slides помогает собрать структуру научного доклада, разложить статью на слайды и сгенерировать файл .pptx для защиты или конференции. CX Codex +1 513установок

Из того же набора232

Весь набор →
service-omni-command-center-analyze Скилл service-omni-command-center-analyze для Claude Code анализирует, выбрать ли Command Center V2 или классический Omni Supervisor, и рекомендует следующий шаг без изменений в организации. CX Codex +1 132установок experience-lwc-widget-assess Скилл experience-lwc-widget-assess для Claude Code оценивает, можно ли представить Lightning Web Component как декларативный виджет HXL. CX Codex +1 129установок life-sciences-fieldsalesrep-coordinate Скилл life-sciences-fieldsalesrep-coordinate запускает все пять этапов настройки Life Sciences Cloud для торгового представителя подряд, с проверкой перед каждым следующим шагом. CX Codex +1 128установок experience-lwc-widget-migrate Скилл experience-lwc-widget-migrate для Claude Code переносит существующий Lightning Web Component (LWC) в декларативный виджет HXL / Agentforce. Запускается по запросу переделать конкретный LWC в виджет. CX Codex +1 126установок life-sciences-kam-coordinate Скилл life-sciences-kam-coordinate для Claude Code пошагово настраивает Life Sciences Cloud в выбранной Salesforce org для роли Key Account Management (KAM). CX Codex +1 123установок education-cloud-course-catalog-migrate Скилл education-cloud-course-catalog-migrate переносит каталог курсов из CSV, PDF или сайта в Education Cloud: парсит данные, создаёт объекты Learning и LearningCourse через REST API, связывает лекции с лабораторными. CX Codex +1 117установок service-omni-queue-deploy Скилл service-omni-queue-deploy для Claude Code проверяет или создаёт очередь в Salesforce для маршрутизируемых объектов через привязку QueueSobject. Задача запускается в CI или агентом при настройке омниканальной маршрутизации. CX Codex +1 116установок service-omni-routing-flow-deploy Скилл service-omni-routing-flow-deploy для Claude Code развёртывает Flow маршрутизации Omni-Channel для Case или VoiceCall. По запросу настраивает маршрутизацию в очередь или по навыкам и проверяет результат. CX Codex +1 116установок

Спонсоры проекта

Компании, которые помогают держать аналитику открытой