All authors
Claude Skills by 2389-research
github.com/2389-research24 skills0 installs26 views
- Authoring Motion DiagramsUse when adding a plugin to the marketplace, or when authoring, editing, or re-rendering a scene under scripts/animations/scenes/ — including when a scene fails the render contract, the contrast gate, or the grid baseline.Votes: 0GitHub stars: 95
- Binary ReAnalyzes ELF binaries, executables, and firmware images to understand behavior without source code; coordinates sub-skills binary-re:triage, binary-re:static-analysis, binary-re:dynamic-analysis, binary-re:synthesis, and binary-re:tool-setup. Use when working with a binary, executable, or ELF file; asked to reverse engineer, disassemble, decompile, or figure out what something does; targeting ARM64, ARMv7, x86_64, or MIPS; or analyzing Python bytecode (.pyc, marshal). For Python bytecode anal...Votes: 0GitHub stars: 18
- Dynamic AnalysisObserves runtime behavior of binaries via QEMU emulation, GDB debugging, and Frida hooking — syscall tracing, breakpoints, memory inspection, and function interception. Use when running, tracing, or debugging a binary, verifying hypotheses from static analysis, or watching actual syscalls, network calls, or file access; requires human approval before any execution.Votes: 0GitHub stars: 18
- Static AnalysisPerforms static analysis of binary code using radare2 and Ghidra — function enumeration, cross-reference tracing, decompilation, and control flow graphs without executing the binary. Use when disassembling or decompiling code, mapping functions, tracing data flow, or building hypotheses before dynamic verification.Votes: 0GitHub stars: 18
- SynthesisCompiles binary analysis findings into structured reports — correlates facts from triage, static, and dynamic phases, validates hypotheses against evidence, and produces traceable documentation. Use when ready to summarize findings, generate a report, document what a binary does, or prepare results for handoff or archival.Votes: 0GitHub stars: 18
- Tool SetupInstalls and configures reverse engineering tools including radare2, Ghidra, GDB, QEMU, Frida, and cross-compilation toolchains for ARM64, ARMv7, x86_64, and MIPS. Use when a tool command fails, a required tool is missing, or you need to set up a fresh analysis environment.Votes: 0GitHub stars: 18
- TriageFingerprints unknown binaries using rabin2 — detects architecture (ARM, x86, MIPS), ABI, libc, dependencies, and strings of interest. Use when first encountering an unknown binary, ELF file, or firmware blob, or when you need architecture or ABI information before committing to deeper analysis.Votes: 0GitHub stars: 18
- CcvaultUse when searching past conversations, recalling previous solutions, understanding project history, or needing context from earlier sessions - proactive conversation history mining via ccvault MCP serverVotes: 0GitHub stars: 10
- ClearnessConvenes a clearness committee of specialized perspectives to examine a question with distributed depth rather than single-context breadth. Use when a topic spans multiple domains and deserves thorough parallel analysis — complex code reviews, architecture decisions, or multi-dimensional research.Votes: 0GitHub stars: 6
- DeliberationStructured deliberation support for decisions worth sitting with — ethical questions, architecture choices, trade-offs, decisions where the user wants clarity rather than a handed-down conclusion. Use when a question deserves genuine discernment; may involve clearness, discernment, or gathered depending on the situation.Votes: 0GitHub stars: 6
- DiscernmentRuns structured internal deliberation before answering, surfacing multiple perspectives and naming tensions rather than jumping to a single conclusion. Use when a question carries ethical weight, has multiple valid approaches, involves significant trade-offs, or risks harm.Votes: 0GitHub stars: 6
- GatheredFacilitates participatory discernment where the user contributes their own voice alongside agent perspectives, finding clarity together rather than receiving analysis. Use when the user has a stake or position in a decision and wants to participate — signaled by phrases like "I'm torn," "I've been thinking about this," or "I don't just want your opinion."Votes: 0GitHub stars: 6
- CookoffRuns parallel implementation competition at the design→implementation transition: dispatches 2-5 agents that each create their own plan from the shared design, then tests and the judge pick the winner. Use when design is complete and implementation is about to start — "let's build", "implement this", "looks good let's code", "ready to implement", or after a design doc is committed.Votes: 0GitHub stars: 4
- JudgeScoring framework for test-kitchen cookoff and omakase-off. Invoked at Phase 4 to evaluate implementations using 5-criteria scoring. Do not invoke directly — called by `test-kitchen:cookoff` and `test-kitchen:omakase-off`.Votes: 0GitHub stars: 4
- Omakase OffIntercepts build/create/implement requests as an entry gate and offers a choice between brainstorming together or omakase (chef's choice parallel design exploration across 3-5 approaches), then dispatches parallel agents and lets tests pick the winner. Use on any "build X", "create Y", "implement Z", "add feature", or indecision signal ("not sure which approach", "try both") — this skill intercepts all such requests to ensure design exploration is offered before implementation begins.Votes: 0GitHub stars: 4
- Test KitchenIntercepts any build/create/implement request and routes to omakase-off (parallel design exploration entry gate) or cookoff (parallel implementation competition exit gate), letting tests pick the winner. Use on any "build X", "create Y", "implement Z", "try both approaches", or "compare implementations" request — this is an aggressive entry gate that intercepts all such requests to offer design exploration and parallel implementation options.Votes: 0GitHub stars: 4
- Git Repo PrepRoutes between prepare (full lifecycle) and review (standalone audit) for open-source release workflows. Use when making a repo public, open-sourcing a project, auditing for secrets or missing documentation, preparing for public release, or reviewing a repo for openness.Votes: 0GitHub stars: 2
- PrepareAudits and prepares a codebase for public or open-source release through 9 interactive phases covering secrets, license, documentation, gitignore, hardening, and metadata. Use when releasing a private or internal repository publicly or open-sourcing a project. For a standalone read-only audit without the preparation workflow, use git-repo-prep:review.Votes: 0GitHub stars: 2
- ReviewAudits a codebase for openness across secrets, license, documentation, gitignore, CI/CD, and metadata, with severity-classified findings. Use when checking a repo for secrets, missing docs, or gaps before making it public — or at any point after preparation to validate state.Votes: 0GitHub stars: 2
- Add FeatureAdds Cloud Functions, Firestore collections, and API endpoints to existing Firebase projects using TDD. Use when adding a function, creating an endpoint, implementing a new Firestore collection, or building a feature in an existing Firebase project.Votes: 0GitHub stars: 2
- DebugSystematically troubleshoots Firebase-specific issues including emulator failures, Firestore rules violations, Cloud Functions errors, Firebase Auth problems, and Firebase deploy failures. Use when Firebase emulators won't start, Firestore returns PERMISSION_DENIED, Cloud Functions return errors, Firebase Auth fails in the emulator, or firebase deploy fails.Votes: 0GitHub stars: 2
- Firebase DevelopmentRoutes Firebase development tasks to specialized sub-skills covering project setup, feature development, debugging, and validation. Use when starting a Firebase project, adding Cloud Functions or Firestore collections, troubleshooting Firebase emulator or deployment issues, or reviewing Firebase security rules and architecture.Votes: 0GitHub stars: 2
- Project SetupInitializes new Firebase projects with TypeScript, emulators, authentication, and security rules using proven architecture patterns. Use when starting a new Firebase project, running firebase init, or setting up Firebase for the first time in a repository.Votes: 0GitHub stars: 2
- ValidateReviews Firebase projects against security best practices, architecture patterns, and production readiness checklists. Use when auditing Firebase security rules, reviewing Firebase configuration, checking Firebase project architecture, or preparing a Firebase project for production deployment.Votes: 0GitHub stars: 2