菜单
Sync bidirectionnel Notion ↔ vault (import/export pages) + génération comms/changelog depuis commits et specs vault. Deux modes : --sync-notion et --publish-comms.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Expert guidance for the App Intents framework on Apple platforms. Use when developers mention: (1) Siri or Shortcuts integration, (2) AppIntent, AppEntity, AppEnum, or AppShortcutsProvider, (3) Spotlight actions or indexed entities, (4) exposing app features to Apple Intelligence, (5) parameters, parameter summaries, or intent donation, (6) widget/control configuration intents. Not for widget timeline design itself (see widgetkit-live-activities skill).
Expert guidance for CloudKit sync on Apple platforms. Use when developers mention: (1) iCloud sync or cross-device sync of app data, (2) SwiftData + CloudKit or NSPersistentCloudKitContainer, (3) CKSyncEngine or custom CloudKit record sync, (4) CloudKit sharing / collaboration (CKShare), (5) CloudKit entitlements, containers, or schema deployment, (6) conflict resolution or offline-first with iCloud. Not for third-party sync backends (Firebase, Supabase) and not for app-server REST sync (see docs/api/sync.md).
Expert guidance for StoreKit 2 in-app purchases and subscriptions on Apple platforms. Use when developers mention: (1) in-app purchases, IAP, or subscriptions, (2) Product, Transaction, or currentEntitlements, (3) receipt validation or transaction verification, (4) SubscriptionStoreView / StoreView / ProductView, (5) restore purchases, offer codes, promotional offers, refunds, (6) StoreKit Testing in Xcode or sandbox testing. Not for RevenueCat or third-party billing SDKs.
Apple Human Interface Guidelines for visionOS (Apple Vision Pro). Use when designing or building spatial apps: (1) windows, volumes, and immersive spaces, (2) ornaments, glass material, and spatial layout, (3) eye/hand input, hover effects, and target sizes, (4) comfort, motion, and immersion levels, (5) porting an iOS/iPadOS app to visionOS, (6) RealityKit + SwiftUI scene composition. Companion to the ehmo *-design-guidelines skills for the other Apple platforms.
Expert guidance for WidgetKit widgets and ActivityKit Live Activities on Apple platforms. Use when developers mention: (1) home screen / lock screen / StandBy widgets, (2) Live Activities or Dynamic Island, (3) widget timelines, TimelineProvider, or reload budgets, (4) interactive widgets with App Intents buttons/toggles, (5) Control Center controls (ControlWidget), (6) updating a Live Activity via APNs push. Not for Siri/Shortcuts intents themselves (see app-intents skill).
Audit the health of your Claude Code configuration across all six layers — permissions, hooks, MCP servers, installed skills, agents, settings conflicts. Use when asked to "/health", "check my Claude Code config", "audit my setup", or before debugging unexpected behavior (silent permission denials, MCP tool not appearing, hooks not firing).
| name | sync-external |
| description | Sync bidirectionnel Notion ↔ vault (import/export pages) + génération comms/changelog depuis commits et specs vault. Deux modes : --sync-notion et --publish-comms. |
| version | 1.1.0 |
| platforms | ["linux","macos"] |
| metadata | {"hermes":{"tags":["sync","notion","comms","changelog","release-notes","email"],"related_skills":["note-taking","github","email"],"model":"deepseek-v4-full","cron":"0 7 * * *"}} |
Adaptation de bifrost (21) + brigitte (24) — ULK → Hermes. Carte :
docs/backlog/2026-06-28-SPEC-HERMES-SYNC-EXTERNAL/CARD.md(P3, GitHub #245).
Fusion de bifrost (sync Notion ↔ vault) et brigitte (comms/changelog). Deux modes activables
séparément ou enchaînés : --sync-notion (import/export pages) et --publish-comms
(changelog/release notes/announcements depuis commits + specs). Vault = source de vérité.
0 7 * * *, frontmatter) + génération changelog hebdo
vendredi 17h (0 17 * * 5) — le second cron est déclaré séparément côté planificateur Hermes.Projects/*/ et Areas/*/ pour l'export Notion ; écriture des pages importées dans Resources/notion-import/.Resources/comms/ (ou affichées telles quelles pour copier-coller — plus pratique).--sync-notion : lister pages Notion via API → convertir en Markdown → écrire dans le vault (et inversement). Écriture par lots (≤ 20 pages/appel), aperçu + confirmation avant tout écrasement (Notion comme vault). notion-id en frontmatter = clé d'idempotence : relancer ne duplique jamais. Option --qa : à l'export, enrichir en fiche recettage (titre user-friendly + User Story « En tant que X, je veux Y pour Z »).notion-locked: true.--publish-comms : choisir d'abord le registre — interne (traduction tech→non-tech, mot d'équipe) ou externe (release notes / annonce / post). Lire commits via github + specs vault → générer le changelog/comm Markdown (sections feat/fix/chore en interne). Source = réalité : ne jamais annoncer une capacité absente des commits/CHANGELOG.--publish-email (optionnel) : passer la comm à la skill email (résumé hebdo / broadcast).source: notion, notion-id: <id>).notion-id) ; aucune écriture Notion/vault sans aperçu + confirmation.--dry-run sans écriture ni appel API).notion-locked: true est le seul cas où le vault écrase d'office (jamais de « vault gagne » silencieux).--tone technical|marketing (brigitte ULK est marketing ; Hermes peut vouloir un format technique pur).github, ne pas réimplémenter un 2ᵉ tracker ici.