@jahia/agentic 0.4.0 → 0.4.1

package/dist/codex/.agents/skills/jahia-content-media-upload/SKILL.md

@@ -1,197 +0,0 @@
----
-name: jahia-content-media-upload
-description: Uploads images, documents, and other files to Jahia via MCP tools. Use when asked to ingest media, organize uploads in site folders, or reference files from content.
----
-
-# Skill: jahia-content-media-upload
-
-Uploads media into Jahia using MCP tools via the `jahia` MCP server.
-Uploaded files land under `/sites/<siteKey>/files/` and can then be referenced from content.
-
-> **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.
-
----
-
-## Upload methods
-
-### Method 1 — URL ingestion
-
-If the file already exists at an HTTP or HTTPS URL:
-
-```
-tool: media.upload.url
-args: {
-  "siteKey": "SITE_KEY",
-  "sourceUrl": "https://example.com/images/hero.jpg",
-  "fileName": "hero.jpg"
-}
-```
-
-Optional parameters:
-- `folder`
-- `mimeType`
-
-Returns the file path, UUID, mime type, and size in bytes.
-
-### Method 2 — Two-phase binary upload
-
-Use this when the file is local or not publicly reachable.
-
-Create the upload ticket:
-
-```
-tool: media.upload.create
-args: {
-  "siteKey": "SITE_KEY",
-  "fileName": "report.pdf",
-  "sizeBytes": 2048576,
-  "folder": "documents"
-}
-```
-
-This returns a `token` and `uploadUrl`.
-
-Upload the raw bytes to `uploadUrl`, then finalize:
-
-```
-tool: media.upload.finalize
-args: { "token": "UPLOAD_TOKEN" }
-```
-
----
-
-## Organize uploads in folders
-
-```
-tool: media.upload.url
-args: {
-  "siteKey": "SITE_KEY",
-  "sourceUrl": "https://example.com/team-photo.jpg",
-  "fileName": "team-photo.jpg",
-  "folder": "images/team"
-}
-```
-
-Folders are created automatically under `/sites/<siteKey>/files`.
-
----
-
-## Reference uploaded media from content
-
-After upload, use the returned UUID or path in the content type's reference property:
-
-```
-tool: content.create
-args: {
-  "parentPath": "/sites/SITE_KEY/home/about/main",
-  "nodeType": "jdnt:imageBlock",
-  "locale": "en",
-  "properties": {
-    "j:node": "UPLOADED_FILE_UUID",
-    "jcr:title": "Team Photo"
-  }
-}
-```
-
-Common reference property names:
-- `j:node`
-- `image`
-
-Use `content.list_definitions` or `content.type` to confirm the correct property name for the target type.
-
----
-
-## Browse existing media
-
-Media files are standard JCR nodes:
-
-```
-tool: content.list
-args: {
-  "parentPath": "/sites/SITE_KEY/files",
-  "childNodeType": "jnt:file"
-}
-```
-
-Or search for them:
-
-```
-tool: content.search
-args: {
-  "siteKey": "SITE_KEY",
-  "nodeType": "jnt:file",
-  "fullText": "hero"
-}
-```
-
----
-
-## Common pattern — upload and publish an image for a page
-
-```
-# 1. Upload
-tool: media.upload.url
-args: {
-  "siteKey": "SITE_KEY",
-  "sourceUrl": "https://cdn.example.com/banner.jpg",
-  "fileName": "banner.jpg",
-  "folder": "images/banners"
-}
-
-# 2. Reference it from content
-tool: content.create
-args: {
-  "parentPath": "/sites/SITE_KEY/home/landing/main",
-  "nodeType": "jdnt:imageBlock",
-  "locale": "en",
-  "properties": {
-    "j:node": "UPLOADED_FILE_UUID",
-    "jcr:title": "Hero Banner"
-  }
-}
-
-# 3. Publish both the media file and the page
-tool: publication.publish
-args: {
-  "path": "/sites/SITE_KEY/files/images/banners/banner.jpg",
-  "languages": ["en"]
-}
-
-tool: publication.publish
-args: {
-  "path": "/sites/SITE_KEY/home/landing",
-  "languages": ["en"]
-}
-```
-
----
-
-## Key rules
-
-| Rule | Detail |
-|------|--------|
-| Files land in EDIT first | Uploads are not automatically live |
-| Publish uploaded files when needed | Use `publication.publish` if public rendering depends on them |
-| Max size depends on the upload method | Respect tool limits and server configuration |
-| Folder paths are relative | Do not start `folder` with a leading slash |
-| File names are plain file names | No path separators in `fileName` |
-
----
-
-## Common errors
-
-| Error | Cause | Fix |
-|-------|-------|-----|
-| `TICKET_NOT_FOUND` | Invalid or expired upload token | Create a new ticket with `media.upload.create` |
-| `FILE_TOO_LARGE` | Payload exceeds the allowed size | Reduce file size or use the correct upload flow |
-| `SOURCE_UNREACHABLE` | Jahia cannot fetch the source URL | Verify the remote URL from the Jahia server |
-| `NODE_EXISTS` | A file with the same name already exists | Use a different `fileName` |
-
----
-
-## Related skills
-
-- `/jahia-content-create-content` — reference uploaded media from newly created content
-- `/jahia-content-publish` — publish uploaded files and the pages that use them
-- `/jahia-content-organize` — reorganize content after media-backed pages are created
-

package/dist/codex/.agents/skills/jahia-content-move-content/SKILL.md

@@ -1,231 +0,0 @@
----
-name: jahia-content-move-content
-description: Focused workflow for moving, copying, renaming, reordering, and deleting Jahia content via MCP tools. Use when asked to restructure an existing content tree safely.
----
-
-# Skill: jahia-content-move-content
-
-Reorganizes an existing content tree 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)
-- Prefer `/jahia-content-explore-structure` first if the tree is unfamiliar
-
----
-
-## Step 1 — Audit the current tree
-
-```
-tool: content.list
-args: {
-  "parentPath": "/sites/SITE_KEY/home/about/main",
-  "limit": 50
-}
-```
-
-For a broader view:
-
-```
-tool: content.search
-args: {
-  "siteKey": "SITE_KEY",
-  "nodeType": "jmix:droppableContent",
-  "locale": "en",
-  "sortBy": "jcr:created",
-  "order": "asc",
-  "limit": 50
-}
-```
-
----
-
-## Step 2 — Move, copy, rename, or reorder
-
-### Move a node
-
-```
-tool: content.move
-args: {
-  "path": "/sites/SITE_KEY/home/blog/main/old-article",
-  "destParentPath": "/sites/SITE_KEY/home/archive/main",
-  "newName": "archived-article"
-}
-```
-
-### Copy a node
-
-```
-tool: content.copy
-args: {
-  "path": "/sites/SITE_KEY/home/templates/main/hero-banner",
-  "destParentPath": "/sites/SITE_KEY/home/landing/main"
-}
-```
-
-### Rename a node
-
-```
-tool: content.rename
-args: {
-  "path": "/sites/SITE_KEY/home/about/main/old-name",
-  "newName": "new-name"
-}
-```
-
-### Reorder siblings
-
-```
-tool: content.reorder
-args: {
-  "parentPath": "/sites/SITE_KEY/home/blog/main",
-  "nodeName": "featured-post",
-  "position": "FIRST"
-}
-```
-
-Or place one node before another:
-
-```
-tool: content.reorder
-args: {
-  "parentPath": "/sites/SITE_KEY/home/blog/main",
-  "nodeName": "featured-post",
-  "position": "INPLACE",
-  "beforeNodeName": "second-post"
-}
-```
-
----
-
-## Step 3 — Update content properties if needed
-
-```
-tool: content.update
-args: {
-  "path": "/sites/SITE_KEY/home/about/main/intro-text",
-  "locale": "en",
-  "properties": {
-    "jcr:title": "Updated Title",
-    "text": "<p>New content here.</p>"
-  }
-}
-```
-
----
-
-## Step 4 — Delete correctly
-
-### Draft-only content: hard delete
-
-```
-tool: content.delete
-args: { "path": "/sites/SITE_KEY/home/draft-page/main/temp-node" }
-```
-
-### Published content: mark for deletion, then publish the deletion
-
-```
-tool: content.markForDeletion
-args: { "path": "/sites/SITE_KEY/home/old-page" }
-```
-
-Publish the deletion to remove it from LIVE:
-
-```
-tool: publication.publish
-args: {
-  "path": "/sites/SITE_KEY/home/old-page",
-  "languages": ["en"]
-}
-```
-
-Undo the mark if needed:
-
-```
-tool: content.unmarkForDeletion
-args: { "path": "/sites/SITE_KEY/home/old-page" }
-```
-
----
-
-## Step 5 — Check and publish after changes
-
-Inspect publication status:
-
-```
-tool: publication.status
-args: {
-  "path": "/sites/SITE_KEY/home/about",
-  "language": "en",
-  "subNodes": true,
-  "references": true
-}
-```
-
-Publish the affected branch:
-
-```
-tool: publication.publish
-args: {
-  "path": "/sites/SITE_KEY/home/about",
-  "languages": ["en"]
-}
-```
-
-Unpublish if the goal is to remove content from LIVE while keeping EDIT:
-
-```
-tool: publication.unpublish
-args: {
-  "path": "/sites/SITE_KEY/home/about/main/outdated-section",
-  "languages": ["en"]
-}
-```
-
----
-
-## Step 6 — Verify the result
-
-```
-tool: content.list
-args: {
-  "parentPath": "/sites/SITE_KEY/home/about/main",
-  "limit": 50
-}
-```
-
-Or preview the page:
-
-```
-tool: page.preview
-args: { "path": "/sites/SITE_KEY/home/about" }
-```
-
----
-
-## Workflow summary
-
-```
-1. Audit      → content.list / content.search
-2. Move/copy  → content.move / content.copy
-3. Rename     → content.rename
-4. Reorder    → content.reorder
-5. Delete     → content.delete or content.markForDeletion + publication.publish
-6. Publish    → publication.status + publication.publish / publication.unpublish
-7. Verify     → content.list / page.preview
-```
-
----
-
-## Related skills
-
-- `/jahia-content-organize` — fuller reorganization lifecycle and patterns
-- `/jahia-content-explore-structure` — understand the tree before changing it
-- `/jahia-content-publish` — publication readiness, publish, and unpublish flows
-

package/dist/codex/.agents/skills/jahia-content-organize/SKILL.md

@@ -1,209 +0,0 @@
----
-name: jahia-content-organize
-description: Moves, copies, renames, reorders, and deletes Jahia content via MCP tools. Use when asked to reorganize a site structure, duplicate content, or manage the deletion lifecycle.
----
-
-# Skill: jahia-content-organize
-
-Covers structural content-tree operations 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.
-
----
-
-## Move content
-
-```
-tool: content.move
-args: {
-  "path": "/sites/SITE_KEY/home/blog/main/old-article",
-  "destParentPath": "/sites/SITE_KEY/home/archive/main",
-  "newName": "archived-article"
-}
-```
-
-- `newName` is optional
-- the entire subtree moves with the node
-- the move happens in EDIT; publish afterward
-
-## Copy content
-
-```
-tool: content.copy
-args: {
-  "path": "/sites/SITE_KEY/home/templates/main/hero-banner",
-  "destParentPath": "/sites/SITE_KEY/home/landing/main"
-}
-```
-
-- deep copy, including children and properties
-- the copy gets a new UUID
-- use `excludeChildTypes` when you need to skip specific child node types
-
-## Rename content
-
-```
-tool: content.rename
-args: {
-  "path": "/sites/SITE_KEY/home/about/main/old-name",
-  "newName": "new-name"
-}
-```
-
-Use `content.update` on `jcr:title` when you need to change the display title rather than the node name.
-
-## Reorder siblings
-
-```
-tool: content.reorder
-args: {
-  "parentPath": "/sites/SITE_KEY/home/blog/main",
-  "nodeName": "featured-post",
-  "position": "FIRST"
-}
-```
-
-Place a node before a specific sibling:
-
-```
-tool: content.reorder
-args: {
-  "parentPath": "/sites/SITE_KEY/home/blog/main",
-  "nodeName": "featured-post",
-  "position": "INPLACE",
-  "beforeNodeName": "second-post"
-}
-```
-
----
-
-## Delete content
-
-### Draft-only content
-
-Hard delete immediately:
-
-```
-tool: content.delete
-args: { "path": "/sites/SITE_KEY/home/draft-page/main/temp-node" }
-```
-
-### Published content
-
-Mark the node for deletion first:
-
-```
-tool: content.markForDeletion
-args: { "path": "/sites/SITE_KEY/home/blog/main/old-post" }
-```
-
-Publish the deletion to propagate it to LIVE:
-
-```
-tool: publication.publish
-args: {
-  "path": "/sites/SITE_KEY/home/blog/main/old-post",
-  "languages": ["en"]
-}
-```
-
-Undo the mark if needed:
-
-```
-tool: content.unmarkForDeletion
-args: { "path": "/sites/SITE_KEY/home/blog/main/old-post" }
-```
-
-You cannot hard-delete already published content without first going through the deletion lifecycle.
-
----
-
-## Reorganization patterns
-
-### Move several items into a new section
-
-```
-# 1. Audit the current branch
-tool: content.list
-args: { "parentPath": "/sites/SITE_KEY/home/news/main" }
-
-# 2. Move items
-tool: content.move
-args: {
-  "path": "/sites/SITE_KEY/home/news/main/item-1",
-  "destParentPath": "/sites/SITE_KEY/home/archive/main"
-}
-
-tool: content.move
-args: {
-  "path": "/sites/SITE_KEY/home/news/main/item-2",
-  "destParentPath": "/sites/SITE_KEY/home/archive/main"
-}
-
-# 3. Publish the affected branch
-tool: publication.publish
-args: {
-  "path": "/sites/SITE_KEY/home/archive",
-  "languages": ["en"]
-}
-```
-
-### Duplicate a page structure
-
-```
-# 1. Copy the page
-tool: content.copy
-args: {
-  "path": "/sites/SITE_KEY/home/template-page",
-  "destParentPath": "/sites/SITE_KEY/home"
-}
-
-# 2. Rename the copy
-tool: content.rename
-args: {
-  "path": "/sites/SITE_KEY/home/template-page1",
-  "newName": "new-section"
-}
-
-# 3. Update the page title
-tool: content.update
-args: {
-  "path": "/sites/SITE_KEY/home/new-section",
-  "locale": "en",
-  "properties": {
-    "jcr:title": "New Section"
-  }
-}
-```
-
----
-
-## Key rules
-
-| Rule | Detail |
-|------|--------|
-| Publish after reorganization | Moves, copies, renames, and reorders affect EDIT first |
-| No hard-delete of published nodes | Use `content.markForDeletion` plus `publication.publish` |
-| Move includes the subtree | Children move with the selected node |
-| Name conflicts fail | Moves and renames validate uniqueness |
-| Reorder stays within one parent | Use `content.move` to change parents, `content.reorder` to change sibling order |
-
----
-
-## Common errors
-
-| Error | Cause | Fix |
-|-------|-------|-----|
-| `NODE_NOT_FOUND` | Source path does not exist | Verify with `content.get` or `content.list` |
-| `NODE_EXISTS` | Target name already exists | Choose a different `newName` |
-| `CANNOT_DELETE_PUBLISHED` | Attempted hard delete on published content | Use `content.markForDeletion` |
-| `DEST_NOT_FOUND` | Destination parent does not exist | Verify with `content.get` |
-
----
-
-## Related skills
-
-- `/jahia-content-explore-structure` — inspect the tree before reorganizing it
-- `/jahia-content-publish` — publish after moves, copies, reorders, or deletions
-- `/jahia-content-move-content` — focused move and deletion workflow for an existing branch
-