@jahia/agentic 0.3.0 → 0.4.1

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

@@ -1,255 +0,0 @@
----
-name: jahia-content-explore-structure
-description: Efficiently maps an unknown Jahia website's sites, template sets, pages, areas, content trees, and type definitions using MCP tools before authoring or restructuring content.
----
-
-# Skill: jahia-content-explore-structure
-
-Use this skill before creating or editing content on an unfamiliar Jahia instance. It produces a reliable map of the CMS so that `/jahia-content-create-content` and `/jahia-content-organize` can work without guesswork.
-
-> **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`, or start with `site.list`
-
----
-
-## Discovery workflow
-
-### Level 1 — What sites exist?
-
-```
-tool: site.list
-```
-
-Returns all sites with `siteKey`, `title`, `languages`, and `defaultLanguage`.
-
-### Level 2 — What template sets are installed for site creation?
-
-```
-tool: site.templateSets
-args: {}
-```
-
-Use this between `site.list` and `site.get` when you need to understand what template sets are available for creating a new site. This is especially useful on fresh instances where a user may ask for a site that does not exist yet.
-
-### Level 3 — Site details
-
-```
-tool: site.get
-args: { "siteKey": "SITE_KEY" }
-```
-
-Returns detailed metadata such as languages, server names, homepage path, template set, and raw JCR properties.
-
-### Level 4 — What pages exist?
-
-```
-tool: page.list
-args: { "siteKey": "SITE_KEY" }
-```
-
-Returns paginated pages with path, title, template, and last modified date.
-
-Useful filters:
-- `templateName`
-- `titleContains`
-- `createdAfter`
-- `modifiedAfter`
-- `sortBy`: `lastModified`, `created`, `title`, `path`
-
-### Level 5 — Page structure and content areas
-
-```
-tool: page.structure
-args: { "path": "/sites/SITE_KEY/home/about" }
-```
-
-Returns:
-- area paths
-- allowed node types per area
-- current children with type, title, and kind classification
-
-This is the authoring contract for a page.
-
-### Level 6 — Content tree navigation
-
-```
-tool: content.list
-args: {
-  "parentPath": "/sites/SITE_KEY/home/about/main",
-  "limit": 50
-}
-```
-
-Returns direct children with path, type, kind, title, and child count.
-
-Optional filters:
-- `childNodeType`
-- `projectProperties`
-
-### Level 7 — Read a specific node
-
-```
-tool: content.get
-args: { "path": "/sites/SITE_KEY/home/about/main/intro-text" }
-```
-
-Returns all readable properties, mixins, and metadata. You can also pass `uuid` instead of `path`.
-
-### Level 8 — Search across content
-
-```
-tool: content.search
-args: {
-  "siteKey": "SITE_KEY",
-  "nodeType": "jnt:bigText",
-  "locale": "en",
-  "fullText": "welcome",
-  "limit": 10
-}
-```
-
-Required parameters:
-- `siteKey`
-- `nodeType`
-
-Optional parameters:
-- `locale`
-- `fullText`
-- `fullTextField`
-- `basePath`
-- `properties`
-- `projectProperties`
-- `sortBy`
-- `order`
-- `offset`
-- `limit`
-
-Property filters combine with AND:
-
-```json
-"properties": [
-  { "name": "jcr:createdBy", "op": "eq", "value": "editor1" },
-  { "name": "jcr:created", "op": "gt", "value": "2026-06-01T00:00:00.000Z" }
-]
-```
-
-Operators: `eq`, `like`, `gt`, `gte`, `lt`, `lte`, `isNull`, `isNotNull`
-
-### Level 9 — Type discovery
-
-All types available on the site:
-
-```
-tool: site.types
-args: { "siteKey": "SITE_KEY" }
-```
-
-Full definition of one type:
-
-```
-tool: content.type
-args: { "name": "mymodule:heroSection" }
-```
-
-Allowed types in one specific area:
-
-```
-tool: content.list_definitions
-args: {
-  "siteKey": "SITE_KEY",
-  "nodePath": "/sites/SITE_KEY/home/my-page/main"
-}
-```
-
----
-
-## Exploration patterns
-
-### Show me everything about this instance
-
-1. `site.list`
-2. `site.templateSets`
-3. `site.get` for the relevant site
-4. `page.list`
-5. `page.structure` on a representative page
-6. `site.types`
-
-### What content is on this page?
-
-1. `page.structure`
-2. `content.get` for any interesting child nodes
-3. `page.preview` if you need rendered output
-
-### Find all articles mentioning a phrase
-
-```
-tool: content.search
-args: {
-  "siteKey": "SITE_KEY",
-  "nodeType": "jnt:page",
-  "locale": "en",
-  "fullText": ""annual report"",
-  "sortBy": "_score",
-  "order": "desc"
-}
-```
-
-### What custom types does this site use?
-
-```
-tool: site.types
-args: { "siteKey": "SITE_KEY", "includeSubTypes": true }
-```
-
-Then inspect any interesting type:
-
-```
-tool: content.type
-args: { "name": "luxe:blogPost", "includeSubTypes": false }
-```
-
----
-
-## Build a property map before creating content
-
-Summarize each target type before authoring:
-
-```
-Content type: mymodule:heroSection
-Properties:
-  jcr:title        STRING    i18n    mandatory
-  subtitle         STRING    i18n    optional
-  image            WEAKREF   -       optional   → UUID of a file node
-  backgroundColor  STRING    -       optional   → choicelist: light|dark
-
-Allowed in area: pagecontent
-```
-
-That property map is what `/jahia-content-create-content` needs to avoid validation errors.
-
----
-
-## Key principles
-
-| Principle | Detail |
-|-----------|--------|
-| Explore before acting | Discover structure before creating, moving, or deleting content |
-| Use `page.structure` for pages | It reveals areas, allowed types, and constraints |
-| Use `content.list_definitions` for areas | It shows exactly what is droppable there and what properties are required |
-| Use `site.templateSets` when the site may not exist yet | It tells you what template sets can be used with `site.create` |
-| Navigate top-down | `site.list` → `site.get` / `site.templateSets` → `page.list` → `page.structure` → `content.list` → `content.get` |
-
----
-
-## Related skills
-
-- `/jahia-content-create-content` — create sites, pages, and content after exploring
-- `/jahia-content-organize` — move, copy, rename, reorder, or delete after understanding structure
-- `/jahia-content-query-content` — inspect and search content once you know where to look
-

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
-