belschak
- 10 skills
- 0 followers
- 8 hours ago last updated
- ▌ Repo Audit · belschak bundleSecurity audit of any third-party repo, package, skill, plugin, or MCP server BEFORE it is installed or executed. Use this skill whenever the user asks "is this safe?", "audit/vet/check this repo", "should I install X", pastes a GitHub/npm/PyPI/marketplace link with intent to install, or whenever you yourself are about to recommend or install third-party code, even if nobody says the word "audit". Covers maintainer reputation, typosquatting, install-time hooks, obfuscation, exfiltration and secrets-harvesting patterns, dependency and CI risks, and prompt injection in agent-facing files (skills, agent configs, MCP tool descriptions). Produces a SAFE / SAFE-WITH-CONDITIONS / UNSAFE verdict with evidence, transparent red flags, and conditions such as version pinning.
- ▌ Claude Design Handoff · belschak bundleContent-first pipeline for Claude Design handoffs, so facts, numbers, and links survive the design pass. Use whenever a Claude Design share link appears in conversation (an api.anthropic.com/v1/design/h/... tar.gz bundle or a claude.ai/design/p/... project link), whenever an existing document is being sent to Claude Design to "make it beautiful", whenever the user wants a polished long-form document for an external recipient (family, a client, an authority, an investor; "magazine layout", "a PDF that does not look like a default word processor"), or, on the web track, whenever a website or UI should get art direction from Claude Design before engineering. Core pattern: freeze facts in FROZEN blocks before design, brief Claude Design with hard constraints, then mechanically re-verify the output against the source. Claude Design rewrites content while designing; one unguarded run produced 23 fact-check findings, 4 of them critical. Not for short notes of one to three pages, internal working documents, day plans
- ▌ Parallel Streams · belschak bundleSplit a larger project into independent work streams and build them in several parallel headless claude -p terminals at once. Limit-tolerant: when the subscription window is exhausted, every stream pauses automatically and resumes until its done marker exists. Use when the user says "in multiple terminals", "build in parallel", "streams", "build through the night", "split it up and run simultaneously", "overnight run", "keep going even when the limit hits", or when a build job is clearly too big for one session (3+ independent work packages). Also use when the user wants to watch running streams live, steer one ("tell stream B that..."), pause one, or take over interactively (steer file / takeover). Not for small tasks (<3 packages: subagents or sequential work).
- ▌ Publish Gate · belschak bundleMandatory security, legal, and quality gate BEFORE anything goes public. Always run when a GitHub repository is about to be created, made public, or pushed; when something is submitted to a package registry or marketplace (npm, PyPI, a skills directory); when a blog post, gist, or artifact containing code or config is published; or when the user says "make it public", "publish", "push the repo", "launch", "release", "go live". Also trigger when publishing is only a sub-step of a larger task, when it seems urgent, or when someone claims "it was already checked". Nothing is published without a complete gate run and an explicit human go.
- ▌ Showpiece · belschak bundleBuild real, shippable, studio-grade artifacts: production websites, portfolios, landing pages, and high-end slide decks or presentations. Use this skill whenever the user wants to create, rebuild, or seriously upgrade an actual website or a real presentation/deck, mentions a portfolio, a landing page, "a real/proper website", "launch", "slides", a client-facing deck, or says "make it as good as possible" about a visual artifact, even if they do not name a tool. It orchestrates a full pipeline: lock the brief, decide the design system (frontend-design taste plus a vendored UI/UX design database), extract design DNA from reference sites or videos, build section by section, run a Playwright screenshot verify-loop, and optionally hand off a Claude Design link for last-mile tuning. Do NOT use this for quick throwaway mockups, a single HTML snippet, a small UI tweak, or visualizing internal research/reports; those are lighter and belong to the frontend-design skill. This is the high-ambition path; frontend-design i
- ▌ Web Research Cascade · belschak bundleA robust web-fetch cascade so that blocked primary sources still get read instead of being silently skipped. Use this skill whenever a URL is fetched, a page needs to be researched, or WebFetch/WebSearch returns a 403/401/429/"unable to fetch"/empty body/CAPTCHA. Also use it for any analysis or comparison research where primary sources matter (not just secondary blogs), and on "read this page", "what does X say", "research Y", "look at this". Cascade: WebFetch, then Jina Reader, then a Firecrawl script (sparingly), then Chrome (browser MCP). Also covers Reddit (threads, subreddits, search) and single X/Twitter tweets, which need their own route instead of the generic cascade. Core rule: a good but blocked source is opened via the cascade, NEVER swapped for a weaker error-free one.
- ▌ Map Scout · belschakAnalyze a city, region, or radius ("15 km around X") and build ranked Google Maps Saved Lists of the best places: restaurants, cafes and breakfast, sights, activities, bars. Research from three source families (Google Maps + TripAdvisor + independent blogs, one third weight each; if TripAdvisor blocks entirely, the other two carry half each), Bayesian rating adjustment, percentile scoring, top 3 per list marked 🥇🥈🥉 plus a ⭐ top-picks list. Use on "scout <place>", "analyze <place> for our trip", "best restaurants/cafes in <place>", "what should we eat or do in <destination>", and any vacation prep that should end in Maps lists, even when the word "Maps" never appears. NOT for flights, hotels, or route planning, and not for pure Maps UI mechanics without research (that is the google-maps skill).
- ▌ Google Maps · belschak bundleCurate Google Maps through the user's own logged-in Chrome (Playwright over CDP). Create Saved Lists, set list emoji icons, save places in ranked order, write per-place notes, generate share links, delete lists; fall back to My Maps for custom lat/lng pins, colored layers, and CSV bulk import. Use whenever a task should end with places on Google Maps or touches existing Maps lists, even if the word "Maps" never appears: "make a list of these restaurants", "save these places", "share a map with the group", "pin these spots", "add notes to my saved places", "toggle themed lists", any trip prep whose result belongs on the user's phone. Not for researching or ranking the places themselves; that is the map-scout skill.
- ▌ Video Watch · belschak bundleTranscribe YouTube videos and podcast episodes in high quality (Whisper via a configurable API endpoint) and distill compact findings with timestamps. Use whenever the user wants a video "watched", summarized, transcribed or analyzed, drops a YouTube or podcast URL together with a question, asks "what does he say about X in that video", or follows up on an earlier video folder, even when the word "transcribe" never appears. For visual questions, frames can be extracted on top. NOT for local audio files (voice memos, recordings); that is the audio-transcribe skill.
- ▌ Audio Transcribe · belschak bundleTranscribe local audio files (voice memos, meeting recordings, dictations, interviews; m4a/mp3/wav/opus/ogg/flac, also the audio track of local video files) in high quality via Whisper (configurable API endpoint) and place the transcript as a dated .md next to the source file. Use whenever the user drops an audio file, mentions a path to a recording, or wants its content as text: "transcribe this", "what do I say in the recording", "turn this into text", "summarize the memo", even without the word "transcribe". NOT for YouTube or podcast URLs; that is the video-watch skill.