Schedule Facebook Story Post
Use this skill only in a workspace that supplies the Page's editorial rules and a deterministic local Facebook publisher. Keep editorial work separate from mechanical publishing.
Require workspace configuration
Before writing or scheduling, locate and read the workspace's content-memory or editorial-rules file completely. Confirm it defines:
- the Page identity, audience, voice, and required languages;
- post folder convention and required deliverables;
- image style and source-file requirements;
- publishing timezone and target time;
- local publisher command(s), CDP address, duplicate-state location, and image/caption metadata format.
Stop and ask for configuration when any of these are absent. Do not infer a Page identity, reuse another Page's credentials, copy cookies/passwords, or expose CDP beyond loopback.
Create a story package
- Select an unused established folktale, fairy tale, or classic fable consistent with the workspace rules. Rotate cultural tradition and visual setting from recent posts.
- Browse trustworthy primary, public-domain, cultural, or academic sources to verify title, tradition, plot, and ending. Retell in fresh words; do not copy a modern translation.
- Create the required post folder with the configured caption file, source notes, image prompt, source image, upload-ready image, bilingual alt text, and any Page-specific metadata.
- Follow the workspace's required reading length, copy format, hashtags, and comments. Preserve plot sequence and consequence; soften graphic wording only without inventing events or changing the ending.
- Generate a language-neutral image with the configured image-generation workflow. Exclude embedded text, logos, watermarks, and unrelated brands unless the workspace explicitly requires them.
- Inspect the final upload image visually and verify its required dimensions. Update the workspace content memory only after every required file passes.
Publish with one Composer tab
- Start the dedicated Chrome profile once at its configured loopback CDP address. Check that it is authenticated and using the configured Page identity.
- Run exactly one dry-run with the workspace publisher. The publisher must close the dry-run Composer tab after saving its screenshot.
- Validate the structured result and screenshot together:
- configured Page identity;
- intended main-language caption only;
- correct upload-ready image;
- correct scheduled date, timezone, and time;
Schedule available and Publish absent.
- If a validation field is wrong, correct the deterministic publisher sequence and run one replacement dry-run. Do not accumulate Composer tabs.
- Click the final Meta action only with explicit user authorization to schedule. Never bypass the publisher's duplicate guard.
- Count success only when Meta displays a scheduling confirmation. Save the evidence screenshot and, where supported, verify the entry in Planner.
- Close the scheduled Composer tab and the dedicated Chrome profile when no longer needed, without affecting unrelated browser profiles.
Common Meta controls
- Treat masked date inputs as text fields: select all, clear, type
MM/DD/YYYY, then blur.
- Set AM/PM before the hour, because Meta may normalize the hour after an AM/PM change.
- On login, 2FA, CAPTCHA, or checkpoint, stop and ask the user to complete it in the dedicated window.
- If Meta changes labels or layout, update selectors only after a new dry-run; never guess through the final action.
Delivery
Return the main-language post and the required secondary-language comment in separate paste-ready code blocks. Then give a short image link and scheduling status. Clearly state any platform limitation, such as an inability to attach the first comment during scheduling.
1---2name: schedule-fb-post-story3description: Create, validate, illustrate, and schedule a bilingual bedtime-story Facebook post for any configured Page through its local Chrome CDP publisher. Use when asked to make the next verified traditional story, generate its Facebook image, prepare or dry-run a Meta Business Suite composer, schedule a story post, check Facebook login/CDP state, or diagnose this Page publishing workflow.4---56# Schedule Facebook Story Post78Use this skill only in a workspace that supplies the Page's editorial rules and a deterministic local Facebook publisher. Keep editorial work separate from mechanical publishing.910## Require workspace configuration1112Before writing or scheduling, locate and read the workspace's content-memory or editorial-rules file completely. Confirm it defines:1314- the Page identity, audience, voice, and required languages;15- post folder convention and required deliverables;16- image style and source-file requirements;17- publishing timezone and target time;18- local publisher command(s), CDP address, duplicate-state location, and image/caption metadata format.1920Stop and ask for configuration when any of these are absent. Do not infer a Page identity, reuse another Page's credentials, copy cookies/passwords, or expose CDP beyond loopback.2122## Create a story package23241. Select an unused established folktale, fairy tale, or classic fable consistent with the workspace rules. Rotate cultural tradition and visual setting from recent posts.252. Browse trustworthy primary, public-domain, cultural, or academic sources to verify title, tradition, plot, and ending. Retell in fresh words; do not copy a modern translation.263. Create the required post folder with the configured caption file, source notes, image prompt, source image, upload-ready image, bilingual alt text, and any Page-specific metadata.274. Follow the workspace's required reading length, copy format, hashtags, and comments. Preserve plot sequence and consequence; soften graphic wording only without inventing events or changing the ending.285. Generate a language-neutral image with the configured image-generation workflow. Exclude embedded text, logos, watermarks, and unrelated brands unless the workspace explicitly requires them.296. Inspect the final upload image visually and verify its required dimensions. Update the workspace content memory only after every required file passes.3031## Publish with one Composer tab32331. Start the dedicated Chrome profile once at its configured loopback CDP address. Check that it is authenticated and using the configured Page identity.342. Run exactly one dry-run with the workspace publisher. The publisher must close the dry-run Composer tab after saving its screenshot.353. Validate the structured result and screenshot together:36 - configured Page identity;37 - intended main-language caption only;38 - correct upload-ready image;39 - correct scheduled date, timezone, and time;40 - `Schedule` available and `Publish` absent.414. If a validation field is wrong, correct the deterministic publisher sequence and run one replacement dry-run. Do not accumulate Composer tabs.425. Click the final Meta action only with explicit user authorization to schedule. Never bypass the publisher's duplicate guard.436. Count success only when Meta displays a scheduling confirmation. Save the evidence screenshot and, where supported, verify the entry in Planner.447. Close the scheduled Composer tab and the dedicated Chrome profile when no longer needed, without affecting unrelated browser profiles.4546## Common Meta controls4748- Treat masked date inputs as text fields: select all, clear, type `MM/DD/YYYY`, then blur.49- Set AM/PM before the hour, because Meta may normalize the hour after an AM/PM change.50- On login, 2FA, CAPTCHA, or checkpoint, stop and ask the user to complete it in the dedicated window.51- If Meta changes labels or layout, update selectors only after a new dry-run; never guess through the final action.5253## Delivery5455Return the main-language post and the required secondary-language comment in separate paste-ready code blocks. Then give a short image link and scheduling status. Clearly state any platform limitation, such as an inability to attach the first comment during scheduling.
thminhVN