███████╗██╗ ██╗██╗██╗ ██╗ ██████╗ █████╗ ███╗ ██╗██╗ ██╗
██╔════╝██║ ██╔╝██║██║ ██║ ██╔══██╗██╔══██╗████╗ ██║██║ ██╔╝
███████╗█████╔╝ ██║██║ ██║ ██████╔╝███████║██╔██╗ ██║█████╔╝
╚════██║██╔═██╗ ██║██║ ██║ ██╔══██╗██╔══██║██║╚██╗██║██╔═██╗
███████║██║ ██╗██║███████╗███████╗ ██║ ██║██║ ██║██║ ╚████║██║ ██╗
╚══════╝╚═╝ ╚═╝╚═╝╚══════╝╚══════╝ ╚═╝ ╚═╝╚═╝ ╚═╝╚═╝ ╚═══╝╚═╝ ╚═╝
Agent Skills 排行榜 · 关键词 + 语义搜索
| # | Skill | 仓库 | 描述 | 安装量 |
|---|---|---|---|---|
| 8051 | event-sponsor-prospectus | samber/dev-event-organizer-skills |
Event Sponsor Prospectus You assemble the sponsorship prospectus for a technical event: the standard, published document a prospect reads before any call. The deliverable is the document itself, its section order, tier table, perks catalog, audience evidence, distribution format, and the per-edition refresh routine. This skill presents content sibling skills produce, never invents it: Value claims and the not-offered list, from samber/dev-event-organizer-skills@event-sponsor-value-proposition . ...
|
2.2K |
| 8052 | event-no-show-management | samber/dev-event-organizer-skills |
Event No-Show Management You decide: How many registrations to accept for a room of a given size. Who gets promoted off the waitlist, and when. How the gap between the registration list and the actual room gets absorbed on the day. Which number goes to catering. You do not: Price the ticket. Write the reminder emails. Staff the check-in desk. Judge whether the event has demand behind it. Every ranking below is this skill's own construction, not a measured ordering: a default, not a law, and it s...
|
2.2K |
| 8053 | event-content-repurposing | samber/dev-event-organizer-skills |
Event Content Repurposing You decide what happens to an edition's captured output once a master file already exists. Inputs, every one of them somebody else's output: a published recording, slides, a transcript, a photo archive, hallway notes. Decisions you own: which derivative artifacts get made, in what order, on what cadence, under which licence, and what each speaker is asked to do about the piece cut from their own talk. Outputs you produce: published derivative artifacts, plus a content i...
|
2.2K |
| 8054 | event-community-building | samber/dev-event-organizer-skills |
Event Community Building You animate one recurring technical event's own audience during the months when no edition is imminent. Your object is an edition cycle , not a product and not a standing meetup series. One outcome pays you: "this person comes back next edition, and some of them bring work with them". Inherit the space, never choose it. samber/dev-event-organizer-skills@event-portfolio-strategy decides whether a continuity surface belongs in the team's property set; decide how to run it ...
|
2.2K |
| 8055 | event-marketing-plan | samber/dev-event-organizer-skills |
Event Marketing Plan You build the acquisition plan that fills a technical event: which audience segments get reached through which channels, at what weight, on what dates, against what per-phase targets. This is the umbrella plan. It decides when and how much each channel gets and hands the channel's own content to the sibling that owns it. Four inputs arrive already decided. Do not re-derive them: The message - samber/dev-event-organizer-skills@event-positioning supplies the promise and the au...
|
2.2K |
| 8056 | event-cultural-identity | samber/dev-event-organizer-skills |
Event Cultural Identity You are a culture designer for technical events. You own the embodiment question: given what the event stands for, how does that identity show up in the room - the MC's first 90 seconds, the signage, the swag, the catering, the closing moment, the norms people follow between talks. This skill takes the event's stated identity as input and hands the register it produces to its neighbors: Not deciding what the event stands for - samber/dev-event-organizer-skills@event-posit...
|
2.2K |
| 8057 | event-schedule-design | samber/dev-event-organizer-skills |
Event Schedule Design You lay already-selected sessions into a physical grid: which talk runs at which time, in which room, with what between them. Your inputs arrive decided, fixed by these sources: Track count, event shape, session-format mix, delivery mode - samber/dev-event-organizer-skills@event-format-selection , which states the split from its own side: "You do not build the schedule - grid layout, clash avoidance, and room-capacity matching belong to samber/dev-event-organizer-skills@eve...
|
2.2K |
| 8058 | event-planning-timeline | samber/dev-event-organizer-skills |
Event Planning Timeline You are a scheduling strategist for technical events. Build the months-long work-back plan that connects a fixed doors-open date to today: parallel tracks, milestones worked backward, cross-track dependency gates, an explicit buffer policy, and checkpoints that trigger replanning before a slip becomes a crisis. This skill owns the general mechanics for any edition: Not the date itself: samber/dev-event-organizer-skills@event-date-selection owns that decision. Not the sour...
|
2.2K |
| 8059 | hackathon-team-formation | samber/dev-event-organizer-skills |
Hackathon Team Formation You decide how people at a hackathon end up building with each other: the team-size rule the brief publishes, the mechanic that runs on the day, what happens to whoever it fails, when membership stops moving, and how all four fit around the opening. This is the participant-to-participant problem. It is not the participant-to-expert problem, and the two get confused constantly. What you own, and what is already decided You own: the team-size number and its solo answer the...
|
2.2K |
| 8060 | event-sponsor-outreach | samber/dev-event-organizer-skills |
Event Sponsor Outreach You run the sale itself: everything between having a sponsor value story and having a signed sponsor. You consume three inputs from sibling skills and output a signed yes, or a tracked no: The claims - samber/dev-event-organizer-skills@event-sponsor-value-proposition . The document - samber/dev-event-organizer-skills@event-sponsor-prospectus . The rate card - samber/dev-event-organizer-skills@event-sponsor-pricing . The output - a signed yes handed to samber/dev-event-orga...
|
2.2K |
| 8061 | hackathon-cash-prize | samber/dev-event-organizer-skills |
Hackathon Cash Prize You decide what a hackathon gives its winners: the medium, the pool size, the split, who may receive an award, and how the handover happens without creating an obligation nobody checked. Organizers ask about cash first. Cash is not the recommended answer, and the one organizer guide that takes a position takes the opposite one. Read the medium menu before assuming the user needs a number. What you own, and what is already decided You own the prize: medium, total pool, split ...
|
2.2K |
| 8062 | event-positioning | samber/dev-event-organizer-skills |
Event Positioning You are a positioning strategist for technical events. You decide what the event stands for, against which named alternatives, and for which audience identity - the audience, promise, and brand at the strategic level. Positioning is context, not messaging: an attendee always evaluates the event relative to alternatives, and your job is to choose the frame (audience, category, alternatives) that makes the event's real strengths obvious before any tagline, CFP copy, or logo exist...
|
2.2K |
| 8063 | event-run-of-show | samber/dev-event-organizer-skills |
Event Run of Show You own the day itself. The grid arrives decided and you never reopen it: samber/dev-event-organizer-skills@event-schedule-design states the split from its own side - "You stop at the published grid: how staff execute it minute by minute on the day, and how they respond live to a no-show or an AV failure, is samber/dev-event-organizer-skills@event-run-of-show ". It also hands you one more artifact besides the grid: a disruption priority order written into the schedule document....
|
2.2K |
| 8064 | event-booth-experience | samber/dev-event-organizer-skills |
Event Booth Experience You design the expo floor as a system for every booth, once per edition: the layout and traffic pattern, the tier-to-physical-spec catalog booths are staged against, the master setup and teardown schedule, the staffing and conduct provisioning rules, and the mechanic that pulls attendees across the floor. Hand per-sponsor day-of execution to samber/dev-event-organizer-skills@event-sponsor-fulfillment . Do not write "how to run a great booth". That is the exhibiting company...
|
2.2K |
| 8065 | business-event-formats | samber/dev-event-organizer-skills |
Business Event Formats You pick which company-run event shape a company runs this year: invite-only dinner or roundtable, executive summit, single-city user conference, multi-city roadshow, or floor-primary event. Pick how its program is sourced, and for floor-primary shapes, which of three floor shapes it takes. Decide the shape and stop. Track count and session mix, floor operations, goals and funding, and positioning claims each belong to a sibling (§ Sibling skills that own adjacent ground)....
|
2.2K |
| 8066 | cross-event-promotion | samber/dev-event-organizer-skills |
Cross-Event Promotion You broker visibility swaps between independent events run by independent organizers: Ticket-discount code exchanges. Newsletter and social mention swaps. Booth and flyer exchanges. Speaker-pipeline sharing. Conference-week co-location. Community-calendar cross-listing. The currency exchanged is mutual visibility, not money: no commission, no reseller mechanics, no cash changing hands. Distinct from: Deals between events under the same organizer, which need none of this cou...
|
2.2K |
| 8067 | event-cfp-design | samber/dev-event-organizer-skills |
Event CFP Design You design the call for papers of a technical event: the public artifact a prospective speaker reads, the form they fill, and the timeline both sides commit to. You do not: Score or select the submissions - the rating grid, review committee, and notifications belong to samber/dev-event-organizer-skills@event-talk-selection . Recruit speakers outside the CFP - that parallel channel belongs to samber/dev-event-organizer-skills@event-speaker-sourcing . The session formats the call ...
|
2.2K |
| 8068 | event-vendor-sourcing | samber/dev-event-organizer-skills |
Event Vendor Sourcing You are a supplier sourcing and contracting advisor for technical events. Find the suppliers the venue does not include, brief them identically, compare what they quote, and get them under terms that survive the event day. You do not pick the venue, decide which insurance the event needs, or write the technical specification an AV supplier delivers against. Those decisions arrive from siblings and you contract against them. Scope In scope: catering, AV and production suppli...
|
2.2K |
| 8069 | event-press-relations | samber/dev-event-organizer-skills |
Event Press Relations You pursue coverage the event does not control and cannot trade for. Somebody else decides whether to write, what to write, and whether to publish at all. That asymmetry is the whole skill. Make a "yes" cheap for a journalist or a creator to give. Make two irreversible failures less likely: A refusal that becomes a public dispute. A statement that cannot be unsaid. Start from the answer that is usually right: this event should not run a press function at all. Two major deve...
|
2.2K |
| 8070 | event-sponsor-value-proposition | samber/dev-event-organizer-skills |
Event Sponsor Value Proposition You articulate the value a technical event can genuinely offer sponsors, before anything is packaged, priced, or pitched. Deliverable : one value-proposition statement per sponsor segment, every claim backed by a proof point, feeding samber/dev-event-organizer-skills@event-sponsor-prospectus (the deck) and samber/dev-event-organizer-skills@event-sponsor-pricing (the rate card). Out of scope : packaging tiers, setting prices, running outreach, drafting contracts, t...
|
2.2K |
| 8071 | virtual-event-production | samber/dev-event-organizer-skills |
Virtual Event Production You run delivery for an event with no room. A software platform is the venue, each attendee's own connection is the uplink, and the crew is a moderator roster plus a remote-speaker pipeline rather than a stage crew. Treat the format as settled: samber/dev-event-organizer-skills@event-format-selection already chose fully-virtual. Never re-argue that choice. Where the room disappears This boundary is written from your side only. Confirm it rather than implying an agreed ha...
|
2.2K |
| 8072 | event-risk-management | samber/dev-event-organizer-skills |
Event Risk Management You are a risk manager for technical events. Take an organizer from "we have signed things and spent money" to a written register, a coverage decision, and a calendar of dates on which someone is authorized to say no. This is the standing discipline, reusable on edition 1 and edition 10, at a meetup or a multi-track conference. It is not a one-time exercise: the register is re-scored at every decision date because a speaker dropout at T-2 weeks is a different risk from the ...
|
2.2K |
| 8073 | hackathon-mentoring | samber/dev-event-organizer-skills |
Hackathon Mentoring You design the mentor programme for one hackathon edition: how much coverage the field needs, who supplies it, how a stuck team reaches it, what mentors are told before they start, and how coverage rotates across the hacking window. Read the published brief before designing anything. Two things in it drive every menu below: The challenge tracks, which name the expertise that has to be on the floor. The sponsor-integration depth, which measures how hard a promise the event has...
|
2.2K |
| 8074 | event-learning-expedition-design | samber/dev-event-organizer-skills |
Event Learning Expedition Design You take your own audience into somebody else's building, where that organization's working operation is the programme. Two decisions follow, and this skill owns nothing else: how much of your agenda depends on a host you cannot direct, and what the host lets your attendees see and repeat. Read first: the scope is much narrower than the name A "learning expedition" sounds like a whole event format. Inside this collection it is not, and pretending otherwise hands ...
|
2.2K |
| 8075 | event-vip-management | samber/dev-event-organizer-skills |
Event VIP Management You receive a named guest whose visit creates an obligation your general attendee flow cannot absorb, and you do it without building a tier the room can see. Those are two jobs, and the second one is the hard one. Two illustrative shapes: A minister arrives with a protective detail whose requirements you did not write and cannot refuse. A funder your event depends on arrives alone and would rather nobody noticed. Both are yours. Neither is a reason to print a different badge...
|
2.2K |
| 8076 | event-attendee-experience | samber/dev-event-organizer-skills |
Event Attendee Experience You design the day a general attendee actually walks through: getting in the door, finding the room, where to go when the day gets loud, eating, asking, and what they remember. Inputs arrive decided - a signed floor plan, a published grid, a register, an accessibility bar - and the output is a design somebody can execute and audit by walking the building. You add only the attendee-specific layer on top of the population-agnostic fundamentals in samber/dev-event-organize...
|
2.2K |
| 8077 | event-volunteers | samber/dev-event-organizer-skills |
Event Volunteers You staff one edition of an event with people who are not paid to be there. The deliverable is a shift grid where every post the schedule needs standing has a named person and a named backup, and every one of those people has been briefed before their first shift. The workforce you design is downstream of two documents you do not own: The run of show - says what has to happen at every hour. The code of conduct - says who a report can reach. Read both before counting anybody. Nev...
|
2.2K |
| 8078 | event-speaker-cold-outreach | samber/dev-event-organizer-skills |
Event Speaker Cold Outreach You write the invitation and run it to an answer. Your input is the packet samber/dev-event-organizer-skills@event-speaker-sourcing hands you - ranked candidates, the evidence-backed "why" behind each name, a Hot/Warm/Cold/Skip score, availability and travel constraints, the honest budget line, the contact route, and the invited-review lane. Your output is a confirmed speaker with terms agreed in writing, or a recorded no. This skill's boundaries: Not sourcing or qual...
|
2.2K |
| 8079 | startup-pitch-contest | samber/dev-event-organizer-skills |
Startup Pitch Contest You design and run a pitch contest: a demo day, a startup showcase, a pitch competition, held inside a larger technical event. It covers: Who gets on the stage. What they do once they are on it. Who judges, and on what. What a judge may do afterwards with a company they just watched. What the winner actually receives. No build phase A hackathon judges an artifact assembled inside the event, in a room the judges can walk into. You judge a company that existed before anyone a...
|
2.2K |
| 8080 | hybrid-event-design | samber/dev-event-organizer-skills |
Hybrid Event Design You design the programme and the staffing for an event with two audiences at once: one in the room, one watching from elsewhere. The format decision arrives made. Never reopen it. This skill is deliberately narrow, and the reason matters Siblings already own most of what a hybrid event needs. The scope left over is small. Say so rather than expanding into their territory: samber/dev-event-organizer-skills@event-format-selection decides whether hybrid happens at all and owns t...
|
2.2K |
| 8081 | event-attendee-email-sequences | samber/dev-event-organizer-skills |
Event Attendee Email Sequences You design and write the emails a technical event sends its attendees. Your inputs arrive fixed from siblings: the campaign calendar and email's channel weight from samber/dev-event-organizer-skills@event-marketing-plan , the early-bird and price-tier cutoffs from samber/dev-event-organizer-skills@event-ticket-pricing , and the on-site facts from samber/dev-event-organizer-skills@event-attendee-experience . Your output is a dated send map plus the copy for every em...
|
2.2K |
| 8082 | event-side-event-coordination | samber/dev-event-organizer-skills |
Event Side Event Coordination You decide what happens when somebody who is not you runs an event inside your event's dates or venue orbit: whether you approve it, whether you list it, what they may call it, when it may run, and what you say you are not responsible for. The default answer is often nothing at all. Most community events never formalise this and are right not to. Decide deliberately once, rather than at T-2 weeks when a poster carrying your logo turns up in a bar. What you own, and ...
|
2.2K |
| 8083 | event-first-edition | samber/dev-event-organizer-skills |
Event First Edition You are a launch strategist for technical events. Take an organizer from "we decided to do this" to doors-open on edition 1: the smallest edition worth running, the first team, the reverse timeline, and the risks specific to an event nobody has heard of yet. This skill assumes demand is already validated - that the event should exist. If the user hasn't tested demand, stop and route to samber/dev-event-organizer-skills@event-market-fit first. Proven demand and a right-sized e...
|
2.2K |
| 8084 | hackathon-judging | samber/dev-event-organizer-skills |
Hackathon Judging You design how a hackathon decides who won: the rubric, the scale, who scores what, how scores combine, how ties break, how conflicts of interest resolve, and how the result is announced and challenged. Two inputs arrive already decided. Consume them, never re-open them: The demo/judging structure (Expo Table, Stage Pitch, Video Only, or the two-stage hybrid) belongs to samber/dev-event-organizer-skills@event-format-selection . It fixes per-team judge-contact time, live or asyn...
|
2.2K |
| 8085 | okx-activity | okx/onchainos-skills |
OKX Activity — registration & participation for OKX campaign activities Each activity's flow, CLI reference, FAQ, and gates live in this skill's references/ behind an <activity>-*.md prefix. This SKILL.md routes only — no templates, no CLI flags, no per-activity copy — so adding an activity never changes the rules of an existing one. Pre-flight Checks Before your first onchainos command, read ../okx-agentic-wallet/_shared/preflight.md once. If it does not exist, read _shared/preflight.md instead...
|
2.1K |
| 8086 | to-issues | vinvcn/mattpocock-skills-zh-cn |
To Issues Break a plan into independently-grabbable GitHub issues using vertical slices (tracer bullets). Process 1. Gather context Work from whatever is already in the conversation context. If the user passes a GitHub issue number or URL as an argument, fetch it with gh issue view <number> (with comments). 2. Explore the codebase (optional) If you have not already explored the codebase, do so to understand the current state of the code. 3. Draft vertical slices Break the plan into tracer bullet...
|
2.1K |
| 8087 | design-an-interface | vinvcn/mattpocock-skills-zh-cn |
Design an Interface Based on "Design It Twice" from "A Philosophy of Software Design": your first idea is unlikely to be the best. Generate multiple radically different designs, then compare. Workflow 1. Gather Requirements Before designing, understand: What problem does this module solve? Who are the callers? (other modules, external users, tests) What are the key operations? Any constraints? (performance, compatibility, existing patterns) What should be hidden inside vs exposed? Ask: "What doe...
|
2.1K |
| 8088 | qa | vinvcn/mattpocock-skills-zh-cn |
QA Session Run an interactive QA session. The user describes problems they're encountering. You clarify, explore the codebase for context, and file GitHub issues that are durable, user-focused, and use the project's domain language. For each issue the user raises 1. Listen and lightly clarify Let the user describe the problem in their own words. Ask at most 2-3 short clarifying questions focused on: What they expected vs what actually happened Steps to reproduce (if not obvious) Whether it's con...
|
2.1K |
| 8089 | edit-article | vinvcn/mattpocock-skills-zh-cn |
First, divide the article into sections based on its headings. Think about the main points you want to make during those sections. Consider that information is a directed acyclic graph, and that pieces of information can depend on other pieces of information. Make sure that the order of the sections and their contents respects these dependencies. Confirm the sections with the user. For each section: 2a. Rewrite the section to improve clarity, coherence, and flow. Use maximum 240 characters per p...
|
2.1K |
| 8090 | obsidian-vault | vinvcn/mattpocock-skills-zh-cn |
Obsidian Vault Vault location /mnt/d/Obsidian Vault/AI Research/ Mostly flat at root level. Naming conventions Index notes : aggregate related topics (e.g., Ralph Wiggum Index.md , Skills Index.md , RAG Index.md ) Title case for all note names No folders for organization - use links and index notes instead Linking Use Obsidian [[wikilinks]] syntax: [[Note Title]] Notes link to dependencies/related notes at the bottom Index notes are just lists of [[wikilinks]] Workflows Search for notes Search ...
|
2.1K |
| 8091 | request-refactor-plan | vinvcn/mattpocock-skills-zh-cn |
This skill will be invoked when the user wants to create a refactor request. You should go through the steps below. You may skip steps if you don't consider them necessary. Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions. Explore the repo to verify their assertions and understand the current state of the codebase. Ask whether they have considered other options, and present other options to them. Interview the user about the im...
|
2.1K |
| 8092 | local-election-candidate-search | nomadamas/k-skill |
Local Election Candidate Search What this skill does 중앙선거관리위원회(NEC) 선거통계시스템의 공개 통합검색에서 후보자 이름을 조회하고, 지방선거 관련 후보자 이력만 기본으로 정리한다. 후보자명, 한자명, 생년월일/성별, 선거일, 선거명, 선거종류, 정당, 선거구, 득표, 직업, 학력, 경력 등을 반환한다. When to use 사용자가 “지방선거 후보”, “시도지사 후보”, “기초의원 후보”, “교육감 후보” 등을 이름/지역/선거일 기준으로 찾아 달라고 할 때 중앙선관위 선거통계시스템에서 공개된 후보자 이력을 확인해야 할 때 동명이인이 있을 수 있어 후보자명 + 선거종류/지역/연도 필터가 필요한 때 Public access path Chosen path: NEC integrated candidate search. Show more Installs 463 Repository nomadamas/k-skill GitHub Stars 5.4K F...
|
2.1K |
| 8093 | writing-great-skills | vinvcn/mattpocock-skills-zh-cn |
A skill exists to wrangle determinism out of a stochastic system. Predictability — the agent taking the same process every run, not producing the same output — is the root virtue; every lever below serves it. Bold terms are defined in GLOSSARY.md ; look them up there for the full meaning. Invocation Two choices, trading different costs: A model-invoked skill keeps a description , so the agent can fire it autonomously and other skills can reach it (you can still type its name too). It contributes...
|
2.1K |
| 8094 | ubiquitous-language | vinvcn/mattpocock-skills-zh-cn |
Ubiquitous Language Extract and formalize domain terminology from the current conversation into a consistent glossary, saved to a local file. Process Scan the conversation for domain-relevant nouns, verbs, and concepts Identify problems : Same word used for different concepts (ambiguity) Different words used for the same concept (synonyms) Vague or overloaded terms Propose a canonical glossary with opinionated term choices Write to UBIQUITOUS_LANGUAGE.md in the working directory using the format...
|
2.1K |
| 8095 | cli-mastery | github/awesome-copilot |
Copilot CLI Mastery UTILITY SKILL — interactive Copilot CLI trainer. INVOKES: ask_user , sql , view USE FOR: "cliexpert", "teach me the Copilot CLI", "quiz me on slash commands", "CLI cheat sheet", "copilot CLI final exam" DO NOT USE FOR: general coding, non-CLI questions, IDE-only features Routing and Content Trigger Action "cliexpert", "teach me" Read next references/module-N-*.md , teach "quiz me", "test me" Read current module, 5+ questions via ask_user "scenario", "challenge" Read reference...
|
2.1K |
| 8096 | antfu-design | antfu/skills |
Use this when building interfaces with UnoCSS in any framework (React, Vue, Svelte, Solid, or plain HTML), from dense devtools panels to landing pages. Read core-design-read first to set the direction, then apply the token system plus the polish and anti-slop rules. Core Rules Use semantic shortcuts ( bg-base , border-base , color-active , btn-action ) instead of raw utility chains in markup. Design light and dark mode together. Core tokens must work in both themes. Name z-index layers ( z-top-n...
|
2.1K |
| 8097 | experience-ui-bundle-localize | forcedotcom/sf-skills |
Localize a React UI Bundle Walk a developer through localizing a React UI Bundle: detect hardcoded user-facing strings, extract them into Salesforce Custom Labels, wire up i18next over the Platform SDK GraphQL backend, and verify labels render across locales. This file is the workflow + guardrail spine . Depth lives in linked docs: references/i18n-setup.md : the two files you write: the i18next init and the label manifest references/label-xml.md : Custom Labels and translation metadata XML shape...
|
2.1K |
| 8098 | cc-skill-security-review | sickn33/agentic-awesome-skills |
Security Review Skill This skill ensures all code follows security best practices and identifies potential vulnerabilities. When to Use Implementing authentication or authorization Handling user input or file uploads Creating new API endpoints Working with secrets or credentials Implementing payment features Storing or transmitting sensitive data Integrating third-party APIs Security Checklist 1. Secrets Management Show more Installs 1.9K Repository sickn33/agentic…e-skills GitHub Stars 45.1K Fi...
|
2.1K |
| 8099 | python-backend | jiatastic/open-python-skills |
python-backend Production-ready Python backend patterns for FastAPI, SQLAlchemy, and Upstash. When to Use This Skill Building REST APIs with FastAPI Implementing JWT/OAuth2 authentication Setting up SQLAlchemy async databases Integrating Redis/Upstash caching and rate limiting Refactoring AI-generated Python code Designing API patterns and project structure Core Principles Async-first - Use async/await for I/O operations Type everything - Pydantic models for validation Dependency injection - Use...
|
2.1K |
| 8100 | sentry-php-sdk | getsentry/sentry-for-ai |
All Skills > SDK Setup > PHP SDK Sentry PHP SDK Opinionated wizard that scans your PHP project and guides you through complete Sentry setup. Invoke This Skill When User asks to "add Sentry to PHP" or "setup Sentry" in a PHP app User wants error monitoring, tracing, profiling, logging, metrics, or crons in PHP User mentions sentry/sentry , sentry/sentry-laravel , sentry/sentry-symfony , or Sentry + any PHP framework User wants to monitor Laravel routes, Symfony controllers, queues, scheduled task...
|
2.1K |