admin
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".
61
73%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/aem/project-management/skills/admin/SKILL.mdQuality
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its domain (AEM Edge Delivery Services admin documentation), lists specific capabilities, and includes explicit trigger guidance. The main weakness is that the trigger terms are somewhat limited and could include more natural variations users might use. The description is concise and uses appropriate third-person voice.
Suggestions
Expand trigger terms to include more natural variations like 'AEM admin setup', 'Edge Delivery permissions', 'cache management guide', 'code sync documentation', or 'project handover docs'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: Config Service setup, permissions, access control, Admin API operations, cache management, and code sync. These are clearly defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (generates admin documentation covering Config Service setup, permissions, access control, Admin API operations, cache management, code sync) and 'when' (explicit 'Use for' clause with trigger terms 'admin guide', 'admin documentation', 'admin handover'). | 3 / 3 |
Trigger Term Quality | Includes some natural keywords like 'admin guide', 'admin documentation', 'admin handover', but misses common variations users might say such as 'AEM admin', 'Edge Delivery admin', 'permissions setup', 'cache management docs', or 'project handover documentation'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific niche: AEM Edge Delivery Services admin documentation for project handover. The combination of AEM EDS, admin-specific topics, and handover context makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is highly actionable with executable commands and a well-structured multi-phase workflow with proper validation checkpoints. However, it is severely bloated by excessive repetition of constraints and prohibitions — the same warnings about fstab.yaml, file paths, and PDF generation appear multiple times. The monolithic structure with the full output template inline makes it harder to maintain and consumes unnecessary tokens.
Suggestions
Consolidate repeated warnings (fstab.yaml prohibition, path requirements, PDF generation urgency) into a single 'Constraints' section at the top instead of scattering them throughout the document.
Extract the Phase 2 admin guide markdown template into a separate bundle file (e.g., templates/ADMIN-GUIDE-TEMPLATE.md) to reduce the main skill's size and improve progressive disclosure.
Remove redundant emphasis formatting — stating a rule once clearly is sufficient; repeating it with ⚠️, ❌, CRITICAL, MANDATORY, etc. wastes tokens without adding clarity for Claude.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Massive repetition of warnings (fstab.yaml prohibition repeated 3+ times, path requirements repeated 4+ times, PDF generation urgency repeated 3+ times). Extensive 'DO NOT' lists and redundant checklists. Claude doesn't need to be told the same constraint five different ways. | 1 / 3 |
Actionability | Highly actionable with concrete, executable bash commands and curl calls throughout. API endpoints are specific, code blocks are copy-paste ready with clear variable substitution patterns, and the workflow includes real commands for every step from authentication to PDF generation. | 3 / 3 |
Workflow Clarity | Clear multi-phase workflow with explicit sequencing (Phase 0 → 0.5 → 1 → 2 → 3 → 4), validation checkpoints (verify authentication with HTTP status codes, check for existing tokens, verify project type), and error recovery (re-authenticate on 401, re-ask for org name). The execution checklist and success criteria provide additional verification. | 3 / 3 |
Progressive Disclosure | The skill is monolithic — all content is inline in a single massive file with no bundle files to offload detail. The Phase 2 template content (the full admin guide markdown) could be in a separate template file. References to external resources (admin API docs, config service docs) exist but the skill itself is a wall of text that mixes orchestration logic with output templates. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (590 lines); consider splitting into references/ and linking | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 9 / 11 Passed | |
- Repository
- adobe/skills
- Commit
31eb0a2
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.