@easysociable/cli 0.1.11 → 0.1.12

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@easysociable/cli",
-  "version": "0.1.11",
+  "version": "0.1.12",
   "description": "Agent-first CLI for EasySociable: Content Engine, Template, Slideshow, and MCP",
   "type": "module",
   "license": "MIT",

package/skills/easysociable-slideshow/SKILL.md

@@ -26,9 +26,15 @@ Page order is the argument of **this pack**, not a catalog recipe.
 3. Choose a Brand (or Profile/Theme) and an explicit Page Template for every
    page. The server never silently chooses or replaces a Page Template.
    Prefer templates already chosen on the Content Engine pack (**Template
-   Selection** after **Page Contracts**). Otherwise select by **platform +
-   canvas + slotSummary + density + layoutFamily**. `role` / `supportedRoles`
-   are weak retrieval tags, not sequence position.
+   Selection** after **Page Contracts**). Otherwise get a shortlist from
+   `easysociable slideshows recommend --file contracts.json --seed <slug>`
+   (MCP `recommend_slideshow_templates`) and pick one per page with a reason.
+   The recommender filters platform + native canvas + slotSummary + cover rule,
+   demotes Layout Families used in the owner's recent Runs, and keeps one
+   unused family per page. `role` / `supportedRoles` are weak retrieval tags,
+   not sequence position. Never browse with bare `templates list` (first 20
+   ids only); use `--platform <p> --all` if you must see the full catalog.
+   Do not copy a previous pack's Template Selection as the default.
 4. **Cover / hook placement (hard):** a template is cover/hook class when
    `supportedRoles` includes `cover` or `hook`. `pages[0]` must use one.
    Cover/hook class templates must not appear on any later page. Later pages
@@ -81,10 +87,13 @@ Page order is the argument of **this pack**, not a catalog recipe.
    `python3 scripts/validate-pack.py runs/<slug>/pack.md` (in the Content Engine).
    Refuse create if contracts are empty or contain `templateId`.
 3. Resolve or create the user's Brand through the unified CLI/MCP.
-4. Prefer pack **Template Selection** ids. If re-listing the catalog, verify
-   hard filters and cover/hook placement; never place a cover/hook class
-   template after page 1. Record Layout Family evidence as `hypothesis` unless
-   comparable history supports `tested` / `supported`.
+4. Prefer pack **Template Selection** ids. Otherwise run
+   `easysociable slideshows recommend --file contracts.json --seed <slug> --json`
+   and choose from each page's `candidates`; never place a cover/hook class
+   template after page 1. Report `gaps` (pages with < 2 role-matching
+   templates) to the user as authoring backlog. Record Layout Family evidence
+   as `hypothesis` unless published comparable results support `tested` /
+   `supported` — a template having been used before is not evidence.
 5. List existing Runs when the Pack has a stable content slug:
 
    ```bash

package/skills/easysociable-slideshow/workflows/CREATE_RUN.md

@@ -11,12 +11,14 @@
    `pageTemplateId`s from Template Selection (explicit — server must not
    silent-replace).
 4. Check platform hardMin/hardMax.
-5. List published Page Templates only to **verify** hard filters still hold:
-   platform → canvas → slotSummary → density → page-position cover/hook.
-   Prefer ranking by Layout Family (`layoutFamily`) + history; `supportedRoles`
-   is a weak tag. `pages[0]` must be cover/hook class. Do not use that class on
-   later pages. Prefer families already recorded on linked W- judgments
-   (`fits` / `avoid` / `trial`) when comparable evidence exists.
+5. No Template Selection on the pack → shortlist with
+   `easysociable slideshows recommend --file contracts.json --seed <slug> --json`
+   (MCP `recommend_slideshow_templates`). Input is the Page Contracts:
+   `{ platform, pages: [{ role, density?, slotSummary?: { text, number, image }, requiresImage? }] }`.
+   Pick one candidate per page and record the reason; `supportedRoles` is a
+   weak tag. `pages[0]` must be cover/hook class. Do not use that class on
+   later pages. W- judgments (`fits` / `avoid`) with comparable evidence may
+   override the recommender's order. Surface `gaps` to the user.
 6. If `contentSlug` already has a Run: update only when topology matches
    (same page count and `pageTemplateId`s). Otherwise create a new Run.
 7. **Before** `create_run` / `slideshows create` (every create, not only the