Explore skills
Showing 23731–23760 of 28280 skills
Closes 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.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexImplements snapshot/golden file tests with temporal normalization so tests don't break daily. Use when implementing tests that compare output against expected snapshots.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexWrites 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.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexRoutes 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.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexPerforms end-of-iteration review with quality grading, metrics, and trend analysis. Use at the end of each development iteration or sprint.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexAnalyzes 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.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexScans staged changes for secrets, debug statements, TODOs without references, and other common commit mistakes. Use before creating any commit.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexChecks 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.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexKeeps 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.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexRuns 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.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexCaptures 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.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexValidates PRD, user stories, or feature requirements against SMART criteria. Use when reviewing requirements to catch vagueness before it causes expensive rework.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexResearches 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.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexDocuments rollback procedures before making risky changes. Covers what's changing, verification steps, rollback procedures, and blast radius assessment. Use before database migrations, breaking API changes, infrastructure or DNS changes, large dependency upgrades, or any change where undo is not obvious.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexPerforms deployment with pre-flight checks, atomic replacement, post-deploy verification, provenance (proving the environment serves the exact commit you pushed), and automatic rollback. Use before any deployment to staging, preview, or production.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexGenerates a behavioral scenario acceptance matrix for comprehensive test coverage planning. Maps user scenarios to acceptance criteria with stable IDs. Use when planning test coverage for a complex feature, before a release or milestone review, or when someone asks what is tested.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexDetects and redirects scope creep during implementation — unrequested features, drive-by refactors, premature abstraction, and over-engineering. Use while implementing, especially when a change is growing beyond the original request.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexQueries all configured services for health status — uptime, restarts, errors, resources. Use when checking the health of running services.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexStrips AI-generation "smell" from prose before it ships (READMEs, docs, release notes, PR descriptions, posts, emails). Counts measurable tells first (keyword saturation, tricolons and anaphora, the "not X, it's Y" reflex, fragment-for-emphasis, bolded thesis lines, listicle-ization, signpost phrases, filler vocabulary, em-dashes, engineered-quotable closers), then applies a "doing work or reflex?" test to each instance so genuine voice survives. Use when asked to de-slop text or make it sound human, when text reads as machine-written, and as the final pass on prose the agent drafted.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexKeeps specification documents and code in agreement. Audit mode finds every divergence when an implementation is claimed complete; sync mode detects spec drift in staged changes and updates the spec after user approval, so each commit is a reconciled snapshot of spec, tests, and code. Use when an implementation is claimed complete against a spec, before committing changes that may drift from the spec, or after approving decisions that must flow back into it.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexRuns a multi-phase project from an orchestrating main thread that plans, routes and verifies but does not build. Defines a few long-lived workstreams, each owning a file area end to end in its own worktree, and routes every follow-up to the owning agent instead of spawning a one-off. Covers base-SHA recording, rebase-before-commit, stale-checkout detection, and shared-machine hygiene (ports, processes, measurement noise). Use when a project spans several phases or sessions with three or more agents working at once.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexReconstruct research-figure images as editable Figma artwork or native PowerPoint figures. Draw, inspect actual previews and correct differences; works without a generation prompt or VLM API.
sidiangongyuan/paper-figure-to-figma
Stars: 163Claude CodeCodex使用外部视觉服务或本地 OCR 分析本地图片、截图、视频及明确提供的媒体 URL,输出 Markdown。用户明确要求 see,或当前主模型缺少完成媒体分析所需的视觉能力时使用。不拦截普通文本、任意 URL 或已有原生视觉可以直接完成的任务;不用于生图、编辑图片或自动操作屏幕。使用外部服务前说明发送的媒体与服务范围,无法识别时如实说明限制。
oil-oil/see-skill
Stars: 162Claude CodeCodexTurn rich agent answers and any file, folder, URL, or export into a polished single-file HTML page. Auto-picks a default route plus 17 concrete design systems (teaching, dashboard, atlas, timeline-story, document, …).
clockless-org/html-anything
Stars: 162Claude CodeCodex在 Codex App 中为复杂、可并行的知识工作或编程任务自动创建多个可指定模型与推理强度的后台任务,由主 Agent 负责规划、分工、集成和验收。用于多来源调研、多章节内容、复杂 Skill/PPT、跨模块开发、独立验证或 2 个以上互不依赖工作流;也用于用户明确要求模型路由、后台 Worker、Agents Team 或持久项目协作。简单问答、状态查询、单文件小改、强顺序任务和发布/付款/删除/账户操作不得自动触发。
zjp1997720/codex-model-routing-team
Stars: 160Claude CodeCodexOrder a private phone number in any country over the API, receive the SMS verification code, and hand the number back. Use when an agent has to pass a phone check during signup, login or account recovery, or needs a TOTP second factor computed locally.
sv-number/skills
Stars: 157Claude CodeCodexUse when an existing repository contains agents, prompts, workflows, playbooks, commands, or Skills and you need to identify which capabilities are worth converting into a ChatGPT/Codex Plugin.
imMamdouhaboammar/chatgpt-codex-plugin-autopilot
Stars: 155Claude CodeCodexUse when converting an agentic repository into a ChatGPT/Codex Plugin or when building, repairing, validating, packaging, submitting, publishing, or auditing an existing Plugin.
imMamdouhaboammar/chatgpt-codex-plugin-autopilot
Stars: 155Claude CodeCodexUse when a ChatGPT/Codex Plugin workflow needs to inspect, search, modify, or verify files in the host workspace using the safest native tools available.
imMamdouhaboammar/chatgpt-codex-plugin-autopilot
Stars: 155Claude CodeCodexUse when a ChatGPT/Codex Plugin needs a production-ready visual identity and SVG logo system that clearly expresses the Plugin's job across light and dark surfaces.
imMamdouhaboammar/chatgpt-codex-plugin-autopilot
Stars: 155Claude CodeCodex