[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7369882RXG675F88HSPGSFY":3,"skill-same:01M7369882RXG675F88HSPGSFY":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7369882RXG675F88HSPGSFY","admin",null,"Generate comprehensive admin documentation for AEM Edge Delivery Services project handover. Creates admin guide covering Config Service setup, permissions, access control, Admin API operations, cache management, and code sync. Use for \"admin guide\", \"admin documentation\", \"admin handover\".","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-admin\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: admin\ndescription: Generate comprehensive admin documentation for AEM Edge Delivery Services project handover. Creates admin guide covering Config Service setup, permissions, access control, Admin API operations, cache management, and code sync. Use for \"admin guide\", \"admin documentation\", \"admin handover\".\nlicense: Apache-2.0\nallowed-tools: Read, Write, Edit, Bash, AskUserQuestion, Skill\nmetadata:\n  version: \"1.0.0\"\n---\n\n# Project Handover - Admin Guide\n\nGenerate comprehensive documentation for administrators taking over an AEM Edge Delivery Services project. Produces a complete admin guide with Config Service setup, permissions, Admin API operations, and troubleshooting.\n\n## When to Use This Skill\n\n- Project handover to client administrators\n- Documenting admin procedures for a project\n- Creating operations runbook\n- \"Generate admin guide\"\n- \"Admin documentation\"\n- \"Admin handover\"\n\n---\n\n## Step 0: Navigate to Project Root and Verify Edge Delivery Services Project (CONDITIONAL)\n\n**Skip this step if `allGuides` flag is set** (orchestrator already validated and navigated).\n\n**CRITICAL: If NOT skipped, you MUST execute the `cd` command. Do NOT use absolute paths — actually change directory.**\n\n```bash\nALL_GUIDES=$(cat .claude-plugin\u002Fproject-config.json 2>\u002Fdev\u002Fnull | grep -o '\"allGuides\"[[:space:]]*:[[:space:]]*true')\nif [ -z \"$ALL_GUIDES\" ]; then\n  # Navigate to git project root (works from any subdirectory)\n  cd \"$(git rev-parse --show-toplevel)\"\n  # Verify it's an Edge Delivery Services project\n  ls scripts\u002Faem.js\nfi\n```\n\n**IMPORTANT:**\n- You MUST run the `cd` command above using the Bash tool\n- All subsequent steps operate from project root\n- Do NOT use absolute paths to verify — actually navigate\n- Guides will be created at `project-root\u002Fproject-guides\u002F`\n\n**If NOT skipped AND `scripts\u002Faem.js` does NOT exist**, respond:\n\n> \"This skill is designed for AEM Edge Delivery Services projects. The current directory does not appear to be an Edge Delivery Services project (`scripts\u002Faem.js` not found).\n>\n> Please navigate to an Edge Delivery Services project and try again.\"\n\n**STOP if check fails. Otherwise proceed — you are now at project root.**\n\n---\n\n## Execution Checklist\n\n```markdown\n- [ ] Phase 1: Gather Project Context\n- [ ] Phase 2: Generate Admin Guide Content\n- [ ] Phase 3: Customize for Project\n- [ ] Phase 4: Generate Professional PDF\n```\n\n---\n\n## Communication Guidelines\n\n- **NEVER use \"EDS\"** as an acronym for Edge Delivery Services in any generated documentation or chat responses\n- Always use the full name \"Edge Delivery Services\" or \"AEM Edge Delivery Services\"\n- This applies to all output files (PDF, HTML, markdown) and all communication with the user\n\n---\n\n## ⚠️ CRITICAL PATH REQUIREMENT\n\n**YOU MUST SAVE THE FILE TO THIS EXACT PATH:**\n\n```\nproject-guides\u002FADMIN-GUIDE.md\n```\n\n**BEFORE WRITING ANY FILE:**\n1. First, create the directory: `mkdir -p project-guides`\n2. Then write to: `project-guides\u002FADMIN-GUIDE.md`\n\n**WHY THIS MATTERS:** Files must be in `project-guides\u002F` for proper organization and PDF conversion.\n\n❌ **WRONG:** `ADMIN-GUIDE.md` (root)\n❌ **WRONG:** `docs\u002FADMIN-GUIDE.md`\n❌ **WRONG:** `\u002Fworkspace\u002FADMIN-GUIDE.md`\n✅ **CORRECT:** `project-guides\u002FADMIN-GUIDE.md`\n\n---\n\n## Output Format\n\n**MANDATORY OUTPUT:** `project-guides\u002FADMIN-GUIDE.pdf`\n\n**STRICTLY FORBIDDEN:**\n- ❌ Do NOT read or analyze `fstab.yaml` — it does NOT exist in most projects and does NOT show all sites\n- ❌ Do NOT create `.plain.html` files\n- ❌ Do NOT use `convert_markdown_to_html` tool — this converts the FULL guide to HTML with raw frontmatter visible, which is NOT what we want\n- ❌ Do NOT tell user to \"convert markdown to PDF manually\"\n- ❌ Do NOT save markdown to root directory or any path other than `project-guides\u002F`\n- ❌ Do NOT say \"PDF will be generated later\" or \"at session end\" — generate it NOW\n\n**The HTML output must be a SHORT summary page** (created with Write tool) containing:\n- Title and brief description\n- \"What's Inside\" bullet list\n- PDF download link\nNOT the full guide content converted to HTML.\n\n**REQUIRED WORKFLOW:**\n1. Run `mkdir -p project-guides` to ensure directory exists\n2. Generate markdown content with YAML frontmatter (title, date)\n3. Save to `project-guides\u002FADMIN-GUIDE.md` (EXACT PATH - no exceptions)\n4. **IMMEDIATELY** invoke PDF conversion (see Phase 4.1)\n5. Clean up all source files (only PDF remains)\n6. Final output: `project-guides\u002FADMIN-GUIDE.pdf`\n\n---\n\n## Phase 0: Get Organization Name (Required First)\n\n**Whenever this skill runs** — whether the user triggered it directly (e.g. \"generate admin guide\") or via the handover flow — you must have the Config Service organization name before doing anything else. Do not skip this phase.\n\n### 0.1 Check for Saved Organization\n\n```bash\n# Check if org name is already saved\ncat .claude-plugin\u002Fproject-config.json 2>\u002Fdev\u002Fnull | grep -o '\"org\"[[:space:]]*:[[:space:]]*\"[^\"]*\"' | head -1\n```\n\n### 0.2 Prompt for Organization Name (If Not Saved)\n\n**If no org name is saved**, you MUST pause and ask the user directly:\n\n> \"What is your Config Service organization name? This is the `{org}` part of your Edge Delivery Services URLs (e.g., `https:\u002F\u002Fmain--site--{org}.aem.page`). The org name may differ from your GitHub organization.\"\n\n**IMPORTANT RULES:**\n- **DO NOT use `AskUserQuestion` with predefined options** — ask as a plain text question\n- **Organization name is MANDATORY** — do not offer a \"skip\" option\n- **Wait for user to type the org name** before proceeding\n- If user doesn't provide a valid org name, ask again\n\n### 0.3 Save Organization Name\n\nOnce you have the org name (either from saved config or user input), save it for future use:\n\n```bash\n# Create config directory if needed\nmkdir -p .claude-plugin\n# Ensure .claude-plugin is in .gitignore (contains auth tokens)\ngrep -qxF '.claude-plugin\u002F' .gitignore 2>\u002Fdev\u002Fnull || echo '.claude-plugin\u002F' >> .gitignore\n\n# Save org name to config file (create or update)\nif [ -f .claude-plugin\u002Fproject-config.json ]; then\n  cat .claude-plugin\u002Fproject-config.json | sed 's\u002F\"org\"[[:space:]]*:[[:space:]]*\"[^\"]*\"\u002F\"org\": \"{ORG_NAME}\"\u002F' > \u002Ftmp\u002Fproject-config.json && mv \u002Ftmp\u002Fproject-config.json .claude-plugin\u002Fproject-config.json\nelse\n  echo '{\"org\": \"{ORG_NAME}\"}' > .claude-plugin\u002Fproject-config.json\nfi\n```\n\nReplace `{ORG_NAME}` with the actual organization name provided by the user.\n\n---\n\n## Phase 0.5: Authenticate with Config Service (Browser Login)\n\n**After getting the organization name, authenticate using Playwright browser automation.**\n\n### 0.5.1 Check for Existing Auth Token\n\n```bash\n# Check if auth token is already saved\nAUTH_TOKEN=$(cat .claude-plugin\u002Fproject-config.json 2>\u002Fdev\u002Fnull | grep -o '\"authToken\"[[:space:]]*:[[:space:]]*\"[^\"]*\"' | sed 's\u002F\"authToken\"[[:space:]]*:[[:space:]]*\"\u002F\u002F' | sed 's\u002F\"$\u002F\u002F')\n\nif [ -n \"$AUTH_TOKEN\" ]; then\n  echo \"Auth token found\"\nelse\n  echo \"No auth token - need to authenticate\"\nfi\n```\n\n### 0.5.2 Open Browser for Login (If No Token)\n\nIf no auth token exists, use Playwright CLI:\n\n1. **Install Playwright (if needed)**:\n```bash\nnpx playwright --version 2>\u002Fdev\u002Fnull || npm install -g playwright\nnpx playwright install chromium 2>\u002Fdev\u002Fnull || true\n```\n\n2. **Get the first site name** (unauthenticated endpoint):\n```bash\nORG=$(cat .claude-plugin\u002Fproject-config.json | grep -o '\"org\"[[:space:]]*:[[:space:]]*\"[^\"]*\"' | sed 's\u002F\"org\"[[:space:]]*:[[:space:]]*\"\u002F\u002F' | sed 's\u002F\"$\u002F\u002F')\nSITE=$(curl -s \"https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F${ORG}\u002Fsites.json\" | grep -o '\"name\"[[:space:]]*:[[:space:]]*\"[^\"]*\"' | head -1 | sed 's\u002F\"name\"[[:space:]]*:[[:space:]]*\"\u002F\u002F' | sed 's\u002F\"$\u002F\u002F')\n```\n\n3. **Display clear instructions and open browser**:\n```bash\necho \"\"\necho \"╔════════════════════════════════════════════════════════════════╗\"\necho \"║                                                                ║\"\necho \"║   BROWSER WINDOW OPENING FOR ADOBE ID LOGIN                    ║\"\necho \"║                                                                ║\"\necho \"║   1. Sign in with your Adobe ID credentials                   ║\"\necho \"║   2. After successful login, CLOSE THE BROWSER WINDOW         ║\"\necho \"║                                                                ║\"\necho \"║   >>> CLOSE THE BROWSER TO CONTINUE \u003C\u003C\u003C                       ║\"\necho \"║                                                                ║\"\necho \"╚════════════════════════════════════════════════════════════════╝\"\necho \"\"\n\nmkdir -p .claude-plugin\nnpx playwright open --save-storage=.claude-plugin\u002Fauth-storage.json \"https:\u002F\u002Fadmin.hlx.page\u002Flogin\u002F${ORG}\u002F${SITE}\u002Fmain\"\n```\n\n### 0.5.3 Extract and Save Auth Token\n\nAfter browser is closed, extract token from storage file:\n\n```bash\necho \"Browser closed. Extracting auth token...\"\n\nAUTH_TOKEN=$(node -e \"\nconst fs = require('fs');\nconst data = JSON.parse(fs.readFileSync('.claude-plugin\u002Fauth-storage.json', 'utf8'));\nconst cookie = data.cookies.find(c => c.name === 'auth_token');\nconsole.log(cookie ? cookie.value : '');\n\")\n\nORG=$(cat .claude-plugin\u002Fproject-config.json | grep -o '\"org\"[[:space:]]*:[[:space:]]*\"[^\"]*\"' | sed 's\u002F\"org\"[[:space:]]*:[[:space:]]*\"\u002F\u002F' | sed 's\u002F\"$\u002F\u002F')\necho \"{\\\"org\\\": \\\"${ORG}\\\", \\\"authToken\\\": \\\"${AUTH_TOKEN}\\\"}\" > .claude-plugin\u002Fproject-config.json\n\nrm -f .claude-plugin\u002Fauth-storage.json\necho \"Auth token saved.\"\n```\n\n### 0.5.4 Verify Authentication\n\nTest the token works:\n```bash\nAUTH_TOKEN=$(cat .claude-plugin\u002Fproject-config.json | grep -o '\"authToken\"[[:space:]]*:[[:space:]]*\"[^\"]*\"' | sed 's\u002F\"authToken\"[[:space:]]*:[[:space:]]*\"\u002F\u002F' | sed 's\u002F\"$\u002F\u002F')\nORG=$(cat .claude-plugin\u002Fproject-config.json | grep -o '\"org\"[[:space:]]*:[[:space:]]*\"[^\"]*\"' | sed 's\u002F\"org\"[[:space:]]*:[[:space:]]*\"\u002F\u002F' | sed 's\u002F\"$\u002F\u002F')\n\n# Test with authenticated endpoint\ncurl -s -w \"%{http_code}\" -o \u002Fdev\u002Fnull -H \"x-auth-token: ${AUTH_TOKEN}\" \\\n  \"https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F${ORG}\u002Fsites.json\"\n```\n\nIf returns 200, authentication is successful. If 401, re-authenticate.\n\n---\n\n## Phase 1: Gather Project Context\n\n### 1.1 Fetch Sites and Code Repo via Config Service API\n\n**⚠️ MANDATORY DATA SOURCE — NO ALTERNATIVES ALLOWED**\n\nYou MUST call the Config Service API. This is the ONLY acceptable source for site information.\n\n**❌ PROHIBITED APPROACHES (will produce incorrect results):**\n- Analyzing `fstab.yaml` — does NOT show all sites in repoless setups\n- Reading `README.md` — may be outdated or incomplete\n- Inferring from codebase structure — misses CDN configs and additional sites\n- Using git remote URLs — org name may differ from Config Service org\n- Making assumptions based on project folder names\n\n**✅ REQUIRED: Execute and save response:**\n\n```bash\nORG=$(cat .claude-plugin\u002Fproject-config.json | grep -o '\"org\"[[:space:]]*:[[:space:]]*\"[^\"]*\"' | sed 's\u002F\"org\"[[:space:]]*:[[:space:]]*\"\u002F\u002F' | sed 's\u002F\"$\u002F\u002F')\n\n# Save response to file - Step 1.2 depends on this file\ncurl -s -H \"Accept: application\u002Fjson\" \"https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F${ORG}\u002Fsites.json\" > .claude-plugin\u002Fsites-config.json\n```\n\n**📁 REQUIRED ARTIFACT:** `.claude-plugin\u002Fsites-config.json`\n\n**API Reference:** https:\u002F\u002Fwww.aem.live\u002Fdocs\u002Fadmin.html#tag\u002FsiteConfig\u002Foperation\u002FgetConfigSites\n\n---\n\nThe response is a JSON object with a `sites` array (each entry has a `name` field). Extract site names and construct per-site URLs:\n- **Preview:** `https:\u002F\u002Fmain--{site-name}--{org}.aem.page\u002F`\n- **Live:** `https:\u002F\u002Fmain--{site-name}--{org}.aem.live\u002F`\n\nMultiple sites = **repoless** setup. Single site = **standard** setup.\n\n**Then fetch individual site config for code and content details:**\n\n```bash\nAUTH_TOKEN=$(cat .claude-plugin\u002Fproject-config.json | grep -o '\"authToken\"[[:space:]]*:[[:space:]]*\"[^\"]*\"' | sed 's\u002F\"authToken\"[[:space:]]*:[[:space:]]*\"\u002F\u002F' | sed 's\u002F\"$\u002F\u002F')\ncurl -s -H \"x-auth-token: ${AUTH_TOKEN}\" \"https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F${ORG}\u002Fsites\u002F{site-name}.json\"\n```\n\n**Example response:**\n```json\n{\n  \"code\": {\n    \"owner\": \"github-owner\",\n    \"repo\": \"repo-name\",\n    \"source\": { \"type\": \"github\", \"url\": \"https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\" }\n  },\n  \"content\": {\n    \"source\": {\n      \"url\": \"https:\u002F\u002Fcontent.da.live\u002Forg-name\u002Fsite-name\u002F\",\n      \"type\": \"markup\"\n    }\n  }\n}\n```\n\n**Extract from response:**\n- `code.owner` \u002F `code.repo` — GitHub repository\n- `content.source.url` — Content mountpath (e.g., `https:\u002F\u002Fcontent.da.live\u002Forg\u002Fsite\u002F`)\n- `content.source.type` — Content source type (markup, onedrive, google)\n\n**⚠️ Do NOT use `fstab.yaml`** — use Config Service API instead.\n\n### 1.2 Build Context\n\n**Read from artifact created in 1.1:**\n\n```bash\ncat .claude-plugin\u002Fsites-config.json\n```\n\nParse the JSON to extract site names, then fetch each site's config for code repo:\n\n```bash\ncurl -s -H \"Accept: application\u002Fjson\" \"https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F${ORG}\u002Fsites\u002F{site-name}.json\"\n```\n\nUse these API responses to build context: site names, code repo (owner\u002Frepo), preview\u002Flive URLs. If site config includes a content source (e.g. content.da.live path), record it for the Sites table.\n\n```\nAdmin Context:\n├── Organization: {org from saved config}\n├── Site(s): {site1}, {site2}, ... (from Config Service API response)\n├── Setup Type: {repoless | standard} (from Config Service API)\n├── Code Repo: {code.owner}\u002F{code.repo} (from Config Service — GitHub or Cloud Manager)\n├── Preview: https:\u002F\u002Fmain--{site}--{org}.aem.page\u002F\n├── Live: https:\u002F\u002Fmain--{site}--{org}.aem.live\u002F\n├── Login URL: https:\u002F\u002Fadmin.hlx.page\u002Flogin\u002F{org}\u002F{site}\n└── Config Service: https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F{org}\u002F\n```\n\n---\n\n## Phase 2: Generate Admin Guide\n\n### Output File: `project-guides\u002FADMIN-GUIDE.md`\n\nGenerate the admin handover document with the following structure:\n\n```markdown\n# [Project Name] - Admin Guide\n\nComplete administration guide for managing this Edge Delivery Services project.\n\n## Quick Reference\n\n### URLs\n\n| Purpose | URL |\n|---------|-----|\n| **Login** | https:\u002F\u002Fadmin.hlx.page\u002Flogin\u002F{org}\u002F{site} |\n| **Config Service** | https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F{org}\u002F |\n| **Preview** | https:\u002F\u002Fmain--{site}--{org}.aem.page\u002F |\n| **Live** | https:\u002F\u002Fmain--{site}--{org}.aem.live\u002F |\n\n### Sites (if multi-site\u002Frepoless)\n\n| Site | Content Source (DA) | Preview | Live |\n|------|---------------------|---------|------|\n| {site1} | [from site config if present] | https:\u002F\u002Fmain--{site1}--{org}.aem.page\u002F | https:\u002F\u002Fmain--{site1}--{org}.aem.live\u002F |\n| {site2} | [from site config if present] | https:\u002F\u002Fmain--{site2}--{org}.aem.page\u002F | https:\u002F\u002Fmain--{site2}--{org}.aem.live\u002F |\n\n## Authentication\n\n### Login\n\n1. Open: https:\u002F\u002Fadmin.hlx.page\u002Flogin\u002F{org}\u002F{site}\n2. Sign in with your Adobe ID\n3. Copy auth token for API operations\n\n### Logout\n\n```bash\ncurl -X POST \\\n  -H \"x-auth-token: $AUTH_TOKEN\" \\\n  \"https:\u002F\u002Fadmin.hlx.page\u002Flogout\u002F{org}\u002F{site}\u002Fmain\"\n```\n\n## User Management\n\n### View Current Access\n\n```bash\ncurl -H \"x-auth-token: $AUTH_TOKEN\" \\\n  \"https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F{org}\u002Fsites\u002F{site}\u002Faccess.json\"\n```\n\n### Add User\n\n| Role | Command |\n|------|---------|\n| Admin | `POST \u002Fconfig\u002F{org}\u002Fsites\u002F{site}\u002Faccess\u002Fadmin.json` with `{\"users\": [\"email\"]}` |\n| Author | `POST \u002Fconfig\u002F{org}\u002Fsites\u002F{site}\u002Faccess\u002Fauthor.json` with `{\"users\": [\"email\"]}` |\n\n### Remove User\n\n```bash\ncurl -X DELETE \\\n  -H \"x-auth-token: $AUTH_TOKEN\" \\\n  \"https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F{org}\u002Fsites\u002F{site}\u002Faccess\u002Fadmin\u002F{email}.json\"\n```\n\n## Content Operations\n\n### Preview\n\n| Operation | Endpoint |\n|-----------|----------|\n| Single page | `POST \u002Fpreview\u002F{org}\u002F{site}\u002Fmain\u002F{path}` |\n| Bulk preview | `POST \u002Fpreview\u002F{org}\u002F{site}\u002Fmain\u002F*` |\n\n### Publish\n\n| Operation | Endpoint |\n|-----------|----------|\n| Single page | `POST \u002Flive\u002F{org}\u002F{site}\u002Fmain\u002F{path}` |\n| Bulk publish | `POST \u002Flive\u002F{org}\u002F{site}\u002Fmain\u002F*` |\n| Unpublish | `DELETE \u002Flive\u002F{org}\u002F{site}\u002Fmain\u002F{path}` |\n\n### Cache\n\n| Operation | Endpoint |\n|-----------|----------|\n| Purge path | `POST \u002Fcache\u002F{org}\u002F{site}\u002Fmain\u002F{path}` |\n| Purge all | `POST \u002Fcache\u002F{org}\u002F{site}\u002Fmain\u002F*` |\n\n## Code Operations\n\n### Sync Code\n\n```bash\ncurl -X POST \\\n  -H \"x-auth-token: $AUTH_TOKEN\" \\\n  \"https:\u002F\u002Fadmin.hlx.page\u002Fcode\u002F{owner}\u002F{repo}\u002Fmain\"\n```\n\n## Common Tasks\n\n| Task | Steps |\n|------|-------|\n| **Add new admin** | POST to `\u002Fconfig\u002F{org}\u002Fsites\u002F{site}\u002Faccess\u002Fadmin.json` |\n| **Republish site** | POST to `\u002Fpreview\u002F{org}\u002F{site}\u002Fmain\u002F*` then `\u002Flive\u002F{org}\u002F{site}\u002Fmain\u002F*` |\n| **Clear all cache** | POST to `\u002Fcache\u002F{org}\u002F{site}\u002Fmain\u002F*` |\n| **Deploy code changes** | POST to `\u002Fcode\u002F{owner}\u002F{repo}\u002Fmain` |\n\n## Troubleshooting\n\n| Issue | Solution |\n|-------|----------|\n| 401 Unauthorized | Token expired - login again |\n| 403 Forbidden | Insufficient permissions - check role |\n| 404 Not Found | Check org\u002Fsite\u002Fpath spelling |\n| 429 Rate Limited | Wait and retry |\n| Cache not clearing | Try with `forceUpdate: true` |\n| Code not syncing | Manual sync: POST to `\u002Fcode\u002F{owner}\u002F{repo}\u002Fmain` |\n\n---\n\n## Resources\n\n| Resource | URL |\n|----------|-----|\n| Admin API Docs | https:\u002F\u002Fwww.aem.live\u002Fdocs\u002Fadmin.html |\n| Config Service | https:\u002F\u002Fwww.aem.live\u002Fdocs\u002Fconfig-service-setup |\n```\n\n## Phase 3: Customize for Project\n\n### 3.1 Fill in Project-Specific Values\n\nReplace all placeholders:\n- `{org}` → actual organization from Config Service API\n- `{site}` → actual site name(s)\n- `{owner}` → code owner from Config Service (GitHub org or Cloud Manager program)\n- `{repo}` → code repo from Config Service\n\n### 3.2 Add Multi-Site Details (if repoless)\n\nIf project has multiple sites, add a section listing all sites with their:\n- Site name\n- Preview URL\n- Live URL\n- Content source\n\n### 3.3 Document Project-Specific Configurations\n\nCheck for and document:\n- Custom headers (`\u002Fconfig\u002F{org}\u002Fsites\u002F{site}\u002Fheaders.json`)\n- CDN configuration\n- Any project-specific admin procedures\n\n---\n\n## Phase 4: Convert to Professional PDF\n\n### 4.1 Generate PDF (MANDATORY)\n\n**THIS STEP IS NOT OPTIONAL. YOU MUST GENERATE THE PDF NOW.**\n\n1. Save markdown to: `project-guides\u002FADMIN-GUIDE.md`\n   - File MUST start with YAML frontmatter:\n     ```yaml\n     ---\n     title: \"[Project Name] - Admin Guide\"\n     date: \"[Full Date - e.g., February 17, 2026]\"\n     ---\n     ```\n   - **Date format**: Always use full date with day, month, and year (e.g., \"February 17, 2026\"), NOT just month and year\n\n2. **IMMEDIATELY after saving the markdown**, invoke the PDF conversion skill:\n\n   ```\n   Skill({ skill: \"project-management:whitepaper\", args: \"project-guides\u002FADMIN-GUIDE.md project-guides\u002FADMIN-GUIDE.pdf\" })\n   ```\n\n3. Wait for PDF generation to complete (whitepaper skill auto-cleans source files)\n\n**DO NOT:**\n- Skip the PDF conversion step\n- Tell user \"PDF will be generated later\" — generate it NOW\n\n### 4.2 Deliver to User\n\nAfter PDF is generated, inform the user:\n\n```\n\"✓ Admin guide complete: project-guides\u002FADMIN-GUIDE.pdf\"\n```\n\n---\n\n## Output\n\n**FINAL OUTPUT:** `project-guides\u002FADMIN-GUIDE.pdf`\n\nAll source files (.md, .html, .plain.html) are deleted after PDF generation. Only the PDF remains.\n\n**Location:** `project-guides\u002F` folder\n\n---\n\n## Success Criteria\n\n**Data Source Validation (CRITICAL):**\n- [ ] Config Service API was called (`https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F{ORG}\u002Fsites.json`)\n- [ ] Site list came from API response, NOT from fstab.yaml or codebase analysis\n- [ ] Code repo info came from site config API, NOT from git remote\n\n**Content Validation:**\n- [ ] All org\u002Fsite values filled from Config Service API\n- [ ] Login URL correct\n- [ ] All API endpoints have correct org\u002Fsite\n- [ ] Multi-site documented (if applicable)\n- [ ] Common tasks listed with correct paths\n\n**Output Validation:**\n- [ ] PDF generated successfully\n- [ ] All source files cleaned up (only PDF remains)\n\n---\n\n## Tips\n\n1. **Always use Config Service API** - org\u002Fsite\u002Fcode repo may differ from what's in the local git remote\n2. **Test login URL** - Verify the login URL works before documenting\n3. **List all sites** - For repoless setups, document every site\n4. **Include examples** - Show actual paths from the project\n","# Project Handover - Admin Guide\n\nGenerate comprehensive documentation for administrators taking over an AEM Edge Delivery Services project. Produces a complete admin guide with Config Service setup, permissions, Admin API operations, and troubleshooting.\n\n## When to Use This Skill\n\n- Project handover to client administrators\n- Documenting admin procedures for a project\n- Creating operations runbook\n- \"Generate admin guide\"\n- \"Admin documentation\"\n- \"Admin handover\"\n\n---\n\n## Step 0: Navigate to Project Root and Verify Edge Delivery Services Project (CONDITIONAL)\n\n**Skip this step if `allGuides` flag is set** (orchestrator already validated and navigated).\n\n**CRITICAL: If NOT skipped, you MUST execute the `cd` command. Do NOT use absolute paths — actually change directory.**\n\n```bash\nALL_GUIDES=$(cat .claude-plugin\u002Fproject-config.json 2>\u002Fdev\u002Fnull | grep -o '\"allGuides\"[[:space:]]*:[[:space:]]*true')\nif [ -z \"$ALL_GUIDES\" ]; then\n  # Navigate to git project root (works from any subdirectory)\n  cd \"$(git rev-parse --show-toplevel)\"\n  # Verify it's an Edge Delivery Services project\n  ls scripts\u002Faem.js\nfi\n```\n\n**IMPORTANT:**\n- You MUST run the `cd` command above using the Bash tool\n- All subsequent steps operate from project root\n- Do NOT use absolute paths to verify — actually navigate\n- Guides will be created at `project-root\u002Fproject-guides\u002F`\n\n**If NOT skipped AND `scripts\u002Faem.js` does NOT exist**, respond:\n\n> \"This skill is designed for AEM Edge Delivery Services projects. The current directory does not appear to be an Edge Delivery Services project (`scripts\u002Faem.js` not found).\n>\n> Please navigate to an Edge Delivery Services project and try again.\"\n\n**STOP if check fails. Otherwise proceed — you are now at project root.**\n\n---\n\n## Execution Checklist\n\n```markdown\n- [ ] Phase 1: Gather Project Context\n- [ ] Phase 2: Generate Admin Guide Content\n- [ ] Phase 3: Customize for Project\n- [ ] Phase 4: Generate Professional PDF\n```\n\n---\n\n## Communication Guidelines\n\n- **NEVER use \"EDS\"** as an acronym for Edge Delivery Services in any generated documentation or chat responses\n- Always use the full name \"Edge Delivery Services\" or \"AEM Edge Delivery Services\"\n- This applies to all output files (PDF, HTML, markdown) and all communication with the user\n\n---\n\n## ⚠️ CRITICAL PATH REQUIREMENT\n\n**YOU MUST SAVE THE FILE TO THIS EXACT PATH:**\n\n```\nproject-guides\u002FADMIN-GUIDE.md\n```\n\n**BEFORE WRITING ANY FILE:**\n1. First, create the directory: `mkdir -p project-guides`\n2. Then write to: `project-guides\u002FADMIN-GUIDE.md`\n\n**WHY THIS MATTERS:** Files must be in `project-guides\u002F` for proper organization and PDF conversion.\n\n❌ **WRONG:** `ADMIN-GUIDE.md` (root)\n❌ **WRONG:** `docs\u002FADMIN-GUIDE.md`\n❌ **WRONG:** `\u002Fworkspace\u002FADMIN-GUIDE.md`\n✅ **CORRECT:** `project-guides\u002FADMIN-GUIDE.md`\n\n---\n\n## Output Format\n\n**MANDATORY OUTPUT:** `project-guides\u002FADMIN-GUIDE.pdf`\n\n**STRICTLY FORBIDDEN:**\n- ❌ Do NOT read or analyze `fstab.yaml` — it does NOT exist in most projects and does NOT show all sites\n- ❌ Do NOT create `.plain.html` files\n- ❌ Do NOT use `convert_markdown_to_html` tool — this converts the FULL guide to HTML with raw frontmatter visible, which is NOT what we want\n- ❌ Do NOT tell user to \"convert markdown to PDF manually\"\n- ❌ Do NOT save markdown to root directory or any path other than `project-guides\u002F`\n- ❌ Do NOT say \"PDF will be generated later\" or \"at session end\" — generate it NOW\n\n**The HTML output must be a SHORT summary page** (created with Write tool) containing:\n- Title and brief description\n- \"What's Inside\" bullet list\n- PDF download link\nNOT the full guide content converted to HTML.\n\n**REQUIRED WORKFLOW:**\n1. Run `mkdir -p project-guides` to ensure directory exists\n2. Generate markdown content with YAML frontmatter (title, date)\n3. Save to `project-guides\u002FADMIN-GUIDE.md` (EXACT PATH - no exceptions)\n4. **IMMEDIATELY** invoke PDF conversion (see Phase 4.1)\n5. Clean up all source files (only PDF remains)\n6. Final output: `project-guides\u002FADMIN-GUIDE.pdf`\n\n---\n\n## Phase 0: Get Organization Name (Required First)\n\n**Whenever this skill runs** — whether the user triggered it directly (e.g. \"generate admin guide\") or via the handover flow — you must have the Config Service organization name before doing anything else. Do not skip this phase.\n\n### 0.1 Check for Saved Organization\n\n```bash\n# Check if org name is already saved\ncat .claude-plugin\u002Fproject-config.json 2>\u002Fdev\u002Fnull | grep -o '\"org\"[[:space:]]*:[[:space:]]*\"[^\"]*\"' | head -1\n```\n\n### 0.2 Prompt for Organization Name (If Not Saved)\n\n**If no org name is saved**, you MUST pause and ask the user directly:\n\n> \"What is your Config Service organization name? This is the `{org}` part of your Edge Delivery Services URLs (e.g., `https:\u002F\u002Fmain--site--{org}.aem.page`). The org name may differ from your GitHub organization.\"\n\n**IMPORTANT RULES:**\n- **DO NOT use `AskUserQuestion` with predefined options** — ask as a plain text question\n- **Organization name is MANDATORY** — do not offer a \"skip\" option\n- **Wait for user to type the org name** before proceeding\n- If user doesn't provide a valid org name, ask again\n\n### 0.3 Save Organization Name\n\nOnce you have the org name (either from saved config or user input), save it for future use:\n\n```bash\n# Create config directory if needed\nmkdir -p .claude-plugin\n# Ensure .claude-plugin is in .gitignore (contains auth tokens)\ngrep -qxF '.claude-plugin\u002F' .gitignore 2>\u002Fdev\u002Fnull || echo '.claude-plugin\u002F' >> .gitignore\n\n# Save org name to config file (create or update)\nif [ -f .claude-plugin\u002Fproject-config.json ]; then\n  cat .claude-plugin\u002Fproject-config.json | sed 's\u002F\"org\"[[:space:]]*:[[:space:]]*\"[^\"]*\"\u002F\"org\": \"{ORG_NAME}\"\u002F' > \u002Ftmp\u002Fproject-config.json && mv \u002Ftmp\u002Fproject-config.json .claude-plugin\u002Fproject-config.json\nelse\n  echo '{\"org\": \"{ORG_NAME}\"}' > .claude-plugin\u002Fproject-config.json\nfi\n```\n\nReplace `{ORG_NAME}` with the actual organization name provided by the user.\n\n---\n\n## Phase 0.5: Authenticate with Config Service (Browser Login)\n\n**After getting the organization name, authenticate using Playwright browser automation.**\n\n### 0.5.1 Check for Existing Auth Token\n\n```bash\n# Check if auth token is already saved\nAUTH_TOKEN=$(cat .claude-plugin\u002Fproject-config.json 2>\u002Fdev\u002Fnull | grep -o '\"authToken\"[[:space:]]*:[[:space:]]*\"[^\"]*\"' | sed 's\u002F\"authToken\"[[:space:]]*:[[:space:]]*\"\u002F\u002F' | sed 's\u002F\"$\u002F\u002F')\n\nif [ -n \"$AUTH_TOKEN\" ]; then\n  echo \"Auth token found\"\nelse\n  echo \"No auth token - need to authenticate\"\nfi\n```\n\n### 0.5.2 Open Browser for Login (If No Token)\n\nIf no auth token exists, use Playwright CLI:\n\n1. **Install Playwright (if needed)**:\n```bash\nnpx playwright --version 2>\u002Fdev\u002Fnull || npm install -g playwright\nnpx playwright install chromium 2>\u002Fdev\u002Fnull || true\n```\n\n2. **Get the first site name** (unauthenticated endpoint):\n```bash\nORG=$(cat .claude-plugin\u002Fproject-config.json | grep -o '\"org\"[[:space:]]*:[[:space:]]*\"[^\"]*\"' | sed 's\u002F\"org\"[[:space:]]*:[[:space:]]*\"\u002F\u002F' | sed 's\u002F\"$\u002F\u002F')\nSITE=$(curl -s \"https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F${ORG}\u002Fsites.json\" | grep -o '\"name\"[[:space:]]*:[[:space:]]*\"[^\"]*\"' | head -1 | sed 's\u002F\"name\"[[:space:]]*:[[:space:]]*\"\u002F\u002F' | sed 's\u002F\"$\u002F\u002F')\n```\n\n3. **Display clear instructions and open browser**:\n```bash\necho \"\"\necho \"╔════════════════════════════════════════════════════════════════╗\"\necho \"║                                                                ║\"\necho \"║   BROWSER WINDOW OPENING FOR ADOBE ID LOGIN                    ║\"\necho \"║                                                                ║\"\necho \"║   1. Sign in with your Adobe ID credentials                   ║\"\necho \"║   2. After successful login, CLOSE THE BROWSER WINDOW         ║\"\necho \"║                                                                ║\"\necho \"║   >>> CLOSE THE BROWSER TO CONTINUE \u003C\u003C\u003C                       ║\"\necho \"║                                                                ║\"\necho \"╚════════════════════════════════════════════════════════════════╝\"\necho \"\"\n\nmkdir -p .claude-plugin\nnpx playwright open --save-storage=.claude-plugin\u002Fauth-storage.json \"https:\u002F\u002Fadmin.hlx.page\u002Flogin\u002F${ORG}\u002F${SITE}\u002Fmain\"\n```\n\n### 0.5.3 Extract and Save Auth Token\n\nAfter browser is closed, extract token from storage file:\n\n```bash\necho \"Browser closed. Extracting auth token...\"\n\nAUTH_TOKEN=$(node -e \"\nconst fs = require('fs');\nconst data = JSON.parse(fs.readFileSync('.claude-plugin\u002Fauth-storage.json', 'utf8'));\nconst cookie = data.cookies.find(c => c.name === 'auth_token');\nconsole.log(cookie ? cookie.value : '');\n\")\n\nORG=$(cat .claude-plugin\u002Fproject-config.json | grep -o '\"org\"[[:space:]]*:[[:space:]]*\"[^\"]*\"' | sed 's\u002F\"org\"[[:space:]]*:[[:space:]]*\"\u002F\u002F' | sed 's\u002F\"$\u002F\u002F')\necho \"{\\\"org\\\": \\\"${ORG}\\\", \\\"authToken\\\": \\\"${AUTH_TOKEN}\\\"}\" > .claude-plugin\u002Fproject-config.json\n\nrm -f .claude-plugin\u002Fauth-storage.json\necho \"Auth token saved.\"\n```\n\n### 0.5.4 Verify Authentication\n\nTest the token works:\n```bash\nAUTH_TOKEN=$(cat .claude-plugin\u002Fproject-config.json | grep -o '\"authToken\"[[:space:]]*:[[:space:]]*\"[^\"]*\"' | sed 's\u002F\"authToken\"[[:space:]]*:[[:space:]]*\"\u002F\u002F' | sed 's\u002F\"$\u002F\u002F')\nORG=$(cat .claude-plugin\u002Fproject-config.json | grep -o '\"org\"[[:space:]]*:[[:space:]]*\"[^\"]*\"' | sed 's\u002F\"org\"[[:space:]]*:[[:space:]]*\"\u002F\u002F' | sed 's\u002F\"$\u002F\u002F')\n\n# Test with authenticated endpoint\ncurl -s -w \"%{http_code}\" -o \u002Fdev\u002Fnull -H \"x-auth-token: ${AUTH_TOKEN}\" \\\n  \"https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F${ORG}\u002Fsites.json\"\n```\n\nIf returns 200, authentication is successful. If 401, re-authenticate.\n\n---\n\n## Phase 1: Gather Project Context\n\n### 1.1 Fetch Sites and Code Repo via Config Service API\n\n**⚠️ MANDATORY DATA SOURCE — NO ALTERNATIVES ALLOWED**\n\nYou MUST call the Config Service API. This is the ONLY acceptable source for site information.\n\n**❌ PROHIBITED APPROACHES (will produce incorrect results):**\n- Analyzing `fstab.yaml` — does NOT show all sites in repoless setups\n- Reading `README.md` — may be outdated or incomplete\n- Inferring from codebase structure — misses CDN configs and additional sites\n- Using git remote URLs — org name may differ from Config Service org\n- Making assumptions based on project folder names\n\n**✅ REQUIRED: Execute and save response:**\n\n```bash\nORG=$(cat .claude-plugin\u002Fproject-config.json | grep -o '\"org\"[[:space:]]*:[[:space:]]*\"[^\"]*\"' | sed 's\u002F\"org\"[[:space:]]*:[[:space:]]*\"\u002F\u002F' | sed 's\u002F\"$\u002F\u002F')\n\n# Save response to file - Step 1.2 depends on this file\ncurl -s -H \"Accept: application\u002Fjson\" \"https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F${ORG}\u002Fsites.json\" > .claude-plugin\u002Fsites-config.json\n```\n\n**📁 REQUIRED ARTIFACT:** `.claude-plugin\u002Fsites-config.json`\n\n**API Reference:** https:\u002F\u002Fwww.aem.live\u002Fdocs\u002Fadmin.html#tag\u002FsiteConfig\u002Foperation\u002FgetConfigSites\n\n---\n\nThe response is a JSON object with a `sites` array (each entry has a `name` field). Extract site names and construct per-site URLs:\n- **Preview:** `https:\u002F\u002Fmain--{site-name}--{org}.aem.page\u002F`\n- **Live:** `https:\u002F\u002Fmain--{site-name}--{org}.aem.live\u002F`\n\nMultiple sites = **repoless** setup. Single site = **standard** setup.\n\n**Then fetch individual site config for code and content details:**\n\n```bash\nAUTH_TOKEN=$(cat .claude-plugin\u002Fproject-config.json | grep -o '\"authToken\"[[:space:]]*:[[:space:]]*\"[^\"]*\"' | sed 's\u002F\"authToken\"[[:space:]]*:[[:space:]]*\"\u002F\u002F' | sed 's\u002F\"$\u002F\u002F')\ncurl -s -H \"x-auth-token: ${AUTH_TOKEN}\" \"https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F${ORG}\u002Fsites\u002F{site-name}.json\"\n```\n\n**Example response:**\n```json\n{\n  \"code\": {\n    \"owner\": \"github-owner\",\n    \"repo\": \"repo-name\",\n    \"source\": { \"type\": \"github\", \"url\": \"https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\" }\n  },\n  \"content\": {\n    \"source\": {\n      \"url\": \"https:\u002F\u002Fcontent.da.live\u002Forg-name\u002Fsite-name\u002F\",\n      \"type\": \"markup\"\n    }\n  }\n}\n```\n\n**Extract from response:**\n- `code.owner` \u002F `code.repo` — GitHub repository\n- `content.source.url` — Content mountpath (e.g., `https:\u002F\u002Fcontent.da.live\u002Forg\u002Fsite\u002F`)\n- `content.source.type` — Content source type (markup, onedrive, google)\n\n**⚠️ Do NOT use `fstab.yaml`** — use Config Service API instead.\n\n### 1.2 Build Context\n\n**Read from artifact created in 1.1:**\n\n```bash\ncat .claude-plugin\u002Fsites-config.json\n```\n\nParse the JSON to extract site names, then fetch each site's config for code repo:\n\n```bash\ncurl -s -H \"Accept: application\u002Fjson\" \"https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F${ORG}\u002Fsites\u002F{site-name}.json\"\n```\n\nUse these API responses to build context: site names, code repo (owner\u002Frepo), preview\u002Flive URLs. If site config includes a content source (e.g. content.da.live path), record it for the Sites table.\n\n```\nAdmin Context:\n├── Organization: {org from saved config}\n├── Site(s): {site1}, {site2}, ... (from Config Service API response)\n├── Setup Type: {repoless | standard} (from Config Service API)\n├── Code Repo: {code.owner}\u002F{code.repo} (from Config Service — GitHub or Cloud Manager)\n├── Preview: https:\u002F\u002Fmain--{site}--{org}.aem.page\u002F\n├── Live: https:\u002F\u002Fmain--{site}--{org}.aem.live\u002F\n├── Login URL: https:\u002F\u002Fadmin.hlx.page\u002Flogin\u002F{org}\u002F{site}\n└── Config Service: https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F{org}\u002F\n```\n\n---\n\n## Phase 2: Generate Admin Guide\n\n### Output File: `project-guides\u002FADMIN-GUIDE.md`\n\nGenerate the admin handover document with the following structure:\n\n```markdown\n# [Project Name] - Admin Guide\n\nComplete administration guide for managing this Edge Delivery Services project.\n\n## Quick Reference\n\n### URLs\n\n| Purpose | URL |\n|---------|-----|\n| **Login** | https:\u002F\u002Fadmin.hlx.page\u002Flogin\u002F{org}\u002F{site} |\n| **Config Service** | https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F{org}\u002F |\n| **Preview** | https:\u002F\u002Fmain--{site}--{org}.aem.page\u002F |\n| **Live** | https:\u002F\u002Fmain--{site}--{org}.aem.live\u002F |\n\n### Sites (if multi-site\u002Frepoless)\n\n| Site | Content Source (DA) | Preview | Live |\n|------|---------------------|---------|------|\n| {site1} | [from site config if present] | https:\u002F\u002Fmain--{site1}--{org}.aem.page\u002F | https:\u002F\u002Fmain--{site1}--{org}.aem.live\u002F |\n| {site2} | [from site config if present] | https:\u002F\u002Fmain--{site2}--{org}.aem.page\u002F | https:\u002F\u002Fmain--{site2}--{org}.aem.live\u002F |\n\n## Authentication\n\n### Login\n\n1. Open: https:\u002F\u002Fadmin.hlx.page\u002Flogin\u002F{org}\u002F{site}\n2. Sign in with your Adobe ID\n3. Copy auth token for API operations\n\n### Logout\n\n```bash\ncurl -X POST \\\n  -H \"x-auth-token: $AUTH_TOKEN\" \\\n  \"https:\u002F\u002Fadmin.hlx.page\u002Flogout\u002F{org}\u002F{site}\u002Fmain\"\n```\n\n## User Management\n\n### View Current Access\n\n```bash\ncurl -H \"x-auth-token: $AUTH_TOKEN\" \\\n  \"https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F{org}\u002Fsites\u002F{site}\u002Faccess.json\"\n```\n\n### Add User\n\n| Role | Command |\n|------|---------|\n| Admin | `POST \u002Fconfig\u002F{org}\u002Fsites\u002F{site}\u002Faccess\u002Fadmin.json` with `{\"users\": [\"email\"]}` |\n| Author | `POST \u002Fconfig\u002F{org}\u002Fsites\u002F{site}\u002Faccess\u002Fauthor.json` with `{\"users\": [\"email\"]}` |\n\n### Remove User\n\n```bash\ncurl -X DELETE \\\n  -H \"x-auth-token: $AUTH_TOKEN\" \\\n  \"https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F{org}\u002Fsites\u002F{site}\u002Faccess\u002Fadmin\u002F{email}.json\"\n```\n\n## Content Operations\n\n### Preview\n\n| Operation | Endpoint |\n|-----------|----------|\n| Single page | `POST \u002Fpreview\u002F{org}\u002F{site}\u002Fmain\u002F{path}` |\n| Bulk preview | `POST \u002Fpreview\u002F{org}\u002F{site}\u002Fmain\u002F*` |\n\n### Publish\n\n| Operation | Endpoint |\n|-----------|----------|\n| Single page | `POST \u002Flive\u002F{org}\u002F{site}\u002Fmain\u002F{path}` |\n| Bulk publish | `POST \u002Flive\u002F{org}\u002F{site}\u002Fmain\u002F*` |\n| Unpublish | `DELETE \u002Flive\u002F{org}\u002F{site}\u002Fmain\u002F{path}` |\n\n### Cache\n\n| Operation | Endpoint |\n|-----------|----------|\n| Purge path | `POST \u002Fcache\u002F{org}\u002F{site}\u002Fmain\u002F{path}` |\n| Purge all | `POST \u002Fcache\u002F{org}\u002F{site}\u002Fmain\u002F*` |\n\n## Code Operations\n\n### Sync Code\n\n```bash\ncurl -X POST \\\n  -H \"x-auth-token: $AUTH_TOKEN\" \\\n  \"https:\u002F\u002Fadmin.hlx.page\u002Fcode\u002F{owner}\u002F{repo}\u002Fmain\"\n```\n\n## Common Tasks\n\n| Task | Steps |\n|------|-------|\n| **Add new admin** | POST to `\u002Fconfig\u002F{org}\u002Fsites\u002F{site}\u002Faccess\u002Fadmin.json` |\n| **Republish site** | POST to `\u002Fpreview\u002F{org}\u002F{site}\u002Fmain\u002F*` then `\u002Flive\u002F{org}\u002F{site}\u002Fmain\u002F*` |\n| **Clear all cache** | POST to `\u002Fcache\u002F{org}\u002F{site}\u002Fmain\u002F*` |\n| **Deploy code changes** | POST to `\u002Fcode\u002F{owner}\u002F{repo}\u002Fmain` |\n\n## Troubleshooting\n\n| Issue | Solution |\n|-------|----------|\n| 401 Unauthorized | Token expired - login again |\n| 403 Forbidden | Insufficient permissions - check role |\n| 404 Not Found | Check org\u002Fsite\u002Fpath spelling |\n| 429 Rate Limited | Wait and retry |\n| Cache not clearing | Try with `forceUpdate: true` |\n| Code not syncing | Manual sync: POST to `\u002Fcode\u002F{owner}\u002F{repo}\u002Fmain` |\n\n---\n\n## Resources\n\n| Resource | URL |\n|----------|-----|\n| Admin API Docs | https:\u002F\u002Fwww.aem.live\u002Fdocs\u002Fadmin.html |\n| Config Service | https:\u002F\u002Fwww.aem.live\u002Fdocs\u002Fconfig-service-setup |\n```\n\n## Phase 3: Customize for Project\n\n### 3.1 Fill in Project-Specific Values\n\nReplace all placeholders:\n- `{org}` → actual organization from Config Service API\n- `{site}` → actual site name(s)\n- `{owner}` → code owner from Config Service (GitHub org or Cloud Manager program)\n- `{repo}` → code repo from Config Service\n\n### 3.2 Add Multi-Site Details (if repoless)\n\nIf project has multiple sites, add a section listing all sites with their:\n- Site name\n- Preview URL\n- Live URL\n- Content source\n\n### 3.3 Document Project-Specific Configurations\n\nCheck for and document:\n- Custom headers (`\u002Fconfig\u002F{org}\u002Fsites\u002F{site}\u002Fheaders.json`)\n- CDN configuration\n- Any project-specific admin procedures\n\n---\n\n## Phase 4: Convert to Professional PDF\n\n### 4.1 Generate PDF (MANDATORY)\n\n**THIS STEP IS NOT OPTIONAL. YOU MUST GENERATE THE PDF NOW.**\n\n1. Save markdown to: `project-guides\u002FADMIN-GUIDE.md`\n   - File MUST start with YAML frontmatter:\n     ```yaml\n     ---\n     title: \"[Project Name] - Admin Guide\"\n     date: \"[Full Date - e.g., February 17, 2026]\"\n     ---\n     ```\n   - **Date format**: Always use full date with day, month, and year (e.g., \"February 17, 2026\"), NOT just month and year\n\n2. **IMMEDIATELY after saving the markdown**, invoke the PDF conversion skill:\n\n   ```\n   Skill({ skill: \"project-management:whitepaper\", args: \"project-guides\u002FADMIN-GUIDE.md project-guides\u002FADMIN-GUIDE.pdf\" })\n   ```\n\n3. Wait for PDF generation to complete (whitepaper skill auto-cleans source files)\n\n**DO NOT:**\n- Skip the PDF conversion step\n- Tell user \"PDF will be generated later\" — generate it NOW\n\n### 4.2 Deliver to User\n\nAfter PDF is generated, inform the user:\n\n```\n\"✓ Admin guide complete: project-guides\u002FADMIN-GUIDE.pdf\"\n```\n\n---\n\n## Output\n\n**FINAL OUTPUT:** `project-guides\u002FADMIN-GUIDE.pdf`\n\nAll source files (.md, .html, .plain.html) are deleted after PDF generation. Only the PDF remains.\n\n**Location:** `project-guides\u002F` folder\n\n---\n\n## Success Criteria\n\n**Data Source Validation (CRITICAL):**\n- [ ] Config Service API was called (`https:\u002F\u002Fadmin.hlx.page\u002Fconfig\u002F{ORG}\u002Fsites.json`)\n- [ ] Site list came from API response, NOT from fstab.yaml or codebase analysis\n- [ ] Code repo info came from site config API, NOT from git remote\n\n**Content Validation:**\n- [ ] All org\u002Fsite values filled from Config Service API\n- [ ] Login URL correct\n- [ ] All API endpoints have correct org\u002Fsite\n- [ ] Multi-site documented (if applicable)\n- [ ] Common tasks listed with correct paths\n\n**Output Validation:**\n- [ ] PDF generated successfully\n- [ ] All source files cleaned up (only PDF remains)\n\n---\n\n## Tips\n\n1. **Always use Config Service API** - org\u002Fsite\u002Fcode repo may differ from what's in the local git remote\n2. **Test login URL** - Verify the login URL works before documenting\n3. **List all sites** - For repoless setups, document every site\n4. **Include examples** - Show actual paths from the project\n",{"name":5,"license":15,"metadata":24,"description":7,"allowed-tools":26},{"version":25},"1.0.0","Read, Write, Edit, Bash, AskUserQuestion, Skill","main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fadobe-admin","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add kalash33\u002Fkstack --skill admin",{"tool":41,"command":42},"bunx","bunx skills add kalash33\u002Fkstack --skill admin",{"tool":44,"command":45},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill admin","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-admin\u002FSKILL.md",true,[49,55,59],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},".releaserc.json","REFERENCE","参考文档",49,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-admin\u002F.releaserc.json",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"CHANGELOG.md",5882,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-admin\u002FCHANGELOG.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"package.json",85,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-admin\u002Fpackage.json",[64,72,79,86,93,100],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M73CF80XCM9K81567MJ8QZFW","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M73CF4YPMF3RA8ZJDXZSMD93","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]