chekos

Run a Tunelito live review room for a local HTML/Markdown file or folder, then process the comments it collects. Use whenever a user wants to share, serve, or preview a local .html page, .md memo, or static site/mini-site from their machine so a designer, client, teammate, or PM can leave feedback on a call; wants a temporary public link to a local page; says "review my HTML", "annotate this page", "review this Markdown draft", "let people comment on my site", "get feedback on index.html", "spin up a review room", or "review this page locally without exposing it"; OR points you at a `*.comments.md` / `site.comments.md` inbox and asks you to apply, process, or act on the comments inside it. Covers starting and sharing a session (Cloudflare Tunnel, keyed bearer URLs), local-only review of sensitive pages, active-agent `tunelito inbox` commands, the opt-in `--agent` worker that edits files from comments, and the comment Markdown schema (scope, page, path, id, status). Do NOT use for reviewing a pull request, IDE

Update or review Tunelito documentation. Use when README, changelog, release docs, examples, security docs, or agent playbooks need to stay in sync with behavior.

Run a live local Tunelito smoke test against an HTML page. Use before declaring browser/client/server/package changes ready.

Prepare Tunelito changes for a PR-ready commit and push, including verification and handoff summary.

Maintain Tunelito npm package quality. Use for package.json, package-lock, npm pack, npm install smoke tests, CI workflows, release docs, or distribution changes.

Prepare a Tunelito package or npm release using the release playbook and package verification.

Maintain Tunelito's agent operating system. Use when editing AGENTS.md, CLAUDE.md, .claude hooks, .claude skills, .claude agents, or docs/agents playbooks.

Reproduce and fix Tunelito bugs. Use when behavior is broken, tests fail, comments do not sync, tunnels fail, mobile selection fails, or the CLI does something surprising.

Audit and modernize aging repositories so they become clean, current, safe, and agent-friendly. Use this skill whenever the user says a repo is old, vibe-coded, stale, confusing, over-engineered, has technical debt, needs cleanup, needs modernization, should be brought up to speed, or should be made agent-friendly or agent-ready — even if they only say "I haven't touched this in a while" or "look around and tell me what's here". Also use it when docs/specs/todos may no longer match the implementation, when tests or builds need a fresh baseline, when CLAUDE.md or agent instructions look outdated, or when the user wants obsolete repo context deleted because git history is the archive.

Generate and edit images using Gemini's Nano Banana Pro model (gemini-3-pro-image-preview). Use this skill when the user asks you to generate images, create visuals, edit photos, create logos, generate product mockups, or perform any image generation/editing task.

Update existing articles with new information, fix outdated content, and republish for renewed reach. Use when content is 6+ months old, tools/libraries have updated, or there's new information to add. Maintains SEO value while providing fresh value to readers.

Use this skill to evaluate, score, and improve essays using Michael Dean's Pattern Language framework. Based on Christopher Alexander's architectural pattern language concept, this provides a systematic approach with 27 interconnected patterns organized into 3 dimensions (Idea, Form, Voice) and 9 elements. Use for essay evaluation, scoring (1-5 per pattern), identifying weaknesses, providing targeted feedback, and guiding systematic improvement.

Verify claims in a draft before publication. Use this skill when reviewing essays, posts, or articles for factual accuracy, checking code examples work correctly, validating statistics and sources, or verifying quotes and attributions. Produces a structured fact-check report with verdicts for each claim.

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive Signs of AI writing guide.

Add, answer, and resolve [!comment] callouts in Obsidian markdown files. Use when leaving editorial comments on a draft, replying to existing comment threads, resolving addressed feedback, flagging claims that need sources, or reviewing writing with annotations instead of direct edits. Defines the callout format: author, date, text reference, type tags ([edit], [question], [flag]), threading, and resolution.