跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
效率与协作

parse-calendar

Parse a monthly content calendar from DOCX, XLSX, Notion, or pasted text into structured calendar-data.json — the source of truth every downstream skill reads. Triggers on \"/parse-calendar\", \"parse the calendar\", \"import this calendar\", \"here is the month\", \"load the content plan\", \"calendar to JSON\", or whenever a client calendar arrives in any format. No calendar yet? /socialforge:ideate-month drafts one in this exact shape.

indranilbanerjee · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add indranilbanerjee/socialforge --skill parse-calendar

技能说明


name: parse-calendar description: "Parse a monthly content calendar from DOCX, XLSX, Notion, or pasted text into structured calendar-data.json — the source of truth every downstream skill reads. Triggers on "/parse-calendar", "parse the calendar", "import this calendar", "here is the month", "load the content plan", "calendar to JSON", or whenever a client calendar arrives in any format. No calendar yet? /socialforge:ideate-month drafts one in this exact shape." argument-hint: "[file-path or Notion URL]" effort: medium user-invocable: true

/socialforge:parse-calendar — Calendar Parser

Parse a monthly social media content calendar into structured JSON that drives the entire production pipeline.

Context efficiency

Asset-heavy skill. Grep before Read the asset catalog (${CLAUDE_PLUGIN_DATA}/socialforge/brands/<brand>/asset-index.json) — never list the asset directory. Reference generated images / videos by path, not by loading metadata. Brand profile loads once per session.

Supported Formats

FormatHow It Works
DOCXRead tables and structured text from Word documents
XLSXRead rows from Excel spreadsheets (one row per post)
NotionRead from Notion database via MCP (requires Notion connector)
Structured textParse markdown or plain text with consistent formatting

Required Fields Per Post

Every post in the calendar must have (or the system will ask for missing ones):

FieldRequiredDescription
post_idAuto-generatedUnique identifier (e.g., P01, P02)
dateYesPublishing date (YYYY-MM-DD)
platformYesTarget platform(s) — linkedin, instagram, x, facebook, etc.
content_typeYesstatic, carousel, video, story, reel, text_only
tierYesHERO, HUB, or HYGIENE
topicYesWhat the post is about
caption_briefYesBrief description of the copy direction
visual_briefRecommendedWhat the image should show
hashtagsOptionalPost-specific hashtags (brand hashtags added automatically)
ctaOptionalCall-to-action text or link
campaignOptionalCampaign this post belongs to
notesOptionalSpecial instructions

Process

  1. Detect format — Check file extension or URL pattern
  2. Extract posts — Parse each post entry from the source
  3. Validate fields — Check required fields present. For missing fields, ask the user.
  4. Normalize — Standardize dates, platform names, content types to schema format
  5. Assign post IDs — Sequential (P01, P02, ...) if not already present
  6. Cross-reference platforms — Check all platforms exist in brand's platform-config.json
  7. Flag issues — Duplicate dates, missing briefs, unsupported content types
  8. Save — Write calendar-data.json to ${CLAUDE_PLUGIN_DATA}/socialforge/output/{brand}/{YYYY-MM}/ (falls back to ~/socialforge-workspace/output/... when ${CLAUDE_PLUGIN_DATA} is unset)

Output

Calendar parsed: 28 posts for April 2026
  LinkedIn: 12 posts (4 carousels, 6 static, 2 video)
  Instagram: 10 posts (3 carousels, 4 reels, 3 static)
  X: 6 posts (all text+image)

Issues found: 2
  - P14: Missing visual_brief (will need manual input during asset matching)
  - P22: Date falls on Sunday — confirm intentional weekend post?

Calendar saved: ${CLAUDE_PLUGIN_DATA}/socialforge/output/acme-corp/2026-04/calendar-data.json

After Parsing

Ask: "Would you like to:

  • Match assets to posts? (/socialforge:match-assets)
  • Review the parsed calendar first? (I'll show the full post list)
  • Fix issues? (I'll walk through each flagged item)"

Timeout & Fallback

  • DOCX/XLSX parsing: 30-second timeout. If file is too large, suggest splitting by week.
  • Notion: 60-second timeout per database query. If Notion is slow, offer to export and parse locally.
  • If format is unrecognized: Ask user to describe the structure, then parse adaptively.