SKILL-RADAR · GITHUB
Nützliche Agent Skills nach echter Nutzung sortiert
Vergleiche verifizierte Skills aus öffentlichen Repositories nach Aufgabe, Paketinhalt, Installationen und nachvollziehbarer Quelle.
- KATALOGUMFANG
- VERIFIZIERT
- Skills
- 15.606
- Repositories
- 2526
- zuletzt synchronisiert
- 12.10.2026
flutterdart-setup-ffi-assets
Guides agents in compiling and packaging C/C++ source code into dynamic or static libraries (Code Assets) using Dart's Native Assets hook system (via hook/build.dart and hook/link.dart utilizing package:hooks and package:nativetoolchainc). Use when a user asks to: 'setup native assets', 'compile C/C++ source code', 'bundle dynamic libraries', 'build native C code', 'link native assets', 'implement build.dart or link.dart hooks', or 'integrate C/C++ interop in Dart/Flutter'. Helps agents avoid ma
- Installationen
- 8
- GitHub Stars
- 3042
- Aktualisiert
- 5. Okt.
flutterdart-use-doc-examples
How to inject external code examples into Dartdoc using the {@example} directive, and how to filter those files using hide, region, and endregion tags.
- Installationen
- 8
- GitHub Stars
- 3042
- Aktualisiert
- 5. Okt.
flutterdart-use-ffigen
Guide agents to use package:ffigen to automatically generate FFI bindings instead of writing them manually. Use this skill when a task involves writing new FFI bindings, extending C/Objective-C/Swift integrations, or replacing hand-crafted dart:ffi setups.
- Installationen
- 8
- GitHub Stars
- 3042
- Aktualisiert
- 5. Okt.
flutterdart-use-path-package
- Cross-platform file and directory path manipulation, segment splitting, extension extraction, and context conversion using package:path and package:file. Use when writing, inspecting, joining, splitting, or refactoring file paths, directory names, or extensions, or replacing raw string path operations (.split('/'), '$dir/$file', .endsWith('.ext'), .replaceAll('\\', '/')). Don't use for HTTP network URI routing, database query strings, or non-path string processing.
- Installationen
- 8
- GitHub Stars
- 3042
- Aktualisiert
- 5. Okt.
expoexpo-project-structure
Folder structure for a new Expo app. Use when scaffolding or laying out a new Expo project with Expo Router, or deciding where a file should live in one. For new projects only — never restructure an existing app to match.
- Installationen
- 8
- GitHub Stars
- 2684
- Aktualisiert
- 7. Okt.
samberevent-vip-management
Receive named guests who are neither speaking nor sponsoring but whose presence creates escort, protocol, security or discretion obligations the general attendee flow cannot absorb - public officials, dignitaries, major funders, executives with no booth duty. Covers the qualification test (obligation, never status), the identification roster, escort depth, and a visibility posture that meets the obligation without building a status tier attendees can read. Use whenever the user mentions receivin
- Installationen
- 8
- GitHub Stars
- 4
- Aktualisiert
- 28. Sept.
samberdev-event-career
Plans a tech-event-organizing career from the candidate side - producer/manager/coordinator roles, and the community-manager-shaped end of the field. States plainly that no universal title ladder exists, gives the one real named ladder and CMX's community-management ladder as the closest dev-event-adjacent counterpart. Covers the volunteer-to-paid entry path, interview prep (portfolio review, scenario questions, CMX's five-competency loop, the paid mini-audit work sample), named practitioner quo
- Installationen
- 8
- GitHub Stars
- 4
- Aktualisiert
- 28. Sept.
samberevent-accessibility-inclusion
Decide which accessibility and inclusion provisions a technical event commits to - the physical, sensory, dietary, economic and digital-access set, at what depth, sized for whom, funded from where - plus the public declaration of it and the data-handling posture for accommodation requests. Use whenever asked what accessibility a conference should offer, whether to caption talks, whether to run a quiet room, childcare or travel grants, how to write an accessibility page, or how to answer an accom
- Installationen
- 8
- GitHub Stars
- 4
- Aktualisiert
- 28. Sept.
samberevent-attendee-experience
Design the general-attendee on-site journey for a technical event - check-in desk and badge pickup, the badge's privacy and scanning posture, wayfinding and signage, the quiet room and other facilities, meal and dietary mechanics, the help path, first-time-attendee orientation, and a walkthrough audit of the finished design. Use whenever asked how to run conference check-in, whether to put a QR code on a badge, where the quiet room goes, how to sign a venue so people find rooms, how to hand out
- Installationen
- 8
- GitHub Stars
- 4
- Aktualisiert
- 28. Sept.
samberevent-first-edition
Launch 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
- Installationen
- 8
- GitHub Stars
- 4
- Aktualisiert
- 28. Sept.
samberevent-growth-strategy
Grow 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
- Installationen
- 8
- GitHub Stars
- 4
- Aktualisiert
- 28. Sept.
samberevent-speaker-sourcing
Find and qualify speakers for a technical event outside the open call for papers - the proactive channel running alongside or instead of a CFP. Covers program gaps worth filling by invitation, sourcing channels (referral asks, expert and speaker directories, prior-talk review, community scouting), international sourcing by region and language, evidence-based Hot/Warm/Cold/Skip qualification, and a ranked shortlist carrying the "why" behind each name. Use whenever the user mentions finding speake
- Installationen
- 8
- GitHub Stars
- 4
- Aktualisiert
- 28. Sept.
samberevent-talk-selection
Run the review and selection process on CFP submissions a technical event already collected - committee composition, how blind review executes (platform hiding versus a dedicated anonymizer role) and what it cannot fix, scoring rubrics, multi-round score-to-shortlist-to-program-fit cascades, conflict-of-interest recusal, diversity and first-time-speaker balancing, acceptance-rate management, and accept/decline/waitlist communication. Use whenever the user mentions a program committee, a talk rat
- Installationen
- 8
- GitHub Stars
- 4
- Aktualisiert
- 28. Sept.
samberhackathon-cash-prize
Structure what a hackathon actually awards - cash versus non-cash medium including no monetary prize at all, total pool size inside the event budget's prizes line, how that pool splits across places and sponsor tracks, and who may legally receive a payout. Use whenever the user mentions hackathon prize amounts, cash versus hardware or credits, splitting a prize pool across tracks, prize eligibility for minors, sponsor employees or cross-border winners, or how winners actually get paid - even if
- Installationen
- 8
- GitHub Stars
- 4
- Aktualisiert
- 28. Sept.
samberhackathon-judging
Design the rubric and the scoring process for judging projects built during a hackathon - evaluation criteria and their weights, the scoring scale, judge coverage and the allocation arithmetic that fits the judging window, cross-judge score normalization, tie-breaking, sponsor and judge conflict-of-interest handling, judge recruitment and briefing, and results announcement including a contested result. Use whenever the user mentions a hackathon judging rubric, criteria weights, how many judges a
- Installationen
- 8
- GitHub Stars
- 4
- Aktualisiert
- 28. Sept.
samberhackathon-mentoring
Design the mentor programme for one hackathon edition - coverage depth sized against the challenge tracks rather than a headcount, recruitment through community and sponsor channels, expertise tagging matched to the brief's tracks and any sponsor API, the request mechanic a stuck team uses to reach a mentor, the mentor briefing including the help-versus-build boundary, and rotation by expertise across shifts. Use whenever the user mentions how many mentors a hackathon needs, recruiting or briefi
- Installationen
- 8
- GitHub Stars
- 4
- Aktualisiert
- 28. Sept.
samberevent-content-repurposing
Turn one edition's already-captured material into derivative published artifacts after the event - which formats get made, on what cadence, under which licence, and what speakers are asked to amplify. Covers publishing latency (dump, batched, drip, evergreen), the rights gate on third-party slide material and attendee photos, and the inventory handed up to the next edition's campaign. Use whenever asked what to do with talk recordings after a conference, how to turn an event into clips, write-up
- Installationen
- 8
- GitHub Stars
- 4
- Aktualisiert
- 28. Sept.
samberevent-debrief
Run 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 ed
- Installationen
- 8
- GitHub Stars
- 4
- Aktualisiert
- 28. Sept.
samberevent-feedback
Design and run participant-feedback collection for one edition of a technical event - what gets asked, who answers it, through which channel, when it goes out, and what goes back to respondents. Covers format-adapted question sets (meetup pulse, conference satisfaction and return intent, hackathon team dynamics, mentors, judging fairness, project continuation), attendee, speaker and sponsor segmentation, in-room versus emailed collection against real response-rate data, survey length, anonymity
- Installationen
- 8
- GitHub Stars
- 4
- Aktualisiert
- 28. Sept.
samberevent-landing-page
Build a technical event's public front door and the small site around it - the page shape for the funding model (a ticketed event's single-CTA hero, or a free event's stats hero with no registration to sell), the section set, a date-gated CTA state machine so Propose renders only during the CFP window and Register only inside the registration window, the accessibility target, and the event structured data. Use whenever asked to build or review a conference, meetup or hackathon website, write the
- Installationen
- 8
- GitHub Stars
- 4
- Aktualisiert
- 28. Sept.
samberevent-no-show-management
Reduce 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 re
- Installationen
- 8
- GitHub Stars
- 4
- Aktualisiert
- 28. Sept.
samberevent-official-social-program
Decide 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 occa
- Installationen
- 8
- GitHub Stars
- 4
- Aktualisiert
- 28. Sept.
samberevent-schedule-design
Lay a technical event's already-selected talks into a published session grid - session-length standardization, room and capacity matching, the four clash types with multi-speaker intersection, break and lunch placement, buffer sizing, keynote and plenary placement as re-sync points, synchronized versus staggered track starts, energy-curve pacing, and speaker travel windows against slot assignment. Use whenever the user mentions building a conference schedule or agenda, a multi-track layout, sess
- Installationen
- 8
- GitHub Stars
- 4
- Aktualisiert
- 28. Sept.
samberevent-sponsor-prospectus
Assemble a technical event's sponsorship prospectus - the published document packaging an existing sponsor value proposition and rate card into a credibility-before-price section anatomy, a checkmark tier table with real disclosed caps, named per-tier perks and add-on packages, an audience-demographics evidence section, and a distribution format (web page or PDF kit) refreshed every edition. Use whenever the user mentions a sponsor deck, a sponsorship kit, a sponsor packages document, a prospect
- Installationen
- 8
- GitHub Stars
- 4
- Aktualisiert
- 28. Sept.