@jahia/agentic 0.4.0 → 0.4.1

package/dist/gemini/.agents/skills/jahia-content-publish/SKILL.md

@@ -1,181 +0,0 @@
----
-name: jahia-content-publish
-description: Publishes and unpublishes Jahia content via MCP tools. Use when asked to make edits live, remove content from live, or check whether a page or subtree is ready for publication.
----
-
-# Skill: jahia-content-publish
-
-Handles publication workflows using MCP tools via the `jahia` MCP server.
-
-> **Never call Jahia's GraphQL API directly.** Use only MCP tools. If a capability is missing, report it — do not work around with curl/GraphQL.
-
----
-
-## Core concepts
-
-- **EDIT workspace** — where authors create and modify draft content
-- **LIVE workspace** — what public visitors see
-- **Publication is language-scoped** — you publish specific language versions
-- **Publishing a parent can include its subtree**
-- **Workflow may apply** — `publication.publish` may start approval instead of publishing directly
-
----
-
-## Step 1 — Check publication status
-
-```
-tool: publication.status
-args: {
-  "path": "/sites/SITE_KEY/home/about",
-  "language": "en",
-  "subNodes": true,
-  "references": true
-}
-```
-
-This tells you:
-- whether the node or subtree is already published
-- whether descendants are modified or unpublished
-- whether references may block publication
-- whether the current user can publish
-
----
-
-## Step 2 — Publish
-
-```
-tool: publication.publish
-args: {
-  "path": "/sites/SITE_KEY/home/about",
-  "languages": ["en", "fr"]
-}
-```
-
-Possible outcomes:
-- direct publish to LIVE
-- workflow started for approval
-
----
-
-## Step 3 — If approval workflow starts, complete it
-
-List pending tasks:
-
-```
-tool: workflow.tasks
-args: {}
-```
-
-Approve:
-
-```
-tool: workflow.complete
-args: {
-  "taskId": "TASK_ID",
-  "outcome": "accept",
-  "comment": "Approved — reviewed and ready"
-}
-```
-
-Reject:
-
-```
-tool: workflow.complete
-args: {
-  "taskId": "TASK_ID",
-  "outcome": "reject",
-  "comment": "Needs revision"
-}
-```
-
----
-
-## Step 4 — Unpublish
-
-Remove content from LIVE while keeping EDIT:
-
-```
-tool: publication.unpublish
-args: {
-  "path": "/sites/SITE_KEY/home/about/main/outdated-section",
-  "languages": ["en"]
-}
-```
-
----
-
-## Common publication patterns
-
-### Publish a newly created page and its content
-
-```
-tool: publication.publish
-args: {
-  "path": "/sites/SITE_KEY/home/new-page",
-  "languages": ["en"]
-}
-```
-
-### Publish translated content
-
-```
-tool: publication.publish
-args: {
-  "path": "/sites/SITE_KEY/home/about",
-  "languages": ["fr"]
-}
-```
-
-### Publish a deletion after `content.markForDeletion`
-
-```
-tool: publication.publish
-args: {
-  "path": "/sites/SITE_KEY/home/old-page",
-  "languages": ["en"]
-}
-```
-
-### Check whether a subtree is ready
-
-```
-tool: publication.status
-args: {
-  "path": "/sites/SITE_KEY/home",
-  "language": "en",
-  "subNodes": true,
-  "references": true
-}
-```
-
----
-
-## Key rules
-
-| Rule | Detail |
-|------|--------|
-| Always specify languages | Publication is language-scoped |
-| Publish is subtree-aware | Publishing a page includes its content areas and descendants |
-| Workflow is automatic | `publication.publish` decides whether it can publish directly |
-| References matter | Use `references: true` in status checks when media or linked content is involved |
-| Mark-for-deletion needs publish | The deletion becomes live only after publication |
-
----
-
-## Common errors
-
-| Error | Cause | Fix |
-|-------|-------|-----|
-| `NODE_NOT_FOUND` | The path does not exist in EDIT | Verify with `content.get` |
-| `NO_PUBLISH_PERMISSION` | User lacks publishing rights | Check the user's roles |
-| Workflow started but content is still not live | Approval is still pending | Complete the task via `workflow.tasks` and `workflow.complete` |
-| `MANDATORY_LANGUAGE_UNPUBLISHABLE` | Required language content is missing | Add the missing translation first |
-
----
-
-## Related skills
-
-- `/jahia-content-create-content` — create pages and content before publishing them
-- `/jahia-content-translate-content` — translate content before publishing new locales
-- `/jahia-content-organize` — publish after moves, copies, reorders, or deletions
-

package/dist/gemini/.agents/skills/jahia-content-query-content/SKILL.md

@@ -1,174 +0,0 @@
----
-name: jahia-content-query-content
-description: Queries JCR content from a running Jahia instance via MCP tools. Use when asked to list, inspect, or retrieve content nodes, check what content exists, or audit a site's content.
----
-
-# Skill: jahia-content-query-content
-
-Retrieves JCR content from a running Jahia instance using MCP tools (via the `jahia` MCP server).
-
-> **Never call Jahia's GraphQL API directly.** Use only MCP tools. If a capability is missing, report it — do not work around with curl/GraphQL.
-
----
-
-## Prerequisites
-
-- MCP server `jahia` connected with a valid API token
-- Know the target **siteKey** (call `site.list` if unsure)
-
----
-
-## Query patterns
-
-### 1 — Get a node by path
-
-```
-tool: content.get
-args: { "path": "/sites/mySite/home/about/main/intro-text" }
-```
-
-Returns all readable properties, mixins, and metadata. Also accepts `uuid`.
-
-### 2 — List children of a node
-
-```
-tool: content.list
-args: {
-  "parentPath": "/sites/mySite/home/about/main",
-  "limit": 50
-}
-```
-
-Optional: `childNodeType` to filter, `projectProperties` to include specific properties.
-
-### 3 — Search by node type
-
-```
-tool: content.search
-args: {
-  "siteKey": "mySite",
-  "nodeType": "mymodule:article",
-  "locale": "en",
-  "sortBy": "jcr:created",
-  "order": "desc",
-  "limit": 10
-}
-```
-
-### 4 — Full-text search
-
-```
-tool: content.search
-args: {
-  "siteKey": "mySite",
-  "nodeType": "jmix:droppableContent",
-  "locale": "en",
-  "fullText": "insurance",
-  "sortBy": "_score",
-  "order": "desc"
-}
-```
-
-### 5 — Filter by property value
-
-```
-tool: content.search
-args: {
-  "siteKey": "mySite",
-  "nodeType": "mymodule:article",
-  "locale": "en",
-  "properties": [
-    { "name": "jcr:createdBy", "op": "eq", "value": "root" }
-  ]
-}
-```
-
-Operators: `eq`, `like`, `gt`, `gte`, `lt`, `lte`, `isNull`, `isNotNull`
-
-### 6 — List all sites
-
-```
-tool: site.list
-```
-
-### 7 — List all pages
-
-```
-tool: page.list
-args: { "siteKey": "mySite" }
-```
-
-Supports: `templateName`, `titleContains`, `createdAfter`, `modifiedAfter`, `sortBy`, `order`.
-
-### 8 — Check publication status
-
-```
-tool: publication.status
-args: {
-  "path": "/sites/mySite/home/about",
-  "language": "en",
-  "subNodes": true
-}
-```
-
-Returns publication status, lock/WIP flags, and permission info.
-
----
-
-## content.search parameter reference
-
-**Required:**
-- `siteKey` — scopes search under `/sites/<siteKey>`
-- `nodeType` — JCR type (e.g. `jnt:page`, `jnt:file`, `jmix:droppableContent`)
-
-**Optional:**
-- `locale` — locale for i18n property resolution (e.g. `"en"`)
-- `fullText` — full-text expression (phrase `"..."`, OR, exclusion `-term`)
-- `fullTextField` — scope full-text to one property
-- `basePath` — restrict to a subtree
-- `properties` — array of property filters (AND-combined)
-- `projectProperties` — properties to include in results
-- `sortBy` — property name (default: `"jcr:lastModified"`) or `"_score"` with fullText
-- `order` — `"asc"` or `"desc"` (default: `"desc"`)
-- `offset` — skip N results (default: 0)
-- `limit` — max results 1–100 (default: 20)
-
----
-
-## Common search patterns
-
-Last 5 created contents:
-```
-tool: content.search
-args: {
-  "siteKey": "mySite",
-  "nodeType": "jmix:droppableContent",
-  "locale": "en",
-  "sortBy": "jcr:created",
-  "order": "desc",
-  "limit": 5
-}
-```
-
-Recently modified pages:
-```
-tool: content.search
-args: {
-  "siteKey": "mySite",
-  "nodeType": "jnt:page",
-  "locale": "en",
-  "sortBy": "jcr:lastModified",
-  "order": "desc",
-  "limit": 10
-}
-```
-
----
-
-## Common errors
-
-| Error | Cause | Fix |
-|-------|-------|-----|
-| `PATH_NOT_FOUND` | Node doesn't exist at given path | Verify path with `content.list` on parent |
-| No results returned | Wrong `nodeType` or `siteKey` | Check available types with `site.types` |
-| Missing i18n properties | `locale` not passed | Always include `locale` for i18n content |

package/dist/gemini/.agents/skills/jahia-content-translate-content/SKILL.md

@@ -1,226 +0,0 @@
----
-name: jahia-content-translate-content
-description: Adds site languages and translates existing Jahia content using MCP tools. Use when asked to enable a locale, fill in missing translations, or publish translated pages and content.
----
-
-# Skill: jahia-content-translate-content
-
-Translates existing content and manages multi-language support using MCP tools via the `jahia` MCP server.
-
-> **Never call Jahia's GraphQL API directly.** Use only MCP tools. If a capability is missing, report it — do not work around with curl/GraphQL.
-
----
-
-## Prerequisites
-
-- MCP server `jahia` connected with a valid API token
-- Know the target `siteKey` (call `site.list` if unsure)
-- Content already exists in a source locale
-
----
-
-## Step 1 — Check site languages
-
-```
-tool: site.get
-args: { "siteKey": "SITE_KEY" }
-```
-
-Check `languages` and `defaultLanguage`.
-
-- If the target locale is already present, continue.
-- If the target locale is missing, add it to the site first before writing translations.
-
----
-
-## Step 2 — Read the source content
-
-```
-tool: content.get
-args: {
-  "path": "/sites/SITE_KEY/home/about/main/intro-text",
-  "locale": "en"
-}
-```
-
-Note the properties that actually contain human-readable text.
-
-To find a batch of nodes to translate:
-
-```
-tool: content.search
-args: {
-  "siteKey": "SITE_KEY",
-  "nodeType": "jmix:droppableContent",
-  "locale": "en",
-  "limit": 50
-}
-```
-
----
-
-## Step 3 — Identify which properties are i18n
-
-```
-tool: content.type
-args: { "name": "jnt:bigText" }
-```
-
-Translate only properties marked as internationalized.
-
-Common i18n properties:
-- `jcr:title`
-- `text`
-- `body`
-- `description`
-- `subtitle`
-
-Common non-i18n properties:
-- `j:view`
-- `j:templateName`
-- `jcr:primaryType`
-- references such as `j:node`
-- numeric or technical settings
-
----
-
-## Step 4 — Write translated properties
-
-Use `content.update` with the target locale:
-
-```
-tool: content.update
-args: {
-  "path": "/sites/SITE_KEY/home/about/main/intro-text",
-  "locale": "fr",
-  "properties": {
-    "jcr:title": "À propos",
-    "text": "<p>Bienvenue sur notre site.</p>"
-  }
-}
-```
-
-Key rules:
-- Set all mandatory i18n properties in the same call.
-- Translate only i18n properties.
-- Preserve the HTML structure for rich text.
-- Do not translate technical choicelist values.
-
----
-
-## Step 5 — Translate page titles
-
-Page titles are also i18n:
-
-```
-tool: content.update
-args: {
-  "path": "/sites/SITE_KEY/home/about",
-  "locale": "fr",
-  "properties": {
-    "jcr:title": "À propos"
-  }
-}
-```
-
----
-
-## Step 6 — Verify translations
-
-Check the translated locale directly:
-
-```
-tool: content.get
-args: {
-  "path": "/sites/SITE_KEY/home/about/main/intro-text",
-  "locale": "fr"
-}
-```
-
-Or search in the target locale:
-
-```
-tool: content.search
-args: {
-  "siteKey": "SITE_KEY",
-  "nodeType": "jmix:droppableContent",
-  "locale": "fr",
-  "limit": 20,
-  "projectProperties": ["jcr:title"]
-}
-```
-
----
-
-## Step 7 — Publish the translated locale
-
-Publish the page or subtree in the target language:
-
-```
-tool: publication.publish
-args: {
-  "path": "/sites/SITE_KEY/home/about",
-  "languages": ["fr"]
-}
-```
-
-If the translation touches both a page and child content, publish the page path so the subtree is included.
-
----
-
-## Common patterns
-
-### Translate all content under a page
-
-1. Discover the page structure:
-   ```
-   tool: page.structure
-   args: { "path": "/sites/SITE_KEY/home/about" }
-   ```
-2. Read each child node in the source locale:
-   ```
-   tool: content.get
-   args: { "path": "CHILD_PATH", "locale": "en" }
-   ```
-3. Write translated values to the target locale:
-   ```
-   tool: content.update
-   args: {
-     "path": "CHILD_PATH",
-     "locale": "fr",
-     "properties": { "jcr:title": "...", "text": "..." }
-   }
-   ```
-4. Publish the page in the new language.
-
-### Audit whether a page is publish-ready in the new locale
-
-```
-tool: publication.status
-args: {
-  "path": "/sites/SITE_KEY/home/about",
-  "language": "fr",
-  "subNodes": true,
-  "references": true
-}
-```
-
----
-
-## Common errors
-
-| Error | Cause | Fix |
-|-------|-------|-----|
-| `MANDATORY_PROPERTY_MISSING` | Not all required i18n properties were set | Set all mandatory translated properties in one `content.update` call |
-| Language not available | Locale not enabled on the site | Add the locale to the site first |
-| Properties appear empty | Wrong locale was used | Verify configured locales with `site.get` |
-| Translation not visible on the public site | It is still only in EDIT | Publish with `publication.publish` |
-
----
-
-## Related skills
-
-- `/jahia-content-explore-structure` — find the right pages, nodes, and types first
-- `/jahia-content-publish` — publish translated content and inspect language-scoped status
-- `/jahia-content-create-content` — create new pages or content that will later need translation
-

package/dist/gemini/.agents/skills/jahia-dev/SKILL.md

@@ -1,124 +0,0 @@
----
-name: jahia-dev
-description: Entry point for Jahia JavaScript module development. Detects your project state and tells you what to do next. Start here if you are new to the project or unsure what skill to use.
----
-
-# Jahia Dev — Project GPS
-
-You are the entry point for Jahia JavaScript module development. Your job is to assess the current project state and guide the user to the right next skill.
-
-## Step 1 — Detect project state
-
-Run all checks in parallel.
-
-### 1. Module exists?
-
-Search for a `package.json` that references `@jahia/javascript-modules-library` in the current directory or subdirectories:
-
-```bash
-find . -name "package.json" -not -path "*/node_modules/*" | xargs grep -l "@jahia/javascript-modules-library" 2>/dev/null | head -5
-```
-
-- Found → record the module name (from the `name` field in that `package.json`)
-- Not found → module does not exist yet
-
-### 2. Jahia running?
-
-```bash
-curl -s -o /dev/null -w "%{http_code}" http://localhost:8080/cms/login
-```
-
-- `200` → Jahia is running at `http://localhost:8080`
-- Anything else → Jahia is not running
-
-### 3. Content types defined?
-
-```bash
-find src/components -name "definition.cnd" 2>/dev/null | wc -l
-```
-
-Record the count of `.cnd` files found under `src/components`.
-
-### 4. Views defined?
-
-```bash
-find src/components -name "*.server.tsx" -o -name "*.client.tsx" 2>/dev/null | wc -l
-```
-
-Record the count of view files found.
-
-### 5. Page templates defined?
-
-```bash
-find src/templates/Page -type f 2>/dev/null | wc -l
-```
-
-Record the count of files in `src/templates/Page/`. More than 1 means custom templates exist (the default `index.server.tsx` is always present).
-
----
-
-## Step 2 — Report project state to user
-
-Print a clear, scannable status summary:
-
-```
-📦 Module:          ✅ <module-name> (found)   OR   ❌ not found
-🐳 Jahia:           ✅ running at http://localhost:8080   OR   ❌ not running
-📋 Content types:   <N> defined
-🖼  Views:          <N> defined
-📄 Page templates:  <N> defined
-```
-
----
-
-## Step 3 — Recommend next action
-
-Use the matrix below to pick exactly one recommendation to highlight:
-
-| Condition | Recommendation |
-|-----------|---------------|
-| No module found | 🚀 **Start here:** invoke `/jahia-dev-create-template-set` to scaffold a new Jahia JavaScript module. |
-| Module found, Jahia not running | 🐳 Your module is ready. Invoke `/jahia-dev-start-local` to start Jahia locally (Docker recommended). |
-| Module + Jahia running, 0 content types | 🎯 Jahia is running! Time to build your first component. Invoke `/jahia-dev-build-component` to create a content type + view. |
-| Module + Jahia running, content types exist, ≤1 page template | 📐 You have components. Invoke `/jahia-dev-create-page-template` to create a page template and start assembling pages. |
-| Module + Jahia running, templates exist (>1) | 🏗 Your module is taking shape! Choose what to do next (see options below). |
-
-When the last condition applies, present all options:
-
-```
-🏗 Your module is taking shape! What would you like to do next?
-  - Add a new component         → /jahia-dev-build-component
-  - Create a content listing    → /jahia-dev-query-content
-  - Review your code for issues → /jahia-dev-review
-  - Screenshot a reference site → /jahia-dev-screenshot
-  - Create a new page template  → /jahia-dev-create-page-template
-  - Clean up boilerplate        → run /jahia-dev-review and look for S10
-```
-
----
-
-## Step 4 — Print the full skill map
-
-Always print this at the end so the user can navigate anywhere:
-
-```
-## Jahia Development Skills
-
-### Setup
-/jahia-dev-create-template-set   Scaffold a new JS/React module
-/jahia-dev-start-local           Start Jahia locally (Docker or bare metal)
-
-### Building
-/jahia-dev-build-component       Build a complete component (content type + view) ← start here
-/jahia-dev-define-content-type   Define a CND content type and types.ts
-/jahia-dev-create-view           Implement a React view (.server.tsx or .client.tsx Island)
-/jahia-dev-create-page-template  Create a page template with Areas
-
-### Content
-/jahia-dev-query-content         Query JCR content with JCR-SQL2 or useJCRQuery
-
-### Quality
-/jahia-dev-review                Review code for Jahia and generic best practices
-/jahia-dev-screenshot            Screenshot reference URL + Jahia render for visual comparison
-/jahia-dev-debug                 Debug build/deploy/runtime errors end-to-end
-```