gavishap
- 17 skills
- 0 followers
- 6 hours ago last updated
- ▌ Relay · gavishapHand work between Claude Code and Codex (or any two agents) with zero copy-paste, via the _relay/STATE.md baton. Use at the start of a session ("catch up", "resume", "where were we") and at the end ("save", "hand off", "wrap up"), or whenever the user says they're switching agents.
- ▌ Taste · gavishap bundleAnti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
- ▌ Council · gavishapConvene a cross-model council on a hard decision — five seats, each filled by ONE real agent (some Codex, some Claude), giving independent opinions that are anonymized, cross-reviewed by the opposite bench, and synthesized into a ruled verdict. Use when the user says "council this", "convene the council", "get multiple perspectives on this", "I'm torn between X and Y", "which option should we pick", "pressure-test this decision", or faces a genuinely uncertain, expensive-if-wrong choice (pricing, positioning, pivot, architecture direction, build-vs-buy). NOT for questions with one right answer, creation tasks, or code review (that's `sparring`). The war-room is the plan; the council is who you ask before changing it.
- ▌ Graphify · gavishap bundleUse for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
- ▌ Sparring · gavishapThe relay's synchronous mode — make Claude and Codex argue BEFORE you build, inside one session, with zero copy-paste. Four phases — SCOUT (recon from the vault's layered memory), LOCK (interrogate the user until intent is locked), SPAR (the rival model attacks the plan in bounded rounds, read-only), SHIP (one model builds, the other grades the diff, then the argument is compiled into the Wiki). Use when the user says "/spar", "spar this", "have codex review this plan", "argue this with codex", "cross-model review", "stress-test this plan", "codex build this", "have the models fight", or is about to build something high-stakes (auth, schema, migrations, concurrency, payments, greenfield architecture). NOT for trivial changes, and not a substitute for the async relay baton (that's the `relay` skill).
- ▌ War Room · gavishapBuild and maintain the project's living plan (the Plan/ folder — roadmap, phases, toolbox), and triage every new meeting or video AGAINST that plan. Use when the user says "/roadmap", "build a plan for this project", "plan before we execute", "here's a video — is this worth using?", "does this change our plan?", "/intel", "incorporate this into the plan", "new technique we should consider", "add this tool to the project", or drops a YouTube link asking whether/how it affects the project. The plan-aware answer to "should we use this?" — not just "what does the video say?".
- ▌ Humanizer · gavishap bundleRemove 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. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases.
- ▌ Video Ingest · gavishapTurn a video or audio recording — a local file OR a URL (YouTube, TikTok, Instagram, ...) — into vault knowledge using the crv (claude-real-video) CLI. Scene-aware keyframes + a Whisper transcript, frames correlated to what's being said, compiled into Raw source + Wiki notes with screenshots. Use when the user points at a recording, a meeting, a screen capture, or a reference video and wants it watched, transcribed, analyzed, or added to the vault.
- ▌ Github Pr API · gavishapOpen, list, and update GitHub pull requests (and other GitHub API operations) from a machine with no gh CLI, using the token already stored in the git credential manager. Use whenever a PR needs to be created, checked, or edited and `gh` is not installed, or any GitHub REST call is needed.
- ▌ LLM Wiki Lint · gavishapValidate Wiki and source note health. Use before commits, after ingests, or when notes were edited by hand.
- ▌ UI UX Pro Max · gavishap bundleUI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation. Searchable local data: 79 searchable styles (50 active), 192 product palettes and reasoning profiles, 74 font pairings, 119 UX guidelines, 105 icons, 17 GSAP presets, 25 chart types, and 22 stacks.
- ▌ Import Project · gavishapAdopt an EXISTING project — codebases, recordings, documents, loose notes — into this Omnia Vault. Use when the user says "import my project", "bring in this repo", "build the vault from what we already have", or drops folders/files into the vault root and wants them wired into the knowledge system.
- ▌ LLM Wiki Query · gavishapAnswer questions from the compiled Wiki. Use whenever the user asks a knowledge question that this vault might cover.
- ▌ LLM Wiki Ingest · gavishapCompile a Raw source into concise, linked Wiki notes. Use when a new source lands in Raw/Sources/ or when a source is marked Processed:false.
- ▌ LLM Wiki Maintain · gavishapRoutine maintenance and safe commits. Use when committing changes, rebuilding indexes, or checking overall vault health.
- ▌ Project Context Query · gavishapAnswer questions about the project using the vault's layered memory — Graphify code graphs, the compiled LLM Wiki, then raw files — instead of re-reading code or transcripts. Use for any question about the project, the codebase, the process, the people, or past decisions.
- ▌ Stakeholder Update Writing · gavishapStyle rules for outward-facing deliverables — client/team chat messages, status reports, results write-ups, meeting follow-ups. Use whenever drafting an update, delivery message, or report that people outside this chat will read.