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 7 ore
49.492 de skill-uri
- focs-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when deciding whether and how computation appears in a FOCS (IEEE Symposium on Foundations of Computer Science) paper — a venue that accepts on theorems with no evaluation section expected — covering machine-verified case analyses, computer-discovered constructions, and honest illustrative plots.MediaFără avertismente★ 1,4 K↓ —
- code-review-webrampstackco/claude-skillsReview web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug, build error, broken, not working, why is X failing, check this code, security check, PR review, audit code, refactor. Also triggers when investigating 4xx or 5xx errors, deploy failures, environment variable issues, and CMS integration problems.InginerieFără avertismente★ 1 K↓ —
- hri-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when planning the supplementary materials for an ACM/IEEE HRI full paper — above all the video figure that shows the embodied interaction, plus study instruments, extended results, and appendices — deciding what a reviewer must see to judge the interaction versus what belongs outside the 8-page body, all anonymized for double-blind review.MediaFără avertismente★ 1,4 K↓ —
- fse-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when deciding what belongs in an ESEC/FSE paper body versus its anonymized artifact and appendices, covering the ACM-template page budget, the rule that decision-critical evidence stays inside the reviewed pages, double-anonymous supplementary material, and how to split an empirical-SE paper between body and package.ȘtiințăFără avertismente★ 1,4 K↓ —
- cvpr-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the experimental program of a CVPR paper, covering benchmark and baseline selection under matched-compute fairness, the ablation study reviewers treat as mandatory, qualitative and failure-case evidence, efficiency metrics tied to the Compute Reporting Form, and generalization tests beyond a single dataset.TestareFără avertismente★ 1,4 K↓ —
- dac-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when drafting or tightening the prose of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the QoR-forward first-page arc, stating the design-automation contribution as a measured delta, fitting a complete argument into six double-column pages plus a references-only page, building column-width EDA figures, and third-person self-citation for double-blind review.RedactareFără avertismente★ 1,4 K↓ —
- readme-writermohitagw15856/pm-claude-skillsWrite a clear, well-structured README for a software project or open-source repo. Use when asked to write or improve a README, document a project, or make a repo approachable. Produces a complete README — one-line pitch, badges, quickstart, usage, install, contributing, license — that gets someone from landing to running fast.RedactareFără avertismente★ 1,5 K↓ —
- eacl-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the empirical evidence for an EACL paper, covering tuned and LLM baselines, multilingual breadth matched to the claim, significance and variance floors, human-evaluation agreement, data-contamination controls, ablations, and error taxonomies, so that every stated result is measured rather than asserted.ȘtiințăFă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↓ —
- 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↓ —
- 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↓ —
- 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↓ —
- 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↓ —
- 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↓ —
- 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↓ —
- 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↓ —
- 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↓ —
- 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↓ —
- 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↓ —
- 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↓ —
- 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↓ —
- 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↓ —
- uist-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when performing the final pre-upload audit of a UIST paper in PCS — the abstract-then-paper deadline pair, 10-page/5-page two-column limits with desk-reject enforcement, anonymous acmart options, video-figure and supplementary uploads, the prior-work overlap rule, and deadline-week sequencing.MediaFără avertismente★ 1,4 K↓ —
- vldb-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing a PVLDB submission before a monthly deadline, covering the mandatory abstract on the 25th, the CMT window, the 1st-of-month 5:00 PM Pacific cutoff, category and page-budget choice, single-blind cover-page requirements, the per-month and per-year author caps, and desk-reject hazards specific to VLDB.PlanificareFără avertismente★ 1,4 K↓ —
debugging-ci-failures
amplifthq/openmeld
InginerieActualizat acum 13 ore
De la autor
Debugs failing GitHub Actions CI runs for PostHog PRs, commits, and branches, and answers broad CI-health questions ("is CI red?", "is master green today?", "what's broken right now?"). Use when the user asks why CI is red, asks for the current CI or master status, or mentions a failing check, GitHub Actions run, Depot runner, workflow, job, shard, merge queue kick, flaky test, lint failure, typecheck failure, snapshot diff, migration check, generated types drift, or skills build failure. Start with the `hogli ci:insights` digest (cross-run CI history from engineering analytics), then guides read-only inspection, failure classification, smallest local reproduction with hogli, and safe reporting without rerunning CI or posting to GitHub. Running unattended as the "Master-red diagnosis" workflow: see references/master-red-incident.md.
Instalare
npx skills add amplifthq/openmeld --skill debugging-ci-failures -a claude-code
Se instalează în .claude/skills/debugging-ci-failures/ · 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ță: MIT
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 88
Securitate100
Proveniență78
Întreținere100
Licență100
Adopție51
Fișiere (5)
- LICENSE
- SKILL.md
- UPSTREAM.json
- references/master-red-incident.md
- references/master-red-workflow-setup.md