Jannat63

Sheet As CMS Toolkit A Claude Skill For Google Sheets Backed Sites — Data skill for Claude Code

Data community

A Claude Skill that sets up, validates, and hardens a website that uses Google Sheets as its CMS.

How to install Sheet As CMS Toolkit A Claude Skill For Google Sheets Backed Sites

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Jannat63/Sheet-as-CMS-Toolkit-A-Claude-Skill-for-Google-Sheets-Backed-Sites and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Sheet As CMS Toolkit A Claude Skill For Google Sheets Backed Sites does

**A Claude Skill that sets up, validates, and hardens a website that uses Google Sheets as its CMS.** It catches schema drift, validates row data, scans for XSS-risk content, recommends the right fetch method for the situation, and hands over working framework code — all with zero API keys and zero paid dependencies.

Alternatives in Data

  • Sprite Gen — Generate clean 2D game sprites & animation atlases — component-row pipeline: state rows, alpha cleanup, frame 763 ★
  • Vibesec — Helps write secure code by preventing common vulnerabilities including IDOR, XSS, SQL injection, SSRF, and wea 687 ★
  • Sitegeist — An AI assistant that lives in your browser 537 ★

README

Sheet-as-CMS Toolkit — A Claude Skill for Google-Sheets-Backed Sites

**A Claude Skill that sets up, validates, and hardens a website that uses Google Sheets as its CMS.** It catches schema drift, validates row data, scans for XSS-risk content, recommends the right fetch method for the situation, and hands over working framework code — all with zero API keys and zero paid dependencies.

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](./LICENSE) ![Claude Skill](https://img.shields.io/badge/Claude-Skill-6B4EFF) ![No API Key Required](https://img.shields.io/badge/API%20Key-Not%20Required-brightgreen) ![Zero pip installs](https://img.shields.io/badge/Dependencies-stdlib%20only-blue)


Table of contents


The problem this solves

Using a Google Sheet as a CMS is one of the best-kept secrets in small-scale web development. It's free, your content editor already knows how to use it, and there's no dashboard to build. Thousands of blogs, product catalogs, and marketing sites run on exactly this pattern right now.

It also fails in three specific, predictable ways, all of which are invisible until they've already caused a problem:

  • A column gets renamed. Someone renames published_date to date because it reads cleaner, or reorders columns while cleaning up the sheet. The site doesn't crash — it just quietly starts rendering blank fields, because the code is still looking for a column that no longer exists under that name.