Sync third-party and MCP marketplace plugins

Constraint: Public skills are published only by explicit administrator action unless they are tracked third-party market sources. Confidence: high Scope-risk: narrow Directive: Keep private/internal skills out of the public marketplace and preserve normal incremental market Git history. Tested: Marketplace validation passed.
2026-08-22 00:01:57 +08:00
parent dc35e1cbf3
commit 0633dfb289
17 changed files with 52 additions and 43 deletions
@@ -51,8 +51,8 @@
      "repo": "https://github.com/Leonxlnx/taste-skill.git",
      "ref": "main",
      "adapter": "skill-collection",
-      "commit": "dfb6f9f9e93a39f673b1827c0889cc28326d1800",
-      "syncedAt": "2026-08-18T16:00:00Z"
+      "commit": "843c8dd4d18ccff0d5a9cd4b0b71d7dbf7278293",
+      "syncedAt": "2026-08-21T15:59:59Z"
    },
    {
      "id": "shadcn",
@@ -60,8 +60,8 @@
      "repo": "https://github.com/shadcn-ui/ui.git",
      "ref": "main",
      "adapter": "claude-skill",
-      "commit": "19b67204fb80b7a7c233c967e4cf3aed73810f80",
-      "syncedAt": "2026-08-21T06:41:32Z"
+      "commit": "c06da1d0e91e97b607d1359372347528bb35b090",
+      "syncedAt": "2026-08-21T15:59:59Z"
    },
    {
      "id": "frontend-slides",
@@ -96,8 +96,8 @@
      "repo": "https://github.com/hugohe3/ppt-master.git",
      "ref": "main",
      "adapter": "claude-skill",
-      "commit": "fb6e5ac969bb066f1f6fa5dcd14349f0813e9e7a",
-      "syncedAt": "2026-08-21T06:41:32Z"
+      "commit": "cdabb4e5e0703651f88738df8b5f43eaee7fd50c",
+      "syncedAt": "2026-08-21T15:59:59Z"
    },
    {
      "id": "grill-me",
@@ -105,8 +105,8 @@
      "repo": "https://github.com/mattpocock/skills.git",
      "ref": "main",
      "adapter": "skill-collection",
-      "commit": "0ab1b63a410a03d3627979a109c8695de27af954",
-      "syncedAt": "2026-08-20T16:00:00Z"
+      "commit": "5b15a47f2d7150f545fbcacbfe381787fc0230dc",
+      "syncedAt": "2026-08-21T15:59:59Z"
    },
    {
      "id": "next-skills",
@@ -114,8 +114,8 @@
      "repo": "https://github.com/vercel/next.js.git",
      "ref": "canary",
      "adapter": "skill-collection",
-      "commit": "14a69ef78b94c9bdb68b2f1d5d1a55599ff8022c",
-      "syncedAt": "2026-08-21T06:41:32Z"
+      "commit": "1c86b8a4fa3bb8795e25fd49bbbd10844dd83263",
+      "syncedAt": "2026-08-21T15:59:59Z"
    }
  ]
 }
@@ -2,8 +2,8 @@
  "sourceId": "grill-me",
  "repo": "https://github.com/mattpocock/skills.git",
  "ref": "main",
-  "commit": "0ab1b63a410a03d3627979a109c8695de27af954",
+  "commit": "5b15a47f2d7150f545fbcacbfe381787fc0230dc",
  "adapter": "skill-collection",
  "sourcePath": "skills/productivity",
-  "syncedAt": "2026-08-20T16:00:00Z"
+  "syncedAt": "2026-08-21T15:59:59Z"
 }
@@ -3,5 +3,5 @@
  "name": "playwright浏览器自动化操作",
  "version": "20260605",
  "keySource": "none",
-  "syncedAt": "2026-08-21T06:43:26Z"
+  "syncedAt": "2026-08-21T16:01:56Z"
 }
@@ -2,8 +2,8 @@
  "sourceId": "next-skills",
  "repo": "https://github.com/vercel/next.js.git",
  "ref": "canary",
-  "commit": "14a69ef78b94c9bdb68b2f1d5d1a55599ff8022c",
+  "commit": "1c86b8a4fa3bb8795e25fd49bbbd10844dd83263",
  "adapter": "skill-collection",
  "sourcePath": "skills",
-  "syncedAt": "2026-08-21T06:41:32Z"
+  "syncedAt": "2026-08-21T15:59:59Z"
 }
@@ -56,7 +56,7 @@ If `partialPrefetching: true` is already set in `next.config.ts`, the app is ado

 The work is identical either way — only the commit boundaries differ. Default by app size: one branch for a handful of links, route by route when the audit is big enough that reviewers need smaller diffs. Note the choice in your report.

-Enumerate the prefetch sites across the whole source tree, not only `app/` — they often live in `src/components` or shared UI packages: `rg -n '\bprefetch\b|router\.prefetch' -g '*.tsx' -g '*.jsx' .`. Keep the `<Link prefetch={true}>` and bare-prop matches (a bare prop is `true`) as the over-prefetching links this audit adopts destinations for, and drop `prefetch={false}` and other values. Also audit existing imperative [`router.prefetch()`](https://nextjs.org/docs/app/api-reference/functions/use-router#userouter) call sites with the same table, because they can be preserving the same "fetch before navigation" behavior and have no dev insight. For new navigation prefetching, prefer [`<Link>`](https://nextjs.org/docs/app/api-reference/components/link), which the docs call the primary navigation API; use [`router.prefetch()`](https://nextjs.org/docs/app/guides/prefetching#manual-prefetch) only for manual prefetching. If the app already passes an internal `kind` option, treat that as existing implementation detail, not a pattern to spread. If nothing matches, check for a custom link wrapper before calling the audit empty. If there's still nothing, say so in your report and move on to [step 2](#step-2-enable-the-flag).
+Enumerate the prefetch sites across the whole source tree, not only `app/` — they often live in `src/components` or shared UI packages: `rg -n '\bprefetch\b|router\.prefetch' -g '*.tsx' -g '*.jsx' .`. Keep the `<Link prefetch={true}>` and bare-prop matches (a bare prop is `true`) as the over-prefetching links this audit adopts destinations for, and drop `prefetch={false}` and other values. Also audit existing imperative [`router.prefetch()`](https://nextjs.org/docs/app/api-reference/functions/use-router#userouter) call sites with the same table, because they can be preserving the same "fetch before navigation" behavior and have no dev insight. For new navigation prefetching, prefer [`<Link>`](https://nextjs.org/docs/app/api-reference/components/link), which the docs call the primary navigation API; use [`router.prefetch()`](https://nextjs.org/docs/app/guides/prefetching#manual-prefetch) only for manual prefetching. If the app already passes an internal `kind` option, treat that as existing implementation detail, not a pattern to spread. Always inspect custom Link wrappers and trace their consumers: a wrapper can call `router.prefetch()` on hover or touch while a consumer omits `prefetch` or passes `prefetch={false}`. Record the declarative and imperative behavior separately, and use keyboard activation when verifying the declarative path so hover prefetching does not mask it. If nothing matches, say so in your report and move on to [step 2](#step-2-enable-the-flag).

 Then, for each one:

@@ -80,6 +80,8 @@ Then, for each one:

 3. **Preserve what that prefetch delivered.** The guide's [audit table](https://nextjs.org/docs/app/guides/adopting-partial-prefetching#auditing-link-prefetchtrue-calls) is the canonical decision — fetch it and apply the matching row. Caching uncached content is the judgment call in that table: trace where the data comes from and what freshness and revalidation it needs, per the [`use cache`](https://nextjs.org/docs/app/api-reference/directives/use-cache) docs, and ask the user when the answer isn't clear-cut. The URL-data routes you marked in the previous item wait for step 5.

+   If the repository already has `instant()` e2e coverage for a destination, run it before editing and preserve its assertion as the contract. A successful build or completed navigation does not prove that the same UI was prefetched. If caching the primary data loader still leaves only a fallback inside `instant()`, inspect rendered descendants and providers for dynamic work, then expand the cache only to the smallest coherent rendered subtree that restores the contract.
+
 > **If you add `use cache`, verify under `next start`, not only the build.** A `cookies()`/`headers()`/session read anywhere in the cached call tree throws at request time while `next build` passes clean. See [`use cache`](https://nextjs.org/docs/app/api-reference/directives/use-cache).

 ## step 2: enable the flag
@@ -2,8 +2,8 @@
  "sourceId": "ppt-master",
  "repo": "https://github.com/hugohe3/ppt-master.git",
  "ref": "main",
-  "commit": "fb6e5ac969bb066f1f6fa5dcd14349f0813e9e7a",
+  "commit": "cdabb4e5e0703651f88738df8b5f43eaee7fd50c",
  "adapter": "claude-skill",
  "sourcePath": "skills/ppt-master",
-  "syncedAt": "2026-08-21T06:41:32Z"
+  "syncedAt": "2026-08-21T15:59:59Z"
 }
@@ -35,10 +35,11 @@ Evaluate branches from each object's actual information model, not only from a C

 **Mandatory — select by visual job**: establish each page's semantic skeleton,
 then run the already-loaded [`svg-effects.md`](./svg-effects.md) §6.1 procedure
-and Visual Job Router before finalizing; use §6.13 for a coordinated page
-recipe when useful. The catalog expands construction vocabulary; it creates no
-effect quota. Active cross-page continuous action additionally loads
-[`animations.md`](./animations.md) §3.1 before authoring both endpoints.
+before finalizing, with its Visual Job Router as recall; use §6.13 for a
+coordinated page recipe when useful. The catalog expands construction
+vocabulary; it creates no effect quota. Active cross-page continuous action
+additionally loads [`animations.md`](./animations.md) §3.1 before authoring
+both endpoints.

 **Hard rule — discovery does not expand compatibility**: Follow
 `svg-effects.md` syntax and fallbacks; unsupported source/backdrop blur, blend
@@ -8,9 +8,9 @@ Compact composition vocabulary for prepared images and illustrations. Use the pa

 | Boundary | Rule |
 |---|---|
-| Selection | **Reference — not a constraint**: use any pattern, combine compatible ones, or author a clearer free-form composition; no ID, family, or coverage quota applies |
+| Selection | **Reference — not a constraint**: use any pattern, combine compatible ones, or author a clearer free-form composition. These entries seed technique; inventing one the catalog never names is equally valid, and no ID, family, or coverage quota applies |
 | Canonical IDs | Two-level prompt handles such as `#P1-01` and `#M2-01`; the letters expose composition responsibility, the first digit selects a family, and the final number follows current browse order. No legacy aliases or exporter mapping |
-| Composition grammar | Select one or more compatible `P` structures, then add only useful `M`, prepared `A`, or cross-page `C` patterns |
+| Composition grammar | Choose the page relationship, then add only the treatments a job needs; `P`, `M`, prepared `A`, and cross-page `C` name the catalogued form of each choice, and an uncatalogued one fills the same slot |
 | Effect options | Direction, side, position, proportion, contour, and intensity are options stated after the ID; they do not create another pattern |
 | Asset ownership | Consume prepared project-local assets; no acquisition or processing during SVG realization |
 | Exact information | Keep exact or editable text, data, labels, and annotations native |
@@ -219,9 +219,9 @@ If motion is enabled, [`animations.md`](./animations.md) owns its implementation

 | Pass | Decision |
 |---|---|
-| Skeleton | Select the `P` relationship: one visual field, comparison, sequence, evidence view, or multi-image system. Compatible Primaries may share one page |
+| Skeleton | Select the page relationship: one visual field, comparison, sequence, evidence view, multi-image system, or another the page needs; `P` entries name the catalogued ones. Compatible relationships may share one page |
 | Job | Name the concrete integration need or stylistic role: contrast, aspect fit, focus, reveal/opening, peer cohesion, exact native information, or a recurring depth/print gesture |
-| Apply | Add the smallest `M` that serves each chosen job; add no technique without a job |
+| Apply | Add the smallest treatment that serves each chosen job, `M` when one already fits; add no technique without a job |
 | Prepared asset | Use `A` only when the named project-local composite, cutout, or derivative already exists |
 | Continuity | Add `C` only when adjacent pages deliberately share a persistent state, camera relationship, or matched framing |
 | Integrate | Reuse contours, baselines, gap rhythm, palette, and required registration so the layers read as one composition |
@@ -26,7 +26,7 @@ Mandatory reference for every route that authors or regenerates slide visuals th
 | Containers | Use a card or panel when it expresses grouping, hierarchy, boundary, capacity, or a distinct material plane. Otherwise prefer spacing, rules, or direct text / geometry; peer containers share treatment unless a semantic difference justifies contrast. An unplanned repeated web-card grid is a carrier / topology problem, not a reason to suppress meaningful borders, shapes, or containers. |
 | Titles and page chrome | Treat the semantic page title as part of the current composition rather than an automatic fixed header band; its position, scale, and relationship may change with page role while preserving the active route's content invariants. Add or retain running headers, footers, and page numbers only when they carry navigation, identity, attribution, or another explicit page job. Fidelity profiles preserve required source chrome. |

-**Default — active effects vocabulary (may resolve to no added technique when no visual job is diagnosed)**: Default and Quick Generate run the already-loaded [`svg-effects.md`](./svg-effects.md) §6.1 Visual Job Router before completing each page; apply a compatible technique only for a diagnosed visual job.
+**Default — active effects vocabulary (may resolve to no added technique when no visual job is diagnosed)**: Default and Quick Generate complete the already-loaded [`svg-effects.md`](./svg-effects.md) §6.1 job diagnostic, which that file makes mandatory, before completing each page; whether any compatible technique is then added is this default's call, with the Visual Job Router as recall.

 **Fidelity labels**:

@@ -83,7 +83,7 @@ References describe visual intent: AI uses subject + intent + composition withou

 **Mandatory**: each placed row gets one executable `Layout pattern`. It is preferred expression, not locked geometry; optional hierarchical ids from the already-read [`image-layout-patterns.md`](./image-layout-patterns.md) must be exact. They are prompt lookup handles for Executor, not exporter effect codes. Executor may adopt, adapt, or decline the suggestion while preserving resource identity/source, must-use status, crop/content, and explicit user/template constraints; layout-only changes need no upstream rewrite.

-**Default — action-bearing image plan (may override when restraint better serves the page)**: For a `hero_page` or other image-led row, name an image/content or image/shape action—not position, size, crop, or legibility scrim alone. Plain split and full bleed remain valid when clearest.
+**Mandatory — job-bearing entry for image-led `adaptive` rows**: name the page job the image resolves alongside the composition serving it. A bare skeleton id, or position, size, crop, or legibility scrim alone, names no job: the entry stays incomplete until it says what the image does to the content or to the page's shapes. The already-read [`image-layout-patterns.md`](./image-layout-patterns.md) is recall for that composition, never a menu — an unlisted combination or a technique it never names answers a job just as well, and the job is never restated to reach a listed entry. Plain split and full bleed stay valid when the named job is best served plainly. A `no-crop` or supporting row keeps one concise suggestion instead.

 Choose narrative intent before dimensions, then apply the already-read [`image-layout-spec.md`](./image-layout-spec.md) to the actual page region. Techniques needing a cutout, blurred crop, or desaturated copy require that prepared asset. Write `Crop Policy: no-crop` whenever cropping could remove required pixels, labels, evidence, identity, or edge content; screenshots, charts, certificates/contracts, dense diagrams, logos, and product markings are common triggers rather than an exhaustive list. Otherwise write `Crop Policy: adaptive`: Executor may use complete display or a focal-safe crop, and the value never commands cropping.

@@ -10,8 +10,9 @@ Authority for advanced paint, effects, transforms, freeform/radial geometry, and

 **Mandatory**: Default and Quick Generate read this file completely before SVG
 authoring and keep its compatible techniques in active construction vocabulary.
-Before finalizing each page, run the §6.1 selection procedure and Visual Job
-Router. Use §6.13 when diagnosed jobs benefit from one coordinated page recipe.
+Before finalizing each page, run the §6.1 selection procedure, with the Visual
+Job Router as recall for the jobs it diagnoses. Use §6.13 when diagnosed
+jobs benefit from one coordinated page recipe.

 **Default — situational use (may override when plain construction is stronger)**:
 “Advanced” means capability depth, not an effect quota. During page authoring,
@@ -22,7 +23,7 @@ rhythm, and style; apply those that materially help.

 | Decision layer | Authority |
 |---|---|
-| Technical validity | Required / Forbidden / Conditional contracts in this file |
+| Technical validity | Required / Forbidden / Conditional contracts in this file, over the shared core's closed authoring surface, the route's other required construction references, and any triggered module |
 | Project values | Default: `<project_path>/spec_lock.md` anchors plus retained Design Spec/page context; Quick: anchors resolved in the current context |
 | Aesthetic fit | Locked or Quick-resolved `visual_style` / `visual_style_behavior` |
 | Per-page choice | Content purpose, hierarchy, legibility, semantics, and rhythm |
@@ -35,7 +36,7 @@ visual job.
 | Pass | Decision |
 |---|---|
 | Skeleton / diagnose | Establish native information, relationships, and hierarchy. Before completion, check image/text integration, plane separation, focus, state/direction, material/style, and the recurring motif; keep plain construction when none needs treatment. |
-| Surface / select | Name the target, confirm its owning subsection and fidelity, then use the Router. Choose a compatible technique that fully performs the job; prefer simpler/native-stable alternatives only when communication is equal. `Approximate` requires review, not automatic rejection. |
+| Surface / select | Name the target, confirm its owning subsection and fidelity, and let the Router recall candidates. Choose a compatible technique that fully performs the job; prefer simpler/native-stable alternatives only when communication is equal. `Approximate` requires review, not automatic rejection. |
 | Integrate / stop | Align paint, contour, light, hierarchy, and z-order; combine only techniques with different jobs. Check legibility, editability, density, fidelity, and style; simplify failures, use legal alternatives, and bake only the smallest pixel-dependent layer. Keep authoritative text/data native. |

 **Default — one dominant composition scaffold (may override when a second
@@ -47,9 +48,14 @@ simplify any competing scaffold without a separate communication job.

 #### Visual Job Router

-**Reference — not a quota**: route diagnosed problems through this table. A
+**Reference — not a quota**: recall candidates for a diagnosed problem from
+this table. A
 page may use no listed technique, one technique, or several techniques with
-different jobs.
+different jobs. The table recalls constructions rather than bounding them: one
+it never names is equally valid when it satisfies every applicable technical
+contract — the shared core's closed authoring surface, this file, the route's
+other required construction references, and any triggered module. Those
+contracts are the boundary; membership in this table is not.

 | Diagnosed visual problem | Candidate technique | Authority / stop |
 |---|---|---|
@@ -21,7 +21,7 @@ and filter/clip contracts.
 ```markdown
 | Filename | Dimensions | Purpose | Type | Layout pattern | Crop Policy | Acquire Via | Status | Reference |
 |----------|------------|---------|------|----------------|-------------|-------------|--------|-----------|
-| team.jpg | 800x600 | Team photo | Photography | `#P1-02 image left, copy right` | adaptive | web | Pending | Diverse engineering team in modern office |
+| team.jpg | 800x600 | Team photo | Photography | `Put faces behind the hiring claim; #P1-02 + #M2-08 fading the photo edge into the page so copy meets it without a frame` | adaptive | web | Pending | Diverse engineering team in modern office |
 ```

 ### Image Status Enum
@@ -172,7 +172,7 @@ in `kebab-case` and add one `Native-ready` map: `<key>=yes|no; ...`. Decide
 object. Qualitative relationships/read order remain unkeyed prose, as do
 incidental microvisuals.

-In §VIII, author every planned or explicitly required resource from the confirmed source boundary. Write one concise, non-empty `Layout pattern` suggestion in ordinary language; optionally cite hierarchical ids from the layout library when they help recall a technique. Set `Crop Policy` to `adaptive` or `no-crop`; set `Acquire Via` to `ai`, `web`, `user`, `placeholder`, or `slice`. Preserve unresolved required assets as `Pending` or `Needs-Manual` instead of dropping or reclassifying them. Native formulas never enter this table or `spec_lock.md images`.
+In §VIII, author every planned or explicitly required resource from the confirmed source boundary. Write one concise, non-empty `Layout pattern` suggestion in ordinary language; optionally cite hierarchical ids from the layout library when they help recall a technique. An image-led `adaptive` row names the page job the image resolves next to the composition serving it; a `no-crop` or supporting row keeps the concise suggestion alone. Set `Crop Policy` to `adaptive` or `no-crop`; set `Acquire Via` to `ai`, `web`, `user`, `placeholder`, or `slice`. Preserve unresolved required assets as `Pending` or `Needs-Manual` instead of dropping or reclassifying them. Native formulas never enter this table or `spec_lock.md images`.

 §VIII `Layout pattern` is a per-resource preference. When a page uses several images, repeats one image in multiple views, or combines an image with native overlays, describe the page-level relationship and participating resources in §IX `Layout` / `Images`; do not duplicate an unchanged resource row merely to encode animation sequencing.

@@ -613,7 +613,7 @@ Read the exact execution references named by this deck's retained
 construction block plus the resolved mode/style detail files as one batch:
 ```
 Read ${SKILL_DIR}/references/shared-standards-core.md      # REQUIRED: SVG compatibility + shared aesthetic/leading baseline
-Read ${SKILL_DIR}/references/svg-effects.md                # REQUIRED: Visual Job Router + effects/construction vocabulary
+Read ${SKILL_DIR}/references/svg-effects.md                # REQUIRED: §6.1 job diagnostic + effects/construction vocabulary
 Read ${SKILL_DIR}/references/native-shape-authoring.md     # REQUIRED: native-shape selection and Boolean construction
 Read ${SKILL_DIR}/references/preset-shape-vocabulary.md    # REQUIRED: complete 187-name authoring vocabulary
 Read ${SKILL_DIR}/references/executor-structure.md         # REQUIRED: qualitative relationship and topology grammar
@@ -622,7 +622,7 @@ Read ${SKILL_DIR}/references/modes/<resolved-id>.md        # one preset id, or e
 Read ${SKILL_DIR}/references/visual-styles/<resolved-id>.md # one preset id, or each `visual_style_references` id
 ```

-Keep the core's shared visual-quality defaults and `svg-effects.md` §6.1 Visual Job Router active during page authoring; they are not passive compatibility reading. Explicit user/template requirements and the locked style override compatible aesthetic defaults, never technical Required / Forbidden boundaries.
+Keep the core's shared visual-quality defaults and `svg-effects.md` §6.1 job diagnostic active during page authoring, with its Visual Job Router as recall; they are not passive compatibility reading. Explicit user/template requirements and the locked style override compatible aesthetic defaults, never technical Required / Forbidden boundaries.

 > Read only the role core, always-on construction references, exact locked detail files, and conditionally triggered modules below. The selection indexes remain planning-only. A preset reads its one locked file. For `custom`, read only the exact bases named by optional `mode_references` / `visual_style_references`: apply one under the corresponding behavior, or synthesize several by their stated contributions. If absent, read no preset file and follow the behavior directly. Do not infer adjacent bases, glob a catalog, or blend unselected identities.

@@ -604,7 +604,7 @@ Chart/Table reference and final information model are independent loading
 signals; load every applicable authority. Selection never makes an object
 native-ready or replaces the per-page Structure decision.

-Keep the core's shared visual-quality / leading defaults and `svg-effects.md` §6.1 Visual Job Router active while authoring. Explicit user/template requirements and the resolved style override compatible aesthetic defaults, never technical Required / Forbidden boundaries, carrier eligibility, or native capability discovery. Treat selected style composition examples as generative vocabulary rather than a finite layout menu.
+Keep the core's shared visual-quality / leading defaults and `svg-effects.md` §6.1 job diagnostic active while authoring, with its Visual Job Router as recall. Explicit user/template requirements and the resolved style override compatible aesthetic defaults, never technical Required / Forbidden boundaries, carrier eligibility, or native capability discovery. Treat selected style composition examples as generative vocabulary rather than a finite layout menu.

 **Per-page execution anchors**: apply the transient core-message, typography-role, semantic-color, body-frame, density, and composition anchors resolved in §2 while authoring; they guide the current run without creating a persisted planning artifact.

@@ -2,8 +2,8 @@
  "sourceId": "shadcn",
  "repo": "https://github.com/shadcn-ui/ui.git",
  "ref": "main",
-  "commit": "19b67204fb80b7a7c233c967e4cf3aed73810f80",
+  "commit": "c06da1d0e91e97b607d1359372347528bb35b090",
  "adapter": "claude-skill",
  "sourcePath": "skills/shadcn",
-  "syncedAt": "2026-08-21T06:41:32Z"
+  "syncedAt": "2026-08-21T15:59:59Z"
 }
@@ -2,8 +2,8 @@
  "sourceId": "taste-skill",
  "repo": "https://github.com/Leonxlnx/taste-skill.git",
  "ref": "main",
-  "commit": "dfb6f9f9e93a39f673b1827c0889cc28326d1800",
+  "commit": "843c8dd4d18ccff0d5a9cd4b0b71d7dbf7278293",
  "adapter": "skill-collection",
  "sourcePath": "skills",
-  "syncedAt": "2026-08-18T16:00:00Z"
+  "syncedAt": "2026-08-21T15:59:59Z"
 }