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.
48.168 de skill-uri din 2.325 de depozite · actualizat acum 16 ore
47.055 de skill-uri
- imc-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ACM IMC submission for HotCRP readiness, covering the paper-registration step, the acmart template with BBL upload, the full/short page limits, double-blind anonymity including vantage-point details, the mandatory Ethics section, the artifact-availability declaration, cycle choice, and desk-reject triage before the AoE cutoff.ȘtiințăFără avertismente★ 1,3 K↓ —
- session-reporthoangsonww/Claude-Code-Agent-MonitorGenerate a comprehensive session report with per-model token usage (input, output, cache_read, cache_write including compaction baselines), cost breakdown via the pricing engine, tool invocations, agent hierarchy, compaction events, API errors, turn durations, and thinking block counts. Use when reviewing a specific session or summarizing activity over a date range.PlanificareFără avertismente★ 1,1 K↓ —
- hri-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when preparing the camera-ready of an accepted ACM/IEEE HRI paper — de-anonymizing systematically, completing ACM+IEEE dual-publication metadata (CCS concepts, ORCID, rights/eRights form), delivering every rebuttal promise within the 8-page budget, finalizing the video and de-anonymized archive, and passing production checks.MediaFără avertismente★ 1,3 K↓ —
- icde-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an IEEE ICDE research-track submission for round choice, Microsoft CMT setup, conflict declarations, the IEEE 12-page format, single-blind requirements, supplemental-material availability, the June/November two-round calendar, desk-reject triggers, and final-week sequencing for a data-engineering systems paper.DateFără avertismente★ 1,3 K↓ —
- icalp-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICALP (EATCS) campaign backward from its single annual February deadline, through abstract registration, the anonymous submission, the Track B rebuttal window, the April notification, and the LIPIcs camera-ready and presentation, and when coordinating a full-version (arXiv/ECCC) release alongside the anonymous submission.ProductivitateFără avertismente★ 1,3 K↓ —
- hpca-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an HPCA submission for the two-step July gate on HotCRP, the 11-page main-body limit, the IEEE template, double-blind anonymity plus the all-authors reference rule, the AI-use disclosure, artifact-link scrubbing, and final-week sequencing before the paper deadline.ȘtiințăFără avertismente★ 1,3 K↓ —
- hri-related-workbrycewang-stanford/Awesome-Journal-SkillsUse when writing or auditing the related-work and positioning of an ACM/IEEE HRI full paper — covering HRI's crossing literatures (robotics, HCI, psychology, design), writing a delta-first argument that credits each community, and keeping self-citation compatible with double-blind review.DesignFără avertismente★ 1,3 K↓ —
- facct-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ACM FAccT project timeline from venue fit through abstract registration, OpenReview submission, the rebuttal window, the new Accept/Revise/Reject revise-and-resubmit round, two-round camera-ready, and in-person presentation, with backward-planning offsets for an interdisciplinary responsible-AI paper and honest handling of the single annual deadline.ProductivitateFără avertismente★ 1,3 K↓ —
- fse-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when preparing an accepted ESEC/FSE paper for its PACMSE camera-ready, covering de-anonymization, the ACM Primary Article Template and PACMSE journal metadata (DOI, ORCID, CCS concepts), integrating reviewer-required changes without scope creep, permanentizing the Data Availability links, and the ACM artifact-badge handoff.ȘtiințăFără avertismente★ 1,3 K↓ —
- openmeld-cliamplifthq/openmeldUse OpenMeld when a task needs Organization knowledge or Skills, Center Agent help, shared Spaces or Files, another Agent or computer, or scheduled cloud work. Also use for OpenMeld setup and Wake replies.InginerieFără avertismente★ 1,4 K↓ —Apare și în 3 alte depozite
- emnlp-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an EMNLP project calendar end to end — choosing the ACL Rolling Review cycle that feeds the conference, backward-planning experiments and annotation to the ARR deadline, scheduling the author response window, deciding commit versus revise-and-resubmit, and mapping camera-ready and Budapest presentation logistics.ProductivitateFără avertismente★ 1,3 K↓ —
- eccv-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ECCV submission for the two-step registration-then-paper deadline chain, the 14-page LNCS single-column limit, CET (not AoE) cutoffs, the trailing supplementary deadline, double-blind rules, the four-page dual-submission definition, the social-media embargo, and reviewer-duty exposure before upload.ȘtiințăFără avertismente★ 1,3 K↓ —
- fast-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing a USENIX FAST submission for HotCRP readiness, covering the choice between the Spring and Fall deadlines, abstract registration, the USENIX two-column template and 12-page (long) / 6-page (short) limit excluding references, double-blind anonymization, the artifact-availability story, and desk-reject triage before the AoE cutoff.AlteleFără avertismente★ 1,3 K↓ —
- dac-related-workbrycewang-stanford/Awesome-Journal-SkillsUse when writing or auditing the related-work and positioning of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the EDA literature lanes (DAC/ICCAD/DATE/ASP-DAC/TCAD/TODAES), delta-first positioning against the strongest prior tool, honest benchmark-suite lineage, and third-person self-citation under double-blind review within the six-page budget.DesignFără avertismente★ 1,3 K↓ —
- wake-traceamplifthq/openmeldUse when diagnosing a Wake that failed, stalled, or produced no visible reply — dispatch, setup handoff, or reply-path issues. Routes to the deterministic trace evidence path.AlteleFără avertismente★ 1,4 K↓ —
- corl-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when preparing or auditing a CoRL OpenReview submission — the corl_2026 LaTeX template, the 8-page main text with a mandatory Limitations section counted inside it, uncounted references and appendix, the supplementary file and 250 MB video, double-anonymous rules, abstract registration, and dual-submission checks.MediaFără avertismente★ 1,3 K↓ —
- ecai-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ECAI submission for readiness — the abstract-then-full-paper two-deadline flow, the tight 7-page body budget, double-blind anonymity, the correct template/publisher regime (ecai.cls/FAIA for a standalone ECAI vs ijcai.sty/IJCAI proceedings for the joint IJCAI-ECAI 2026), the per-author submission cap, the ethics statement, and desk-reject triage before the AoE cutoff.ȘtiințăFără avertismente★ 1,3 K↓ —
- dac-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when preparing the final ACM/IEEE Design Automation Conference (DAC) Research-Manuscript camera-ready after acceptance, covering de-anonymization, restoring author/affiliation/acknowledgement/funding blocks, the ACM copyright form and rights stamp, the April proceedings deadline, ACM Digital Library metadata and archival-flow checks, and the still-fixed 6+1 page budget.DesignFără avertismente★ 1,3 K↓ —
- icse-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICSE research-track campaign end to end, covering the single-cycle calendar from the June abstract deadline through September response, October decisions, the November revision sprint, artifact evaluation, camera-ready, and the April conference, plus rerouting timelines after rejection.ProductivitateFără avertismente★ 1,3 K↓ —
- cscw-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when readying a CSCW manuscript for upload — confirming the current pathway (rolling via Manuscript Central as of mid-2026), the single-column ACM template, the word-length scrutiny band, anonymization of author and community identifiers, ethics statements, and desk-risk triage.AlteleFără avertismente★ 1,3 K↓ —
- jama-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when deciding which jama-* sub-skill to invoke next, or when sequencing a clinical manuscript from scope check through revision for JAMA (Journal of the American Medical Association). Routes — does not replace — the specialized skills.ProductivitateFără avertismente★ 1,3 K↓ —
- isca-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a full ISCA campaign on a calendar — working back from the expected mid-November abstract and paper deadlines to freeze simulation evidence in time, staffing the winter two-round review wait, preparing for the February-March rebuttal and revision window, and branching to camera-ready, artifacts, and the June conference.ProductivitateFără avertismente★ 1,3 K↓ —
- icra-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICRA submission calendar end to end — the September paper deadline, the two video-attachment windows, winter review silence, late-January notification, March camera-ready, and the May/June conference — or when interleaving a fallback RA-L or IROS plan around the single annual ICRA shot.ProductivitateFără avertismente★ 1,3 K↓ —
- ipsn-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an IPSN-lineage project timeline from track/venue selection through the CPS-IoT Week deadline, double-blind submission, deployment and hardware logistics, rebuttal, the Best Research Artifact Award, and the dual ACM/IEEE camera-ready — with honest handling of the fact that IPSN merged into SenSys.ProductivitateFără avertismente★ 1,3 K↓ —
debugging-ci-failures
amplifthq/openmeld
InginerieActualizat alaltăieri
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