Loading…
Showing 7141–7170 of 10180 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| book-skills-creatorTire-C/book-skills-creatorTurn explicitly selected sources into a planned, modular, evidence-linked Agent Skill pack with atomic skills, combo workflows, routing, references, and validation. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| outreach-conductormariagorskikh/outreach-conductorRuns a weekly outbound cycle end to end, on its own. Finds candidate companies that match your ICP, verifies the company, the website and the right person, researches each person, dedupes against your CRM, sent mail and drafts, writes personalized emails in your own voice, runs a self-review gate, sends them from your own mailbox in daily batches inside your caps (or creates drafts if no sender is configured), ranks a short list of LinkedIn connection requests, logs everything to your CRM, and learns from last week's reply rates. Asks setup questions once; after that it only asks before spending money. Uses parallel subagents and a resumable state folder per week. Use when the user says "weekly outreach", "run the outreach cycle", "this week's prospects", "find, verify and draft", "build this week's outbound", "prospect and email", "outbound conductor", or asks for a full week of researched prospects, emails and LinkedIn connects. | Stars: 7 | Updated | Claude CodeCodex | Verified | Install |
| skf-quick-skillarmelhbobdad/oh-my-skillsFast skill from a package name or GitHub URL — no brief needed. Use when the user requests a "quick skill" or "skill from URL" or "skill from package." | Stars: 7 | Updated | Claude CodeCodex | Unverified | Install |
| image-skillbookAlbertAZ1992/image-skillbookCompare Image Skillbook treatments and route an image request to the most suitable installed style Skill. Use when the user wants help choosing an AI photo treatment, wants several styles compared, or names Image Skillbook without choosing a style. Do not use for ordinary image conversion or when a specific style Skill is already named. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| pelagornis-skill-authoringpelagornis/styleguideCreate, review, or improve portable Agent Skills using the Pelagornis conventions and the open Agent Skills specification. Use when adding or maintaining a reusable agent workflow. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| patentradaryuc16/PatentRadar专利侵权竞品分析 skill。输入专利公开号(CN/US/EP/JP 等),输出可人工复核的 markdown 竞品分析报告。工作流:拆解权利要求 → 搜索市场竞品 → 抓证据(含图像)→ 全部权利要求逐特征对比 → 生成报告。触发词:专利侵权分析、专利竞品、claim chart、专利公开号、CN/US/EP/JP 专利号、专利对比、技术特征对比、专利保护范围、侵权风险评估。不适用:专利申请文书撰写、专利无效宣告、知识产权法律咨询、专利诉讼策略。 | Stars: 71 | Updated | Claude CodeCodex | Verified | Install |
| poteto-mode0xrsydn/pstack-pipoteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style. | Stars: 7 | Updated | Claude CodeCodex | Verified | Install |
| principle-build-the-lever0xrsydn/pstack-piApply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun. | Stars: 7 | Updated | Claude CodeCodex | Verified | Install |
| teach0xrsydn/pstack-piExplain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'. | Stars: 7 | Updated | Claude CodeCodex | Verified | Install |
| subagent-promptexistential-birds/beagleProduce a comprehensive prompt that hands off the current session's work to a fresh session for sub-agent-orchestrated execution. Use when the user wants to execute discussed/planned work in a new session, run a job to completion via sub-agents, or generate a portable handoff prompt with per-task verification. Assumes the target session supports sub-agents. Triggers on "subagent-prompt", "give me a prompt to run this in a new session", "hand this off to sub-agents", "execute this with sub-agents". | Stars: 88 | Updated | Claude CodeCodex | Verified | Install |
| camera1-to-cameraxinehemiasm/AiAssistantUse this skill to migrate legacy Android camera implementations (Camera1 or raw Camera2 APIs) to CameraX. CameraX is a lifecycle-aware Jetpack library built on top of Camera2 that resolves camera rotation issues and handles device dependencies. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| pace-sharemohamedzhioua/agentpacePreviews the exact agentpace rows a user could contribute to the open dataset. Use only when the user explicitly runs /pace-share or asks to share or contribute their runs. Never start this on your own. | Stars: 7 | Updated | Claude CodeCodex | Verified | Install |
| dev-event-kickoffsamber/dev-event-organizer-skillsBefore answering any event-organizing request that opens a new project or a new session, run this router first - it maps the task onto the 72-skill samber/dev-event-organizer-skills collection, or says plainly that none fits, and bootstraps or resumes the project's shared context so the next session starts warm. This fires on a conversational state, not on a subject - invoke it at every event project start even when the collection's skills are already in daily use on another event, at every recurring check-in on the same project, and whenever routing between siblings is unclear. Covers conference, meetup and hackathon kickoffs, "which event skill do I need", "where do I start organizing this event", event organizer skill routing, and recurring event check-ins. Use this whenever someone describes an event-organizing problem without naming a skill, even if they never say "kickoff", "routing" or "start". | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| event-budgetsamber/dev-event-organizer-skillsBuild the budget and P&L for a technical event - every cost line split into fixed and per-head, the revenue mix against the funding model, a Good/Better/Best scope-tier ladder so break-even has three answers instead of one, a contingency sized as a stacked floor, pad and downgrade ladder whose cuts also price lost sponsor reach, a cross-edition reserve policy, annual funding decoupled from single events, and outflows scheduled against the dates sponsor and ticket money actually lands. Use whenever asked to build an event budget, model conference or hackathon costs, find break-even, size a contingency reserve, set a reserve or surplus policy across editions, fund a recurring meetup series annually, plan event cash flow, or decide what to cut when revenue falls short. Consumes prices and real vendor quotes, never sets them. Do NOT use to set ticket or sponsor prices - use samber/dev-event-organizer-skills@event-ticket-pricing or samber/dev-event-organizer-skills@event-sponsor-pricing. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| event-community-buildingsamber/dev-event-organizer-skillsAnimate one recurring technical event's own audience in the gaps between editions - the cadence posture for the standing space, the conversion of attendees into returning participants and contributors, keeping a local cohort of the same event's fans warm, and handing the community asset over when organizers change. Use whenever asked how to keep an event's community alive between editions, what to post in the quiet months, whether a between-editions space should stay dormant or be programmed, how to make attendees come back next year, or who takes over the community platform when an organizer leaves. Do NOT use to decide whether that space belongs in the team's property set at all - use samber/dev-event-organizer-skills@event-portfolio-strategy. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| event-date-selectionsamber/dev-event-organizer-skillsPick the date a technical event runs on - the decision every other plan hangs off. Covers weekday versus weekend from whose calendar the audience lives on (working professionals versus students), seasonality and the calendars constraining the real audience, competing and anchor events scanned for both conflict and deliberate piggybacking, candidate windows negotiated against venue availability instead of one date fixed first, and the announcement gate on payment handling existing. Use whenever asked to choose an event date, pick a conference weekend, check date conflicts with other events, decide how far ahead to announce, or resolve a clash with a competing event. Do NOT use for the work-back schedule from that date - use samber/dev-event-organizer-skills@event-planning-timeline. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| event-debriefsamber/dev-event-organizer-skillsRun the organizing team's own internal retrospective on one finished edition of a technical event - the blameless frame, the reconstructed timeline, what went well split from what went poorly, what fired reconciled against the risk register, budget plan and run of show, team-health findings, and dated lessons-learned entries each carrying an owner and a due date. Use whenever asked to run a post-event debrief, a post-mortem or a retrospective after a conference, meetup or hackathon, review an edition against the goals the team set, build a lessons-learned log, or publish a public recap. Do NOT use to collect participant feedback - use samber/dev-event-organizer-skills@event-feedback - or for trends across editions - use samber/dev-event-organizer-skills@event-continuous-improvement. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| event-first-editionsamber/dev-event-organizer-skillsLaunch the first edition of a tech event (conference, hackathon, large meetup) from zero - a minimum viable edition 1, scope discipline against the full vision, the first cross-organization team, the decision-to-doors-open reverse timeline, and a pre-mortem of first-edition-specific risks with written go/no-go dates. Use whenever asked to start a new conference or hackathon, plan a first edition, scope a minimum viable event, form a founding organizer team, or set a launch timeline for an event with no track record. Strategy layer for edition 1 only. Do NOT use to validate demand first - use samber/dev-event-organizer-skills@event-market-fit - or to grow an established event - use samber/dev-event-organizer-skills@event-growth-strategy. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| event-growth-strategysamber/dev-event-organizer-skillsGrow an established technical event edition over edition, or decide not to - the demand-headroom read, one discrete lever per edition (venue squeeze, track or day addition, venue step-up, price-led growth), the contract-risk gate on venue moves (deposits, attrition penalties, F&B minimums, long lead times), the pricing posture before scaling, and deliberate non-growth (caps, lotteries, shrinking back down) as a real strategy. Use whenever asked whether a conference or hackathon should grow, how to scale capacity, whether to add a track, a day or a venue, or how to stay small under excess demand. Do NOT use for a first launch - use samber/dev-event-organizer-skills@event-first-edition - or multi-event portfolios - use samber/dev-event-organizer-skills@event-portfolio-strategy. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| event-market-fitsamber/dev-event-organizer-skillsRead whether a technical event's concept, audience and price combination actually meets demand - before launch (community baseline, CFP oversubscription, saturation mapping), mid-sale (checkpoint ladder and pace index against expected sales), and after an edition (attendee return, sponsor renewal, sellout-speed trend) - composed into a go, hold, pivot or stop call. Use whenever asked to validate demand for a conference, hackathon or a meetup-to-conference jump, judge whether ticket sales are on pace, decide whether an event should recur or scale, or diagnose why an edition underperformed. Reads signals only. Do NOT use for launch scoping - use samber/dev-event-organizer-skills@event-first-edition - or growth levers - use samber/dev-event-organizer-skills@event-growth-strategy. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| event-marketing-plansamber/dev-event-organizer-skillsBuild the attendee-acquisition plan for a technical event - audience segments mapped to channels, the campaign-calendar spine (a ticketed event's percent-of-ticket-sales ladder or a free event's percent-of-attendance-goal curve), campaign moments pinned to pricing and program dates fixed elsewhere, budget allocated across the channel mix, funnel targets per phase, and each channel routed to the sibling that executes it. Use whenever asked to plan how to fill an event, run a ticket-sales or registration campaign, choose promotion channels, split promotion budget, or set registration targets by date. Do NOT use for the email copy itself - use samber/dev-event-organizer-skills@event-attendee-email-sequences - or ticket prices - use samber/dev-event-organizer-skills@event-ticket-pricing. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| event-media-partnershipssamber/dev-event-organizer-skillsSet up barter media and community partnerships for a technical event - visibility-for-visibility deals with newsletters, podcasts, online communities and developer-ambassador programs, where no cash changes hands. Covers deal classes, partner types, the exchange format (calendar listing, logo-and-social swap, newsletter mention swap, podcast exchange, full media-partner tier), the deal terms, and both sides' delivery tracking. Use whenever asked to find media partners, set up a community-sponsor tier, trade newsletter mentions or podcast slots for event visibility, or formalize a logo-for-promotion deal. Do NOT use for earned press - use samber/dev-event-organizer-skills@event-press-relations - or swaps with other events - use samber/dev-event-organizer-skills@cross-event-promotion. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| event-no-show-managementsamber/dev-event-organizer-skillsReduce and absorb no-shows at a technical event - an overbooking ratio against the room's real capacity and a stated ceiling, the waitlist and what triggers a promotion off it, the day-of walk-in lane, and the expected-show-up number handed to catering instead of the registration count. Use whenever asked how many registrations to accept for a free event, whether to overbook, how to run an event waitlist, why half the RSVPs did not turn up, or how many people to order food for. Do NOT use for reminder email copy - use samber/dev-event-organizer-skills@event-attendee-email-sequences - the check-in desk - use samber/dev-event-organizer-skills@event-attendee-experience - or the demand verdict behind a low show-up rate - use samber/dev-event-organizer-skills@event-market-fit. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| event-official-social-programsamber/dev-event-organizer-skillsDecide how many official social occasions a technical event runs and how they sit against each other one occasion, two on separate slots, or a themed multi-activity track - plus the inclusion floor a whole slate must clear rather than each activity separately. Use whenever asked whether to run more than one social activity, whether two social activities can run in the same hours, how to publish a social track, or which activity a caregiver or a non-drinker can be in. Do NOT use for a single occasion's format, food, drink or alcohol posture - use samber/dev-event-organizer-skills@event-hospitality - third-party satellites - use samber/dev-event-organizer-skills@event-side-event-coordination - or invite-only gatherings - use samber/dev-event-organizer-skills@event-vip-social-program. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| event-planning-timelinesamber/dev-event-organizer-skillsBuild the months-long work-back plan for a tech event, any edition - the doors-open anchor date, parallel tracks (venue, program/CFP, sponsors, marketing, ticketing) each worked back from that date, cross-track dependency gates, a buffer policy through latest-safe commitment dates, and replanning checkpoints that cut scope instead of moving the date. Use whenever asked to build an event planning timeline, conference retroplanning, a work-back or reverse schedule, event milestone sequencing, or to replan an event running behind schedule. Scheduling mechanics only. Do NOT use to pick the date itself - use samber/dev-event-organizer-skills@event-date-selection - or for the day-of run of show - use samber/dev-event-organizer-skills@event-run-of-show. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| event-portfolio-strategysamber/dev-event-organizer-skillsShape one organizing team's set of event properties - flagship conference, meetup series, hackathon, podcast or always-on online space - into a portfolio where each one feeds the others. Covers what each property is for, the funnel path between them, cadence collisions against one team and audience, how much brand, audience list, team and sponsors are shared, the allocation posture, add/kill criteria written before they are needed, and the dated change-the-recipe, merge or retire call when attendance falls. Use whenever asked whether to add a second event or format, how a meetup feeds a conference, how to keep momentum between editions, whether to merge overlapping meetups, or which property to retire. Do NOT use for growing one event - use samber/dev-event-organizer-skills@event-growth-strategy - or swaps with other organizers' events - use samber/dev-event-organizer-skills@cross-event-promotion. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| event-positioningsamber/dev-event-organizer-skillsDefine a technical event's positioning - what it stands for, against which alternatives, for which audience identity. Covers the governance axis (community-run, foundation, media-run, vendor-owned), competitive-alternative mapping, best-fit attendee and sponsor segments (and when a conference may serve several targets), the business-oriented layer sponsors buy, market-category strategy (head-to-head, subcategory, new category and its education tax), the positioning statement, contrast-not-attack anti-positioning, and the rebrand gate. Use whenever asked to position a conference, meetup or hackathon, differentiate it from neighboring events, decide who it is for, write a positioning statement, weigh a vendor-neutrality claim, or judge an event rename. Strategy only. Do NOT use for on-site embodiment - use samber/dev-event-organizer-skills@event-cultural-identity. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| event-risk-managementsamber/dev-event-organizer-skillsBuild and maintain the standing risk register for a technical event - risks named by category, scored on a likelihood x impact matrix adapted to a dated one-shot deliverable, split into prevention, contingency or insurance, the insurance stack including the communicable-disease buy-back, internal go/no-go decision dates set against the venue's escalating cancellation-fee curve, and the on-site emergency plan. Use whenever the user mentions event insurance, cancelling or postponing an event, a go/no-go call, an emergency or evacuation plan, weather or speaker-dropout contingency, or a risk register - even if they never say "risk". Not legal or insurance advice. Do NOT use for day-of live incident handling - use samber/dev-event-organizer-skills@event-run-of-show instead. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| event-side-event-coordinationsamber/dev-event-organizer-skillsApprove and coordinate third-party-run satellite events around a technical event - the vetting gate, calendar deconfliction against the published grid, name and logo usage rules, and the disclaimer stating what the main event does not vouch for. Use whenever a user group, sponsor or attendee wants to run a party, meetup, dinner, workshop or afterparty during the event's dates, when someone is already using the event's name on their own page, or when fringe events collide with the main programme - even if they never say "side event". Approving nothing is often the right answer; routes trademark and liability exposure to counsel. Do NOT use for the organizer's own evening programme - use samber/dev-event-organizer-skills@event-official-social-program instead. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| event-speaker-cold-outreachsamber/dev-event-organizer-skillsWrite and sequence the cold invitation to a speaker a shortlist already picked - the message, not the search. Covers what a first invitation must disclose up front (event basics, honest budget and travel terms, the answer deadline, how you found them), personalization built from the shortlist's own "why", ranked first-touch channels, follow-up cadences that add a new angle instead of bumping, and the fee conversation where speakers have no rate card. Use whenever the user mentions writing a speaker invitation, pitching a keynote candidate, following up on an unanswered invitation, or a speaker who asks for a fee - even if they never say "outreach". Do NOT use to find or qualify candidates - use samber/dev-event-organizer-skills@event-speaker-sourcing instead. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |