Explore skills
Showing 26491–26520 of 77104 skills
Enriches data catalog entries with automated metadata
a5c-ai/babysitter
Stars: 1.9kClaude CodeCodexSelects and configures optimal incremental model strategies
a5c-ai/babysitter
Stars: 1.9kClaude CodeCodexDesigns and optimizes One Big Table (OBT) patterns
a5c-ai/babysitter
Stars: 1.9kClaude CodeCodexDesigns optimal windowing strategies for stream processing
a5c-ai/babysitter
Stars: 1.9kClaude CodeCodexBlockchain node deployment and operations. Supports Ethereum execution and consensus clients, validator operations, node monitoring, MEV-Boost configuration, and archive node management.
a5c-ai/babysitter
Stars: 1.9kClaude CodeCodex给一个主题,产出一条黑底 MG 风格(幕底可选星点或点阵波)、有配音字幕章节进度条的科普讲解视频(中文或英文;Remotion 代码动画;时长由用户定,常用 3–5 分钟)。内含可编译模板、图元库、配音/分镜/渲染工具、风格与动效规范、多 agent 分工协议与 QC 判据,以及一条完整样片(《RAG 与知识库》)作为质量标尺。Turn any topic into a narrated motion-graphics explainer video in Chinese or English, on a black canvas with a star-field or dot-field backdrop, TTS voiceover, subtitles and a chapter progress bar, every frame drawn in code with Remotion. Use when the user asks for an explainer, educational or science-communication video about a topic, or wants an article or document turned into a video.
anbeime/skill
Stars: 9.6kClaude CodeCodexWriting, explore: mine raw fragments, no structure yet.
gentleeduck/duck-ttlog
Stars: 14Claude CodeCodexRun a deep code review across the manifold-csg crates
zmerlynn/manifold-csg
Stars: 21Claude CodeCodexPush a branch and open a PR with pre-flight checks
zmerlynn/manifold-csg
Stars: 21Claude CodeCodexRun a deep code review across the manifold-csg crates
zmerlynn/manifold-csg
Stars: 21Claude CodeCodexBest practices for polars data processing with dataframely. Covers definitions of Schema and Collection, usage of .validate() and .filter(), type hints, and testing. Use when writing or modifying code involving dataframely or polars data frames.
Quantco/dataframely
Stars: 627Claude CodeCodex分析 claude.com/blog 的新文章,提取可操作洞察並更新 workspace 設定。手動調用。
zeuikli/claude-code-workspace
Stars: 157Claude CodeCodex對 staged changes 執行三維度平行審查(安全、效能、風格),合成優先排序的發現摘要。
zeuikli/claude-code-workspace
Stars: 157Claude CodeCodexTranslate a confirmed mini-program product specification or bounded feature into an implementable architecture covering modules, pages, components, services, canonical state sources, data models, interfaces, permissions, failures, caching, concurrency, idempotency, migration, rollback, external dependencies, and architecture decision records. Use when users ask how to structure a mini program, design data or APIs, divide frontend and cloud responsibilities, evolve an existing system safely, or prepare implementation after product semantics are stable. Preserves product meaning, current repository constraints, user-owned changes, and verifiable acceptance behavior rather than redesigning the product for technical convenience.
NocodeMrLi/mini-program-engineering-skill-suite
Stars: 101Claude CodeCodexDiagnose and fix mini-program failures through reproducible, evidence-driven root-cause analysis across source, state, asynchronous timing, caches, mock data, build versions, platform behavior, devices, cloud calls, and external services. Use when users report white screens, crashes, stale or jumping values, missing data, intermittent behavior, permission failures, performance stalls, device-only defects, API or cloud-function errors, source-versus-build mismatches, or regressions whose cause is not yet established. Freezes the observation environment, ranks competing hypotheses, runs discriminating checks, creates a failing regression test before repair, covers analogous states, and never hides a known failure with longer waits, swallowed errors, forced success, or cosmetic patches.
NocodeMrLi/mini-program-engineering-skill-suite
Stars: 101Claude CodeCodexImplement bounded features and fixes in existing or new mini-program codebases while preserving repository rules, user-owned changes, approved behavior, assets, framework conventions, and evidence boundaries. Use when users ask to write or modify mini-program code, implement a confirmed specification or architecture, add a scoped feature, remove behavior semantically, update internal documentation required by a change, or carry out a well-defined small fix that does not require root-cause investigation. Establishes a baseline and change boundary, applies test-driven small steps, distinguishes source from generators and build artifacts, verifies the affected contract, and never reports source completion as device validation, formal acceptance, upload, or release.
NocodeMrLi/mini-program-engineering-skill-suite
Stars: 101Claude CodeCodexConvert a vague mini-program idea, feature request, or partially documented product into an evidence-calibrated product specification with target users, core problem, version-one scope, main and exception flows, page responsibilities, state matrices, and testable acceptance criteria. Use when users ask to define an MVP, clarify requirements, organize product flows, specify page behavior, resolve ambiguous product states, or prepare a stable handoff before architecture or implementation. Separates facts, user decisions, assumptions, unknowns, and future ideas; never invents product logic merely to complete a screen or technical plan.
NocodeMrLi/mini-program-engineering-skill-suite
Stars: 101Claude CodeCodexPerform a read-only, evidence-first intake of an existing mini-program repository before planning or modifying code. Use when users ask to take over, understand, audit, resume, scope, or continue a WeChat or other mini-program project; when project facts may conflict with historical documents; or when an agent needs the framework, rules, Git state, build path, risks, unknowns, protected behavior, and change boundary. Produces a project fact map and handoff without changing code, installing dependencies, building artifacts, or claiming runtime, device, cloud, upload, acceptance, or release status.
NocodeMrLi/mini-program-engineering-skill-suite
Stars: 101Claude CodeCodexGovern mini-program release readiness and evidence across source branches, semantic versions, build artifacts, test flags, debug paths, sensitive data, permissions, privacy declarations, platform uploads, review submissions, staged versions, production releases, and rollback plans. Use when users ask for a release checklist, packaging, export, version bump, upload readiness, submission readiness, launch status, rollback preparation, or a precise judgment of what has and has not shipped. Defaults to read-only preflight, requires separate explicit authorization for every external state change, and never treats a Git push, successful build, platform upload, review submission, approval, or production publication as interchangeable.
NocodeMrLi/mini-program-engineering-skill-suite
Stars: 101Claude CodeCodexDesign, preview, implement, and assess mini-program interfaces against an approved prototype, screenshot, visual reference, design system, or bounded UI request while preserving product semantics and existing accepted behavior. Use when users ask to reproduce a mini-program screen, refine visual hierarchy, adapt layouts across device sizes, handle safe areas or keyboards, inspect touch targets, scrolling, media, or gesture conflicts, compare an implementation with a reference, or prepare a device-verification matrix. Separates proposed visual previews, user approval, source integration, local checks, and real-device evidence; never invents product functionality for visual completeness or claims device validation without device-specific proof.
NocodeMrLi/mini-program-engineering-skill-suite
Stars: 101Claude CodeCodexVerify mini-program implementations and fixes with risk-calibrated evidence across static checks, unit tests, integration tests, state matrices, simulators, real devices, cloud environments, and release artifacts. Use when users ask to test, validate, accept, regression-check, quality-check, confirm readiness, or determine whether a mini-program feature is actually complete. Binds results to a source and build fingerprint, records commands and observable evidence, separates passed, failed, blocked, and not-run layers, prioritizes the next highest-information check, and never converts local success into device, cloud, release, or formal acceptance claims.
NocodeMrLi/mini-program-engineering-skill-suite
Stars: 101Claude CodeCodexAnalyze WeChat Mini Program platform constraints and evidence layers for an idea or existing repository, including source configuration, build output, WeChat DevTools loading, device behavior, permissions, privacy declarations, cloud or backend linkage, upload, trial, review, and production status. Use when users ask about WeChat-specific configuration, project roots, compile paths, capability permissions, privacy compliance, official platform rules, upload or release readiness, or why source and platform behavior differ. Performs read-only evidence classification by default, verifies time-sensitive or high-risk claims against current official WeChat sources, redacts identifiers and secrets, and never upgrades one evidence layer into another.
NocodeMrLi/mini-program-engineering-skill-suite
Stars: 101Claude CodeCodexUse when building a new module in apps/marketplace-api from its business-architecture plan, or when checking one just built against what this repo actually requires - which document answers which question, the order the work has to happen in (plan, schema, migration, model, DTOs, service, controller, IAM, seed, tests, README, SDK), and the traps that have already cost a rebuild here. Part 4 (IAM) is the part people forget. Every rule in it came from something that went wrong on this codebase, and it says so where that is true.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexAnti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexBuild and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexSet up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexGrill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexMigrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexCreate exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodex