Monitor CI
nrwl/nx
Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.
AEM Cloud Service expert skill — check a JCR/Oak query is actually served by an index and, when it is not, propose the property/Lucene index-definition change so the query is answered by the index…
Install Tuning Oak Query Indexes
$ npx skills add adobe/skills --skill tuning-oak-query-indexes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install adobe/skills tuning-oak-query-indexes --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/adobe/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/aem/cloud-service/skills/code-assessment/tuning-oak-query-indexes .claude/skills/tuning-oak-query-indexes && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "tuning-oak-query-indexes" agent skill from https://github.com/adobe/skills/tree/main/plugins/aem/cloud-service/skills/code-assessment/tuning-oak-query-indexes into .claude/skills/tuning-oak-query-indexes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tuning-oak-query-indexes", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/adobe/skills/tree/main/plugins/aem/cloud-service/skills/code-assessment/tuning-oak-query-indexesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add adobe/skills --skill tuning-oak-query-indexes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install adobe/skills tuning-oak-query-indexes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adobe/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/aem/cloud-service/skills/code-assessment/tuning-oak-query-indexes .agents/skills/tuning-oak-query-indexes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tuning-oak-query-indexes" agent skill from https://github.com/adobe/skills/tree/main/plugins/aem/cloud-service/skills/code-assessment/tuning-oak-query-indexes into .agents/skills/tuning-oak-query-indexes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tuning-oak-query-indexes", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add adobe/skills --skill tuning-oak-query-indexes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install adobe/skills tuning-oak-query-indexes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adobe/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/aem/cloud-service/skills/code-assessment/tuning-oak-query-indexes .cursor/skills/tuning-oak-query-indexes && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "tuning-oak-query-indexes" agent skill from https://github.com/adobe/skills/tree/main/plugins/aem/cloud-service/skills/code-assessment/tuning-oak-query-indexes into .cursor/skills/tuning-oak-query-indexes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tuning-oak-query-indexes", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/adobe/skills.git --path plugins/aem/cloud-service/skills/code-assessment/tuning-oak-query-indexes--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add adobe/skills --skill tuning-oak-query-indexes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install adobe/skills tuning-oak-query-indexes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adobe/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/aem/cloud-service/skills/code-assessment/tuning-oak-query-indexes .gemini/skills/tuning-oak-query-indexes && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "tuning-oak-query-indexes" agent skill from https://github.com/adobe/skills/tree/main/plugins/aem/cloud-service/skills/code-assessment/tuning-oak-query-indexes into .gemini/skills/tuning-oak-query-indexes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tuning-oak-query-indexes", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install adobe/skills tuning-oak-query-indexesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add adobe/skills --skill tuning-oak-query-indexes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/adobe/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/aem/cloud-service/skills/code-assessment/tuning-oak-query-indexes .github/skills/tuning-oak-query-indexes && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "tuning-oak-query-indexes" agent skill from https://github.com/adobe/skills/tree/main/plugins/aem/cloud-service/skills/code-assessment/tuning-oak-query-indexes into .github/skills/tuning-oak-query-indexes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tuning-oak-query-indexes", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add adobe/skills --skill tuning-oak-query-indexes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install adobe/skills tuning-oak-query-indexes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adobe/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/aem/cloud-service/skills/code-assessment/tuning-oak-query-indexes .opencode/skills/tuning-oak-query-indexes && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "tuning-oak-query-indexes" agent skill from https://github.com/adobe/skills/tree/main/plugins/aem/cloud-service/skills/code-assessment/tuning-oak-query-indexes into .opencode/skills/tuning-oak-query-indexes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tuning-oak-query-indexes", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
tuning-oak-query-indexes- GitHub stars
- 197
- Token cost
- ~1.5k tokens
- SKILL.md length
- 627 words
- Files
- 4 (incl. references)
- Skills in repo
- 66
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
AEM Cloud Service expert skill — check a JCR/Oak query is actually served by an index and, when it is not, propose the property/Lucene index-definition change so the query is answered by the index…
- Traversal warning
- SKILL.md covers Overview, Classification — confirm this…, Discovery and Resolution contract, plus 2 more sections
- Calls bash
- Is my query indexed
What it does
Tuning Oak Query Indexes is an agent skill from adobe/skills. AEM Cloud Service expert skill — check a JCR/Oak query is actually served by an index and, when it is not, propose the property/Lucene index-definition change so the query is answered by the index instead of in-memory filtering or sorting. Use for "query is slow", "traversal warning", "is my query indexed", "tune oak index", or a scan that flags a JCR/QueryBuilder query. The analyzer locates every query-construction site (createQuery, getQueryManager, Sling findResources / queryResources, PredicateGroup.create /…
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `recipe.md`, `references/ai-agent-indexing-guide.md` and `references/extracting-jcr-queries.md`).
It sits in DevOps & Cloud. It works with Adobe Experience Manager. The repository describes itself as: Adobe Skills for Agents. The licence is Apache-2.0.
When your agent uses it
- Traversal warning
- Is my query indexed
- A scan that flags a JCR/QueryBuilder query
Example prompts
- “query is slow”
- “traversal warning”
- “is my query indexed”
- “/tuning-oak-query-indexes”
What it can do on your machine
Read from SKILL.md and the folder at commit c8f44ec. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Tuning Oak Query Indexes loads about 1.5k tokens when it runs, and up to ~33k if it reads all its reference files. Until then it costs about 219 tokens; SKILL.md has 627 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from adobe/skills at commit c8f44ec, republished under its Apache-2.0 licence (© adobe). 627 words, ~1,492 tokens.
Download SKILL.mdSave it as
.claude/skills/tuning-oak-query-indexes/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- tuning-oak-query-indexes
- description
- AEM Cloud Service expert skill — check a JCR/Oak query is actually served by an index and, when it is not, propose the property/Lucene index-definition change so the query is answered by the index instead of in-memory filtering or sorting. Use for "query is slow", "traversal warning", "is my query indexed", "tune oak index", or a scan that flags a JCR/QueryBuilder query. The analyzer locates every query-construction site (createQuery, getQueryManager, Sling findResources / queryResources, PredicateGroup.create / new PredicateGroup); the recipe assesses each flagged query against the supplied index definition(s). Resolution is user-supplied: the index definition(s) are required input — if none is provided the whole pattern is deferred, never guessed. Guided fix — the developer reviews and applies the proposed index change; never auto-apply.
- license
- Apache-2.0
Tuning Oak query indexes — AEM as a Cloud Service
This pattern is executed by the code-assessment runbook — follow
../references/runbook.mdfor the full flow. This skill supplies the detection + recipe the runbook applies.
Overview
An Oak query only uses an index for the parts the index actually covers. Any WHERE/ORDER BY/fulltext
field without a matching, correctly-flagged property definition gets evaluated node-by-node in memory —
same for a wrong nodetype or path scope, even if every field is indexed. An uncovered query traverses
the repository: slow, traversal-warning-logged, and a load risk at scale. This pattern finds exactly
which fields/conditions aren't covered and what index-definition change fixes each one.
Classification — confirm this pattern applies
- A JCR/QueryBuilder query is slow, logs a
traversal/TraversingIndexwarning, or you're adding/changing a query and need to confirm it's served by an index rather than in-memory filtering or sorting. - The user asks "is my query indexed", "tune the oak index", "why is this query slow", or a scan flagged a
query-construction site (
createQuery/PredicateGroup.create). - Not this pattern: an explicitly unbounded query (
p.limit=-1/setLimit(-1)) — that'sunbounded-query; this pattern is about index coverage, not result-set size. (A query can be both — assess index coverage here, bound it there.)
Discovery
Detection is performed by the analyzer (../scripts/analyze.sh), run by the runbook:
bash ../scripts/analyze.sh <workspace-root> --pattern tuning-oak-query-indexesMatch criteria (what the detector flags) — query-construction sites, matched on written names (parse-level, no type resolution). These mirror the Java-API anchors the folded extracting JCR queries guide used, so moving detection from grep to code keeps the same capture:
- any invocation named
createQuery— JCRQueryManager.createQuery(...)and AEM QueryBuilderbuilder.createQuery(...). - any invocation named
getQueryManager— the JCR query entry point (Workspace.getQueryManager()). - any invocation named
findResourcesorqueryResources— the SlingResourceResolverquery APIs, which run a real indexed repository query. PredicateGroup.create(...)(acreateinvocation whose receiver's trailing simple name isPredicateGroup) andnew PredicateGroup(...)— QueryBuilder predicate-group construction.
One finding per distinct source line, with the call as the snippet. The detector locates where queries are built; it does not judge coverage — that requires the query text (read the surrounding code) and the index definition(s) (see Resolution contract).
Known limits (out of a parse-level Java detector's reach — use the extracting guide's manual fallback):
non-Java queries (XPath/SQL2 in JSP/HTL/config, stored dam:query / Smart-Collection predicate strings,
query-string form) and queries hidden behind a non-JCR wrapper method whose body has no direct query call.
Show full SKILL.md (243 more words)Show less
Resolution contract
user-supplied — the required input is the Oak/Lucene index definition(s) the query could use. The whole assessment is a comparison of the query against its candidate index definition(s), so:
- Required input — the index definition(s). This skill does not run without them. Accept any of: a
FileVault
.content.xmlunder an/apps/.../installpackage, a JSON export, or the live dump atGET /system/console/status-oak-index-defn.json(admin auth). - If no index definition is available, DEFER THE WHOLE PATTERN with a single line — e.g.
tuning-oak-query-indexes: deferred — index definition not provided. Do not emit a per-query skip for every finding, and do not emit a coverage assessment from the query alone (a guess reads as a finding and gets acted on as one). - When index definitions ARE supplied, assess each flagged query's coverage and propose the
index-definition change where a field is uncovered.
fix: guided— never auto-apply: write the corrected definition out for the developer to review and apply.
Recipe
Read recipe.md in full before assessing or proposing any change: the input contract, the
Section A/B segregation, the field-construct → required-flag table, the two scoping gotchas, the
index-size/storage pitfalls, the common mistakes, the target-index selection, explain verification, and
the two-section report shape. Ground truth for every claim is the bundled
AI agent indexing guide; build a query inventory from scratch with
the bundled extracting JCR queries guide.
Handoff
The skill never commits and never applies an index change to a live instance. See
../references/runbook.md for the full flow and handoff.
© adobe, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in plugins/aem/cloud-service/skills/code-assessment/tuning-oak-query-indexes of adobe/skills.
- SKILL.md
- recipe.md
- references/ai-agent-indexing-guide.md
- references/extracting-jcr-queries.md
Open the folder on GitHubat commit c8f44ec
Compare with similar skills
Tuning Oak Query Indexes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Tuning Oak Query Indexes this skilladobe/skills | 197 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Monitor CInrwl/nx | 29k | 6 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Terraform and OpenTofu Guideagentscope-ai/QwenPaw | 36k | 6 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 8 repos | ~4.3k | Automated safety check: Pass | None | |
| Analyze GitHub Action Logswithastro/astro | 63k | 1 repos | ~1.3k | Automated safety check: Pass | Custom licence | |
| Openclaw Live Updateropenclaw/openclaw | 392k | — | ~3.7k | Automated safety check: Pass | MIT |
Similar skills
Terraform and OpenTofu Guide
agentscope-ai/QwenPaw
Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.
- Official
Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
- Official
Analyze GitHub Action Logs
withastro/astro
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
Openclaw Live Updater
openclaw/openclaw
Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.
Docs Learn PR Preview
netdata/netdata
Use only when the user explicitly asks to build, run, preview, inspect, or validate learn.netdata.cloud locally using the contents of a PR or documentation branch before merge.
More from adobe/skills
All 66 skills in this repoAdobe App Builder Action Scaffolder
adobe/skills
Scaffolds, implements, deploys and debugs Adobe Runtime actions in App Builder projects, with templates for webhooks, events, database CRUD, sequences and Asset Compute workers.
CDP Extension Pilot
adobe/skills
Launches Chrome with an unpacked extension over CDP, opens its sidepanel, popup or options page, and hands over to cdp-connect for clicks, typing and screenshots.
Web Page Resource Collector
adobe/skills
Extracts icons, metadata, text, forms, videos and social links from any web page with playwright-cli, with SVG icon classification and cleanup.
Page Langs
adobe/skills
Detect all languages used on a webpage — both declared (html@lang, hreflang alternate links, nested lang= attributes, meta content-language) and actually present in the body text (Google CLD3 via…
Page Prep
adobe/skills
Prepare any webpage for clean interaction by detecting and removing disruptive overlays (cookie banners, GDPR consent, modals, popups, newsletter signups, paywalls, login walls).
Page Reduce
adobe/skills
Reduce a webpage to a structural skeleton with semantic tokens.
Related
Works with
Categories
Questions about Tuning Oak Query Indexes
What does Tuning Oak Query Indexes do?
AEM Cloud Service expert skill — check a JCR/Oak query is actually served by an index and, when it is not, propose the property/Lucene index-definition change so the query is answered by the index…. Tuning Oak Query Indexes is an agent skill from adobe/skills. AEM Cloud Service expert skill — check a JCR/Oak query is actually served by an index and, when it is not, propose the property/Lucene index-definition change so the query is answered by the index instead of in-memory filtering or sorting.
When should I use Tuning Oak Query Indexes?
Tuning Oak Query Indexes fits situations like: traversal warning; is my query indexed; A scan that flags a JCR/QueryBuilder query.
How do I install Tuning Oak Query Indexes in Claude Code?
Run `npx skills add adobe/skills --skill tuning-oak-query-indexes -a claude-code`. Or copy the skill folder (plugins/aem/cloud-service/skills/code-assessment/tuning-oak-query-indexes in adobe/skills) into .claude/skills/tuning-oak-query-indexes in your project. Claude Code loads it when a task matches its description.
How do I install Tuning Oak Query Indexes in Codex?
Run `npx skills add adobe/skills --skill tuning-oak-query-indexes -a codex`. Or copy the skill folder (plugins/aem/cloud-service/skills/code-assessment/tuning-oak-query-indexes in adobe/skills) into .agents/skills/tuning-oak-query-indexes in your project. Codex loads it when a task matches its description.
Can I use Tuning Oak Query Indexes in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add adobe/skills --skill tuning-oak-query-indexes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tuning-oak-query-indexes, .gemini/skills/tuning-oak-query-indexes, .github/skills/tuning-oak-query-indexes and .opencode/skills/tuning-oak-query-indexes in your project.
What does Tuning Oak Query Indexes need to run?
Going by SKILL.md and its folder, Tuning Oak Query Indexes needs the command-line tools its instructions call (bash).
Does Tuning Oak Query Indexes access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Tuning Oak Query Indexes safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Tuning Oak Query Indexes use?
Tuning Oak Query Indexes is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Tuning Oak Query Indexes use?
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 31k tokens, read only when the agent opens those files.
What are the alternatives to Tuning Oak Query Indexes?
Skills that share tags, products or a category with Tuning Oak Query Indexes: Monitor CI (nrwl/nx, 29k stars), Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 36k stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Analyze GitHub Action Logs (withastro/astro, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Tuning Oak Query Indexes?
adobe (a GitHub organization) maintains it in adobe/skills, which has 197 GitHub stars. The repository holds 66 skills in this directory. The repository was last updated on October 10, 2026.
Source: adobe/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.