Overview CLI FAQ

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

按 / 聚焦搜索框
正在使用 AI 进行语义搜索...
29,272
总 Skills
228.1M
总安装量
2,816
贡献者
# Skill 仓库 描述 安装量
8001 tech-podcast-youtube-channel samber/dev-event-organizer-skills
Tech Podcast and Video Channel You run one organizing team's own standing media property: a podcast or video channel that publishes on its own cadence, keeps its own back-catalogue, and outlives any single edition of the event. Treat the object as a property , not an artifact. The outcome is "this show is still publishing next year, and the people it reaches are people the room could not hold." Inherit the decision to have one. samber/dev-event-organizer-skills@event-portfolio-strategy decides w...
 2.2K
8002 event-sponsor-pricing samber/dev-event-organizer-skills
Event Sponsor Pricing You price event sponsorship: the rate card - how many tiers, at what ratios, which add-ons, which premiums, which discounts, and what the organizer will and won't negotiate. Upstream, samber/dev-event-organizer-skills@event-sponsor-value-proposition has articulated what each tier's price buys; value claims justify the rate card, never the reverse. samber/dev-event-organizer-skills@event-budget owns the revenue target the card must hit. Downstream, samber/dev-event-organizer...
 2.2K
8003 event-format-selection samber/dev-event-organizer-skills
Event Format Selection You are a format strategist for technical events. You own: whether the event is one program or several which shape it takes: meetup, hackathon, unconference, single-day or multi-day conference how workshops relate to talks which session formats fill the day whether delivery is in-person, virtual, or hybrid You do not build the schedule - grid layout, clash avoidance, and room-capacity matching belong to samber/dev-event-organizer-skills@event-schedule-design . You decide s...
 2.2K
8004 sentry-dotnet-sdk getsentry/sentry-for-ai
All Skills > SDK Setup > .NET SDK Sentry .NET SDK Opinionated wizard that scans your .NET project and guides you through complete Sentry setup: error monitoring, distributed tracing, profiling, structured logging, and cron monitoring across all major .NET frameworks. Invoke This Skill When User asks to "add Sentry to .NET", "set up Sentry in C", or "install Sentry for ASP.NET Core" User wants error monitoring, tracing, profiling, logging, or crons for a .NET app User mentions SentrySdk.Init , Us...
 2.2K
8005 interface-kit juliusbrussee/skills
Interface Kit: Implementation Guide for Exceptional Interfaces If a DESIGN.md exists at the project root, its tokens and specifications override all defaults in this skill. This skill provides sensible defaults for when no design system exists, and implementation guidance that applies regardless. For deep dives on any section, see the reference files in this skill's references/ directory. 1. Core Philosophy Taste is trained, not innate. Study why great interfaces feel right. Deconstruct apps you...
 2.2K
8006 data-visualization owl-listener/designer-skills
Data Visualization Skill Chart selection guidance, Python visualization code patterns, design principles, and accessibility considerations for creating effective data visualizations. Chart Selection Guide Choose by Data Relationship What You're Showing Best Chart Alternatives Trend over time Line chart Area chart (if showing cumulative or composition) Comparison across categories Vertical bar chart Horizontal bar (many categories), lollipop chart Ranking Horizontal bar chart Dot plot, slope char...
 2.2K
8007 grammar-checker daleseo/korean-skills
grammar-checker: 한국어 문법 검사기 소개 당신은 표준 한국어 규칙에 기반한 문법 검사 전문가입니다. 맞춤법, 띄어쓰기, 문법 구조, 구두점 오류를 감지하고 교정하며, 각 오류에 대한 명확한 설명을 제공합니다. 핵심 원칙: 규칙 기반 접근: 국립국어원의 표준 한국어 규정과 맞춤법 규칙 준수 확신도 표시: 확실한 오류와 권장 사항을 명확히 구분 학습 지향: 단순 교정이 아닌 이유와 근거를 설명 문맥 고려: 문체(격식체/비격식체)와 분야(기술 문서 등)를 고려한 유연한 적용 검사 범위: 맞춤법/철자: 되/돼, -ㄴ지/-는지, -ㄹ게/-를게, 던/든, -로써/-로서 등 띄어쓰기: 의존명사, 보조용언, 단위명사, 합성어 문법 구조: 조사 사용 (-을/를, -이/가, -은/는, -와/과), 시제, 어미 구두점: 쉼표, 마침표, 느낌표, 따옴표 사용 작업 흐름 1단계: 텍스트 입력 받기 다음 방법으로 텍스트를 받을 수 있습니다: 사용자가 직접 제공한 텍스트 파일 경로 ...
 2.2K
8008 om-code-review open-mercato/skills
Code Review Review code changes against the repository's architecture, security, convention, and quality standards. Produce actionable, categorized findings and a clear merge verdict. Contract Input — exactly one unit of review: a PR number (fetch the diff and metadata via the tracker operations get-pr-diff / get-pr ), a branch name (review its diff against the merge-base with $BASE_BRANCH ), an explicit commit range or diff, nothing — default to the current branch's diff against the merge-base ...
 2.2K
8009 poteto mode backnotprop/pstack
Poteto mode Non-negotiables Start every multi-step task with a todolist whose first item is to read the Principles section below in full. The principles ground every trigger here. In your reply, name each principle that shaped a decision and the specific choice it changed. A citation with no decision behind it means you skipped its leaf skill; it must trace to a real choice the leaf's rule drove. Remaining triggers: Show more Installs 268 Repository cursor/plugins GitHub Stars 4.4K First Seen Ma...
 2.2K
8010 setup-pstack backnotprop/pstack
Setup pstack Write ~/.cursor/rules/pstack-models.mdc , an always-applied rule that sets pstack's model per role. The skills read it and fall back to their inline defaults when a line is absent, so this is an override layer, not a requirement. Steps 1. Detect available models Enumerate the model slugs you can pass to a Task subagent in this session; that is the dependable source. If Cursor also exposes a models API or CLI that lists the user's entitled models, prefer it for completeness. If you c...
 2.2K
8011 figure-it-out backnotprop/pstack
Figure it out When the task matches no playbook, design one. The deliverable before any code is the workflow itself: a sequence of phases that scales rigor to the task, runs the scientific method, and leaves a decision trail a human can audit after stepping away. Bias toward more rigor. The cost of building the wrong thing dwarfs the cost of being careful. Don't reinvent a playbook you already have. A focused single-unit task that matches Bug fix, Perf, Feature, Visual parity, Eval, or Multi-pha...
 2.2K
8012 maintain-verification-skill backnotprop/pstack
Maintain a verification skill A feature map rots the moment the app changes. This skill is the upkeep loop for a skill generated by /create-verification-skill (or any project-local verification skill with a feature map). The unit of rigor is the feature, not every sentence: cover every feature file from source and exercise every feature live, without terminalising every bullet. Outcomes Pick one, and say which: clean — every feature got source and live coverage; nothing worth shipping. No branch...
 2.2K
8013 reflect backnotprop/pstack
Reflect Mine the current conversation for durable learnings, then route them into skill edits. When to invoke The user said "reflect" or "/reflect". A complex task (5+ tool calls) just landed cleanly and the recipe is worth keeping. The agent hit dead ends, found the working path, and the path generalizes. The user corrected the agent's approach mid-task. A non-trivial workflow emerged that isn't captured anywhere. Skip when the conversation is trivial, off-topic, or already covered by an existi...
 2.2K
8014 event-debrief samber/dev-event-organizer-skills
Event Debrief You run the organizing team's retrospective on one finished edition: the meeting, the reconstruction, the findings, and the log that reaches next edition's plan. Internal-facing only - nothing here reaches an attendee, a speaker or a sponsor. Run it every edition, unconditionally. The SRE incident-postmortem lineage this skill borrows from gates a postmortem on a severity threshold (SEV1/SEV2, an outage over fifteen minutes); that gate does not transfer. A quiet edition where nothi...
 2.2K
8015 event-date-selection samber/dev-event-organizer-skills
Event Date Selection You are a scheduling advisor for technical events. Pick the date: the day type the audience can actually attend, the window the season and the calendars leave open, the competing events to dodge or deliberately attach to, the candidate windows the venue can serve, and the moment the date becomes public. This skill ends the moment the date is announced. Three sibling skills border it: samber/dev-event-organizer-skills@event-planning-timeline owns the work-back schedule that s...
 2.2K
8016 event-social-media samber/dev-event-organizer-skills
Event Social Media You run the social channel of a technical event's acquisition campaign: which platforms the event posts on, which hashtag carries which purpose, what gets posted at each campaign phase, who else is asked to amplify, and what happens on the day. Three things arrive already decided. Do not re-derive them, and do not argue against them: The weight, the phase and the dates - samber/dev-event-organizer-skills@event-marketing-plan owns the channel mix, the campaign calendar spine an...
 2.2K
8017 event-talk-selection samber/dev-event-organizer-skills
Event Talk Selection You run the review process on proposals a call for papers already collected: who reviews, on what scale, in how many rounds, and what every submitter hears back. This skill does not: Design the call. Its timeline, form, published criteria, and anonymization policy belong to samber/dev-event-organizer-skills@event-cfp-design ; you inherit that policy rather than re-deciding it. Recruit speakers outside the call. That parallel channel is samber/dev-event-organizer-skills@event...
 2.2K
8018 event-ticket-pricing samber/dev-event-organizer-skills
Event Ticket Pricing You price attendee tickets. This covers: whether to charge at all how many public price points which personas get their own price what gates a discount who gets in for free or nearly free what happens when someone asks for their money back samber/dev-event-organizer-skills@event-budget owns the revenue target this ladder has to hit upstream, and samber/dev-event-organizer-skills@event-sponsor-pricing owns the sponsorship share that cross-subsidizes it. You set attendee numbe...
 2.2K
8019 dev-event-career samber/dev-event-organizer-skills
Dev Event Career You are a tech-event-organizing career coach for one person. Help them choose which operating context to target, break in from wherever they stand today, prepare for the loop this field actually runs, and read an offer against comp data that mostly isn't tech-specific. Out of scope, hand off instead: The hiring loop, job postings and scorecards from the employer side - samber/dev-event-organizer-skills@dev-event-hiring is the mirror image of this skill. The standing organizing t...
 2.2K
8020 event-budget samber/dev-event-organizer-skills
Event Budget You model the money for one edition of a technical event. Produce five things: The cost lines, and which of them scale with heads. The revenue total, and where it comes from. The cushion. The dates cash moves. The cut order when revenue falls short. Consume prices - ticket, sponsor, venue, vendor - never derive them. Hand back every number as either a dated quote or a labelled placeholder. Treat every ranking below as a default, not a law. Re-rank against what the interview turns up...
 2.2K
8021 hackathon-brief-design samber/dev-event-organizer-skills
Hackathon Brief Design You write the document a hackathon hands its teams: what to build, under which rules, who may enter, what to submit, and what "good" will be called. It is the only artifact every participant reads, and every dispute at the ceremony traces back to a sentence it did or did not contain. What "track" means here A challenge track is a thematic category a team enters its project into: an AI track, a sponsor's API track, a beginners track. It is a content and prize construct. sam...
 2.2K
8022 dev-event-kickoff samber/dev-event-organizer-skills
Dev Event Kickoff You are the entry point and router for the 71-skill dev-event-organizer-skills collection. Route the current task to exactly one sibling skill, or say plainly that none fits, and make the next session start warm instead of cold. Routing is the reason this skill exists; everything else serves it. The collection is too large for its own members to see each other. An organizer inside event-sponsor-pricing cannot know the number it needs came from event-budget , or discover event-b...
 2.2K
8023 event-vip-social-program samber/dev-event-organizer-skills
Event VIP Social Program You run a room that not everyone can walk into, at an event where everyone can walk into everything else. Three decisions, and only three, cover the job: How the seat list gets assembled when more than one party is putting names forward. How the invitation and the door work without publishing that a tier exists. Where the gathering sits against the public programme. The default answer is that there is no separate room. That is a rung on the first menu, not a refusal to h...
 2.2K
8024 event-landing-page samber/dev-event-organizer-skills
Event Landing Page You build the page a prospective attendee, speaker or sponsor lands on: its shape, its sections, what its primary button does on any given day, and what it says about content that does not exist yet. This is channel execution, not strategy. Almost everything the page says was decided upstream. Four things arrive already decided. Do not re-derive them, and do not argue against them: The campaign weight, phases and dates - samber/dev-event-organizer-skills@event-marketing-plan o...
 2.2K
8025 event-portfolio-strategy samber/dev-event-organizer-skills
Event Portfolio Strategy You are a portfolio strategist for one organizing team that runs (or is thinking about running) several event properties at once: a flagship conference, a meetup series, a hackathon, a startup weekend, a podcast, an always-on community space. You decide which properties belong in the set, how each one feeds the others, what they share, how their dates relate, and which one gets retired. You never plan or produce a single edition. Scope edge, stated up front: a portfolio ...
 2.2K
8026 event-comms-channels samber/dev-event-organizer-skills
Event Comms Channels You design the set of channels a technical event talks to its attendees on, for one edition, from the moment attendees exist to the moment the last channel is closed. Your output is an architecture somebody else executes: A roster of channels with a stated job each. A rule that says where any given message goes. A process that keeps several writers sounding like one event. A dated wind-down for every channel you opened. This skill writes no copy. The register, what the event...
 2.2K
8027 corporate-event-strategy samber/dev-event-organizer-skills
Corporate Event Strategy You decide what a company-run technical event is for , and nothing else: The goal mix. Who owns the budget line that funds it. The measurement commitment written down before registration opens. Never plan the event, produce it, price it, or model its P&L. Say company-run and community-run for the two poles, even when the user says corporate . That word is what a searcher types, not a third pole. Mirror the meaning, not the label. This skill sits at the company-run pole o...
 2.2K
8028 event-media-partnerships samber/dev-event-organizer-skills
Event Media Partnerships You set up reciprocal visibility deals between a technical event and media or community properties that are not themselves events: newsletters, podcasts, online communities (Slack/Discord, developer-ambassador programs), blogs, and media outlets. The exchange is symmetric exposure for exposure: the event gives logo placement and mentions, the partner gives a newsletter blurb, a podcast slot, or a community post. No cash changes hands by default. Organizer guides name thi...
 2.2K
8029 workshop-program-design samber/dev-event-organizer-skills
Workshop Program Design You design the internal mechanics of a hands-on workshop or training session: How many people can be in the room. Who helps them when they get stuck. What has to be true about their machine before they sit down. What they leave with. What happens when the room's network cannot carry what the exercise needs. Your inputs arrive decided: Whether a workshop day or track exists at all, how it is bracketed against the talk days, and how it is ticketed - samber/dev-event-organiz...
 2.2K
8030 event-growth-strategy samber/dev-event-organizer-skills
Event Growth Strategy You are a growth strategist for established technical events. Decide whether the next edition should be bigger, the same size, or smaller, and through which single lever, for an event that has already run at least one edition. You consume a demand read from samber/dev-event-organizer-skills@event-market-fit . You never rebuild its signals, and you never plan a first launch. Scope edge, stated up front: growing by opening a satellite city with the same organizing team is the...
 2.2K
8031 event-official-social-program samber/dev-event-organizer-skills
Event Official Social Program You decide one thing: how many official social occasions the event runs, and how they sit against each other. One occasion, a second on its own slot, or a themed track of several. That is the whole subject. samber/dev-event-organizer-skills@event-hospitality already decides what any single occasion is . None of the following reopens here: its format its food its drink its alcohol posture who it is for where it happens what it costs to attend when it starts and ends ...
 2.2K
8032 difit yoshiko-pg/difit
This skill requests a code review from the user using the difit command. If the user leaves review comments, they are printed to stdout when the difit command exits. When review comments are returned, continue work and address them. If the server is shut down without comments, treat it as "no review comments were provided." Commands Review the HEAD commit: difit Review uncommitted changes before commit: difit . Basic Usage difit < target > View single commit diff difit < target > [ compare-with...
 2.2K
8033 blender-mcp vladmdgolam/agent-skills
Blender MCP Tool Selection Use structured MCP tools ( get_scene_info , screenshot ) for quick inspection. Use execute_python for anything non-trivial: hierarchy traversal, material extraction, animation baking, bulk operations. It gives full bpy API access and avoids tool schema limitations. Use headless CLI for GLTF exports — the MCP server times out on export operations. Health Check (Always First) get_scene_info — verify connection (default port 9876) execute_python with print("ok") — verify ...
 2.2K
8034 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.2K
8035 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.2K
8036 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.2K
8037 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.2K
8038 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.2K
8039 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.2K
8040 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.2K
8041 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.2K
8042 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.2K
8043 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.2K
8044 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.2K
8045 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.2K
8046 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.2K
8047 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.2K
8048 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.2K
8049 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.2K
8050 event-sponsor-agreement samber/dev-event-organizer-skills
Event Sponsor Agreement This skill does not give legal advice and never produces a signable document. Its output is a term sheet - a structured clause checklist, with example language options and open questions marked - that a qualified lawyer in the event's own jurisdiction turns into a contract. Every path through this skill ends at counsel. Say this to the user at the start and again at handoff. An organizer who signs this skill's output unreviewed has been failed by it. You formalize a deal ...
 2.2K