CtrlK
BlogDocsLog inGet started
Tessl Logo

sitecore

Sitecore integration. Manage data, records, and automate workflows. Use when the user wants to interact with Sitecore data.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/sitecore/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, largely executable guide to driving Sitecore through the Membrane CLI, with a solid connection workflow. Its main weaknesses are conceptual padding up front and minor gaps in validation and result verification.

Suggestions

Remove or condense the opening conceptual paragraph and the vague 'Sitecore Overview' taxonomy, which restate knowledge Claude already has.

Add an explicit verification step after running actions (e.g. check the `output` field and confirm the expected record changed) for destructive or batch operations.

Fix the step-numbering inconsistency ('skip to Step 2' with no labeled Step 2) and de-duplicate the 'Popular actions' and 'Searching for actions' sections.

DimensionReasoningScore

Conciseness

The body is mostly efficient CLI guidance but opens with conceptual background Claude already knows ('Sitecore is a digital experience platform...') and a vague overview taxonomy that could be trimmed.

3 / 5

Actionability

Provides copy-paste-ready commands for install, login, connection, search, run, and proxy with a flags table; minor gaps remain where placeholders like CONNECTION_ID and actionId are not illustrated with concrete values.

4 / 5

Workflow Clarity

The connection workflow has a clear sequence with a state-polling feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but step numbering references a 'Step 2' that is not labeled and action execution lacks an explicit result-verification checkpoint.

4 / 5

Progressive Disclosure

No bundle files exist and all content is inline, but sections are well-organized with no nested references; minor redundancy between 'Popular actions' and 'Searching for actions' keeps it below a 5.

4 / 5

Total

15

/

20

Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description correctly uses third person and includes an explicit 'Use when' trigger tied to a distinct product niche, but its capability list is generic and its trigger terms are narrow.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete Sitecore operations such as 'create and edit content items, manage media, and update templates'.

Broaden trigger terms to include natural variations users might say, e.g. 'Use when the user wants to manage Sitecore content items, media, templates, or marketing workflows'.

Tighten the 'what' so it reads as specific capabilities rather than abstract verbs.

DimensionReasoningScore

Specificity

Names the Sitecore domain plus a few actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete Sitecore-specific operations, sitting between the generic-anchor and the concrete-action anchor.

3 / 5

Completeness

Both 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Sitecore data') are present; the 'what' is somewhat vague which keeps it just below a 5.

4 / 5

Trigger Term Quality

Relevant keywords ('Sitecore', 'Sitecore data') are present but coverage is narrow, missing common variations or synonyms a user might say (content items, CMS, marketing, experience platform).

3 / 5

Distinctiveness Conflict Risk

Sitecore is a named product giving it a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.