Find the open-source solution that fits.

Use this skill to draft or review labels, errors, empty states, onboarding, settings, and AI feature copy, with several options and concise tradeoffs. Its guidance is grounded in established US design systems and checks accessibility, inclusive language, and localization risks. It is intended for product interfaces, not blogs, ads, landing pages, or email campaigns.

Use zero-cost-deploy as an agent-driven playbook for shipping a web app with Vercel, Render, Supabase, Upstash, and GitHub Actions free tiers. It covers setup, secrets, database migrations, environment variables, custom domains, smoke tests, and documented workarounds for common deployment failures. The stack still carries free-tier constraints, including Render cold starts, storage and usage caps, single-region operation, and Vercel Hobby's non-commercial terms.

Keito Time Track installs lifecycle hooks for Claude Code and Codex, maps each Git worktree to a Keito company, client, project, and task, and records one agent-sourced time entry when a session ends. Credentials stay with the Keito CLI, while the repository stores only local identifiers in `.keito/config.yml`. Each repository needs its own setup, and the best-effort hooks log failures without breaking the coding session.

buy-me-a-car combines 16 Claude Code skills into a buyer-side workflow for vehicle research, quote collection, out-the-door calculations, dealer replies, CARFAX review, insurance, and closing checks. The full flow searches multiple sites and creates Gmail drafts for review rather than sending binding messages automatically. It is a single-author alpha, and fee, incentive, and eligibility data can drift, so figures should be verified before signing.

Use slidoc to extract slide frames from lecture or training videos, transcribe the audio locally with whisper.cpp, align narration to each frame, and produce searchable Markdown notes. You can run its Python CLI stage by stage or let the bundled Claude Code skill drive the workflow. It requires ffmpeg, whisper.cpp, and a local Whisper model, and transcription of long batches can still take several hours.

Portfolio README Writer documents a finished project for either a personal portfolio audience or a hackathon judge. It reads the repository, asks only for details it cannot infer, and writes a structured README with a pitch, quick start, stack, architecture, caveats, and mode-specific sections. It avoids emoji and inflated language, shows a diff before replacing an existing README, and does not modify code, media, or deployment.

Use mdrise when a README, report, or article needs a polished web version without changing its wording. The Claude skill chooses a visual treatment based on the document type, adds a floating table of contents, supports many writing systems, and embeds a source hash so unchanged Markdown is not rendered again unnecessarily.

Use this lightweight skill when you already know the gameplay-video workflow and want a concise output. It delivers six image prompts, video prompts, and a minimal UI dictionary while keeping four-view character references, HUD anchors, opening-frame guidance, and aspect-ratio constraints. It omits process explanations, checklists, generation steps, and post-production notes to save context.

Browse a verified catalog of Telegram Premium Emoji IDs with previews, search, sections, and fallback characters. The accompanying Claude Code skill can choose icons for a bot style and generate aiogram code, while the Telegram bot accepts new emoji descriptions and pushes catalog updates to GitHub Pages. Running the update bot requires Telegram and GitHub credentials.

Deck Pipeline takes a Chinese presentation through design analysis, page-by-page English rewriting, layout checks, and a documented handoff. It produces edited PPTX files and a bilingual comparison workbook, while a polish-only mode can clean up single-language decks without translating them. Slide checkpoints let users correct terminology or direction before changes spread across the deck.

Mirador lets several people refine the same Markdown-based artifact while each collaborator’s Claude Code, Codex, or Gemini session interprets changes through its own private context. A deterministic CLI handles rendering, section-level diffs, intent notes, handoffs, status, and Git-based sharing, while thin agent shims translate conversation into commands. It is asynchronous rather than real-time and expects Node 20+, GitHub repositories, and Vercel for published views.

Urd activates when an agent moves from a plan or design into implementation and encounters an uncovered edge case, contradiction, unsanctioned fallback, weakened test, or uncertain workaround. It prompts the agent to explain the exact step, quote the relevant specification, describe the gap, present options, and recommend a choice while separating verified facts from beliefs. This is a behavioral guardrail rather than a runtime guarantee, and it deliberately trades extra clarification rounds for fewer silent deviations.

compbio-pi gives Claude Code an opinionated decision framework for routine computational-biology work, answering with a decision, reason, and next step instead of a menu of options. It favors simple baselines, reproducibility, interpretability, targeted ablations, and reviewer-style stress tests. The skill still asks the researcher before changing a core scientific claim or journal tier, purchasing new data or compute, seeking collaborators, or handling ethics and data agreements.

CLI Trainer guides a no-code fine-tuning run on Baidu AI Studio. It lists allowed models, checks dataset formats, recommends framework-specific hyperparameters, submits the job, polls its status, opens TensorBoard when available, and summarizes loss and artifact usability. It supports ERNIE through PaddleFormers and several open models through LlamaFactory, but requires Python, requests, an AI Studio access token, and network access to the training service.

Find What You Live By uses guided conversation to help someone derive personal principles from meaningful life experiences rather than adopting a generic list. Each principle is translated into observable behavior, and the skill is designed to preserve the user’s own language and agency. A quiet 30–60 minute session suits reflective work, but the project explicitly excludes acute crises, severe trauma, active psychiatric symptoms, and uncontrolled addiction.

Playing to Win applies Roger Martin and A.G. Lafley’s choice cascade to an idea, offer, codebase, or market move. It gathers context, labels claims as fact, inference, assumption, or speculation, tests the winning aspiration, where-to-play and how-to-win choices, and ends with one of five verdicts. Each run writes an offline interactive HTML page plus Markdown, with assumptions highlighted for follow-up validation.

Specdd turns a vague feature request into a tech-free specification and short plan before implementation. It scales the workflow from a small Quick change to a Feature or Project, asks only missing questions, and runs a production checklist for states, accessibility, keyboard use, mobile behavior, and observability. It works with coding agents that can read skill instructions and needs no dedicated CLI.

personal-brand-ops starts by identifying an audience-size stage, then routes founders, creators, or media operators to relevant frameworks and fillable worksheets. It covers positioning, content cadence and distribution, hiring, team structure, and monetization without giving the same playbook to every account size. The methodology is deliberately opinionated and does not cover paid acquisition, SEO, or visual design, so those areas need separate tools.