Recently active skills
Trending is calculated from star growth this site has recorded itself. No history is estimated or back-filled.
Not enough history yet: 2 of 7 days recorded. Until then this list is ordered by the most recent content change.
71602 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| setupgrijalva10/oc-seller-finderFirst-time setup of OC Seller Finder on Steve's computer. Use when Steve says "set up", "get started", "install", or when settings.toml has no name under [me]. | Stars: 1 | Updated | Claude CodeCodex | Verified | Install |
| systematic-debugginggrijalva10/oc-seller-finderUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 1 | Updated | Claude CodeCodex | Verified | Install |
| undogrijalva10/oc-seller-finderSafely undo changes or go back to an earlier version of the code. Use when Steve says undo, go back, revert, "it was working before", or "I broke it". | Stars: 1 | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completiongrijalva10/oc-seller-finderUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 1 | Updated | Claude CodeCodex | Verified | Install |
| write-emailsgrijalva10/oc-seller-finderWrite personal emails to the owners of Steve's top homes and save them as Gmail drafts for him to review and send. Use when Steve asks to write, draft or prepare emails or outreach. | Stars: 1 | Updated | Claude CodeCodex | Verified | Install |
| vibe-acceptance-gateash1794/vibe-engineeringValidates completed work against defined acceptance criteria. Use after completing a task that has specific success criteria defined in issues, specs, or task descriptions. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-adversarial-test-generationash1794/vibe-engineeringGenerates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests. Use after happy-path tests exist and before claiming coverage is complete, when requirements lack tests, or before a security review. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-anti-rationalization-checkash1794/vibe-engineeringCatches shortcuts and reward hacking — weakening or deleting tests to make them pass, hard-coding expected outputs, silently dropping requirements, or claiming work is done without running it. Use before declaring a task complete and whenever a test or requirement feels like it's in the way. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-cherry-pick-integrationash1794/vibe-engineeringSafely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-concurrent-test-safetyash1794/vibe-engineeringAudits tests for concurrency safety — race conditions, shared mock state, cleanup ordering. Use when writing tests that involve goroutines, async operations, or shared mutable state. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-coverage-enforcerash1794/vibe-engineeringEnforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Use before claiming code is complete. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-decision-journalash1794/vibe-engineeringExtracts and records architectural decisions from diffs, conversation context, and explicit choices. Supports automatic extraction from staged changes, deduplication against prior decisions, and persistent ADR-format logging with spec traceability. Use after a significant design or architecture choice, before committing a diff that embeds implicit decisions, or when the same question keeps resurfacing. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-devil-advocate-reviewash1794/vibe-engineeringChallenges a recommendation, design, large change, or any artifact submitted for hard review (spec, proposal, policy, plan) across 5 dimensions (consistency, completeness, actionability, alignment, risk), from the standards of a named senior expert in the artifact's domain and ideally from a fresh context or a different model. Searches assuming defects exist and reports only those that survive evidence. Panel mode runs several independent lenses in parallel on a release candidate, verifies every finding against the current head, and routes confirmed ones to file owners. Use before shipping a significant recommendation, design, large branch, or multi-agent release, or when asked to tear something apart, be brutally honest, or poke holes in it. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-doc-quality-gateash1794/vibe-engineeringPerforms a fast 6-point quality check for technical documents (specs, design docs, READMEs). Use after editing any specification or design document. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-flake-root-causeash1794/vibe-engineeringRefuses "flaky" as a diagnosis. Turns an intermittent failure into a reproduction by isolating it from the environment, naming the variable that controls it, forcing that variable, and measuring before and after with enough runs to count. Separates real defects from environment contention with evidence, and never retries to green or widens a threshold. Use when a test, performance check, or deploy step fails intermittently or passes on rerun. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-fuzz-parser-inputsash1794/vibe-engineeringGenerates fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input). Seeds corpus from existing fixtures and runs initial pass. Use when implementing or changing a parser, or any code that ingests user input, webhook payloads, API responses, or file formats. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-gap-analysisash1794/vibe-engineeringAssesses production readiness or audits a codebase against its specs. Supports quick static mode, deep 17-dimension audit, or single-dimension focus. Use before a production launch, after a major refactor, when inheriting a codebase, or when someone asks how done the project is. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-gap-closure-loopash1794/vibe-engineeringCloses a large backlog of findings (a gap analysis, an audit, or 10+ bugs) in prioritized waves. Loops through triage, dependency analysis, parallel fix streams, a test gate, and re-audit until the target is met. Use after a gap analysis, audit, or review produces 10+ findings, or to burn down a large bug or tech-debt backlog. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-golden-file-testingash1794/vibe-engineeringImplements snapshot/golden file tests with temporal normalization so tests don't break daily. Use when implementing tests that compare output against expected snapshots. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-handover-docash1794/vibe-engineeringWrites a handover document so another person, another agent, or a different tool can pick up multi-session work cold. Use when handing work to someone else, switching tools, or pausing work that will not resume in the same session. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-helpash1794/vibe-engineeringRoutes to the right vibe-engineering skill for the current task and lists the full catalog. Use when the user asks which skill to use, asks what vibe-engineering can do, or is unsure how to approach a task. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-iteration-reviewash1794/vibe-engineeringPerforms end-of-iteration review with quality grading, metrics, and trend analysis. Use at the end of each development iteration or sprint. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-parallel-task-decompositionash1794/vibe-engineeringAnalyzes large tasks for independent subtasks that can be safely parallelized. Produces a DAG-based dispatch plan with dependency ordering and maximum parallelism. Use when a task has 5+ subtasks touching independent files, or the user asks to speed up or parallelize the work. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-pre-commit-auditash1794/vibe-engineeringScans staged changes for secrets, debug statements, TODOs without references, and other common commit mistakes. Use before creating any commit. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-production-mindsetash1794/vibe-engineeringChecks production-bound code for observability, error handling at system boundaries, input validation, graceful degradation, and resource management, scaled to the project's real stakes. Use before declaring a production feature done. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-publication-leak-guardash1794/vibe-engineeringKeeps private and unapproved material out of a public build. Scans the built output (HTML, serialized component payloads, client JS and CSS chunks, static data routes, public files) against a private tier that always applies and a draft tier that applies in production. Gates work-in-progress so it shows in preview and is absent from production, and keeps sign-off in a ledger only the human writes. Use when a site or app publishes content that agents drafted or that came from private sources. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-quality-loopash1794/vibe-engineeringRuns the Implement→Review→Test→Fix cycle until the work is actually clean, with evidence. Use after any non-trivial implementation and before claiming it is done. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-reflect-and-compoundash1794/vibe-engineeringCaptures reusable knowledge after work is done — learnings from feedback or failures, resolved bugs (symptom, root cause, prevention), and recurring code patterns — into the project's persistent memory file. Use after feedback, a non-trivial bug fix, a failed attempt, or the third repetition of a pattern. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-requirements-validatorash1794/vibe-engineeringValidates PRD, user stories, or feature requirements against SMART criteria. Use when reviewing requirements to catch vagueness before it causes expensive rework. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |
| vibe-research-before-designash1794/vibe-engineeringResearches real projects, papers, and documented failures before proposing a new feature, architecture, or technology choice. Use for design decisions with multiple valid approaches, not for implementing an existing spec or fixing a known bug. | Stars: 163 | Updated | Claude CodeCodex | Verified | Install |