ワンクリックでManusで任意のスキルを実行

aem

スター0

フォーク3

更新日2026年7月8日 22:00

AEM Edge Delivery Services (EDS) skill for reading, writing, previewing, and publishing EDS pages via the `aem` CLI. Use when the user asks about AEM Edge Delivery Services, EDS pages, Franklin, Helix, AEM EDS, edge delivery content, document-based authoring, or needs to list, get, put, preview, publish, or upload content in AEM EDS. Supports the full get→edit→put→preview→publish pipeline.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

ai-ecoverse

ai-ecoverse/skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

AEM (Edge Delivery Services)

Shell command for AEM Edge Delivery Services. Manages EDS page content.

Authentication

Run oauth-token adobe to authenticate (auto-triggered on first use). No manual configuration needed — no client IDs, no service tokens.

Usage

aem <command> <eds-url-or-path> [options]

All commands accept full EDS URLs: https://main--repo--org.aem.page/path Or use --org/--repo flags with a plain path.

Commands

aem list <url> — List pages in a directory
aem get <url> [--output <vfs-path>] — Get page HTML
aem put <url> <vfs-file> — Write HTML from a VFS file
aem preview <url> — Trigger AEM preview
aem publish <url> — Trigger AEM publish
aem upload <vfs-file> <url> — Upload a media file
aem help — Show usage

Typical Workflow

For editing a page, follow this sequence:

Get — Fetch the current page HTML:

aem get https://main--myrepo--myorg.aem.page/page --output /workspace/page.html

Edit — Modify /workspace/page.html as needed.
Put — Write the updated HTML back. Verify the command exits successfully (exit code 0) before continuing:
```
aem put https://main--myrepo--myorg.aem.page/page /workspace/page.html
```
Preview — Trigger a preview and confirm the response indicates success:
```
aem preview https://main--myrepo--myorg.aem.page/page
```
Verify — Optionally re-fetch the page (aem get) or inspect the preview URL to confirm the changes appear correctly.

Publish — Once the preview looks correct, publish:

aem publish https://main--myrepo--myorg.aem.page/page

Error guidance:

If aem put fails, check that the VFS file path is correct and the file is valid HTML before retrying.
If aem preview or aem publish fails, re-run the command — transient network issues are common. If it continues to fail, verify authentication with oauth-token adobe.
Always confirm aem put succeeds before running aem preview to avoid publishing stale content.

Examples

aem list https://main--myrepo--myorg.aem.page/
aem get https://main--myrepo--myorg.aem.page/products/overview
aem get https://main--myrepo--myorg.aem.page/page --output /workspace/page.html
aem put https://main--myrepo--myorg.aem.page/page /workspace/page.html
aem preview https://main--myrepo--myorg.aem.page/page
aem publish https://main--myrepo--myorg.aem.page/page
aem upload /workspace/image.png https://main--myrepo--myorg.aem.page/media_123.png

このリポジトリの他の Skills

同じリポジトリ

github

ai-ecoverse/skills

Interact with GitHub via gh.jsh — a lightweight GitHub CLI for SLICC agents. Use this skill for any GitHub task: listing or viewing pull requests, merging PRs, posting comments, checking out branches, viewing issues, inspecting workflow runs, listing releases, searching PRs, managing Actions variables, creating branches, pushing file content, archiving repos, or calling any GitHub API endpoint directly. Trigger on requests like "list open PRs", "check CI status", "merge this PR", "what issues are open", "show the latest release", "post a comment on PR #42", "set a repo variable", "archive this repo", "create a branch", "push this file", or any task involving a GitHub repository.

2026-07-100

outlook

ai-ecoverse/skills

Interact with Microsoft Outlook (Office 365) — read inbox, search mail, view calendar events, send email, and produce aggregated inbox items for the monday dispatcher. Uses the live Outlook browser session via MSAL token extraction from localStorage. Triggers on requests involving Outlook, email, inbox, calendar, meetings, sending mail, checking unread messages, or monday inbox aggregation that includes Outlook data.

2026-07-100

ai-ecoverse/skills

Manage a LinkedIn company page — publish posts with consistent brand voice, grow engagement, respond to comments, analyze performance, preview profiles, and aggregate engagement for the monday dispatcher. Maintains a knowledge base of content ideas, audience insights, and brand guidelines. Use when the user wants to publish a LinkedIn post, draft LinkedIn content, check LinkedIn comments, respond to engagement, plan content strategy, review brand voice, view a LinkedIn profile, or manage a company page. Activate on mentions of LinkedIn, LinkedIn post, company page, social media, content calendar, engagement, brand voice, or audience growth.

2026-07-100

concur

ai-ecoverse/skills

Interact with SAP Concur (Concur Expense / Travel) via its API — list expense reports, view report and line-item details, list available receipts and smart expenses, check approvals, and call any of 50+ Concur GraphQL operations directly. Use whenever the user mentions Concur, SAP Concur, Concur Expense, expense reports, expense submission, expense receipts, smart expenses, T&E (travel and expense), reimbursements at Adobe, or wants to automate, query, or extract data from Concur without clicking through https://us2.concursolutions.com. Activate on mentions of "concur", "expense report", "expense receipts", "submit expenses", "T&E", "reimbursement", "travel allowance", or related Adobe expense workflows.

2026-07-100

gmail

ai-ecoverse/skills

Interact with Gmail — read inbox, search messages, view full message bodies, send email, reply to threads, and produce aggregated inbox items for the monday dispatcher. Uses OAuth2 refresh token flow via GWS_* env vars. Triggers on requests involving Gmail, Google email, inbox, sending mail, checking unread messages, or monday inbox aggregation that includes Gmail data.

2026-07-100

teams

ai-ecoverse/skills

Interact with Microsoft Teams via the Graph API — read messages, post to channels, search, read threads, look up users, view mentions/activity, and get channel info. Supports all teams and channels the user has access to, with auth via the live browser session. Use when the user wants to check Teams messages, post a Teams message, search Teams channels, read a thread, get user info, view mentions, or automate any Teams task. Triggers on mentions of Teams, channels, messages, threads, mentions, activity, or digest.

2026-07-090

name	aem
description	AEM Edge Delivery Services (EDS) skill for reading, writing, previewing, and publishing EDS pages via the `aem` CLI. Use when the user asks about AEM Edge Delivery Services, EDS pages, Franklin, Helix, AEM EDS, edge delivery content, document-based authoring, or needs to list, get, put, preview, publish, or upload content in AEM EDS. Supports the full get→edit→put→preview→publish pipeline.
allowed-tools	bash

AEM (Edge Delivery Services)

Shell command for AEM Edge Delivery Services. Manages EDS page content.

Authentication

Run oauth-token adobe to authenticate (auto-triggered on first use). No manual configuration needed — no client IDs, no service tokens.

Usage

aem <command> <eds-url-or-path> [options]

All commands accept full EDS URLs: https://main--repo--org.aem.page/path Or use --org/--repo flags with a plain path.

Commands

aem list <url> — List pages in a directory
aem get <url> [--output <vfs-path>] — Get page HTML
aem put <url> <vfs-file> — Write HTML from a VFS file
aem preview <url> — Trigger AEM preview
aem publish <url> — Trigger AEM publish
aem upload <vfs-file> <url> — Upload a media file
aem help — Show usage

Typical Workflow

For editing a page, follow this sequence:

Get — Fetch the current page HTML:

aem get https://main--myrepo--myorg.aem.page/page --output /workspace/page.html

Edit — Modify /workspace/page.html as needed.
Put — Write the updated HTML back. Verify the command exits successfully (exit code 0) before continuing:
```
aem put https://main--myrepo--myorg.aem.page/page /workspace/page.html
```
Preview — Trigger a preview and confirm the response indicates success:
```
aem preview https://main--myrepo--myorg.aem.page/page
```
Verify — Optionally re-fetch the page (aem get) or inspect the preview URL to confirm the changes appear correctly.

Publish — Once the preview looks correct, publish:

aem publish https://main--myrepo--myorg.aem.page/page

Error guidance:

If aem put fails, check that the VFS file path is correct and the file is valid HTML before retrying.
If aem preview or aem publish fails, re-run the command — transient network issues are common. If it continues to fail, verify authentication with oauth-token adobe.
Always confirm aem put succeeds before running aem preview to avoid publishing stale content.

Examples

aem list https://main--myrepo--myorg.aem.page/
aem get https://main--myrepo--myorg.aem.page/products/overview
aem get https://main--myrepo--myorg.aem.page/page --output /workspace/page.html
aem put https://main--myrepo--myorg.aem.page/page /workspace/page.html
aem preview https://main--myrepo--myorg.aem.page/page
aem publish https://main--myrepo--myorg.aem.page/page
aem upload /workspace/image.png https://main--myrepo--myorg.aem.page/media_123.png