From release
Clone GitHub and git repos into a conventional local location, inspect them, and recommend the most useful next steps. Use when the user asks to clone, download, inspect, evaluate, look over, or assess a repository, especially when they want it placed under the usual owner/repo path in ~/code/github and reviewed before deeper work.
npx claudepluginhub fairchild/dotclaude --plugin skill-creatorThis skill uses the workspace's default tool permissions.
Clone repositories into a predictable location, inspect them conservatively, and turn the result into an actionable recommendation.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Clone repositories into a predictable location, inspect them conservatively, and turn the result into an actionable recommendation.
Prefer these destinations:
~/code/github/<owner>/<repo>~/code/git/<host>/<owner>/<repo>~/code/tmp/<owner>-<repo>If the user gives a different destination explicitly, follow the user's instruction.
Use this skill when the user asks for things like:
Parse the repo URL or shorthand and determine:
If the user provides GitHub shorthand like owner/repo, treat it as https://github.com/owner/repo.
If the repo already exists, inspect the existing checkout first. Fetch remote state only if useful, and do not switch branches unless the user asks.
Read the most relevant project files first:
README*AGENTS.md / CLAUDE.mdpackage.json, bun.lock, pnpm-lock.yaml, uv.lock, pyproject.toml, Cargo.toml, etc.)Detect the stack from the repo files instead of guessing.
Provide a concise summary covering:
If the repo is a catalog, awesome list, template collection, or index, also extract the entries most relevant to the user's workflow instead of only describing the catalog itself.
Give 3-5 ranked suggestions and clearly identify the single highest-leverage next step.
Prefer suggestions that help the user:
If the user explicitly asks for deeper evaluation, you may go beyond inspection and:
test, check, lint, or buildBefore expensive, stateful, or external side effects, ask for confirmation. Be conservative.
Do not deploy, publish, edit files, or commit unless the user explicitly asks.
Always include:
~/code/github/ so related repos are easy to discover and maintain.