content-sdk-troubleshoot-editing

content-sdk-troubleshoot-editing is a skill for Claude Code, Codex from Sitecore/content-sdk. It costs 29 tokens per session (357 once invoked), scanned A, original, Apache-2.0.

Troubleshooting guidance for Sitecore editing and preview in an Angular application. Sitecore Pages is a visual content editor, and preview lets editors see content before it is published.

In plain words
What is it for?
Use it to diagnose broken editing endpoints, missing component mappings, stale editor content, and fields that cannot be edited.
Why use it?
It gives checks for middleware order, preview requests, component names, secrets, caching, and editable fields when the editor shows stale content, empty placeholders, or rejected requests.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to diagnose broken editing endpoints, missing component mappings, stale editor content, and fields that cannot be edited.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sitecore/content-sdk/content-sdk-troubleshoot-editing
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Sitecore/content-sdk --skill content-sdk-troubleshoot-editing
Clone the repo
git clone --depth 1 https://github.com/Sitecore/content-sdk

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for content-sdk-troubleshoot-editing

README.md
[![agentmods](https://agentmods.dev/badge/skills/sitecore/content-sdk/content-sdk-troubleshoot-editing/github.svg)](https://agentmods.dev/skills/sitecore/content-sdk/content-sdk-troubleshoot-editing)
Your own site
<a href="https://agentmods.dev/skills/sitecore/content-sdk/content-sdk-troubleshoot-editing"><img src="https://agentmods.dev/badge/skills/sitecore/content-sdk/content-sdk-troubleshoot-editing/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for content-sdk-troubleshoot-editing

Your own site · 80×15
<a href="https://agentmods.dev/skills/sitecore/content-sdk/content-sdk-troubleshoot-editing"><img src="https://agentmods.dev/badge/skills/sitecore/content-sdk/content-sdk-troubleshoot-editing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 357 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.00357
Opus 5.5 $0.00012 $0.00143
Sonnet 5.5 $0.00006 $0.00071
Haiku 4.5 $0.00003 $0.00036

Measured 15d ago against content hash 37b948a6b16c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

content-sdk-troubleshoot-editing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 15d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

packages/create-content-sdk-app/src/templates/angular/.agents/skills/content-sdk-troubleshoot-editing/SKILL.md · 30 lines

What it actually says

Troubleshoot editing (Angular)

Detail: AGENTS-key-concepts.md#editing-and-preview Read first: src/server.ts, src/content-sdk/loaders/page.loader.ts

When

  • Editing, preview, or Design Library misbehaves
  • Pages shows stale content or an empty placeholder in the editor

Rules

  • Check middleware order: createEditingConfigMiddleware, createExperimentalFeaturesMiddleware and createEditingRenderMiddleware must be registered before express.static and the SSR handler
  • Verify /api/editing/config returns the expected component names and editMode: 'metadata'; missing names usually mean a stale .sitecore/component-map.ts
  • Verify SITECORE_EDITING_SECRET is set on the server (a missing value falls back to a placeholder and the render request is rejected)
  • Confirm getEditingPreviewData(context.csdkRequestData) is reached in pageLoader — if it is not, the request never went through the editing render middleware
  • Stale content in the editor points at the loader cache; editing requests are supposed to bypass it
  • Fields not editable usually means interpolation was used instead of an *sc* directive

Stop

  • Escalate if the problem is in the Pages editor or the platform rather than app code

Docs: Content SDK for Angular.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 15d ago First seen · 30 lines · 29 tokens per session scan A 37b948a6b16c

Subscribe to this mod's changes

content-sdk-troubleshoot-editing is a skill published in the GitHub repository Sitecore/content-sdk (37 stars, last pushed yesterday), licensed Apache-2.0. It adds 29 tokens to every session and 357 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-02.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens