Skill-uri pentru agenți pe care le poți verifica înainte să le instalezi
Skill-uri SKILL.md publice din depozite GitHub cu peste 50 de stele și de la producători, scanate și evaluate. Instalează oricare dintre ele cu o singură comandă în Claude Code, Cursor, Codex, GitHub Copilot sau Gemini CLI.
49.492 de skill-uri din 2.391 de depozite · actualizat acum 17 ore
49.492 de skill-uri
- aaai-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical significance, robustness, human evaluation, AI-for-Social-Impact and alignment/safety evidence, compute and cost reporting, and reproducibility-checklist alignment for Phase-1 survival.AlteleFără avertismente★ 1,4 K↓ —
- vis-related-workbrycewang-stanford/Awesome-Journal-SkillsUse when positioning an IEEE VIS submission against the visualization literature across TVCG, the six VIS areas, EuroVis/CGF, PacificVis, and adjacent HCI/graphics venues, writing delta-first contrast rather than a citation catalog, keeping self-citations double-blind when opted in, and handling concurrent, preprint, and prior-version overlap for a TVCG journal article.RedactareFără avertismente★ 1,4 K↓ —
- uai-related-workbrycewang-stanford/Awesome-Journal-SkillsUse when positioning a UAI submission within the probabilistic reasoning, graphical-model, causality, and Bayesian ML literature, covering PMLR archival status of recent UAI volumes, double-blind self-citation discipline, concurrent arXiv and workshop versions, and the cross-community citation coverage UAI reviewers check first.ȘtiințăFără avertismente★ 1,4 K↓ —
- wacv-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing a WACV submission before an OpenReview round deadline, covering the Round 1 vs Round 2 choice, the Applications vs Algorithms track field, the 8-page-including-figures limit, double-blind anonymity and OpenReview-profile requirements, the anonymized supplement, dual submission, and desk-reject triage.PlanificareFără avertismente★ 1,4 K↓ —
- atc-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when drafting or revising an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) systems paper — writing a self-standing two-page extended abstract for the round-one gate, structuring the implementation-and-measurement narrative, reporting costs beside gains, and holding the two-column 12-page budget.RedactareFără avertismente★ 1,4 K↓ —
- acmmm-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning the end-to-end ACM MM (ACM Multimedia) campaign calendar — from thematic-area scoping and track choice, through the April OpenReview abstract/paper/supplement chain, the June anonymous rebuttal, the July decision, the August camera-ready, and the November presentation in Rio, with the right skill invoked at each stage.ProductivitateFără avertismente★ 1,4 K↓ —
- ase-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when deciding what belongs in the 10-page ASE (IEEE/ACM Automated Software Engineering) paper body versus the artifact and supplementary material, splitting content by decision-criticality so nothing that decides acceptance lives outside the reviewed pages under the 10+2 budget.ȘtiințăFără avertismente★ 1,4 K↓ —
- acl-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when organizing appendices and supplementary material for an ACL paper under ACL Rolling Review, covering the mandatory Limitations and optional ethics sections, appendices after references, anonymized software and data archives, the no-cloud-links rule, and deciding what must stay in the 8-page or 4-page body.ȘtiințăFără avertismente★ 1,4 K↓ —
- acl-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when revising an ACL paper for computational-linguistics house style, covering task-first framing, linguistic examples tied to quantitative error analysis, scoping language claims to tested languages, LLM-era claim discipline, anonymous self-reference, Limitations prose, and compressing into the 8-page or 4-page ACL format.RedactareFără avertismente★ 1,4 K↓ —
- ase-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when shaping the prose and structure of an ASE (IEEE/ACM Automated Software Engineering) research paper, covering the automation-first first-page arc, stating the automated task precisely, keeping the tool runnable and the model-swap test in mind, threats-as-argument, and the 10+2 page discipline on the ACM acmart template.RedactareFără avertismente★ 1,4 K↓ —
- colm-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the empirical core of a COLM paper — contamination analysis for evaluation data, fair baselines under matched prompting and compute, pinned model versions and decoding parameters, uncertainty over runs and samples, scaling coverage, and honest reporting of API-model comparisons.ȘtiințăFără avertismente★ 1,4 K↓ —
- chi-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when drafting or revising the prose of an ACM CHI paper — contribution statements, structure for mixed reviewer audiences, participant voice, calibrated claims, accessible and bias-free writing, and length discipline in a venue that reviews words against contribution instead of pages.RedactareFără avertismente★ 1,4 K↓ —
- colt-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when deciding whether a COLT (Conference on Learning Theory) paper needs numerical content at all — COLT has no experiments requirement — and, when numerics genuinely help, designing small illustrative simulations that visualize a proved bound, a separation, or a phase transition without diluting the theory.MediaFără avertismente★ 1,4 K↓ —
- cikm-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the empirical program of a CIKM paper — matching evidence to the claim's lanes across retrieval, mining, and knowledge-management evaluation cultures, choosing datasets and baselines that survive a blended panel, isolating the boundary mechanism, and meeting applied-track deployment-evidence bars.DevOpsFără avertismente★ 1,4 K↓ —
- cav-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when revising a CAV (Computer Aided Verification) paper for a precise verification contribution on the first page, an explicit soundness/completeness statement, theorem-and-proof discipline in the LNCS page budget, fair benchmark claims, honest scope and limits, and double-blind wording for the anonymized categories.RedactareFără avertismente★ 1,4 K↓ —
- motion-formatsNouhashgraph-online/awesome-codex-pluginsSeven complete motion formats, each with a beat structure in seconds, a shot list and presets: a found-footage analog-horror trailer of a website, an authentic VHS bouncing-logo screensaver, a pixel-art runner on a CRT, a wordmark with a wave running through it, a one-shot music video that follows a DAW timeline, a launch trailer for an import feature, and a kinetic lyric video. Values come from VHS signal models (ntsc-rs, Finn McKenty), pixel-art conventions (Pedro Medeiros, Slynyrd), School of Motion, Netflix timing rules, screenlife rules and launch-film designers on X. Use when someone asks for one of these formats, a VHS or analog-horror look, a pixel art animation, a lyric video or a beat-synced launch video. NOT for generating the song or footage (varg-ai, varg-music-video).MediaFără avertismente★ 1,5 K↓ —
- dispute-lettermohitagw15856/pm-claude-skillsWrite a letter to dispute an incorrect charge, bill, or record. Use when asked to dispute a credit-card charge, contest a bill or invoice, challenge a credit-report error, or formally dispute a fee. Produces a clear dispute letter — what's being disputed, why it's wrong, the evidence, and the correction requested — in the firm, paper-trail tone these situations need.ȘtiințăFără avertismente★ 1,5 K↓ —
- improve-architecturedaveebbelaar/bamaArchitecture check-in for a growing macOS Swift codebase. Finds hot spots, proposes deeper modules, and refactors one step per commit with behavior proven unchanged. Use at the end of a milestone, before a big feature, when a file passes 600 lines, when one feature touches many files, when bugs repeat in one area, or when the user asks to refactor or clean up the code.PlanificareFără avertismente★ 1,5 K↓ —
- content-optimizationkostja94/marketing-skillsWhen the user wants to optimize content for SEO—word count, H2 keywords, keyword density, multimedia, tables, lists. Also use when the user mentions "content length," "word count," "keyword stuffing," "H2 keywords," "keyword density," "tables," "bullet points," or "content structure." For keywords, use keyword-research.ȘtiințăFără avertismente★ 1,1 K↓ —
- email-to-tasksmohitagw15856/pm-claude-skillsConvert an email (or a whole thread) into real tasks — the actual asks extracted from the prose, each with owner, deadline, and the done-test, so nothing lives in the inbox as its own reminder. Use when asked what am I actually being asked to do here, turn this thread into a task list, extract the action items from this email, or I keep re-reading this thread. Produces the ask extraction with quoted sources, the task list in owner-verb-deadline form, and the reply that confirms the commitments.ProductivitateFără avertismente★ 1,5 K↓ —
- design-from-appdaveebbelaar/bamaRebuild the look of an app the user likes as a native SwiftUI design kit, by measuring its screenshots (sizes, spacing, type, colors, icons), building its parts, and comparing pixel by pixel until they match. Use when the user names an app whose look they want, shares screenshots of one, or says "make it look like X".DesignFără avertismente★ 1,5 K↓ —
- layout-griddaveebbelaar/bamaGrid and alignment rules for a macOS SwiftUI app, with three checks that catch misalignment (a lint for off-grid numbers, a layout probe that measures real frames in snapshot mode, and a grid overlay). Use when building or reviewing a custom page, card, row, form, or sheet, after every build that touched layout, or when the user says something looks misaligned, crooked, cramped, or unevenly spaced.AlteleFără avertismente★ 1,5 K↓ —
- test-mac-appdaveebbelaar/bamaTest a macOS app at three levels, from Swift Testing unit tests and an in-app self-test to a debug bridge that lets an agent drive the running app and read its state, plus computer use for real clicks. Use when adding logic, fixing a bug, before a release, or when the user asks for tests, end-to-end checks, or "make sure it works".TestareFără avertismente★ 1,5 K↓ —
- minutes-briefsilverstein/minutesFast non-interactive briefing before any meeting — auto-detects your next calendar event, pulls relationship history, surfaces open commitments, and produces a one-page brief in under 30 seconds. Use this whenever the user says "brief me", "give me a quick brief", "what's coming up", "background on my next call", "who am I meeting next", "brief me on Sarah", "I have a call in 10 min", "quick rundown", or right before walking into a meeting. Different from /minutes-prep — brief is the fast hook-fireable version that doesn't ask questions and doesn't set goals. Use brief when speed matters; use prep when the user wants to think hard about goals first.ProductivitateFără avertismente★ 1,6 K↓ —Apare și în 1 alt depozit
clean-gone-branches
fcakyon/claude-codex-settings
AlteleActualizat ieri
De la autor
This skill should be used when user asks to "clean gone branches", "remove deleted local branches", "prune branches removed from remote", or explicitly invokes "clean-gone-branches".
Instalare
npx skills add fcakyon/claude-codex-settings --skill clean-gone-branches -a claude-code
Se instalează în .claude/skills/clean-gone-branches/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Descarcă .zip
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
La ce are acces
Doar instrucțiuniNu am văzut acces la rețeaLicență: APACHE-2.0
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 88
Securitate100
Proveniență77
Întreținere100
Licență100
Adopție50
Fișiere (1)
- SKILL.md