Agent skill

Ship Check

by textura-agency in textura-agency/next16-claude-starter

Pre-launch gate for this starter — build, mechanical rule checks, SEO, metadata and brand-kit completeness, the robot form, measured load (Lighthouse people + robot) and scroll (PC + phone)…

UnlicenseAuto-check: notesFrontend & Design

Install Ship Check

skills CLI

$ npx skills add textura-agency/next16-claude-starter --skill ship-check -a claude-code

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

GitHub CLI

$ gh skill install textura-agency/next16-claude-starter ship-check --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/textura-agency/next16-claude-starter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/ship-check .claude/skills/ship-check && 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/

Paste into Claude Code

Install the "ship-check" agent skill from https://github.com/textura-agency/next16-claude-starter/tree/main/.claude/skills/ship-check into .claude/skills/ship-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-check", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/textura-agency/next16-claude-starter/tree/main/.claude/skills/ship-check

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add textura-agency/next16-claude-starter --skill ship-check -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install textura-agency/next16-claude-starter ship-check --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/textura-agency/next16-claude-starter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/ship-check .agents/skills/ship-check && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ship-check" agent skill from https://github.com/textura-agency/next16-claude-starter/tree/main/.claude/skills/ship-check into .agents/skills/ship-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-check", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add textura-agency/next16-claude-starter --skill ship-check -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install textura-agency/next16-claude-starter ship-check --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/textura-agency/next16-claude-starter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/ship-check .cursor/skills/ship-check && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ship-check" agent skill from https://github.com/textura-agency/next16-claude-starter/tree/main/.claude/skills/ship-check into .cursor/skills/ship-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-check", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/textura-agency/next16-claude-starter.git --path .claude/skills/ship-check

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add textura-agency/next16-claude-starter --skill ship-check -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install textura-agency/next16-claude-starter ship-check --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/textura-agency/next16-claude-starter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/ship-check .gemini/skills/ship-check && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "ship-check" agent skill from https://github.com/textura-agency/next16-claude-starter/tree/main/.claude/skills/ship-check into .gemini/skills/ship-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-check", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install textura-agency/next16-claude-starter ship-check

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add textura-agency/next16-claude-starter --skill ship-check -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/textura-agency/next16-claude-starter.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/ship-check .github/skills/ship-check && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "ship-check" agent skill from https://github.com/textura-agency/next16-claude-starter/tree/main/.claude/skills/ship-check into .github/skills/ship-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-check", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add textura-agency/next16-claude-starter --skill ship-check -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install textura-agency/next16-claude-starter ship-check --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/textura-agency/next16-claude-starter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/ship-check .opencode/skills/ship-check && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ship-check" agent skill from https://github.com/textura-agency/next16-claude-starter/tree/main/.claude/skills/ship-check into .opencode/skills/ship-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-check", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: ship-check
GitHub stars: 133
Token cost: ~1.5k tokens
SKILL.md length: 657 words
Files: 1
Skills in repo: 16
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Unlicense

At a glance

Pre-launch gate for this starter — build, mechanical rule checks, SEO, metadata and brand-kit completeness, the robot form, measured load (Lighthouse people + robot) and scroll (PC + phone)…

Works in 9 steps: It builds and it obeys the rules → It is correct → It can be found → …
The user says ready to ship
SKILL.md covers 1. It builds and it obeys the…, 2. It is correct, 3. It can be found and 4. It is fast, plus 5 more sections
Calls node, yarn and curl

What it does

Ship Check is an agent skill from textura-agency/next16-claude-starter. Pre-launch gate for this starter — build, mechanical rule checks, SEO, metadata and brand-kit completeness, the robot form, measured load (Lighthouse people + robot) and scroll (PC + phone), real-phone behaviour, accessibility, env and secret hygiene, the deploy steps and a closing retro. Use when the user says "ready to ship", "deploy this", "launch checklist", "is this production ready", or before handing a site to a client.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Web performance, Brand strategy and identity and Product launch strategy. The repository describes itself as: AI-first Next.js 16 starter for animation-heavy sites, wired with an Obsidian vault & Claude Code hooks. The licence is Unlicense.

When your agent uses it

The user says ready to ship
Launch checklist
Is this production ready
Before handing a site to a client

Example prompts

“ready to ship”
“deploy this”
“launch checklist”
“/ship-check”

Requirements

Pre-approved tools (allowed-tools): Bash, Read, Grep, Glob, Edit, Write, WebFetch

Workflow steps

9 steps, taken from the step headings in SKILL.md.

It builds and it obeys the rules
It is correct
It can be found
It is fast
It works on a phone in a hand
It is usable by everyone
Nothing leaks
Deploy
Hand over — and retro

What it can do on your machine

Read from SKILL.md and the folder at commit 6c6edf9. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash
- Read
- Grep
- Glob
- Edit
- Write
- WebFetch
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- node
- yarn
- curl
- git
- vercel
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use yarn, curl, git and vercel, 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

Ship Check loads about 1.5k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 657 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~110
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:93

- `.env` is gitignored; `.env.example` documents every key with placeholder values

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Bash, Read, Grep, Glob, Edit, Write, WebFetch
```

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 textura-agency/next16-claude-starter at commit 6c6edf9, republished under its Unlicense licence (© textura-agency). 657 words, ~1,473 tokens.

Download SKILL.mdSave it as .claude/skills/ship-check/SKILL.md (or your agent's skills folder).

name: ship-check
description: Pre-launch gate for this starter — build, mechanical rule checks, SEO, metadata and brand-kit completeness, the robot form, measured load (Lighthouse people + robot) and scroll (PC + phone), real-phone behaviour, accessibility, env and secret hygiene, the deploy steps and a closing retro. Use when the user says "ready to ship", "deploy this", "launch checklist", "is this production ready", or before handing a site to a client.
allowed-tools: Bash, Read, Grep, Glob, Edit, Write, WebFetch

Ship check

Run in order. Anything unchecked is stated as unchecked in the summary — never assume a pass.

1. It builds and it obeys the rules

bash

yarn lint
yarn build                       # must pass, no warnings you cannot explain
.claude/scripts/verify.sh        # zero FAILs

2. It is correct

Run the qa-verify skill across the site — every route, every breakpoint. Then click through the real thing: yarn build && yarn start, not just dev.

3. It can be found

Run the seo-audit skill. Non-negotiable before launch:

every public route is in sitemap.ts; every href resolves (no 404s from nav items or the banner's /privacy-policy)
robots.ts allows crawling and no staging noindex survives
NEXT_PUBLIC_SITE_URL set in the production environment — and on the deployed site the canonical names the real domain and curl -sI <og:image> returns 200
no TODO: placeholder in src/lib/site.ts (a production build fails on them by design); the brand kit is the site's own — favicon set from its logo, a 1200×630 share image you looked at (tools/qa/brand-kit.mjs)
unique title + description per route
the robot form: curl -A "Googlebot/2.1" and -A "GPTBot/1.0" get <meta name="x-robot-view">, the same title/canonical/<h1>, no text under a hidden ancestor; the human / is still prerendered (optimize-load/references/robot-path.md)
Organization + WebSite JSON-LD renders and validates
if this replaces an existing site → the site-migration skill's redirect map is live and verified

4. It is fast

Measure, do not guess — against the deployed URL (localhost is a floor: one site's mobile LCP was 4.8 s local, 31 s hosted). If a WebGL/three.js scene exists → the optimize-3d-scene skill first.

bash

node tools/qa/lighthouse.mjs  --url https://<deploy>/ --runs 3   # people, mobile + desktop
node tools/qa/lighthouse.mjs  --url https://<deploy>/ --as-bot   # the robot form (what PageSpeed sees)
node tools/qa/scroll-test.mjs --url https://<deploy>/ --first-scroll   # PC wheel + phone touch, cold + warm, + the unlock moment
node tools/qa/axe-sweep.mjs   --url https://<deploy>/            # contrast through the entrance
node tools/qa/check-motion.mjs --url https://<deploy>/           # reduced motion + robot don't hang

Performance ≥ 90 on mobile and desktop; Accessibility, Best Practices, SEO = 100 — people and robot (optimize-load). A gap is stated with its number and cause.
Scroll ideal on PC and phone: no frame > 50 ms, ≤ 1 % dropped (optimize-performance). Lighthouse never scrolls.
LCP ≤ 2.5 s, CLS ≤ 0.1, INP ≤ 200 ms; grep -l ZodError .next/static/chunks/*.js prints nothing.

5. It works on a phone in a hand

Run the mobile-device-qa skill's close-out: iOS toolbar probe and context-loss probe for any live scene, scene fps (no fixed phone caps), the menu in light and dark scheme, overflow at 320–430, touch sliders, WebKit for anything iOS-only. Then push a preview and have the client (or a teammate) open it on their phone, naming what to try. State what could only be checked in emulation.

6. It is usable by everyone

Keyboard-only pass through every interactive element; focus always visible
prefers-reduced-motion honoured — content readable with motion off
Contrast AA; alt text everywhere; landmarks named
44px touch targets; no horizontal scroll at 320px
tools/qa/resize-check.mjs — live resizes and device-preset switches land where a fresh load does

Show full SKILL.md (243 more words)Show less

7. Nothing leaks

bash

grep -rniE "sb_secret|service_role|BEGIN (RSA|PRIVATE)" src/ .env.example
git log --oneline -20            # no secrets in history

Every secret is server-only via getServerEnv(); nothing sensitive is NEXT_PUBLIC_
.env is gitignored; .env.example documents every key with placeholder values
Every production env var is actually set on the host — a missing one fails the zod parse at boot, which is the intended behaviour, so check before launch not after

8. Deploy

Vercel is the default target for this stack (vercel → vercel --prod, or a Git integration). Confirm after deploying:

production env vars set for the Production environment, not just Preview
custom domain + HTTPS resolving, www/apex normalised one way
if Payload is installed: payload migrate has run against the production database, and push is false in production
a real page loads, a form submits, an image from storage renders
a Git-connected deploy that stops updating production: check the commit author's email belongs to the Vercel team (a repo-local user.email outside the team blocked every deploy on three sites for months)

9. Hand over — and retro

Summarise: what was checked and passed, what failed and was fixed, what could not be verified and why, plus the measured numbers (the grid, the scroll verdicts). Update obsidian/meta/changelog.md with the launch.

Then a short retro, for the next project cut from this starter: a measured fix worth reusing → obsidian/knowledge/fix-catalog.md (symptom, fix, before → after, rule/observed); something that misled you → obsidian/knowledge/pitfalls.md; a defect that came from the starter itself → note it there as a starter fix candidate; a skill that was wrong or silent → edit it.

Files

Just SKILL.md in .claude/skills/ship-check of textura-agency/next16-claude-starter.

Open the folder on GitHubat commit 6c6edf9

Compare with similar skills

Ship Check 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.

Ship Check compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Ship Check this skilltextura-agency/next16-claude-starter	133	—	~1.5k	Automated safety check: Notes	Unlicense	4 days ago
Landing CraftEliasOulkadi/shokunin	114	—	~4.5k	Automated safety check: Pass	MIT	6 days ago
Roier SEOdavila7/claude-code-templates	33k	—	~2.7k	Automated safety check: Pass	MIT	yesterday
Web Quality Auditaddyosmani/web-quality-skills	2.9k	—	~2.6k	Automated safety check: Pass	MIT	1 mo ago
Web Quality Auditmidudev/100cosas.dev	114	3 repos	~1.7k	Automated safety check: Pass	MIT	12 days ago
Accessibilityericrisco/rsc-harness	190	—	~3.4k	Automated safety check: Pass	MIT	today

Similar skills

Landing Craft
EliasOulkadi/shokunin
Build conversion-optimized landing pages with CRO frameworks (Conversion Research, LIFT Model), scroll effects, A/B testing, personalization, form optimization, and Core Web Vitals (INP, LCP, CLS).
114 GitHub stars~4.5k tokensUpdated 6 days ago
Frontend & DesignAuto-check passed
Roier SEO
davila7/claude-code-templates
Technical SEO auditor and fixer. An agent skill from davila7/claude-code-templates.
33k GitHub stars~2.7k tokensUpdated yesterday
Frontend & DesignAuto-check passed
Web Quality Audit
addyosmani/web-quality-skills
Run an evidence-led web quality audit covering performance, accessibility, SEO, best practices, and agentic browsing.
2.9k GitHub stars~2.6k tokensUpdated 1 mo ago
Frontend & DesignAuto-check passed
Web Quality Audit
midudev/100cosas.dev
Comprehensive web quality audit covering performance, accessibility, SEO, and best practices.
114 GitHub starsUsed in 3 repos~1.7k tokens
Frontend & DesignAuto-check passed
Accessibility
ericrisco/rsc-harness
A skill your agent uses when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast…
190 GitHub stars~3.4k tokensUpdated today
Frontend & DesignAuto-check passed
Web Perf
elithrar/dotfiles
Diagnose page-load and interaction performance using browser traces, network evidence, and source code.
202 GitHub stars~721 tokensUpdated today
Frontend & DesignAuto-check passed

More from textura-agency/next16-claude-starter

All 16 skills in this repo

Mobile Device QA
textura-agency/next16-claude-starter
Make a site behave on real phones — the defects no Lighthouse run or headless scroll test sees, learned from site owners reviewing production sites on an iPhone.
135 GitHub stars~5k tokensUpdated yesterday
Auto-check: notes
Optimize Load
textura-agency/next16-claude-starter
Get a page into Lighthouse's green zone on desktop and mobile, for people AND for the robot form crawlers get — build it, audit all four categories (Performance, Accessibility, Best Practices, SEO)…
135 GitHub stars~4.6k tokensUpdated yesterday
Auto-check: notes
Optimize Performance
textura-agency/next16-claude-starter
Make a page in this starter actually smooth — build it, scroll it in real Chrome on PC and on an emulated phone, fix what the measurement blames, re-measure to prove it.
135 GitHub stars~3.7k tokensUpdated yesterday
Auto-check: notes
Payload Admin
textura-agency/next16-claude-starter
Make a Payload admin feel like part of the site and explain itself — the skin re-tinted from the site's own tokens (calm, light, no added motion), the site's wordmark and favicon, a dashboard…
135 GitHub stars~1.5k tokensUpdated yesterday
Auto-check passed
Payload Cms
textura-agency/next16-claude-starter
Put a Payload CMS admin on a site built from this starter — every visible string and content photo editable, derived from the site's own content objects with the code's copy as the fallback, a…
135 GitHub stars~3.7k tokensUpdated yesterday
Auto-check: notes
Aeo Visibility
textura-agency/next16-claude-starter
Answer Engine Optimisation — make the site citable by ChatGPT, Claude, Perplexity, Gemini and AI Overviews.
135 GitHub stars~1.4k tokensUpdated yesterday
Auto-check: notes

Questions about Ship Check

What does Ship Check do?

Pre-launch gate for this starter — build, mechanical rule checks, SEO, metadata and brand-kit completeness, the robot form, measured load (Lighthouse people + robot) and scroll (PC + phone)…. Ship Check is an agent skill from textura-agency/next16-claude-starter. Pre-launch gate for this starter — build, mechanical rule checks, SEO, metadata and brand-kit completeness, the robot form, measured load (Lighthouse people + robot) and scroll (PC + phone), real-phone behaviour, accessibility, env and secret hygiene, the deploy steps and a closing retro.

When should I use Ship Check?

Ship Check fits situations like: the user says ready to ship; launch checklist; is this production ready; before handing a site to a client.

How do I install Ship Check in Claude Code?

Run `npx skills add textura-agency/next16-claude-starter --skill ship-check -a claude-code`. Or copy the skill folder (.claude/skills/ship-check in textura-agency/next16-claude-starter) into .claude/skills/ship-check in your project. Claude Code loads it when a task matches its description.

How do I install Ship Check in Codex?

Run `npx skills add textura-agency/next16-claude-starter --skill ship-check -a codex`. Or copy the skill folder (.claude/skills/ship-check in textura-agency/next16-claude-starter) into .agents/skills/ship-check in your project. Codex loads it when a task matches its description.

Can I use Ship Check 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 textura-agency/next16-claude-starter --skill ship-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ship-check, .gemini/skills/ship-check, .github/skills/ship-check and .opencode/skills/ship-check in your project.

What does Ship Check need to run?

Going by SKILL.md and its folder, Ship Check needs the command-line tools its instructions call (node, yarn, curl, git and vercel). Its frontmatter pre-approves these tools: Bash, Read, Grep, Glob, Edit, Write, WebFetch.

Does Ship Check access the network?

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

Is Ship Check safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file; pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Ship Check use?

Ship Check is published under the Unlicense licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ship Check use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ship Check?

Skills that share tags, products or a category with Ship Check: Landing Craft (EliasOulkadi/shokunin, 114 stars), Roier SEO (davila7/claude-code-templates, 33k stars), Web Quality Audit (addyosmani/web-quality-skills, 2.9k stars) and Web Quality Audit (midudev/100cosas.dev, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ship Check?

textura-agency (a GitHub organization) maintains it in textura-agency/next16-claude-starter, which has 133 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 7, 2026.

Source: textura-agency/next16-claude-starter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Ship Check

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Ship check

1. It builds and it obeys the rules

2. It is correct

3. It can be found

4. It is fast

5. It works on a phone in a hand

6. It is usable by everyone

7. Nothing leaks

8. Deploy

9. Hand over — and retro

Files

Compare with similar skills

Similar skills

More from textura-agency/next16-claude-starter

Related

Questions about Ship Check