Claude Skills by VivekHZTL

github.com/VivekHZTL

17 skillsA× 170 installs0 views

Content Ops ApplyAThe write step - apply a dry run's ready pages to Sitecore, or create page shells for content marked create. Use only after a plan exists and the user says apply, write, run it, go ahead, create the pages, naming the environment. Journaled, read back, auto-rolled back; never publishes.ai-agentsgoshellVotes: 0GitHub stars: 2
Content Ops BuildAWhen a Sitecore content task needs something no content-ops command already does - a shared datasource, records under Data, renaming or moving items, swapping a page's content, repointing references, redirects, unpublishing, a new sheet shape - work out the solution and build it as a governed operation (read-only build step that proposes change sets; the engine plans, applies with a journal, verifies and undoes). Use when someone describes a new kind of change, asks "can we do X across these ...ai-agentsgonodeVotes: 0GitHub stars: 2
Content Ops CleanupAFind and remove leftover items (old Data folders, test copies, parked pages, backup nodes) safely - scan the tree, find every reference, plan deletes that refuse referenced items, delete to the recycle bin with a journal, prove zero references, undo if needed. Use when someone says clean up, delete the old items, remove the test pages, what references this, is it safe to delete.ai-agentsgonodeVotes: 0GitHub stars: 2
Content Ops Inspect CodeAExplain what a Sitecore component accepts - its fields, children, placeholder, theme support, and any limits visible in the head app code - from catalog.json and the component source. Read-only. Use when someone asks what fields does X have, how many panels or cards fit, is there an image, where is the code for this component, or when a mapping needs a field name.ai-agentsnodeVotes: 0GitHub stars: 2
Content Ops IntakeATurn the files in sources/ (workbooks, Word copy decks, legacy HTML, TSV lists) into content JSON and an inventory with questions grouped by owner. Use when someone says intake, inventory, what is in these decks, read the workbook, what is missing, questions for the client, or before a plan when work/ is empty or stale. Read-only; never touches Sitecore.ai-agentsnodeVotes: 0GitHub stars: 2
Content Ops LessonsARecord and read what this project taught the tool - lessons, remembered sheet shapes, rule overrides - and bundle the shareable ones for the plugin owners. Use when someone says remember this, lesson, what have we learned, why does it map like that, note for next time, export lessons, or right after a confirmation, override or new reader was accepted. Writes project files only.ai-agentsnodeVotes: 0GitHub stars: 2
Skills DirectorySkills Directory 3 slots · $399/mo · one ad per page · sponsors can never buy grades.See placements
Content Ops MapAConfirm how source structure maps to Sitecore components - a workbook profile (column to component field) or a deck section map (heading alias to component, label to field). Use when intake wrote a proposed profile or section map, when someone asks which column goes where, why did this column get ignored, map this header, or wants to add an alias. Records confirmations as decisions.ai-agentsgonodeVotes: 0GitHub stars: 2
Content Ops PlanARead-only dry run of content JSON against Sitecore - what would be created, updated or re-laid out, what is pending, what the engine refuses. Use when someone says plan, dry run, rehearse, what would change, show me before you write, pending, needs review, or before any apply. Never writes.ai-agentsgonodeVotes: 0GitHub stars: 2
Content Ops ReviewAReview one authored page against its source content - copy verbatim, links, images, flags, components in order - and report every difference with a locator. Use when someone says review this page, compare with the deck, is the copy exact, check what was written, QA the page.ai-agentsgonodeVotes: 0GitHub stars: 2
Content Ops SetupAConnect Claude to a SitecoreAI environment with nothing but a key file - make or check ~/.content-ops/<project>/<env>.env, sign in, read the site's home page, write the smallest project config, then carry on with what was asked. Also joins a project that already has .content-ops/ and, for the tech team, optional extras (answers file, .env.local copy). Use when someone says set up, connect me to prod/dev/qa, set up content ops, join this project, I got the repo, new laptop, credentials, key fi...developmentgobashVotes: 0GitHub stars: 2
Content Ops SourcesARegister, list and verify the source files (decks, workbooks, sheets, legacy HTML, lists) a content run uses. Use when someone downloads a file from SharePoint, asks which version is current, says a file changed, or before any intake or plan.ai-agentsgonodeVotes: 0GitHub stars: 2
Content Ops StrategistASenior content strategist pass over an intake - where legacy pages fit in the new sitemap, component fit, SEO title and description lengths, duplicates, gaps, consistency - as proposed decisions, never as changed copy. Use when someone asks for suggestions, strategy, where does this go, does this fit the template, SEO check, what is missing, what repeats.ai-agentsgonodeVotes: 0GitHub stars: 2
Content Ops TemplateAMake the client intake sheet for a page type from the catalog (xlsx or csv), so clients hand back content in a shape that maps itself. Use when someone says make me a sheet, template, intake format, what format should the client use, standard spreadsheet, or when a client asks how to send content. Writes a file in sources/ only; never touches Sitecore.ai-agentsnodeVotes: 0GitHub stars: 2
Content Ops TransformASitecore-to-Sitecore bulk changes - export existing pages to content JSON, apply named rich-text rules (strip images from a host, unwrap an anchor, rewrite hrefs, replace text) or edit the content by hand, then dry run and apply through the normal gates. Use when someone says bulk update, change this on every page, strip the old images, remove that link everywhere, rewrite legacy URLs, update existing pages from Sitecore itself.developmentgonodeVotes: 0GitHub stars: 2
Content Ops VerifyAProve and finish a content run - re-verify written pages, publish them to Experience Edge after a separate OK, check the live site, or undo one page from its journal. Use when someone says verify, is it right, check live, publish, go live, undo, roll back, restore.ai-agentsgonodeVotes: 0GitHub stars: 2
Content OpsASitecoreAI content authoring with the content-ops engine. Use whenever someone asks to check, set up, register sources, intake, map, plan, dry run, rehearse, apply, write, create pages, verify, review, publish, undo, live-check, or get strategy suggestions for Sitecore pages built from decks, workbooks, legacy sites or lists. Routes to the role skills (content-ops-setup, -sources, -intake, -map, -plan, -apply, -verify, -review, -strategist, -inspect-code, -build, sync-repo) and holds the grou...developmentgonodeVotes: 0GitHub stars: 2
Sync RepoABring the user's copy of the project repo up to date without changing history. Use when someone says sync, pull, get the latest, update my repo, am I up to date, or before a content run. Fetch and fast-forward only; refuses merge, rebase, stash, commit, push, branch changes.ai-agentsgitVotes: 0GitHub stars: 2