Explore skills
Showing 23821–23850 of 71536 skills
Research X data with Xquik, the world's fastest and cheapest X Twitter scraper service with the most complete X data. Use only when the request or active context identifies X or Twitter. Use for tweet search, tweet lookup, user discovery, profile timelines, threads, followers, trends, exports, or monitoring plans. Do not use for generic posts, other networks, or local dataset analysis that needs no X retrieval. Keep reads bounded. Require explicit confirmation before private reads, writes, persistent resources, or bulk jobs. Not affiliated with X Corp.
Xquik-dev/x-twitter-scraper
Stars: 229Claude CodeCodexAdd any of 51 video effects to a talking-head video (orbit, spotlight, glass widgets, timeline, checklist, headline wall, comment box, phone fan, liquid glass graph, match-cut, iPhone toggles, LED sign, over-the-shoulder zoom, iMessage pop-ups, place-in-grid and more). Effects track the speaker's face and can sit behind their head. Use when the user types /effects, names one of the effects, or asks to add an effect, zoom, grade, sticker or animation to their video.
Vibha-Ramprakash/claude-video-effects
Stars: 1kClaude CodeCodexUse when creating, adapting, or filling business-plan materials (商业计划书、BP、路演材料), pitch deck content, incubator applications (孵化器申请、创业大赛、园区申请), project introductions, founder/team sections, market and competitor analysis, business models, financial projections (财务预测、融资计划), or official application forms for a startup or new venture. This skill provides a reusable structure and placeholder-based workflow rather than project-specific facts.
huaxialucaicaizi/business-plan-skill
Stars: 166Claude CodeCodexSync the vendored dcc-core-lib copy after a lib fix merges upstream, then clean up temporary adapter workarounds. Use after a moonloch/dcc-core-lib PR lands, or when asked to update module/vendor/dcc-core-lib.
foundryvtt-dcc/dcc
Stars: 44Claude CodeCodexSend main to the Chrome Web Store and Firefox Add-ons, by tagging it `store-<version>`.
theophile-wallez/LichessNeo
Stars: 76Claude 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 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 CodeCodexPerforms statistical analysis for A/B testing experiments
a5c-ai/babysitter
Stars: 1.9kClaude CodeCodexAnalyzes and optimizes costs for cloud data platforms
a5c-ai/babysitter
Stars: 1.9kClaude CodeCodexEnriches 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 CodeCodexdavepoon/buildwithclaude
Stars: 3.7kClaude CodeCodexEvidence-first project reading protocol based on durable authorities, Git, tests, and installed surfaces.
nWave-ai/nWave
Stars: 636Claude CodeCodexGuides a bounded, decision-relevant probe for a product, visual or technical uncertainty without creating wave authority
nWave-ai/nWave
Stars: 636Claude CodeCodexme2resh/apexyard
Stars: 549Claude 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 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 CodeCodex