Explore skills
Showing 13771–13800 of 77076 skills
Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work, and before telling the user that something was never recorded.
michael-denyer/pstack-claude
Stars: 4.4kClaude CodeCodexFan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.
michael-denyer/pstack-claude
Stars: 4.4kClaude CodeCodexUse only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
michael-denyer/pstack-claude
Stars: 4.4kClaude CodeCodexExplain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
michael-denyer/pstack-claude
Stars: 4.4kClaude CodeCodexLayered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
michael-denyer/pstack-claude
Stars: 4.4kClaude CodeCodexRun an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
michael-denyer/pstack-claude
Stars: 4.4kClaude CodeCodexComprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch/PR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.
michael-denyer/pstack-claude
Stars: 4.4kClaude CodeCodexLaunch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for thermos, double thermo review, or combined bug/security and code-quality branch audits.
michael-denyer/pstack-claude
Stars: 4.4kClaude CodeCodexTypeScript best practices. Use when reading or editing any .ts or .tsx file.
michael-denyer/pstack-claude
Stars: 4.4kClaude CodeCodexUse for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
michael-denyer/pstack-claude
Stars: 4.4kClaude CodeCodexReview a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.
zacharyfmarion/openscad-studio
Stars: 253Claude CodeCodexUse when the user asks to take a feature or bug fix from prompt to implementation, especially prompts like "/create a new feature", "build this feature end-to-end", "take this from plan to PR", or "own this change through validation and handoff". This skill is for repo-local delivery workflows that must create and maintain implementation plans, choose appropriate tests, run deterministic validation, open a draft PR against main, and return the preview deployment URL when one is available.
zacharyfmarion/openscad-studio
Stars: 253Claude CodeCodexAdd moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful.
zacharyfmarion/openscad-studio
Stars: 253Claude CodeCodexImprove interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready.
zacharyfmarion/openscad-studio
Stars: 253Claude CodeCodexDesign or improve onboarding flows, empty states, and first-time user experiences. Helps users get started successfully and understand value quickly.
zacharyfmarion/openscad-studio
Stars: 253Claude CodeCodexImprove interface performance across loading speed, rendering, animations, images, and bundle size. Makes experiences faster and smoother.
zacharyfmarion/openscad-studio
Stars: 253Claude CodeCodexPush interfaces past conventional limits with technically ambitious implementations. Whether that's a shader, a 60fps virtual table, spring physics on a dialog, or scroll-driven reveals — make users ask "how did they do that?"
zacharyfmarion/openscad-studio
Stars: 253Claude CodeCodexCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
zacharyfmarion/openscad-studio
Stars: 253Claude CodeCodexOne-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
zacharyfmarion/openscad-studio
Stars: 253Claude CodeCodexGenerate synthetic PCB inspection images on Kubernetes with the SMT Defect Image Generation (DIG) DAG in CDF Orchestration. The DAG renders components in simulation, turns the renders into realistic golden images (sim2real), and uses AnomalyGen to add texture defects such as solder bridges, excess solder or missing components. Simulation can also render shift, tombstone and sideflip pose defects. Use it to build DIG payloads, pick a pipeline mode (full, simulation, sim2real or defect-only), check GPU readiness, follow a run, and match each defect image to its golden and simulated source. Not for running Simulation, Augmentation or AnomalyGen on their own.
NVIDIA/skills
Stars: 4kClaude CodeCodexMANDATORY for every coding agent (Claude Code, Codex, or any other) — keep this repository's documentation in sync after any change to behavior, configuration, interfaces, events, schema, or features. Use automatically at the end of change-sets that alter an env var, event type, hook or state behavior, API, schema, WebSocket message, MCP tool, CLI command, or user-facing feature, and whenever the user asks to update documentation.
hoangsonww/Claude-Code-Agent-Monitor
Stars: 1.1kClaude CodeCodexBreak down Claude Code usage by model family (Opus / Sonnet / Haiku) from the Agent Monitor dashboard — each family's share of tokens, share of cost, and the spots where an expensive model is doing cheap work. Pulls per-model token and cost splits from /api/pricing/cost, current rates from /api/pricing, fleet token totals from /api/analytics, and per-session model assignment from /api/sessions. Use when deciding model routing or whether to downshift work to a cheaper tier.
hoangsonww/Claude-Code-Agent-Monitor
Stars: 1.1kClaude CodeCodexGenerate a comprehensive session report with per-model token usage (input, output, cache_read, cache_write including compaction baselines), cost breakdown via the pricing engine, tool invocations, agent hierarchy, compaction events, API errors, turn durations, and thinking block counts. Use when reviewing a specific session or summarizing activity over a date range.
hoangsonww/Claude-Code-Agent-Monitor
Stars: 1.1kClaude CodeCodexRun a full audit of the user's Claude Code configuration via the Agent Monitor Config Explorer API: counts per surface (user vs project), duplicate or overlapping skills and subagents, hooks that run shell commands, and which surfaces are read-only vs mutable. Reads /api/cc-config/overview, /skills, /agents, /commands, /hooks, and /settings. Use when reviewing your Claude Code setup for sprawl, duplication, or risk.
hoangsonww/Claude-Code-Agent-Monitor
Stars: 1.1kClaude CodeCodexInventory hooks across the user, project, and project-local settings plus the ~/.claude/hooks scripts directory — read through the Agent Monitor Config Explorer API — and flag hooks that POST to the network or run arbitrary commands. Reads /api/cc-config/hooks and /api/cc-config/hook-scripts. Use when auditing hook safety.
hoangsonww/Claude-Code-Agent-Monitor
Stars: 1.1kClaude CodeCodexAudit the configured MCP servers (user + project scope) via the Agent Monitor Config Explorer API: transport (stdio vs http), command/args and env variable names, headers, and the source file each definition came from. Reads /api/cc-config/mcp. Use when reviewing MCP integrations for hygiene, duplication, or unexpected transports.
hoangsonww/Claude-Code-Agent-Monitor
Stars: 1.1kClaude CodeCodexInventory the installed skills and which plugins contribute them, then flag overlap with the user's own skills — read through the Agent Monitor Config Explorer API. Reads /api/cc-config/skills and /api/cc-config/plugins. Use when managing skills: deduping, deciding what to keep, or tracing a skill back to the plugin that ships it.
hoangsonww/Claude-Code-Agent-Monitor
Stars: 1.1kClaude CodeCodexReview the configured cost alert rules and the alerts currently fired on the Agent Monitor dashboard, then explain exactly what tripped and why. Uses /api/alerts (fired feed) and /api/alerts/rules (definitions). Use when checking spend alerts or asking why a cost alarm went off.
hoangsonww/Claude-Code-Agent-Monitor
Stars: 1.1kClaude CodeCodexRun a daily spend check-in against a daily budget on the Agent Monitor dashboard — today's spend vs the daily target, pace through the day, and the projected overage if the current pace holds. Uses /api/pricing/cost and /api/sessions (grouped by started_at = today). Use for a quick daily spend check-in or a morning/evening budget pulse.
hoangsonww/Claude-Code-Agent-Monitor
Stars: 1.1kClaude CodeCodexForecast Claude Code spend to the end of the week or month from the daily session trend on the Agent Monitor dashboard — moving average of daily spend × days remaining, added to spend-to-date. Uses /api/analytics daily_sessions, /api/pricing/cost, and /api/sessions for a per-day cost curve. Use when projecting cost or asking "where will my spend land".
hoangsonww/Claude-Code-Agent-Monitor
Stars: 1.1kClaude CodeCodex