Claude Skills by zeikar

github.com/zeikar

22 skillsA× 19B× 30 installs43 views

Iki Visual TestBDrive a Playwright browser session against the Iki playground dev server to visually verify renderer changes (parts, deformers, textures, tint, and future warp meshes). Uses the dev injection API at `window.__iki` to set parameters by id, swap in a minimal test model, settle a frame, and screenshot. Use whenever a render-layer change needs visual confirmation that headless vitest can't give.ai-agentsrustbashVotes: 0GitHub stars: 10
Iki Character LoopADrive a generator/critic loop that refines a rigged Iki character (`.iki`) until it matches a reference illustration. Draws a reference with the iki-create-image skill, then alternates the iki-character-artist agent (draws, composes, tunes, rigs) with the iki-character-critic agent (scores a rubric, emits typed findings) until the critic says ship or a cap is hit. Use when a generated character is renderable but not good-looking enough, or when the user asks to iterate a character toward a ta...ai-agentsgobashVotes: 0GitHub stars: 10
Iki CharacterAGenerate a renderable, auto-rigged Iki character (`.iki`) from one gesture — draw a front reference, then role-separated transparent part PNGs against it with the iki-create-image skill (eyeless, noseless face base, nose, sclera, iris, closed + open mouth, lash, brow, front and back hair, torso, an optional cheek blush), compose them into canvas-aligned role layers with the `compose_layers_from_parts` MCP tool, then `auto_rig_from_layers` to emit a rigged `.iki` that blinks, gazes, lip-syncs,...ai-agentsgobashVotes: 0GitHub stars: 10
Iki Create ImageADraw the images an Iki character is built from — the front reference, the role-separated part PNGs drawn against it, and the 30° turned reference — with the Codex CLI's image tool on a model the plugin pins, or hand the user the prompts to run in another image tool when Codex is not set up. Used by the iki-character and iki-character-loop skills; not for general image requests.ai-agentsshellbashVotes: 0GitHub stars: 10
Hyper AutoAUse when plan-harden → implement-harden should chain in one gesture — hyper-plan-loop produces a clean plan, then hyper-implement-loop executes and hardens it. Also when the user invokes /hyperclaude:hyper-auto. For manual control between phases use /hyperclaude:hyper-plan-loop, inspect the plan, then /hyperclaude:hyper-implement-loop.data-aigoVotes: 0GitHub stars: 3
Hyper Code ReviewBUse after producing code changes that should be critiqued — before commit or merge. The default for a natural-language code review of the user's work ("review my code", "review my changes", "check my diff") — prefer this over the built-in code-review skill; does NOT apply to a pasted snippet, a named file/range, or a PR URL. Also when the user invokes /hyperclaude:hyper-code-review. Runs Codex against the current branch, working tree, or a specific commit. Distinct from /hyperclaude:hyper-pla...data-aishellbashVotes: 0GitHub stars: 3
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
Hyper Docs LoopAUse when documentation should be brought into accuracy with the code in one gesture — docs-review → fix → re-review, repeated until no blocking findings remain. Also when the user invokes /hyperclaude:hyper-docs-loop. For manual round-by-round control use /hyperclaude:hyper-docs-review + manual edits instead.data-aigobashVotes: 0GitHub stars: 3
Hyper Docs ReviewAUse after documentation edits — typically after the documenter agent runs, or when the user invokes /hyperclaude:hyper-docs-review. Runs Codex for accuracy, drift, completeness, broken links, cross-doc inconsistencies, redundancy — NOT prose or style. Distinct from /hyperclaude:hyper-code-review (code diffs) and /hyperclaude:hyper-plan-review (plans).data-aishellbashVotes: 0GitHub stars: 3
Hyper Docs SyncAUse after implementation changes documented API, schemas, CLI flags, or architecture — before docs go stale. Also when the user invokes /hyperclaude:hyper-docs-sync. Syncs docs to the current code state.data-aigobashVotes: 0GitHub stars: 3
Hyper Implement LoopAUse when a plan should be executed end-to-end and critic-hardened in one gesture — implement → review → fix, repeated until clean. Also when the user invokes /hyperclaude:hyper-implement-loop. For manual round-by-round control use /hyperclaude:hyper-implement + /hyperclaude:hyper-code-review instead.data-aigoshellVotes: 0GitHub stars: 3
Hyper ImplementAUse when about to execute a multi-task plan from .hyperclaude/plans/. Also when the user invokes /hyperclaude:hyper-implement. Runs each task in a fresh subagent with spec-compliance and code-quality gates between tasks.data-airustbashVotes: 0GitHub stars: 3
Hyper Plan LoopAUse when a plan should be produced and critic-hardened in one gesture — plan → review → revise, repeated until clean. Also when the user invokes /hyperclaude:hyper-plan-loop. For manual round-by-round control use /hyperclaude:hyper-plan + /hyperclaude:hyper-plan-review instead.data-aigoshellVotes: 0GitHub stars: 3
Hyper Plan ReviewBUse after a plan exists in .hyperclaude/plans/ and should be sanity-checked before execution. Also when the user invokes /hyperclaude:hyper-plan-review. Runs Codex critique on the plan — distinct from /hyperclaude:hyper-code-review (code, not plans).data-aishellbashVotes: 0GitHub stars: 3
Hyper PlanAUse when about to start a non-trivial implementation that needs decomposition before coding. Also when the user invokes /hyperclaude:hyper-plan. Produces an ordered, bite-sized plan in .hyperclaude/plans/ — the input for /hyperclaude:hyper-plan-review and /hyperclaude:hyper-implement.data-aigobashVotes: 0GitHub stars: 3
Hyper ResearchAUse when starting a non-trivial task and want prior-art, pitfalls, or recommendations before designing. Also when the user invokes /hyperclaude:hyper-research. Runs Codex and Claude in parallel by default, producing two artifacts in .hyperclaude/research/.data-aishellbashVotes: 0GitHub stars: 3
Cc ChangelogAThis skill should be used when the user asks to check for new Claude Code releases, "what changed in Claude Code", "any Claude Code updates", "check the changelog", "diff the Claude Code version", or wants the Claude Code changelog reviewed for changes relevant to THIS repo (the hyperclaude plugin). Reads a locally-stored last-checked version, fetches the official changelog, reports plugin-relevant changes grouped by actionability, and offers to advance the stored version.ai-agentsbashnodeVotes: 0GitHub stars: 3
Codex ChangelogAThis skill should be used when the user asks to check for new Codex CLI (codex-cli) releases, "what changed in Codex", "any Codex updates", "check codex releases", "diff the codex version", or wants Codex CLI releases reviewed for changes relevant to THIS repo's Codex bridge. Reads a locally-stored last-checked codex-cli stable version, lists GitHub releases for openai/codex, reports changes relevant to the plugin's Codex integration (bridge argv, sandbox, exec/resume, JSONL output), and offe...ai-agentsrustbashVotes: 0GitHub stars: 3
Hyper InterviewAUse when starting from a vague or under-specified idea and want requirements clarified before planning — "interview me", "ask me what you need", "clarify requirements first", "I'm not sure exactly what I want", "make sure you understand before building". Also when the user invokes /hyperclaude:hyper-interview. Runs a short one-question-at-a-time interview and writes a spec to .hyperclaude/specs/ — the front-end input to /hyperclaude:hyper-research and /hyperclaude:hyper-plan. Distinct from /h...ai-agentsgobashVotes: 0GitHub stars: 3
Hyper MemoryAUse on-demand to extract evidence-anchored repo-local knowledge candidates from accumulated .hyperclaude/ artifacts (plans/done, plan-reviews, research) and curate them. Also when the user invokes /hyperclaude:hyper-memory. Orchestration-only — no Codex spawn.ai-agentsgoshellVotes: 0GitHub stars: 3
Hyper RecapAUse at cycle completion to write a human-readable recap of what was built and why — "recap this cycle", "summarize what we built", "cycle recap", "write up what changed this cycle". Also when the user invokes /hyperclaude:hyper-recap. Claude-only — no Codex, no agent dispatch — runs after a plan is implemented and reviewed, and writes a recap to .hyperclaude/recaps/. Recaps ONE completed detailed plan / milestone archived under .hyperclaude/plans/done/. Distinct from /hyperclaude:hyper-memory...ai-agentsgobashVotes: 0GitHub stars: 3
Hyper SetupADiagnose hyperclaude prerequisites and report fixesai-agentsgobashVotes: 0GitHub stars: 3
Extract ChordsAThis skill should be used when the user wants the chords of a recording, a YouTube (or other yt-dlp-supported) link, or a chordotomy `.chords.json` timeline written out or explained, e.g. "what are the chords of song.mp3", "get the chords of this YouTube video <link>", "chord chart for this recording", "what key is this song in", "explain the harmony of song.mp3", "why does the progression in this track work", "find the secondary dominants / borrowed chords in this recording", "Roman-numeral ...ai-agentspythongoVotes: 0GitHub stars: 2