New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Small Business Website Spec

by hewi333 in hewi333/Mom-n-Pop-Skills

Planning reference for rebuilding a small business website: page structure, copy voice, estimator widget, SEO requirements, form handling, DNS migration, and the no-code vs static-framework decision…

MITAuto-check passedFrontend & Design

Install Small Business Website Spec

skills CLI
$ npx skills add hewi333/Mom-n-Pop-Skills --skill small-business-website-spec -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hewi333/Mom-n-Pop-Skills small-business-website-spec --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hewi333/Mom-n-Pop-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/small-business-website-spec .claude/skills/small-business-website-spec && rm -rf skills-src

Use ~/.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/

Facts

Skill name
small-business-website-spec
GitHub stars
122
Token cost
~3.2k tokens
SKILL.md length
1,702 words
Files
2 (incl. references)
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Planning reference for rebuilding a small business website: page structure, copy voice, estimator widget, SEO requirements, form handling, DNS migration, and the no-code vs static-framework decision…

  • Works in 12 steps: Home — hero image, value proposition,… → Service pages — one per service line… → Service area / location pages — one per… → …
  • Tasks that involve Static sites and blogs
  • SKILL.md covers When to Use, Platform Decision: No-Code vs…, Prerequisites and Website Architecture, plus 4 more sections
  • Calls npx and git

What it does

Small Business Website Spec is an agent skill from hewi333/Mom-n-Pop-Skills. Planning reference for rebuilding a small business website: page structure, copy voice, estimator widget, SEO requirements, form handling, DNS migration, and the no-code vs static-framework decision (Base44 vs Astro/Vercel vs WordPress). NOT a deploy tool for no-code platforms — no-code builders have no agent-accessible CLI. Includes the honest reasons we pivoted from no-code to a static framework.

Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/base44-pricing.md`).

It sits in Frontend & Design, covering Static sites and blogs and Forms and validation. It works with Vercel, Astro and WordPress. The repository describes itself as: Collection of skills for small businesses using AI Agents. The licence is MIT.

When your agent uses it

  • Tasks that involve Static sites and blogs
  • Tasks that involve Forms and validation

Example prompts

  • “/small-business-website-spec”

Requirements

  • Node.js

Workflow steps

12 steps, taken from the first numbered list in SKILL.md.

  1. Home — hero image, value proposition, primary CTA ("Get Free Estimate"), estimator above the fold
  2. Service pages — one per service line (built from a template route; each names the reader's exact situation in the first two sentences)
  3. Service area / location pages — one per market city (template route, real local copy, not doorway spam)
  4. Realtors & property managers — the B2B repeat-revenue page, if referrals drive the business
  5. About / Why Us — owner story, process steps, trust signals, real photos
  6. Gallery — real job photos, captioned
  7. FAQ — include a "what makes you different from everyone else?" answer
  8. Contact — form with estimator pre-fill flow
  9. Reviews — embedded review widget (or hold back until the widget is wired)
  10. Thank you — noindex, conversion event fires here
  11. Terms — warranty/terms as a proper page (not a PDF scan)
  12. 404, plus robots.txt, llms.txt (for AI/agentic search), sitemap-index.xml

What it can do on your machine

Read from SKILL.md and the folder at commit 70a2273. 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:

    • npx
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx and git, which can reach the network depending on how they are called.

    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

Small Business Website Spec loads about 3.2k tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 107 tokens; SKILL.md has 1,702 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~107
When it runs · the whole SKILL.md, loaded when a task matches
~3.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.8k

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 hewi333/Mom-n-Pop-Skills at commit 70a2273, republished under its MIT licence (© hewi333). 1,702 words, ~3,205 tokens.

Download SKILL.mdSave it as .claude/skills/small-business-website-spec/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
small-business-website-spec
description
Planning reference for rebuilding a small business website: page structure, copy voice, estimator widget, SEO requirements, form handling, DNS migration, and the no-code vs static-framework decision (Base44 vs Astro/Vercel vs WordPress). NOT a deploy tool for no-code platforms — no-code builders have no agent-accessible CLI. Includes the honest reasons we pivoted from no-code to a static framework.
version
2.0.0
author
Hermes Agent
license
MIT

Small Business Website Spec

⚠️ This is a planning/specification reference, not a deployable skill for no-code platforms. Base44 and similar builders have no CLI the agent can call — building there means dragging pages in a web editor, done by a human. A static framework (Astro/Hugo/Eleventy) on Vercel/Netlify/Cloudflare Pages is agent-workable: the agent can clone the repo, edit, run checks, and push. Either way, this skill is the spec: page structure, copy voice, estimator widget, SEO checklist, form handling, and the DNS cutover runbook.

When to Use

  • Planning a website rebuild for a small service business
  • Choosing between no-code (Base44, Wix Studio, Squarespace) and a static framework (Astro on Vercel)
  • Page structure, copy voice, estimator widget, SEO requirements
  • DNS migration notes (registrar → new host)
  • Wiring contact-form submissions into the agent (email → IMAP polling → CRM → Telegram)
  • NOT for automated no-code deployment — no agent-accessible CLI exists there

Platform Decision: No-Code vs Static Framework

Both paths are valid. Pick by workload, not by hype:

FactorNo-code (Base44 etc.)Static framework (Astro/Vercel etc.)
Who builds itHuman, in a web editor (drag-and-drop)Human or AI coding agent, in a repo
Time to first draftHoursDays
Monthly cost~$50/mo for domain connection + GitHub sync on Builder-tier plans$0 on Vercel/Netlify free tiers (or an existing plan)
SEOPrerendering exists but is often a black box you can't controlStatic HTML — fully crawlable, you own everything
Export/exitFrontend only; backend (auth, DB, entities) stays on the platform SDK — you can't self-host by exportingIt's your repo. Portable by definition.
Site types that fitInteractive apps, member areas, anything needing a real backendMarketing sites: pages + one estimator widget + one contact form
MutabilityA living app on their platform — platform updates can change rendering without you touching anythingAn immutable build artifact on CDN edge — it can't break while untouched
Agent's rolePaying for the subscription (via stripe-link-cli) and writing the spec — not the buildFull repo work: edit, test, verify, push, deploy

How to choose: if the site needs user accounts, database writes, or complex app behavior, no-code (or a real framework with a backend) earns its subscription. If it's a marketing site — pages, photos, an estimator widget, a contact form — a static build is cheaper, faster to load, better for SEO, and fully agent-workable.

We started on Base44 (for a hackathon "the agent bought the subscription" beat, which is what stripe-link-cli is for), then pivoted to Astro-on-Vercel for the production site because a static marketing site had zero backend needs. The pivot itself was cheap because the spec (this document) was written before either build — page inventory, copy voice, estimator logic, and SEO checklist all carried over unchanged.

Prerequisites

  • Domain at a registrar (GoDaddy or similar) — keep DNS there, repoint records
  • Static path: git repo, framework (Astro recommended), hosting account (Vercel/Netlify)
  • No-code path: builder account, manual signup + build in the web interface
  • Form delivery: an email API (Resend/Postmark/SES) or SMTP — forms should email the owner's inbox
  • Payment for no-code subscriptions via the stripe-link-cli skill (agent handles the spend, human handles the build)

Website Architecture

Pages needed (marketing site for a service business)
  1. Home — hero image, value proposition, primary CTA ("Get Free Estimate"), estimator above the fold
  2. Service pages — one per service line (built from a template route; each names the reader's exact situation in the first two sentences)
  3. Service area / location pages — one per market city (template route, real local copy, not doorway spam)
  4. Realtors & property managers — the B2B repeat-revenue page, if referrals drive the business
  5. About / Why Us — owner story, process steps, trust signals, real photos
  6. Gallery — real job photos, captioned
  7. FAQ — include a "what makes you different from everyone else?" answer
  8. Contact — form with estimator pre-fill flow
  9. Reviews — embedded review widget (or hold back until the widget is wired)
  10. Thank you — noindex, conversion event fires here
  11. Terms — warranty/terms as a proper page (not a PDF scan)
  12. 404, plus robots.txt, llms.txt (for AI/agentic search), sitemap-index.xml
Estimator tool integration

The estimator is the conversion hook AND the differentiator. Pricing logic lives in ONE place (see estimator-engine skill; a rate-card.json both the website widget and the agent read is the cleanest split).

  • Input: square footage, region tier, property type (residential/commercial/apartment), add-ons
  • Output: a ±15% range, never a single number, never internal line-item math
  • Flow: result → one tap → contact form pre-filled with all inputs + quoted range
  • Mobile-first: thumb-reachable controls, ≤60 seconds, ≤8 taps
  • The website widget, the agent's chat estimator, and the rate-card file must all read from the same rate card. If a price changes, change the rate card first; both consumers pick it up. Canonical source: estimator-engine.
Contact form handler
  • Serverless function (or the host's form feature) receives the POST
  • Email API (Resend etc.) delivers to the owner's inbox — reply-to set to the submitter so the owner can hit Reply
  • Honeypot spam field (hidden "company" input — if filled, reject silently)
  • Validate: required core fields, plus "at least one of phone or email"
  • Carrying estimator data into the form? Keep it as structured fields in the submission email — the agent's inbox monitor parses them (see below)
  • Optional webhook to the agent — but see "Lead intake" before exposing one
Lead intake (agent integration)

Two ways to get form submissions to the agent:

A. IMAP polling (recommended default). The form emails the owner's inbox with a stable subject prefix (New website lead: ...) and a structured plain-text body. A no_agent=True cron script polls the inbox every 3 min, parses the fields, logs to CRM, and texts the owner's Telegram. Latency ~3 min — irrelevant for a few leads a week. No public endpoint, nothing to attack. Full pattern: grasshopper-voicemail-monitor skill and its notification-email reference.

B. Webhook (faster, more surface). The form handler POSTs straight to an agent endpoint. You get instant delivery but you must expose, secure, rate- limit, and monitor a public URL on the agent box. Only worth it at volume.

Choose A unless leads/minute is a real metric for you. The webhook code can stay in the form handler, dormant, if you want the option open.

Content guide

Show full SKILL.md (690 more words)Show less
Copy voice
  • Premium-because-[your real differentiator] — never "affordable," "budget-friendly," "cheap" (they attract price-shoppers, not your buyers)
  • Lead with the outcome (it works, it's guaranteed, it's permanent) — not the chemistry
  • Name the reader's exact situation in the first 2 sentences of every service page
  • Specificity = trust: real cities, real timeframes, real guarantee terms
  • ~7th-grade reading level, short sentences
Banned-word check

Add a verify-script check for cheap-sounding words: affordable, budget-friendly, cheap, competitive pricing, "we work with many budgets," best-in-class, world-class, "look no further." Ban list lives in the repo and runs in CI — banned words slip back in with every copy edit otherwise.

Guarantee

If you advertise a guarantee, state its exceptions wherever the guarantee appears — exceptions buried on a distant page erode trust and invite disputes.

Common Pitfalls

  • Contact-form cutover risk: the OLD site's form probably works and goes to the owner's inbox. Do NOT repoint DNS until the new form is verified delivering to that same inbox on a staging domain. Breaking a working lead path is worse than keeping the old site live another week.
  • DNS propagation: 24-48h. Save old DNS values for instant rollback.
  • Email routing: changing A/CNAME records is fine, but MX records stay pointed at the email host (e.g. Workspace: imap.secureserver.net / smtpout.secureserver.net). Repointing MX silently breaks the business's email.
  • Mobile-first: most service-business leads come from phones. Test at 320px, 375px, 414px widths.
  • 301 redirects: map old (especially WordPress) URLs → new pages before cutover, or years of accumulated SEO equity 404s overnight.
  • Banned words: enforce via the verify script, not vigilance.
  • Terms & conditions: a scanned-image PDF has no extractable text — transcribe it into a real page.
  • Stock photos: verify licensing before a live launch; "we scraped them from our old site" is not a license.
  • Browserless agent box: no-code checkout and Lighthouse audits need a browser. The agent can't drive a web UI without Chromium (npx playwright install --with-deps chromium); run audits via web tools.
  • Region classification sync: if you update region tiers in estimator-engine, update the estimator widget options AND the rate-card file. All three must match. Canonical source: estimator-engine.
  • No-code export is a one-way door: the frontend exports; the backend doesn't. If you start on no-code, treat it as a prototype — don't wire business logic (auth, DB, entities) into it that you'll have to rebuild.
  • Agent pushes to main: for a 1-2 person shop, direct-push with a quality gate (tests + verify script) is faster than PR review. Whatever you choose, make it a written convention — agents follow conventions, they don't infer them.
  • GitHub PATs expire: if the clone URL embeds a PAT, pushes fail mysteriously ~30 days later. Check the token's expiry when setting up, and note the git remote set-url fix before it bites.

DNS Configuration (registrar → Vercel example)

Type: CNAME
Name: www
Value: cname.vercel-dns.com

Type: A
Name: @
Value: 76.76.21.21 (Vercel default)

(No-code hosts give you their own CNAME/A targets — same idea.)

Do NOT touch MX records — email stays with the email host.

Cutover order:

  1. New contact form verified delivering to the owner's inbox (staging domain)
  2. Owner sign-off on content + design
  3. THEN repoint DNS
  4. Old DNS values saved for instant rollback

Verification Checklist

Quality gate (automated — run before every push)
  • Every page renders static HTML with copy in the raw HTML (no client-only content)
  • Unique title (≤60 chars) + meta description (≤155 chars) per indexable page
  • Exactly one H1 + substantial body copy per page
  • Zero banned words (enforced by script)
  • Estimator output matches the agent's chat estimator (same rate card, test N quotes)
  • Guarantee caveats reachable from every page mentioning "guarantee"
  • Structured data (LocalBusiness, Service, FAQPage) + tap-to-call on every page
  • robots.txt, llms.txt, sitemap-index.xml present; /thank-you is noindex
  • Unit tests pass (pricing engine + form validation)
Pre-cutover (manual)
  • Owner sign-off on the site
  • Form submissions verified delivering to the owner's inbox on the real domain
  • Schema.org validates (Google Rich Results Test)
  • Lighthouse mobile: Performance ≥90, SEO ≥95, Accessibility ≥90
  • Real photos on the site (machines/equipment/jobs, not stock)
Post-cutover
  • DNS propagated (dig yourdomain.com) + HTTPS working
  • 301 redirects from old URLs live
  • Email MX records preserved (don't break email)
  • Search Console + Bing Webmaster verified; sitemap submitted
  • Analytics events firing (estimator_start, estimator_complete, form_submit, call_click)
  • Mobile responsive verified on real devices
  • Lead-intake monitor (if used) picking up form submissions → CRM → Telegram

© hewi333, MIT. 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 1 other file (references) in skills/small-business-website-spec of hewi333/Mom-n-Pop-Skills.

  • SKILL.md
  • references/base44-pricing.md

Open the folder on GitHubat commit 70a2273

Compare with similar skills

Small Business Website Spec 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.

Small Business Website Spec compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Small Business Website Spec this skillhewi333/Mom-n-Pop-Skills122—~3.2kAutomated safety check: PassMIT
Tabler Menus and Redirectstabler/tabler42k—~1.2kAutomated safety check: PassMIT
Sentry Browser SDKgetsentry/sentry-for-ai268—~6.5kAutomated safety check: NotesApache-2.0
Tabler Astro Dev Servertabler/tabler42k—~1.2kAutomated safety check: PassMIT
Tabler Astro Component Scriptstabler/tabler42k—~2.1kAutomated safety check: PassMIT
Kill AI Slopyetone/kill-ai-slop1.3k—~1.4kAutomated safety check: PassApache-2.0

Similar skills

  • Tabler Menus and Redirects

    tabler/tabler

    Keeps Tabler pages reachable by updating the preview menu, docs menu and redirect table whenever a page is added, renamed, moved or removed.

    42k GitHub stars~1.2k tokensUpdated yesterday
    Frontend & DesignAuto-check passed

  • Sentry Browser SDK

    getsentry/sentry-for-ai

    Official

    Full Sentry SDK setup for browser JavaScript. An agent skill from getsentry/sentry-for-ai.

    268 GitHub stars~6.5k tokensUpdated yesterday
    Frontend & DesignAuto-check: notes

  • Tabler Astro Dev Server

    tabler/tabler

    Starts the right Tabler dev server, keeps it from clashing with builds and verifies changes in the browser before a page or component is handed back.

    42k GitHub stars~1.2k tokensUpdated yesterday
    Frontend & DesignAuto-check passed

  • Tabler Astro Component Scripts

    tabler/tabler

    Rules for adding or fixing client-side scripts in Tabler's Astro components so the copied preview HTML stays readable, self-contained and runs in the right order.

    42k GitHub stars~2.1k tokensUpdated yesterday
    Frontend & DesignAuto-check passed

  • Kill AI Slop

    yetone/kill-ai-slop

    Find and remove AI slop — the generic, machine-default visual and copy tics of vibe-coded products — from a web project.

    1.3k GitHub stars~1.4k tokensUpdated 26 days ago
    Frontend & DesignAuto-check passed

  • Motion Dev Animations

    199-biotechnologies/motion-dev-animations-skill

    Creates 120fps GPU-accelerated animations with Motion.dev (Framer Motion successor) for React, Next.js, Svelte, and Astro projects.

    133 GitHub starsUsed in 1 repo~2.8k tokens
    Frontend & DesignAuto-check: notes

More from hewi333/Mom-n-Pop-Skills

All 13 skills in this repo

  • Construction Business Agent

    hewi333/Mom-n-Pop-Skills

    Runs a construction company's back office by bridging Gmail, Drive and JobTread: routing email attachments to the PM system, checking project status and sending daily Telegram briefings.

    122 GitHub stars~2.3k tokensUpdated 29 days ago
    Auto-check: notes

  • Lead-to-Payment Sales Flow

    hewi333/Mom-n-Pop-Skills

    Runs a small service business lead from intake through estimate, owner approval over Telegram, Stripe payment link and customer email draft to payment tracking.

    122 GitHub stars~2.8k tokensUpdated 29 days ago
    Auto-check: notes

  • QuickBooks Online Integration

    hewi333/Mom-n-Pop-Skills

    Connects a small business to QuickBooks Online for customers, estimates, invoices and payments, using Intuit OAuth 2.0 with token refresh and sandbox or production setups.

    122 GitHub stars~1.9k tokensUpdated 29 days ago
    Auto-check passed

  • Hermes Production Gateway Operations

    hewi333/Mom-n-Pop-Skills

    Procedures for changing the model, restarting and quietly tuning a live Hermes gateway that serves end-users on messaging platforms such as Telegram.

    122 GitHub stars~2k tokensUpdated 29 days ago
    Auto-check: warnings

  • CRM Lite

    hewi333/Mom-n-Pop-Skills

    A skill your agent uses when tracking customer interactions, managing leads, or building a lightweight CRM for small businesses without dedicated CRM software.

    122 GitHub stars~1.5k tokensUpdated 29 days ago
    Auto-check passed

  • Estimator Engine

    hewi333/Mom-n-Pop-Skills

    A skill your agent uses when calculating service estimates for jobs.

    122 GitHub stars~3.1k tokensUpdated 29 days ago
    Auto-check passed

Works with

Categories

Questions about Small Business Website Spec

What does Small Business Website Spec do?

Planning reference for rebuilding a small business website: page structure, copy voice, estimator widget, SEO requirements, form handling, DNS migration, and the no-code vs static-framework decision…. Small Business Website Spec is an agent skill from hewi333/Mom-n-Pop-Skills. Planning reference for rebuilding a small business website: page structure, copy voice, estimator widget, SEO requirements, form handling, DNS migration, and the no-code vs static-framework decision (Base44 vs Astro/Vercel vs WordPress).

When should I use Small Business Website Spec?

Small Business Website Spec fits situations like: tasks that involve Static sites and blogs; tasks that involve Forms and validation.

How do I install Small Business Website Spec in Claude Code?

Run `npx skills add hewi333/Mom-n-Pop-Skills --skill small-business-website-spec -a claude-code`. Or copy the skill folder (skills/small-business-website-spec in hewi333/Mom-n-Pop-Skills) into .claude/skills/small-business-website-spec in your project. Claude Code loads it when a task matches its description.

How do I install Small Business Website Spec in Codex?

Run `npx skills add hewi333/Mom-n-Pop-Skills --skill small-business-website-spec -a codex`. Or copy the skill folder (skills/small-business-website-spec in hewi333/Mom-n-Pop-Skills) into .agents/skills/small-business-website-spec in your project. Codex loads it when a task matches its description.

Can I use Small Business Website Spec 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 hewi333/Mom-n-Pop-Skills --skill small-business-website-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/small-business-website-spec, .gemini/skills/small-business-website-spec, .github/skills/small-business-website-spec and .opencode/skills/small-business-website-spec in your project.

What does Small Business Website Spec need to run?

Going by SKILL.md and its folder, Small Business Website Spec needs the command-line tools its instructions call (npx and git). Our summary lists: Node.js.

Does Small Business Website Spec access the network?

SKILL.md contains no URLs. Its commands use npx and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Small Business Website Spec 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 Small Business Website Spec use?

Small Business Website Spec is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Small Business Website Spec use?

About 3.2k tokens (SKILL.md is roughly 13k 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 594 tokens, read only when the agent opens those files.

What are the alternatives to Small Business Website Spec?

Skills that share tags, products or a category with Small Business Website Spec: Tabler Menus and Redirects (tabler/tabler, 42k stars), Sentry Browser SDK (getsentry/sentry-for-ai, 268 stars), Tabler Astro Dev Server (tabler/tabler, 42k stars) and Tabler Astro Component Scripts (tabler/tabler, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Small Business Website Spec?

hewi333 (a GitHub user) maintains it in hewi333/Mom-n-Pop-Skills, which has 122 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on September 11, 2026.

Source: hewi333/Mom-n-Pop-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.