Implement custom AEM Workflow Java components on AEM as a Cloud Service. Use when writing WorkflowProcess steps, ParticipantStepChooser implementations, registering services via OSGi DS R6 annotations, reading step arguments from MetaDataMap, accessing JCR payload via WorkflowSession adapter, reading and writing workflow metadata and variables, and handling errors with WorkflowException for retry behavior.
80
100%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 an excellent skill description that clearly defines a narrow, well-scoped domain (AEM Workflow Java components) with highly specific actions and trigger terms. It follows the recommended pattern with an explicit 'Use when...' clause and uses third-person voice throughout. The technical specificity ensures minimal conflict risk with other skills while providing strong signal for when to select it.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists multiple specific concrete actions: writing WorkflowProcess steps, ParticipantStepChooser implementations, registering services via OSGi DS R6 annotations, reading step arguments from MetaDataMap, accessing JCR payload via WorkflowSession adapter, reading/writing workflow metadata and variables, and handling errors with WorkflowException. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement custom AEM Workflow Java components) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios like writing WorkflowProcess steps, registering OSGi services, reading MetaDataMap arguments, etc. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a developer would use: 'AEM', 'Workflow', 'WorkflowProcess', 'ParticipantStepChooser', 'OSGi', 'MetaDataMap', 'WorkflowSession', 'JCR payload', 'WorkflowException', 'AEM as a Cloud Service'. These are precisely the terms an AEM developer would mention when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a very specific niche: AEM Workflow Java components on AEM as a Cloud Service. The combination of AEM-specific terminology (WorkflowProcess, ParticipantStepChooser, MetaDataMap, WorkflowSession) makes it extremely unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that efficiently covers AEM workflow development for Cloud Service. It provides two complete, executable Java templates with proper OSGi annotations, a clear development workflow checklist, important guardrails for common pitfalls, and well-organized references for deeper content. The content is concise, actionable, and well-structured throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows Java, OSGi, and AEM concepts without explaining them. Every section serves a purpose — templates are concrete, guardrails are specific, and there's no padding or unnecessary explanation. | 3 / 3 |
Actionability | Both templates are fully executable Java classes with correct annotations, method signatures, and realistic inline comments showing how to read arguments, access payloads, and handle errors. The code is copy-paste ready and covers the two main component types. | 3 / 3 |
Workflow Clarity | The checklist-style workflow clearly sequences the 8 development steps from identification through deployment verification. Error handling is explicitly addressed (step 7: throw WorkflowException for retry), and the guardrails section adds critical validation constraints around session management and resource resolvers. | 3 / 3 |
Progressive Disclosure | The SKILL.md provides a concise overview with executable templates inline, then clearly signals five one-level-deep reference files organized into logical categories (process patterns, participant patterns, variables, API reference, guardrails). Navigation is straightforward and well-structured. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
9ca1da2
Table of Contents
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.