How do I install the Inject In Sling Model skill?

Run npx skillmds@latest add adobe/inject-in-sling-model-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Inject In Sling Model safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Inject In Sling Model?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Inject In Sling Model free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Inject In Sling Model?

Adobe (@adobe) published this skill as a verified publisher. Their other Agent Skills are listed on their SkillMD profile.

Inject In Sling Model by adobe — Agent Skill

Name: Inject In Sling Model
Rating: 4.2 (5 reviews)
Author: Adobe

Inject In Sling Model

AEM Cloud Service expert skill — migrate javax.inject.@Inject fields in Sling Model (@Model) classes to injector-specific annotations (@ValueMapValue / @OSGiService / @SlingObject). Self-discoverable (scan for @Model classes with field-level @Inject); the replacement is chosen deterministically from each field's declared type. Use for "fix @Inject in HeroModel.java", "modernize my Sling Models", or when scanning an AEM project for @Inject misuse. Detailed decision table, companion-annotation handling, import management, and file-level skip policy are in recipe.md.

Adobe Updated Sep 22, 2026 142 repo stars

File contents

@Inject in Sling Models — AEM as a Cloud Service

This pattern is executed by the code-assessment runbook — follow ../references/runbook.md for the full flow (preflight → plan → apply → verify, run log). This skill supplies the detection + recipe the runbook applies.

Overview

javax.inject.@Inject on fields of @Model classes is discouraged by the Apache Sling Models documentation. Removing @Inject without a replacement breaks injection, so each field is migrated to an injector-specific annotation chosen from its declared type.

Classification — confirm this pattern applies

A *.java file whose class is annotated @Model, with at least one field annotated @Inject.
Constructor-parameter and setter-method @Inject are out of scope (trigger the file-level skip).

Discovery

Detection is performed by the analyzer (../scripts/analyze.sh), run by the runbook:

bash ../scripts/analyze.sh <workspace-root> --pattern inject-in-sling-model

Match criteria (what the detector flags): a class annotated @Model (org.apache.sling.models.annotations.Model, confirmed import-aware) with at least one field annotated @Inject (javax.inject.Inject or jakarta.inject.Inject). One finding per matching field. Constructor/setter @Inject and non-@Model classes are not flagged. The replacement annotation is chosen from the field's declared type by the decision table in recipe.md.

Resolution contract

self-evident — the replacement annotation is fully determined by the field's declared Java type via the decision table in recipe.md. No external input is required.

Review checklist

Each migrated field maps to exactly one injector-specific annotation per the decision table
Sling objects (Resource / ResourceResolver / request / response) → @SlingObject, not @Self
@Named merged into the new annotation's name; @Default / @Via preserved
@Optional → per-field injectionStrategy = InjectionStrategy.OPTIONAL (never a class-level defaultInjectionStrategy change)
Unused imports removed; new imports added and ordered per the file's convention
File-level skip respected — no partial migration of a file with any ambiguous field

Recipe

Read recipe.md in full before editing: input contract, decision table, companion annotations, import management, unlocatable / skip-file policy, per-file procedure, before/after example, editing strategy.

Handoff

The skill never commits. See ../references/git-workflow.md for git vs in-place handoff and the suggested commit message.

---name: inject-in-sling-model-2description: AEM Cloud Service expert skill — migrate javax.inject.@Inject fields in Sling Model (@Model) classes to injector-specific annotations (@ValueMapValue / @OSGiService / @SlingObject). Self-discoverable (scan for @Model classes with field-level @Inject); the replacement is chosen deterministically from each field's declared type. Use for "fix @Inject in HeroModel.java", "modernize my Sling Models", or when scanning an AEM project for @Inject misuse. Detailed decision table, companion-annotation handling, import management, and file-level skip policy are in recipe.md.license: Apache-2.0---# @Inject in Sling Models — AEM as a Cloud Service> This pattern is executed by the code-assessment runbook — follow [`../references/runbook.md`](../references/runbook.md) for the full flow (preflight → plan → apply → verify, run log). This skill supplies the detection + recipe the runbook applies.## Overview`javax.inject.@Inject` on fields of `@Model` classes is discouraged by the Apache Sling Models documentation. Removing `@Inject` without a replacement breaks injection, so each field is migrated to an injector-specific annotation chosen from its declared type.## Classification — confirm this pattern applies- A `*.java` file whose class is annotated `@Model`, with at least one **field** annotated `@Inject`.- Constructor-parameter and setter-method `@Inject` are out of scope (trigger the file-level skip).## DiscoveryDetection is performed by the analyzer ([`../scripts/analyze.sh`](../scripts/README.md)), run bythe runbook:```bashbash ../scripts/analyze.sh <workspace-root> --pattern inject-in-sling-model```**Match criteria (what the detector flags):** a class annotated `@Model`(`org.apache.sling.models.annotations.Model`, confirmed import-aware) with at least one **field**annotated `@Inject` (`javax.inject.Inject` or `jakarta.inject.Inject`). One finding per matchingfield. Constructor/setter `@Inject` and non-`@Model` classes are not flagged. The replacementannotation is chosen from the field's declared type by the decision table in `recipe.md`.## Resolution contract**self-evident** — the replacement annotation is fully determined by the field's declared Java type via the decision table in `recipe.md`. No external input is required.## Review checklist- [ ] Each migrated field maps to exactly one injector-specific annotation per the decision table- [ ] Sling objects (`Resource` / `ResourceResolver` / request / response) → `@SlingObject`, **not** `@Self`- [ ] `@Named` merged into the new annotation's `name`; `@Default` / `@Via` preserved- [ ] `@Optional` → per-field `injectionStrategy = InjectionStrategy.OPTIONAL` (**never** a class-level `defaultInjectionStrategy` change)- [ ] Unused imports removed; new imports added and ordered per the file's convention- [ ] File-level skip respected — no partial migration of a file with any ambiguous field## RecipeRead [`recipe.md`](recipe.md) in full before editing: input contract, decision table, companion annotations, import management, unlocatable / skip-file policy, per-file procedure, before/after example, editing strategy.## HandoffThe skill never commits. See [`../references/git-workflow.md`](../references/git-workflow.md) for git vs in-place handoff and the suggested commit message.

Frequently asked questions