Overview CLI FAQ

Agent Skills 排行榜 · 关键词 + 语义搜索

按 / 聚焦搜索框
正在使用 AI 进行语义搜索...
29,269
总 Skills
227.7M
总安装量
2,816
贡献者
# Skill 仓库 描述 安装量
8201 prisma-next-migrations prisma/prisma-next
Prisma Next — Migration Authoring Edit your data contract. Prisma Next plans the migration. You fill in any data transforms. The three-step user model: You edit your data contract. ( prisma-next-contract ) Prisma Next plans the migration for you. ← this skill If a data transform is needed, you edit migration.ts and self-emit. ← this skill Once the contract changes, you choose how the change reaches the database. This skill covers the two paths ( db update and migration plan + migrate ), the migr...
 2.1K
8202 prisma-next-queries prisma/prisma-next
Prisma Next — Queries Edit your data contract. Prisma handles the rest. Once the contract is emitted and the DB is up to date, this skill covers everything you do with the data: reading, writing, eager-loading relations, aggregating, and the choice between the ORM and the lower-level query lane. When to Use User wants to read, write, update, or delete data. User wants to include / eager-load relations. User wants to paginate, sort, filter, project. User wants to wrap operations in a transaction ...
 2.1K
8203 statistical-analysis k-dense-ai/scientific-agent-skills
Statistical Analysis Skill Descriptive statistics, trend analysis, outlier detection, hypothesis testing, and guidance on when to be cautious about statistical claims. Descriptive Statistics Methodology Central Tendency Choose the right measure of center based on the data: Situation Use Why Symmetric distribution, no outliers Mean Most efficient estimator Skewed distribution Median Robust to outliers Categorical or ordinal data Mode Only option for non-numeric Highly skewed with outliers (e.g., ...
 2.1K
8204 roblox-game-development greedychipmunk/agent-skills
Roblox Game Development Skill Description Expert Roblox game developer specializing in Luau scripting, game mechanics, UI/UX design, and monetization strategies. Assists with everything from simple scripts to complex multiplayer experiences. Resource Library This skill includes a comprehensive collection of production-ready resources: 📜 Helper Scripts - Professional utility modules for data management, networking, UI, game flow, and audio 📋 Document Templates - Complete project documentation...
 2.1K
8205 alphagenome-single-variant-analysis google-deepmind/science-skills
Variant Analysis using AlphaGenome Prerequisites Show more Installs 431 Repository google-deepmind…e-skills GitHub Stars 1.2K First Seen May 19, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass
 2.1K
8206 plan-crafting sentimony/skills
Plan Crafting Overview Write comprehensive implementation plans assuming the engineer has zero context for the codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, and docs they might need to check. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits. Per-task commits are the working granularity for review gates; the final shape of the history (squash, amend, branch flow) follows the user's git pref...
 2.1K
8207 release-stable getpaseo/paseo
Release stable Follow the applicable flow and the Stable release (or promotion) completion checklist in docs/release.md end-to-end. Installs 886 Repository getpaseo/paseo GitHub Stars 14.4K First Seen May 21, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass
 2.1K
8208 n8n-workflow-lifecycle-official n8n-io/skills
n8n Workflow Lifecycle The six stages PLAN. Gather requirements, ask clarifying questions, search for existing workflows / sub-workflows that already do this. BUILD. Write SDK code (with skills: subworkflows, node-config, expressions, code-nodes; readability section below). Use validate_node_config as a side-channel for iteration, debugging, or small single-node edits: clean per-parameter errors without full-graph noise. Not a replacement for validate_workflow in VALIDATE. VALIDATE. validate_wor...
 2.1K
8209 speckit-implement dceoy/speckit-agent-skills
Spec Kit Implement Skill When to Use The plan and tasks are complete and you are ready to implement. Inputs specs/<feature>/tasks.md and plan.md Optional artifacts: data-model.md , contracts/ , research.md , quickstart.md User constraints (e.g., scope, testing expectations) If tasks are missing or incomplete, ask the user to run speckit-tasks first. Workflow Run .specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks from repo root and parse FEATURE_DIR and AVAILABLE_...
 2.1K
8210 copy-to-output-directory dotnet/skills
Choosing a CopyToOutputDirectory Mode Overview The CopyToOutputDirectory metadata (and its publish counterpart CopyToPublishDirectory ) controls whether an item — Content , None , EmbeddedResource , or Compile — is copied next to your build output, and under what conditions the copy happens. Picking the wrong mode causes either stale files in bin/ or an unnecessary per-build performance hit. As of MSBuild 17.13 / .NET SDK 9.0.2xx there are four values: Mode Copies when… Incremental cost Typical ...
 2.1K
8211 zoom-mcp anthropics/knowledge-work-plugins
Zoom MCP Guidance for the bundled Zoom MCP connector in this Claude plugin. Prefer design-mcp-workflow or setup-zoom-mcp first, then route here for tool-surface details, auth expectations, and MCP-specific constraints. Zoom MCP Server This plugin bundles Zoom's hosted MCP server at mcp-us.zoom.us for AI-agent access to: semantic meeting search meeting-linked asset retrieval recording resource retrieval Zoom Docs are exposed through a separate bundled server: zoom-docs-mcp at mcp.zoom.us purpose-...
 2.1K
8212 ensembl-database google-deepmind/science-skills
Ensembl Database: ID Mapping and Genomic Features Prerequisites uv : Read the uv skill and follow its Setup instructions to ensure uv is installed and on PATH. User Notification : If LICENSE_NOTIFICATION.txt does not already exist in this skill directory then (1) prominently notify the user to check the terms at https://useast.ensembl.org/index.html and https://github.com/Ensembl/ensembl-rest/wiki , then (2) create the file recording the notification text and timestamp. Overview The Ensembl data...
 2.1K
8213 ito-inference affaan-m/ecc
Itô Inference ito-inference is the sole canonical ECC skill for inference serving on Itô compute. Requests naming ito-serve route here; do not create or install a second ito-serve skill. ECC never SSHes to nodes, downloads weights, launches an engine, or exposes an endpoint; it never books, reserves, or spends. Current production boundary Managed serving is unavailable today. The ECC bridge exposes only login , auth , find , status , and explicitly gated evals . It has no serve verb. The canonic...
 2.1K
8214 ito-training affaan-m/ecc
Itô Training ito-training is the canonical ECC skill for training on Itô compute. ECC never runs a trainer, scheduler, or data pipeline of its own; it never books, reserves, or spends. This skill chains off a completed booking from ito-compute . Current production boundary Managed training is unavailable today. The ECC bridge exposes only login , logout , auth , find , status , and explicitly gated evals . It has no train verb, and the canonical CLI's run verb and desk training-run backend remai...
 2.1K
8215 find-models replicate/skills
Always search the API for current models The AI model landscape changes weekly. New models ship constantly and older ones are deprecated or surpassed. Don't rely on model names you've seen before, including names from past conversations or training data. A specific model you "know" may no longer be the best choice, may be slower than newer alternatives, or may not exist anymore. Always start by querying the Replicate API. Use search and collections to discover what's currently available, then re...
 2.1K
8216 create-datadriven-aspnetcore dotnet/skills
Generate or Scaffold ASP.NET Core Code Generate ASP.NET Core scaffolded code — controllers, views, Razor Pages, Blazor components, Minimal API endpoints. The generated code matches the project's existing CSS framework, layout conventions, and coding patterns. No CLI-based scaffolding/code-generation tools are used; standard dotnet CLI commands for build, restore, and migrations are still expected. When to Use Adding CRUD pages, views, or components for a model in an ASP.NET Core project Scaffold...
 2.1K
8217 om-integration-tests open-mercato/skills
Integration Tests Generate executable integration tests by exploring the running application — never by guessing selectors or flows — and run existing suites with disciplined, artifact-based failure reporting. This skill deliberately prescribes no environment : how the app starts, which ports it uses, and how a test database is provisioned are the repository's business. Your first job is always to discover that from the repo itself. Workflow Agentic setup — follow references/agentic-setup.md : l...
 2.1K
8218 living-docs-governance affaan-m/ecc
Living Docs Governance Long-lived projects often rot at the documentation layer first: the README describes an old pipeline, architecture notes describe a refactor that never shipped, and every new session re-derives context that should already be available. Living Docs Governance assigns four non-overlapping roles to the project's existing documentation, links those roles from the active agent harness, and defines small update rules that keep the sources useful. The roles matter; the filenames ...
 2.1K
8219 principle-boundary-discipline backnotprop/pstack
Boundary Discipline Place validation, type narrowing, and error handling at system boundaries. Trust internal code unconditionally. Business logic lives in pure functions; the shell is thin and mechanical. Why: Scattered validation is noisy, redundant, and gives a false sense of safety. Validate data once at the boundary. Keep logic out of framework wiring so it can be tested without the framework. The pattern: At boundaries (CLI args, config files, external APIs, network protocols): validate, r...
 2.1K
8220 principle-laziness-protocol backnotprop/pstack
Laziness Protocol Writing code is cheap for you, which makes over-engineering easy. Counter it by borrowing a human maintainer's fatigue. Aim for the most result with the least code and complexity. Prefer deletion. When asked to refactor or improve, look for removals before additions. Maintain a flat call hierarchy. Avoid deep call chains. A rich interface that hides substantial work is not a deep call chain. If answering a question requires tracing through more than 3 files or layers, flatten i...
 2.1K
8221 principle-type-system-discipline backnotprop/pstack
Type System Discipline The type checker is a proof assistant. Use it to eliminate impossible states, mismatched primitives, and unhandled variants at compile time. A case the types let you ignore becomes a runtime failure the compiler could have stopped. Prefer defining errors and special cases out of existence over proliferating handlers; unrepresentable states, total functions, and interface redesign (the patterns below) are the tools. Applies to any typed language. Skills like typescript-best...
 2.1K
8222 principle-subtract-before-you-add backnotprop/pstack
Subtract Before You Add When evolving a system, remove complexity first, then build. Deletion gives you a simpler base, which makes the next addition smaller and less brittle. Why: Adding to a complex system compounds complexity. Removing first cuts the surface area, reveals the essential structure, and usually makes the next design obvious. Default to subtraction. Make simplification a continual investment. Leave the design slightly simpler and more capable behind the same or smaller surface th...
 2.1K
8223 principle-never-block-on-the-human backnotprop/pstack
Never Block on the Human The human supervises asynchronously. Agents must stay unblocked: make reasonable decisions, proceed, and let the human course-correct after the fact. Code is cheap. Waiting is expensive. Why: Every permission pause stalls the pipeline and makes the human the bottleneck. Since code changes are reversible and reviewable, a wrong decision usually costs less than blocking. Pattern: Proceed, then present. Do the work, show the result. Don't ask "should I do X?" Do X, explain ...
 2.1K
8224 principle-guard-the-context-window backnotprop/pstack
Guard the Context Window The context window is finite and non-renewable within a session. Every token that enters should earn its place. Why: Context overflow degrades reasoning quality, creates compression artifacts, and halts progress. Unlike compute or time, context spent inside a session cannot be reclaimed. Pattern: Isolate large payloads. Route verbose outputs, screenshots, and large documents to subagents. The main context gets summaries, not raw data. Don't read what you won't use. Read ...
 2.1K
8225 principle-sequence-verifiable-units backnotprop/pstack
Sequence work into verifiable units Order work as a sequence of small units, each ending in a state you can check, and don't advance until the current one is green. The same discipline runs at two altitudes, how you execute and how you deliver. Why: A break caught at the unit that caused it is cheap to localize. A break caught after a batch is buried, and you have already built further on a broken base. Sequencing those same units into a delivery a reviewer can replay turns "trust me" into "watc...
 2.1K
8226 principle-outcome-oriented-execution backnotprop/pstack
Outcome-Oriented Execution Optimize for the intended, verifiable end state rather than preserving smooth intermediate states. Why: Keeping every intermediate step fully stable often creates temporary compatibility code that becomes long-lived debt. Converge on the target architecture and prove correctness at explicit verification boundaries. Core rule: Prioritize end-state integrity over transitional stability Intermediate breakage is acceptable when it is planned, scoped, and reversible Always ...
 2.1K
8227 principle-model-the-domain backnotprop/pstack
Model the Domain Encode the real domain in a data structure instead of scattering it across conditionals. Why: Scattered booleans, repeated shape assumptions, and branching spread across files are accidental complexity. A structure that matches the domain makes invalid states unrepresentable and deletes branches. Choosing it at write time is cheap; recovering it later reads as a refactor and gets deferred. Reach for structures like these: A state machine instead of scattered booleans, phases, or...
 2.1K
8228 principle-encode-lessons-in-structure backnotprop/pstack
Encode Lessons in Structure Encode recurring fixes in mechanisms (tools, code, metadata, automation) instead of textual instructions. Every error, human correction, and unexpected outcome is a learning signal. Capture it, route it, and close the loop. Why: Textual instructions are easy to miss. They require the reader to notice, remember, and comply. Structural mechanisms (lint rules, metadata flags, runtime checks, automation scripts) enforce the rule without cooperation. Pattern: When you catc...
 2.1K
8229 principle-redesign-from-first-principles backnotprop/pstack
Redesign From First Principles When integrating a change, don't bolt it onto the existing design. Redesign as if the requirement had been there from the start. The result should look like what we would have built if we'd known on day one. Read all affected files and understand the current design holistically Ask: "if we were writing this from scratch with this new requirement, what would we build?" Propagate the change through every reference: types, docs, examples, rationale sections Think abou...
 2.1K
8230 principle-foundational-thinking backnotprop/pstack
Foundational Thinking Structural decisions protect option value. Code-level decisions protect simplicity. Over-engineering is often a premature decision that closes doors. The right foundational data structure keeps doors open. Data structures first. Get the data shape right before writing logic. The right shape makes downstream code obvious. Define core types early, trace every access pattern, and choose structures that match the dominant paths. A data-structure change late is a rewrite. Early,...
 2.1K
8231 principle-build-the-lever backnotprop/pstack
Build the Lever When the work isn't trivial, build the tool that does it instead of doing it by hand. Why: Two payoffs. Throughput: a codemod, generator, or script does the work the same way every time and reruns for free. Confidence: the tool is one artifact a reviewer can read and rerun to check the work. Hand-done changes can only be re-verified by redoing them. A deterministic script turns "trust me" into "run this". Pattern: Default to building the lever. Skip it only when the task is genui...
 2.1K
8232 tdd backnotprop/pstack
Test-Driven Development Philosophy Core principle : Tests should verify behavior through public interfaces, not implementation details. Code can change entirely; tests shouldn't. Good tests are integration-style: they exercise real code paths through public APIs. They describe what the system does, not how it does it. A good test reads like a specification - "user can checkout with valid cart" tells you exactly what capability exists. These tests survive refactors because they don't care about i...
 2.1K
8233 principle-make-operations-idempotent backnotprop/pstack
Make Operations Idempotent Design operations so they converge to the correct state regardless of how many times they run or where they start from. Every state-mutating operation should answer: "What happens if this runs twice? What happens if the previous run crashed halfway?" Why: Commands, lifecycle operations, and processing loops run where crashes, restarts, and retries are normal. If partial state changes the next run's outcome, every restart becomes a debugging session. The pattern: Conver...
 2.1K
8234 principle-minimize-reader-load backnotprop/pstack
Minimize Reader Load Maintainability is the work a reader must do to understand code. Track two axes: Layers to trace. How many indirections sit between the question and the answer. State to hold. How much hidden or mutable context the reader must keep in their head. Why: Code is read far more than it is written. LOC, cyclomatic complexity, and "clean architecture" are proxies. Reader load is the thing that matters. The two axes are independent. A flat file with 50 globals can be as hard to reas...
 2.1K
8235 principle-separate-before-serializing-shared-state backnotprop/pstack
Separate Before Serializing Shared State When concurrent actors might share mutable state, first ask whether they truly need the same mutable object. If not, eliminate the sharing. When sharing is real, enforce serialization structurally: lockfiles, sequential phases, exclusive ownership. Instructions and conventions are not concurrency control. Why: Concurrent writes to shared state create race conditions that are intermittent, hard to reproduce, and expensive to debug. Telling agents or gorout...
 2.1K
8236 principle-experience-first backnotprop/pstack
Experience First The product is the experience. Every technical decision either helps or hurts it. When implementation convenience conflicts with user delight, choose delight. Say no to 1,000 things (every feature, control, and option must earn its place) Ship less, ship better (polished experience with three features beats rough one with ten) Prototype before committing (design decisions are cheaper in throwaway HTML than production code) Sweat the details (transitions, alignment, spacing, feed...
 2.1K
8237 principle-exhaust-the-design-space backnotprop/pstack
Exhaust the Design Space When a novel interaction or architectural decision has no established precedent, explore several concrete alternatives before implementation. Building the wrong thing costs more than exploring three options. The rule. When the right answer is not obvious, build 2-3 competing prototypes or sketches. Compare them side by side. Only then commit. Design it twice is this rule by another name. A second flavor of the first shape does not count. When it applies: Novel UI interac...
 2.1K
8238 event-hospitality samber/dev-event-organizer-skills
Event Hospitality You decide what the event feeds everybody, when, and what the social half of it looks like. Your output is a hospitality brief somebody else turns into an order, a contract and a rota. Four decisions: The catering service style. What a scheduled break contains. The alcohol posture. Whether an evening or social programme exists. Set the shared floor, never a population's top-up. Every other hospitality skill layers on it: samber/dev-event-organizer-skills@event-speaker-experienc...
 2.1K
8239 event-market-fit samber/dev-event-organizer-skills
Event Market Fit You are a demand analyst for technical events. Answer one question at three moments: does this concept/audience/price combination meet real demand - before anything is committed, while tickets are on sale, and after an edition has run? Deliver a signal read and a decision (go, hold-and-fix, pivot, stop), never the response plan. What to cut, how to launch, and which format to pick belong to sibling skills. Practitioners read event demand by composing signals rather than by runni...
 2.1K
8240 event-b2b-matchmaking samber/dev-event-organizer-skills
Event B2B Matchmaking You design the mechanic that turns two populations at one event into scheduled 1:1 business conversations. Own the whole chain: whether the program runs at all, how the two sides are matched, how slots get booked and placed, what meeting number a sponsor package may honestly commit to, how a missed booking is absorbed, and what gets measured afterwards. Answer no by default. Most community technical events correctly never run this, and "no meeting program at all" is a ranke...
 2.1K
8241 event-sponsor-fulfillment samber/dev-event-organizer-skills
Event Sponsor Fulfillment You deliver what the sale promised: everything between a countersigned sponsorship agreement and a renewal case handed back to the sales motion. You consume what the siblings fixed upstream, and you output delivered perks with evidence, plus the post-event report that samber/dev-event-organizer-skills@event-sponsor-outreach anchors its renewal contact on: The promises, from samber/dev-event-organizer-skills@event-sponsor-value-proposition . The packages and prices, from...
 2.1K
8242 acquire-codebase-knowledge github/awesome-copilot
Acquire Codebase Knowledge Produces seven populated documents in docs/codebase/ covering everything needed to work effectively on the project. Only document what is verifiable from files or terminal output — never infer or assume. Output Contract (Required) Before finishing, all of the following must be true: Exactly these files exist in docs/codebase/ : STACK.md , STRUCTURE.md , ARCHITECTURE.md , CONVENTIONS.md , INTEGRATIONS.md , TESTING.md , CONCERNS.md . Every claim is traceable to source fi...
 2.1K
8243 paper-lookup k-dense-ai/scientific-agent-skills
Paper Lookup You have access to 10 academic paper databases through their REST APIs. Your job is to figure out which database(s) best serve the user's query, call them, and return the results. Core Workflow Understand the query -- What is the user looking for? A specific paper by DOI? Papers on a topic? An author's publications? Open access PDFs? Full text? This determines which database(s) to hit. Select database(s) -- Use the database selection guide below. Many queries benefit from hitting mu...
 2.1K
8244 om-fix open-mercato/skills
Apply Fix You are step 3 of an autofix chain ( om-verify-in-repo → om-root-cause → om-fix → om-open-pr → om-auto-review-pr ). The chain is driven end-to-end by the om-auto-fix-issue skill, or by an external flow runner. The previous step ( om-root-cause ) wrote a brief telling you what to change and where. The repo is checked out on an isolated branch in the current working directory. Your job: implement the proposed change, prove it works, and stop. The next step ( om-open-pr ) handles commit/p...
 2.1K
8245 speckit-constitution dceoy/speckit-agent-skills
Spec Kit Constitution Skill When to Use Initial project setup or when governance principles need updates. Inputs User-provided principles or amendments. Existing .specify/memory/constitution.md and templates. If the request is missing or ambiguous, ask focused questions before proceeding. Workflow You are updating the project constitution at .specify/memory/constitution.md . This file is a TEMPLATE containing placeholder tokens in square brackets (e.g. [PROJECT_NAME] , [PRINCIPLE_1_NAME] ). Your...
 2.1K
8246 minimal bergside/awesome-design-skills
Minimal Design Design System Skill (Universal) Mission You are an expert design-system guideline author for minimal design. Create practical, implementation-ready guidance that can be directly used by engineers and designers. Brand Style Foundations Visual style: minimal, clean, bold Typography scale: desktop-first expressive scale | Fonts: primary=Open Sans, display=Inter, mono=Inconsolata | weights=100, 200, 300, 400, 500, 600, 700, 800, 900 Color palette: primary, neutral, success, warning, d...
 2.1K
8247 run-models replicate/skills
Docs Reference: https://replicate.com/docs/llms.txt OpenAPI schema: https://api.replicate.com/openapi.json MCP server: https://mcp.replicate.com Per-model docs: https://replicate.com/{owner}/{model}/llms.txt Set Accept: text/markdown when requesting docs pages for Markdown responses. Workflow Choose the right model - Search with the API or ask the user. Get model metadata - Fetch input and output schema via API. Create prediction - POST to /v1/predictions. Poll for results - GET prediction until...
 2.1K
8248 teach backnotprop/pstack
No SKILL.md available for this skill. View on GitHub
 2.1K
8249 swarm backnotprop/pstack
Swarm Process many independent items in parallel. create builds a table handle; run fans work out across rows and merges results back. One row = one unit of work — swarm handles batching automatically. Flow Create. Build a table from a source — files, a glob pattern, or pre-parsed records. One row per item. Returns a handle. Run. Dispatch an instruction template across rows. Results are merged back into the table. Returns { completed, failed, skipped, failures } . Aggregate. Use rows() and plain...
 2.1K
8250 principle-migrate-callers-then-delete-legacy-apis backnotprop/pstack
Migrate Callers Then Delete Legacy APIs When we decide a new API is the right design, migrate callers and remove the old API in the same refactor wave instead of preserving compatibility layers. Rule: Do not keep legacy API paths alive only because internal callers still exist Inventory callers, migrate them, and delete the old API immediately Treat temporary adapters as exceptional and time-boxed, not default architecture Update tests to assert the new contract, and delete tests that only prote...
 2.1K