Explore skills
Showing 36871–36900 of 71983 skills
Use when the user explicitly requests a grilling interview to resolve or challenge material decisions. For a written critique, review the artifact directly.
MVPavan/via
Stars: 2Claude CodeCodexUse for requested standalone HTML documents or interactive explanations when that format materially helps. Skip agent-facing files, Markdown-native deliverables, and ordinary short answers.
MVPavan/via
Stars: 2Claude CodeCodexFind evidence-backed architecture improvements within a named area or requested codebase survey.
MVPavan/via
Stars: 2Claude CodeCodexUse only for an explicitly requested council of named models or agents with a judge. Ordinary review and brainstorming do not need a council.
MVPavan/via
Stars: 2Claude CodeCodexUse for measured latency, throughput, memory or cost problems, profiling, or explicit resource targets. Skip prose optimization and speculative tuning.
MVPavan/via
Stars: 2Claude CodeCodexUse only when the user explicitly requests a perspective council or war room. Answer ordinary decisions and critique requests without a council.
MVPavan/via
Stars: 2Claude CodeCodexUse when settled work needs a durable implementation plan, dependency graph, or workstream decomposition. Skip planning ceremonies for clear bounded tasks.
MVPavan/via
Stars: 2Claude CodeCodexUse when a runnable throwaway experiment can resolve a specific design, state-model, algorithm, or UI question.
MVPavan/via
Stars: 2Claude CodeCodexUse when a decision needs multiple sources gathered and weighed. Answer a single factual lookup directly from an appropriate source.
MVPavan/via
Stars: 2Claude CodeCodexUse for material changes to trust boundaries, sensitive data, permissions, dependency execution, or untrusted inputs, and for requested security reviews.
MVPavan/via
Stars: 2Claude CodeCodexShow the current topic visually, inline in the conversation. Use when the user asks to see the shape of code, a flow, an architecture, or a change ("/show-me", "show me", "sketch it", "draw the flow", "what does the structure look like"). For a rendered standalone document, use html-artifact instead.
MVPavan/via
Stars: 2Claude CodeCodexUse when unsure which skill or command fits a task, when two seem to overlap, or when the user asks what skills or commands exist, what one does, or which to use.
MVPavan/via
Stars: 2Claude CodeCodexUse when a failure cause is unclear, an attempted fix failed, or flaky behavior needs investigation. Handle obvious localized errors with a focused reproduction and fix.
MVPavan/via
Stars: 2Claude CodeCodexTeach a concept, walk through a session, or conduct an explicitly requested ongoing course.
MVPavan/via
Stars: 2Claude CodeCodexUse for risky behavior changes, regression proof, legacy characterization, or substantive test design. Trivial test renames do not require a test-first workflow.
MVPavan/via
Stars: 2Claude CodeCodexEvaluate unevaluated beads issues and move each to an intake state — ready-for-agent, human, needs-info, backlog, or a wontfix close. Use to review what needs attention or to triage a specific issue.
MVPavan/via
Stars: 2Claude CodeCodexMap and resolve material decision dependencies across a multi-session effort.
MVPavan/via
Stars: 2Claude CodeCodexMandatory for every task in a Java codebase, including planning, implementation, debugging, refactoring, review, testing, Maven or Gradle build and dependency changes, performance or security analysis, and Java-related documentation. Detect Java projects from pom.xml, Gradle files, gradlew, or .java sources. Load before inspecting or changing the repository even when the user does not explicitly mention Java. Covers Java 21+, Spring Boot, Swing/EDT, code style, testing, security, and desktop UI.
drafael/coding-harness
Stars: 1Claude CodeCodexUse when reviewing code for security vulnerabilities, implementing authentication/authorization, handling user input, or discussing web application security. Covers OWASP Top 10:2025, ASVS 5.0, and Agentic AI security (2026).
drafael/coding-harness
Stars: 1Claude CodeCodexUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
drafael/coding-harness
Stars: 1Claude CodeCodexRender beautiful Mermaid diagrams as SVG or ASCII art using the beautiful-mermaid library. Supports 15+ themes, 5 diagram types (flowchart, sequence, state, class, ER), and ultra-fast rendering. Use this skill when: 1. User asks to "render a mermaid diagram" or provides .mmd files 2. User requests "create a flowchart/sequence diagram/state diagram" 3. User wants to "apply a theme" or "beautify a diagram" 4. User needs to "batch process multiple diagrams" 5. User mentions "ASCII diagram" or "terminal-friendly diagram" 6. User wants to visualize architecture, workflows, or data models
drafael/coding-harness
Stars: 1Claude CodeCodexAnalyze and improve test coverage. Use when reviewing coverage gaps, writing missing tests, setting up coverage tooling, or improving branch/line/statement coverage for any language or framework.
drafael/coding-harness
Stars: 1Claude CodeCodexBuild AI-powered software with TypeSafe: small units of AI intelligence you can use like programming primitives. Its System One models, including Jev, turn natural language and application state into typed judgments and probabilities that code can combine. Use when a feature needs programmable common sense, when brainstorming what AI could make possible in an app, or when an LLM prompt-and-parse step could become a structured decision. Applications include routing, ranking, extraction, verification, and interactive experiences; these are starting points, not the limits. Read live docs and cookbooks to find useful patterns and discover new combinations.
drafael/coding-harness
Stars: 1Claude CodeCodexProduction Stage 10 — on-demand rollup report of eng-flow/analytics.jsonl (time/token log) and eng-flow/findings.jsonl (bug counts), both incrementally written by other eng-flow skills. Reports per-story and per-stage totals, tokens by category, cycle time (elapsed vs. active), stage-transition gaps, review/QA rework cycles, and bug rate. Read-only; doesn't instrument itself.
m3dcodie/eng-flow
Stars: 0Claude CodeCodexProduction Stage 3 — takes a saved eng-flow spec and domain model and produces the technical design — tech stack, a tech-labeled system diagram, API contracts, quantified non-functional requirements, deployment topology, and ADRs. This is where technical decisions actually get made; Stages 1 and 2 deliberately deferred all of them here.
m3dcodie/eng-flow
Stars: 0Claude CodeCodexProduction Stage 6 — reviews an implemented diff (branch vs. base, or a specific story's commits) across five axes before it ships. Post-implementation counterpart to Stage 3.5's pre-implementation architecture review — this one reviews actual code, not a design doc.
m3dcodie/eng-flow
Stars: 0Claude CodeCodexProduction Stage 2 — takes a saved eng-flow spec and turns its named domains into a domain model, data flows, and a conceptual system diagram. No tech stack, no deployment, no API shape — that's Stage 3. Run by an "architect" persona, after eng-flow-spec, before eng-flow-architecture.
m3dcodie/eng-flow
Stars: 0Claude CodeCodexProduction Stage 3.5 — reviews a saved architecture.md against engineering-leadership judgment before it becomes epics/stories/tasks. Catches architecture problems while they're still cheap to fix (before backlog breakdown, before implementation), not a code review — no code exists yet at this point in the track.
m3dcodie/eng-flow
Stars: 0Claude CodeCodexProduction Stage 4 — turns a spec's domains and journeys, cross-checked against the architecture's system diagram, into epics and stories in a project-level backlog (not per-spec — epics/stories outlive any one spec run). Task-level breakdown is separate and on-demand, only generated per-story once the user decides to implement it.
m3dcodie/eng-flow
Stars: 0Claude CodeCodexProduction Stage 5 — implements one pending task from a story's tasks.md, one at a time, using an incremental TDD loop (implement, test, verify, commit). Terminal stage after eng-flow-epics-stories-tasks. Whole-story auto mode is not built yet — this only ever does the next single task, then stops.
m3dcodie/eng-flow
Stars: 0Claude CodeCodex