karero
- 33 skills
- 0 followers
- 3 days ago last updated
- ▌ Website Positioning Check · kareroGive an existing website a fast, fresh-eyes positioning check: can the right visitor tell what is on offer, for whom, and why to believe it? Read-only and concise — a one-screen Clear / Blurred / Broken verdict, the single biggest blur, and the three highest-leverage fixes. Use whenever someone asks if a site's offer is clear, differentiated, outcome-led, too technical, or consistent between homepage and offer pages — even without the word "positioning". Trigger phrases: "is our positioning clear", "fresh eyes on the homepage", "what are we actually selling", "is it obvious who this is for", "we sound too technical", "homepage and services page disagree", "positioning sanity check", "does the site make sense to a stranger". Do not use for developing positioning from scratch (website-positioning), a full copy rewrite (copywriting), an SEO audit, or the pre-launch website-review.
- ▌ Search Console Insights · karero bundlePull and act on Google Search Console DATA for a verified site. Free GSC Search Analytics API (OAuth, read-only): where target keywords rank, striking-distance queries (pos ~8-20), and high-impression/low-CTR pages flagged for snippet/SERP investigation (title/meta rewrite only if the live-SERP check shows a snippet problem you control). Optional add-ons: the live competitor Top-10 via a SERP API, Bing Webmaster Tools query stats, and a weekly check of whether AI engines name the business (GEO). First use runs a guided onboarding for non-technical owners. Trigger phrases: "GSC insights", "Search Console data", "connect GSC", "where do I rank", "top queries", "striking distance keywords", "quick SEO wins", "why is my CTR low", "which pages to optimize", "competitor Top 10", "how do I rank on Bing", "Copilot visibility", "track my rankings over time", "weekly SEO report", "does AI name my business", "weekly AI check", "show me my AI report".
- ▌ Website Testimonials · kareroEncode customer / attendee testimonials as proper schema.org `Review` JSON-LD AND render the "What people say" UI from ONE typed source of truth (`src/data/testimonials.ts`). Individual Review nodes only — author + 5/5 reviewRating + reviewBody + inLanguage + itemReviewed pointing at the SPECIFIC thing reviewed (Event / Product / Service), never a fabricated org-wide AggregateRating. Use when adding quotes, testimonials, social proof, ratings, or star reviews to a site built with the new-website kit (pipeline step 5, alongside `website-seo-geo`). Delegates other schema types to `schema-markup`. Trigger phrases: "add testimonials", "customer quotes", "attendee feedback", "review schema", "star ratings", "social proof section", "encode the quotes", "schema.org Review", "what people say section".
- ▌ Website Content Guide · kareroCreate and maintain a new site's CONTENT_GUIDE.md and BRAND.md — Tone of Voice and EEAT (Experience/Expertise/Authoritativeness/Trust) signals — so every page hangs off one source of truth for HOW it says it. Reads positioning from POSITIONING.md (owned by website-positioning, which runs first); it does not redefine positioning. Use at the start of a new site (step 3 of the new-website pipeline, after website-positioning), before writing page copy, and whenever reviewing/editing copy for voice. Pairs with the tone test (tests/tone.spec.ts) which hard-enforces the voice rules. Trigger phrases: "content guide", "tone of voice", "brand voice", "is this on brand", "EEAT", "E-E-A-T", "write the content guide", "set up the brand doc", "review the copy", "does this sound like AI".
- ▌ Website Design System · kareroThe visual build standards for a new site: mobile-first responsive graphics (WebP/AVIF, sized-to-display, srcset, lazy-load, descriptive alt, no layout shift), dark mode (CSS-variable theme tokens + a no-FOUC script + WCAG AA contrast in BOTH themes), and the brand/theme token block that BRAND.md mirrors. Use when building or reviewing layout, images, theming, or BRAND.md (step 6 of the new-website pipeline). Contrast is enforced by a11y.spec.ts (light+dark). Trigger phrases: "dark mode", "theme toggle", "responsive images", "mobile optimization", "image optimization", "WebP", "layout shift", "CLS", "design system", "theme tokens", "brand colors", "BRAND.md".
- ▌ Website Hero Carousel · karero bundleAdd a photo place whose photos take turns by themselves, with one dot per photo, to a new-website site: a component, one script of the site's own (so a strict Content-Security-Policy holds), its texts in English and German, and tests/hero-carousel.spec.ts. Settings: pause "button" (default, a visible Pause / Resume button) or "dots" (no button, a dot stops it); swap "instant" (default) or "fade". Built to keep the page from jumping, the dots readable on any photo, and phones usable. Run on request, for a home page or any page. Trigger phrases: "photos that rotate", "auto-rotating hero", "carousel", "slider", "key visual that changes", "dots under the photo", "slideshow", "Bildwechsel", "Karussell". Not for one photo (no carousel needed), a gallery the visitor pages through, or video.
- ▌ Business Listings Setup · kareroPost-launch: claim Google Business Profile, Bing Places, and category directories, then verify the `sameAs` profiles already in schema actually resolve. The action skill for E-E-A-T's Authoritativeness component (owned by `website-content-guide`): other pages linking to or citing you are one signal search and AI answer engines read as authority. Human-in-the-loop, same shape as `search-console-setup` — the agent drafts every value, the owner clicks. Trigger phrases: "claim my Google Business Profile", "Google Maps listing", "Bing Places", "business listings", "improve E-E-A-T", "authoritativeness is thin", "sameAs profiles".
- ▌ Search Console Setup · kareroPost-launch: register the LIVE site with Google Search Console and Bing Webmaster Tools, verify ownership, submit the sitemap, and turn on IndexNow so Bing/Yandex get pinged the moment content changes. For a Cloudflare-hosted Astro site: GSC Domain property verified by a Cloudflare DNS TXT record + submit `sitemap-0.xml`; Bing the easy way via "Import from Google Search Console" (auto-verifies + pulls the sitemap); IndexNow by flipping ONE toggle — Cloudflare Crawler Hints — no key file to host. Account creation + the DNS record are human actions the agent drafts but can't click. Trigger phrases: "set up Google Search Console", "Search Console", "GSC", "Bing Webmaster Tools", "submit my sitemap", "register the site with Google", "verify site ownership", "enable IndexNow", "Crawler Hints", "get indexed", "submit the website to search engines".
- ▌ Website Contact Form · karero bundleAdd a contact form to a new-website site that needs no server and no setup: the visitor fills in a few fields, presses a button, and their own email program opens with a message to the owner, ready to send. Nothing is sent or stored by the site. Adds a form component, its texts in English and German, one small script of the site's own (so a strict Content-Security-Policy holds), and tests/mail-form.spec.ts. The owner's address is always shown under the form for visitors without a mail program or without JavaScript. Run when new-website Q2 asks for a contact form, or later when the owner wants one. Trigger phrases: "contact form", "add a form", "enquiry form", "visitors should be able to write to us", "kontaktformular". Not for newsletter sign-up, file uploads, or anything that has to be stored.
- ▌ Website Launch Check · karero bundleLaunch readiness check for a site built with this toolkit: runs the site's own build and tests first, then checks only what they cannot (legal pages, E-E-A-T and local signals, content the site's settings call for, testimonial consent, what only a deployed site shows, the Cloudflare zone settings the owner reads in the dashboard), asks only where the owner's intent decides, and writes a dated report with a verdict to docs/launch/ as Markdown plus a self-contained HTML page. When the site replaces an older one, also a current-vs-new comparison with a redirect map for every old address. Runs three times in new-website (baseline after the scaffold, the verdict before launch, the live re-check once launch day's work is done) and on its own. Trigger phrases: "launch check", "ready to launch", "what's missing before launch", "pre-launch", "go live", "launch audit", "relaunch", "compare the old and the new site", "post-launch gap analysis".
- ▌ Internal Link Audit · kareroInternal-linking tool for an Astro site built with the new-website kit. Builds the site's inbound-link graph from dist/ and reports which pages are ORPHANED (in the sitemap but no internal link points at them), THIN (a single inbound link, no contextual in-body link), or DEEP (more than ~3 clicks from home), then suggests WHERE to add the missing links using `site-architecture`'s internal-linking strategy. The judgment-side complement to the offline `tests/orphans.spec.ts` gate. Run before a release, after adding pages, or when GSC reports orphaned/low-coverage pages. Trigger phrases: "internal link audit", "orphaned pages", "are any pages orphaned", "internal linking", "which pages link to nothing", "fix orphan pages", "improve internal links", "cross-link the comparison pages".
- ▌ Outgoing Link Audit · kareroLiveness audit of every OUTGOING (external) link on an Astro site built with the new-website kit. Builds the site, extracts each external href from dist/, fetches it, and classifies it OK / REDIRECT / REBRAND / DEAD — flagging links that 404, time out, or now redirect to a different domain (a rebrand), with the source page and a suggested fix. This is the network-dependent complement to the offline `tests/links.spec.ts` guard (which only blocks already-known-dead domains from regressing). Run it about once a month, or before a release/launch. Trigger phrases: "audit outgoing links", "check external links", "are our links still live", "monthly link check", "any dead links", "did any linked site rebrand", "link rot check", "review outgoing links".
- ▌ Website Permissions · karero bundleCut the number of permission prompts on a new-website repo to near-zero for the routine build loop, while keeping destructive actions gated. Installs the bundled `.claude/settings.json` allowlist into the project, explains the allow/deny model (npm / astro / playwright / git read verbs and the exact pull and push forms the skills use / gh read verbs and repo create / the link script are pre-approved; `rm -rf`, the usual force pushes, `git reset --hard`, and any `wrangler/gh … delete` are blocked), and safely EXTENDS the allowlist from the commands you keep approving — narrowly, never with a blanket wildcard. The allowlist travels with the repo, so a handoff party also gets the quiet build loop. Trigger phrases: "reduce permission prompts", "too many permission prompts", "stop asking me to approve", "set up permissions for this site", "fewer prompts", "allowlist this repo", "why does it keep asking me".
- ▌ Website Positioning · kareroWork out a new site's POSITIONING before any SEO or content — what you offer, for whom, and the market category it sits in — using April Dunford's five-component framework, captured in POSITIONING.md and threaded through every page's title, description, H1 and schema. Owns the positioning spine; enforced by tests/positioning.spec.ts (a hermetic per-page string test, sibling to the tone test). Use FIRST on a new site (step 2 of the new-website pipeline), before website-content-guide, before page copy, and whenever the offer or audience shifts. Trigger phrases: "positioning", "value proposition", "what are we offering", "who is this for", "market category", "positioning statement", "Dunford", "frame the offer", "how do we describe ourselves".
- ▌ Wordpress Inspector · karero bundleCount what a live WordPress site holds before anyone promises to move it, write the new site's redirects, and check them after the move. Read-only toward the site: no login, no backup. scripts/wp_inventory.py counts each content type the REST API lists, where the sitemap disagrees, page builders and forms, and whether the count is complete. scripts/make_redirects.py turns its address list and the owner's decisions into public/_redirects lines. scripts/check_move.py asks the new site for each old address and names those missing, sent home or not where the decisions say. Stdlib Python. Trigger phrases: "how big is this WordPress site", "count the pages", "WordPress migration estimate", "what plugins does this site use", "write the redirects", "redirect map for the move", "did every page make the move", "check the redirects after the move", "are any old addresses broken".
- ▌ Independent Review · karero bundleDomain-agnostic cross-model review gate: run a planning markdown (PLAN gate) or a branch/PR diff (DIFF gate) through INDEPENDENT external reviewers via scripts/independent_review.sh — the standard pair (Codex + your signed-in ollama-cloud model) runs automatically; Antigravity/Gemini only on explicit opt-in, its credits are scarce. Consolidates a ranked BUG/RISK/NIT list and BLOCKS until every BUG is fixed, refuted, or owner-deferred (only a BUG the change did not introduce), and every RISK/NIT is fixed, refuted, or owner-waived; first use runs a guided onboarding wizard. Use BEFORE building from any non-trivial plan, BEFORE merging any non-trivial PR, and whenever asked for a "codex review", "gemini review", "antigravity review", "agy review", "adversarial review", "cross-model review", "independent review", "get a second model to review", "review before I merge", "which review tool should I use", or to "set up AI code review" / "set up codex, ollama, or antigravity for review".
- ▌ Website Team Setup · karero bundleTurn a one-owner new-website repo into one several people and AI assistants (Codex, Claude Code) can work on at once without overwriting each other: invite collaborators, set the repo settings, prove the CI workflow starts on its own (the fix for a silent one is bundled), block direct pushes to `main`, connect Cloudflare (a Worker, or Pages for an older site) to GitHub without the known traps, write rights, merge rule and who publishes live into `AGENTS.md`, hand the team a one-page guide. Run once, when a second person joins. Use it whenever the user mentions a colleague, client or second assistant joining a site repo, inviting someone to GitHub, "Update branch", pull requests not running CI, or connecting Cloudflare to the repo, even without the word "team". Trigger phrases: "set up the team", "my colleague will work on the site", "invite a collaborator", "block pushes to main", "CI is not running on pull requests".
- ▌ Website Scorecard · karero bundleOPTIONAL public scorecard: publish what a site's own test gate checked, as a dated section on one page. `npm run scorecard` runs the whole suite and writes scorecard.json (checks passed per area, pages, date, tested version); a component renders it and tells the reader when the site was edited after the run. The owner can add the four Lighthouse scores of a PageSpeed run, with a re-run link. A red run writes nothing, so a card never shows a failed run as passed. Never runs unasked: publishing test results is the owner's choice. Ships an opt-in tests/scorecard.spec.ts. Trigger phrases: "publish our test results", "public scorecard", "quality report", "show the Lighthouse scores on the site", "proof the site is tested", "update the scorecard". Not a performance audit (website-qa) and not an SEO report (search-console-insights).
- ▌ Website Tagline · karero bundleOPTIONAL: find the one short line that sits under the logo (the tagline; a German-speaking owner calls it the "Claim"). Leads with purpose: starts from what the business is there to do for its customer, taken from POSITIONING.md, not from clever wording. Shows the owner six to eight candidate lines in three or four different directions, asks which direction sounds like them, then refines on the owner's feedback, for at most three rounds, until they pick ONE or stop. Records it in TAGLINE.md and writes SITE.tagline; ships an opt-in tests/tagline.spec.ts. Adds no claim POSITIONING.md lacks and loses every conflict with it. Never runs unasked. Trigger phrases: "tagline", "Claim", "strapline", "slogan", "motto", "the line under the logo", "a line for under our logo", "what do we stand for in five words". Not for positioning itself, the page headline, or the story one-liner.
- ▌ Astro I18N Setup · karero bundleTurn a new-website scaffold into a turnkey multi-language site: Astro i18n routing (clean default locale + prefixed others), self-referencing hreflang + x-default in the Base layout, i18n sitemap alternates, a language switcher, and the test-harness changes that keep the green-from-commit-1 gate honest across locales. Run at scaffold time when new-website Q4 = "two+ languages at launch", OR later to add a second language to a single-locale site whose default stays unprefixed (phased rollout). Trigger phrases: "multi-language site", "add i18n", "DE+EN site", "internationalization", "hreflang setup", "two languages at launch".
- ▌ Website New Page · karero bundleAdd a page to a site, or rewrite one, so it is worth reading and findable before it is built. Writes one page document (a brief, then the full draft), has a fresh pair of eyes judge it for the reader, for search and AI answers, and for originality, takes the owner's go on the exact sentences, builds, then checks the build kept the approved text. It calls the checks other skills own (website-seo-geo, ai-seo, seo-audit, copywriting, search-console-insights, website-review) and does not repeat them. Use for a new page, a new article, a page rewrite, or "is this page any good". Trigger phrases: "add a page", "new page", "write a page about", "new article", "rewrite this page", "this page feels thin", "what should this page rank for", "review the draft before we build it", "move this page from the old site".
- ▌ Website Brand Kit · karero bundleOPTIONAL colours and logo for a site whose owner is not a designer. Writes three prompts the owner pastes into the design tool she likes (three palettes, five variations of a simple SVG mark, a download package of her favourite), then checks what comes back with code and installs it: contrast of every text colour on every background in both themes, SVG safety, the seven icon files, the theme tokens, the share cards. Refuses and names the problem instead of adjusting anything silently; puts every file back if the site's tests go red. Never runs unasked: asked once after positioning, or run later on an existing site. Trigger phrases: "I need a logo", "pick colours", "colour palette", "brand colours", "favicon", "app icons", "my logo as the favicon", "install my logo", "new colours for the site", "does my palette pass contrast". Not for a tagline, fonts, a raster (PNG/JPG) logo, generated photos (image), or the share-card design (og-images).
- ▌ SEO Reposition · karero bundleReposition a LIVE site whose category/keyword phrasing is not ranking or is being mis-filed by Google/LLMs into unrelated concepts (GSC shows brand-only demand; category pages pull ~0 non-brand impressions). Method proven on two sites: SERP trap-test every candidate phrase → find the winnable wedge → rewording plan with a target-vs-copy rule → GUARD TESTS FIRST (red→green ratchet) → phased gated implementation → ship → schedule a predicted-vs-actual grading run. Review at the plan and PR gates is the owner's choice (the phase gates state the options). Trigger phrases: "reposition the site's SEO", "our keywords collide with X", "we're not ranking for our category", "Google files us under the wrong thing", "trap-phrase audit", "rewording plan", "find our SEO wedge".
- ▌ Website Motion · karero bundleOPTIONAL polish layer: two motion effects that make a long marketing page feel authored rather than dumped — a count-up on hero stat numbers, and a 12px rise-and-fade reveal on section headings — plus the reduced-motion contract, the a11y gate change, and the motion.spec.ts that keep them from silently costing a visitor access to content. Not part of the default new-website build: add it only when a site has a long scrolling homepage and real numbers worth reading. Also carries the one-line hero-height check (a binding min-height:100vh hides the next section at every screen height). Trigger phrases: "add some motion", "scroll reveal", "fade in on scroll", "animate the stats", "count-up numbers", "animated counter", "the page feels flat", "eye candy", "make the homepage less static", "prefers-reduced-motion", "does the animation break accessibility".
- ▌ Website Review · kareroThe Double-Knuth review for a site — a two-pass correctness + cross-file consistency audit run at the END of a build (pre-launch) and after ADDING or substantially editing a page. Pass 1 = bugs/correctness (delegates the diff to /code-review); Pass 2 = completeness + route/URL/SEO/config/email/docs consistency against the site contract. Read-only: returns a ranked BUG/RISK/NIT list with file:line + fixes. Prerequisite: website-qa green. Also owns the "review depth" decision for website work — when this free default suffices vs. an owner-approved single external reviewer for genuinely higher-stakes changes (its "Review depth" section has the rule). Trigger phrases: "double-knuth", "double knuth the site", "review the site", "site review", "final review before launch", "review this page", "did adding the page break anything", "consistency check the site", "audit the site code", "how much review does this need", "do I need a second opinion on this", "should I use independent-review for this".
- ▌ Keystatic Setup · kareroAdd Keystatic — a git-based CMS from the Keystone team — to a new-website Astro scaffold, so a non-technical person can edit content through a UI while the data still rests as Markdown in the GitHub repo. Wires LOCAL storage mode (edit in the dev server, commit/push); documents the GitHub cloud-mode upgrade for browser editing. Run ONCE, at scaffold time, when new-website Q3 = "a non-technical person edits content". Trigger phrases: "add a CMS", "Keystatic", "non-technical editor", "client edits content", "git-based CMS".
- ▌ Website SEO Geo · kareroThe on-page SEO + GEO contract for a new site: exact metadata limits (title 50–60 chars, meta description 140–160 with a 120 floor), og:title/og:description == title/desc, twitter inherits OG, clean canonical == og:url, required JSON-LD schema, and an llms.txt index of the site. Use when building or reviewing a page's head / metadata (step 6 of the new-website pipeline), or when a title/description is too long or tags are out of sync. Enforced by the seo.spec.ts check in the new-website test suite. Delegates depth to ai-seo (GEO) and schema-markup. Trigger phrases: "SEO metadata", "title too long", "meta description length", "og tags", "twitter card", "canonical", "is my SEO set up", "llms.txt", "GEO", "head tags", "structured data on this page".
- ▌ Double Knuth · kareroGeneric two-pass "Double-Knuth" review for ANY repo or file set: Pass 1 = correctness/bugs on the change (delegates to /code-review when a git diff exists, agent-based otherwise), Pass 2 = completeness + cross-file/doc consistency — the defect class a diff reviewer structurally cannot see (stale counts/enumerations, docs contradicting changed behavior, dead paths, orphaned files, contract drift). Read-only: returns a ranked BUG/RISK/NIT list with file:line + concrete fixes. Specialized versions take precedence: websites → website-review; this skill covers everything else (skill suites, scripts, tools, configs). Trigger phrases: "double knuth this", "double knuth the code", "double knuth the repo", "two-pass review", "consistency review", "did the docs drift", "review the whole repo, not just the diff".
- ▌ Website Story · karero bundleOPTIONAL story layer: narrate the home page as the customer's story — the visitor as hero, their problem as the villain, the brand as the guide with a three-step plan — captured in STORY.md and mapped onto a seven-section home page. Inspired by Donald Miller's StoryBrand framework, in this suite's own words. POSITIONING.md still decides WHAT is claimed; STORY.md decides only how the home page tells it and loses every conflict. Never runs unasked: offered once after website-positioning, or run later on an existing site when asked. Ships an opt-in tests/story.spec.ts. Trigger phrases: "tell it as a story", "customer as the hero", "story layer", "StoryBrand", "one-liner", "grunt test", "homepage reads like a feature list", "lead magnet", "what do they lose if they do nothing". Not for positioning itself, voice, or a quick check.
- ▌ New Website · karero bundleOrchestrates building a NEW website end-to-end, from insights to launch-ready and handoff-ready. Self-contained: it runs the stack decision interview, sequences the website-* skills + existing marketing skills in order, and scaffolds the project from its own templates/ (Astro starter overlay + full QA test suite + GDPR privacy draft + owner docs + permission allowlist), copying the bundled skill set into the project's skills dir (full copy list in §3) so the repo is self-contained for a third party. Default stack Astro → GitHub → Cloudflare Workers. Use at the very start of any new site. Trigger phrases: "new website", "start a new site", "scaffold a website", "spin up a site", "build a new website", "set up a new web project", "website starter", "which stack for this site".
- ▌ Facts Check · karero bundleRead-only consistency check of any live site, on any stack. FACTS: one approved facts list (value, source, owner); scripts/facts_check.py reports every figure on the sitemap's pages that differs from it (text, titles, descriptions, alt texts, structured data, llms.txt) and retired phrases (old names, taglines, claims) still in use. POSITIONING: rules map page paths (/en/business/*) to an audience and the term each page owns; it lists pages that lost the term in title, meta description or H1/intro, as the starter's positioning test does. AI answer engines quote whatever figure and wording they find. Stdlib Python; runs weekly beside the AI check, in-house. Trigger phrases: "facts check", "check our figures", "do our pages contradict each other", "claims register", "is the old name still on the site", "positioning check of the live site", "do our pages still carry their terms".
- ▌ Og Images · kareroGenerate branded per-page Open Graph (social share) cards for a website: a 1200×630 JPEG ≤300 KB for every page, rendered by a committed Python+Pillow script and wired so each page sets its own `image=` (with a default fallback) and the test suite proves the card exists at the right size. Use when building or auditing a site's share previews — "OG image", "og:image", "social share image", "share card", "WhatsApp/Slack/LinkedIn preview", "Twitter card image", "the picture when I share the link", "per-page OG images", "generate share images". For general marketing image creation/optimization use the `image` skill; this one is specifically the build-time, tested, per-page card generator for the suite's Astro starter.
- ▌ Website QA · kareroThe pre-launch QA gate for a new site: run the starter's basic tests (a11y light+dark, seo, navigation, images, tone, positioning, placeholders, email, links and the rest of tests/*.spec.ts), fix to green, then handle technical SEO / performance — run Lighthouse on the deployed site (PageSpeed Insights as the fallback) and act on First Contentful Paint (FCP) and Largest Contentful Paint (LCP). Use before launch (steps 7–8 of the new-website pipeline) and after any code/copy change. Delegates Core Web Vitals / crawl depth to seo-audit. Trigger phrases: "run the tests", "QA the site", "is the site launch ready", "a11y check", "accessibility test", "Lighthouse", "PageSpeed", "FCP", "LCP", "page speed", "Core Web Vitals", "performance check", "are the tests green".