Explore skills
Showing 65161–65190 of 71451 skills
Senior-level roofing, estimating, and operations guidance for contractors, adjusters, inspectors, and sales teams. Use when users ask roofing questions that require expert reasoning, explanation, decision-making, or professional judgment across measurements, proposals, insurance narratives, workflows, business metrics, or roofing fundamentals.
kbarbel640-del/skills
Stars: 1Claude CodeCodexA hardware-aware, hybrid (SMB + SSH) suite for ASUSTOR NAS metadata scraping. Functions as a versatile Coder, Project Manager, and System Architect while maintaining strict read-only safety and i3-10th Gen resource throttling.
kbarbel640-del/skills
Stars: 1Claude CodeCodexCreate distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
kbarbel640-del/skills
Stars: 1Claude CodeCodexMustafaKucukcoskun/Refine-agent-kit
Stars: 0Claude CodeCodexUse when working with comprehensive review full review
mateusoliveiradev1/frescari
Stars: 1Claude CodeCodexDeploy Expo apps to production
mateusoliveiradev1/frescari
Stars: 1Claude CodeCodexPragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments
MuharremTozan/Agentic-Duel
Stars: 0Claude CodeCodexHigh-fidelity universal planning orchestrator. Transmutes complex requests into structured, skill-aware roadmaps with sequential phases, dependency-aware task sequencing, embedded test procedures, and gap-free coverage enforced by targeted user questioning before any plan is saved.
MuharremTozan/Agentic-Duel
Stars: 0Claude CodeCodexUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
MuharremTozan/Agentic-Duel
Stars: 0Claude CodeCodexImplements "Composition over Inheritance" using ScriptableObject configs and C# Tuples. Replaces deep class hierarchies with modular, has-a relationships.
MuharremTozan/Agentic-Duel
Stars: 0Claude CodeCodexRobust Save/Load system using Data Binding, Serializable DTOs, and swappable Data Service backends (File/JSON default). Supports per-entity GUID identity for saving multiple actors (player, inventory, enemies).
MuharremTozan/Agentic-Duel
Stars: 0Claude CodeCodexImplements Dependency Inversion and Injection patterns. Decouples high-level logic from concrete implementations using attributes and reflection.
MuharremTozan/Agentic-Duel
Stars: 0Claude CodeCodexImplementation of Model-View-Controller (MVC) and Model-View-Presenter (MVP) patterns in Unity. Focuses on Separation of Concerns for scalable UI and game systems.
MuharremTozan/Agentic-Duel
Stars: 0Claude CodeCodexReactive Property system for Unity. Decouples data from UI and logic using observable wrappers and UnityEvents.
MuharremTozan/Agentic-Duel
Stars: 0Claude CodeCodexImplementation of global manager access with strict lifecycle control. Supports Standard, Persistent, and Regulator variations.
MuharremTozan/Agentic-Duel
Stars: 0Claude CodeCodexManages the structured relationship between ScriptableObjects (Data) and Prefabs (Logic/Visuals) in Unity 6. Follows the 'SO-to-Mono' Bridge pattern to ensure instance independence (e.g., individual health for identical robots) while maintaining a clean, data-driven architecture. Use when: (1) Creating new unit/item types, (2) Wiring SO data to Prefab MonoBehaviours, (3) Resolving data-sharing bugs where changing one SO affects all instances.
MuharremTozan/Agentic-Duel
Stars: 0Claude CodeCodexImplementation of MVVM-style Data Binding for Unity UI Toolkit using the [CreateProperty] attribute and BindableProperty wrappers.
MuharremTozan/Agentic-Duel
Stars: 0Claude CodeCodexAdvanced UI construction using C# code instead of UI Builder. Includes fluent extension methods and reusable pointer manipulators.
MuharremTozan/Agentic-Duel
Stars: 0Claude CodeCodex[FILL IN: what this skill does and exactly when to use it -- the phrases a user would actually type, not just the topic]
colomet/skill-boilerplate
Stars: 0Claude CodeCodexLocal text-to-speech via sherpa-onnx (offline, no cloud)
Solizardking/clawd-bot
Stars: 0Claude CodeCodexExtract frames or short clips from videos using ffmpeg.
Solizardking/clawd-bot
Stars: 0Claude CodeCodexStart voice calls via the Clawdbot voice-call plugin.
Solizardking/clawd-bot
Stars: 0Claude CodeCodexGet current weather and forecasts (no API key required).
Solizardking/clawd-bot
Stars: 0Claude CodeCodexUse when deciding whether to run a task on the OpenCode agent runtime (the open-source, provider-agnostic coding agent — usable as a terminal TUI, a non-interactive `opencode run` CLI, an IDE bridge via ACP, a desktop app (beta), a web UI, or a headless `opencode serve` server), how to invoke it non-interactively, how to pick a `provider/model` string, or how OpenCode differs from Claude Code and Codex. Covers its 75+-provider model routing, the OpenCode Zen curated/free model service and the separate OpenCode Go subscription lane, model-selection and config-source (8-layer) precedence, the `--format json` JSONL event stream, the full CLI command surface (serve/web/attach/acp/session/stats/export/import/github/pr/plugin/mcp/db/debug), built-in build/plan agents and LSP code intelligence, permissions vs provider policies, native Agent Skills / MCP / references / commands extension layers, local models, and scripting/automation. Do NOT use when choosing WHICH free model to route specific work to (use `opencode-free-models`), when the runtime is already chosen and you only need to write the agent loop (use `autonomous-loop-patterns`), or for GitHub Copilot's premium-request economics (use `github-copilot`).
jacob-balslev/skills
Stars: 2Claude CodeCodexUse when reasoning about building language-model-integrated systems by writing evaluations before and alongside the system: the statistical (not binary) nature of LLM evals, the five primitives (dataset, evaluation function, aggregation, iteration loop, regression budget), the judgment-mechanism taxonomy (programmatic, model-graded, human-graded, preference comparison, trace/hybrid), the eval-surface stack (final response, trajectory/tool-use, retrieval/RAG, safety, side effects, cost/latency), continuous evals and model-upgrade gates, the statistical-significance discipline (paired tests, McNemar's test, bootstrap CI on the delta, minimum-detectable-effect, clustered standard errors), trajectory-vs-final-output evaluation for multi-step agents, judge calibration and bias, Goodhart's Law and suite saturation, benchmark contamination and eval-awareness, cost-aware regression budgets, the difference between system-specific evals and canonical benchmarks (MMLU, HumanEval, BIG-bench, GAIA), and the offline-eval-vs-production-telemetry distinction with its graded rollout spectrum. Do NOT use for deterministic unit testing (use testing-strategy), production monitoring (use evaluation or error-tracking), general-software TDD (use testing-strategy), or the construction of individual eval rubrics and task sets (outside this skill; construction belongs in task-specific eval artifacts, while this skill owns the iteration discipline).
jacob-balslev/skills
Stars: 2Claude CodeCodexDeciding what to cache, where, and how to keep it coherent — trading freshness for speed and load reduction across the cache layers (client, CDN/edge, application in-memory, distributed cache, database). Covers the two hard problems (cache invalidation and choosing the layer), the write/read patterns (cache-aside/lazy, read-through, write-through, write-behind, refresh-ahead), expiry and TTL design, eviction policies (LRU/LFU/FIFO/TTL), staleness budgets and tolerated inconsistency, cache coherence and invalidation strategies (TTL expiry, explicit invalidation, key/tag versioning, write-through), the thundering-herd / cache-stampede problem and its mitigations (request coalescing, locks, jitter, stale-while-revalidate), HTTP caching semantics (Cache-Control, ETag, conditional requests, stale-while-revalidate/stale-if-error), CDN and edge caching, multi-layer cache hierarchies, cache key design and cardinality, negative caching, and measuring hit ratio and the cost of a miss. Stack-agnostic across Redis/Memcached, CDNs, browser cache, and framework data caches.
jacob-balslev/skills
Stars: 2Claude CodeCodexUse when designing or reviewing Next.js Route Handlers (the `route.ts`/`route.js` file convention in App Router): when a Route Handler is the right public HTTP endpoint surface vs Server Actions or Server Components, the HTTP-method-as-export contract (GET/POST/PUT/PATCH/DELETE/HEAD/OPTIONS), the Web-standard Request/Response interface (no Node `req`/`res`), the body-parsing primitives (`request.json`/`formData`/`text`/`blob`/`arrayBuffer`) and one-shot body consumption, the default caching behavior of GET responses (NOT cached by default since Next 15; opt IN via `dynamic = 'force-static'`) and the Cache Components `use cache` model, async `params`/`cookies`/`headers` and `RouteContext` typed params, dynamic segments and search params, the rule that every Route Handler is a PUBLIC surface that must authenticate/authorize/validate inside the handler, manual CORS, runtime/deployment selection (Node default and recommended after Vercel folded standalone Edge Functions onto Vercel Functions; the Edge runtime still selectable; `maxDuration`/`preferredRegion`/static-export limits), streaming via `ReadableStream` including `pull()` backpressure, status-code and header discipline, error responses, webhook-style handlers (signature verify before parse, ACK fast, `after()` for short post-response work), and the design rule that a Route Handler is the right surface when the caller is not your own Next.js UI. Do NOT use for internal mutations triggered from your own UI (use server-actions-design), for render-time reads from your own Server Components (call the data source directly), for the broader REST/contract/versioning discipline (use api-design), for HTTP method/status semantics in the abstract (use http-semantics), for request preprocessing across all routes — now `proxy.ts`/`middleware.ts` (use middleware-patterns), or for the broader webhook reliability story — HMAC verification, idempotency, retries, queue handoff (use webhook-integration).
jacob-balslev/skills
Stars: 2Claude CodeCodexUse when reasoning about how a database schema changes over time without breaking deployed application code — the multi-release path from the current schema to a target schema: the expand/contract pattern (Ambler & Sadalage / Fowler's parallel change), the zero-downtime change rules, the backwards-and-forwards compatibility envelope (deploy ordering and rollback discipline), the catalog of schema changes (add column, drop column, rename, type change, add constraint, add index) and the safe procedure for each, the dual-write and dual-read transitions (with named source-of-truth and production consistency-check discipline) that make non-trivial changes safe, the lock-acquisition hazard (why even a metadata-only DDL needs a bounded lock-acquisition budget — Postgres lock_timeout + retry, or the engine equivalent — because lock acquisition is a FIFO queue), the cross-engine online-change mechanisms (Postgres CONCURRENTLY / NOT VALID, MySQL INSTANT/INPLACE/COPY Online DDL, gh-ost / pt-osc ghost-table cutover, Vitess/PlanetScale deploy requests and revert windows), the view-based multi-version tooling that automates expand/contract (pgroll, Reshape), the migration-lint enforcement layer (Strong Migrations, Squawk, Atlas), and the relationship between schema evolution as a design discipline and database-migration mechanics as its tooling. Do NOT use for the mechanical execution of one migration (use database-migration), schema design from scratch (use entity-relationship-modeling), query tuning (use query-optimization), or distributed-data partitioning (use sharding-strategy).
jacob-balslev/skills
Stars: 2Claude CodeCodexUse when designing or reviewing the Next.js request-preprocessing layer — the single root file that runs cross-cutting request/response transforms before route resolution. As of Next.js 16 this file is `proxy.ts` (function `proxy`, Node.js runtime, default export or named); `middleware.ts` (function `middleware`, Edge Runtime by default — Node.js opt-in since 15.5) is deprecated but retained for Edge use cases. Covers: the runtime split (proxy = Node.js, runtime config throws; middleware.ts = Edge by default with its capability ceiling, Node.js opt-in since 15.5), the `matcher` config that decides which paths it runs on, the `NextRequest`/`NextResponse` API for cookies/headers (and `geolocation()`/`ipAddress()` from `@vercel/functions` since `request.geo`/`request.ip` were removed in Next.js 15), the four response shapes (`next`/`rewrite`/`redirect`/direct response), `waitUntil` for background work, the official `next/experimental/testing/server` test utilities, the canonical patterns (auth gate, locale routing, A/B testing, header injection, geo-routing, bot blocking), the per-matched-request performance discipline, the CVE-2025-29927 lesson that this layer is NOT a security boundary, and the design rule that it is for cross-cutting concerns across many routes — never per-route business logic. Do NOT use for per-route HTTP endpoint logic (use route-handler-design), the Server Action mutation surface (use server-actions-design), abstract HTTP method/status/header semantics (use http-semantics), Content Security Policy and broader hardening (use security-fundamentals), or the cross-cutting streaming model (use streaming-architecture).
jacob-balslev/skills
Stars: 2Claude CodeCodexUse when designing or reviewing React ref usage: the distinction between refs (mutable handle that survives renders without triggering them) and state (reactive value that triggers renders when changed), the `useRef` hook for DOM access and mutable instance values, ref callbacks for fine-grained mount/unmount hooks, `forwardRef` for passing refs through component boundaries (and the React 19 ref-as-prop change that retires it for new code), `useImperativeHandle` for exposing a controlled imperative surface to parent refs, ref forwarding through compound-component primitives (the Radix `Slot` / Headless UI pattern), and the design rule that refs are an escape hatch — for DOM access, integration with non-React DOM libraries, focus management, animation, measurement, and exposing imperative APIs sparingly, never as a substitute for state. Do NOT use for the broader hook discipline — Rules of Hooks, dependency arrays, custom hooks (use hooks-patterns), for the cross-product component-layering question — primitives/composites/headless-vs-styled (use component-architecture), for state location and ownership decisions (use state-management), for the `'use client'` / `'use server'` boundary mechanics (use client-server-boundary), or for form-state and validation patterns (use form-ux-architecture).
jacob-balslev/skills
Stars: 2Claude CodeCodex