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 19 ore
48.451 de skill-uri
- writing-livekit-scenariosfcakyon/claude-codex-settingsCreates and maintains the scenarios a LiveKit agent simulation runs, and wires the agent to consume them. Use when the user asks "what should I test", "generate simulation scenarios", "write scenarios for my agent", "add a scenario for X", "organize my scenario files", "my simulations are flaky", "the scenario hits my real database", "seed state per scenario", "it passed but booked the wrong thing", "grade the final state", or wants to stress-test a flow before shipping. Covers generating a baseline with the LiveKit scenario generator and refining it, writing the cases generation misses, phrasing simulated-user instructions so they steer reliably, splitting scenarios into sets across files, and the agent-side code that seeds deterministic state from a scenario and fails a run on its final state. To run them use running-livekit-simulations.RedactareFără avertismente★ 1,2 K↓ —Apare și în 1 alt depozit
- chi-review-processbrycewang-stanford/Awesome-Journal-SkillsUse when interpreting the ACM CHI Papers review pipeline — 1AC and 2AC roles, the A/ARR/RR/RRX/X recommendation scale, desk-reject and rubric-based assisted desk-reject screening, the revise-and-resubmit threshold, round-2 PC decisions — and what each stage means for authors.InginerieFără avertismente★ 1,4 K↓ —
- nextjs-on-cloudflarefcakyon/claude-codex-settingsBuild, migrate, and deploy Next.js apps on Cloudflare Workers with vinext. Use when starting a Next.js project on Cloudflare, moving an existing app to Workers, choosing between vinext and OpenNext, or setting up vinext for Workers. For setup, migration, or deployment, install vinext's upstream skills with `npx skills add cloudflare/vinext` if missing, then read and follow the applicable skill and docs.DevOpsFără avertismente★ 1,2 K↓ —
- isca-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of an ISCA paper — pinning simulator fidelity to the claims it must carry, documenting gem5-class configurations and sampling choices, selecting workload suites that represent the claim's domain, tuning baselines in good faith, and separating architectural effect from modeling artifact.ȘtiințăFără avertismente★ 1,4 K↓ —
- uai-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when splitting a UAI paper between the 8-page main part, the unlimited in-PDF appendix for proofs and protocols, and the optional 50 MB supplementary ZIP, deciding what reviewers must see in the body versus what may sit in material they are not required to read, all under double-blind and single-file constraints.DocumenteFără avertismente★ 1,4 K↓ —
- kdd-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when splitting a KDD paper across its 8 content pages, the optional appendix after the references, and the cited repository, under the camera-ready rule capping references plus appendix at 3 of 12 pages. Covers appendix triage, reviewer-discretion reality, and the one-page cross-cycle resubmission change summary.ȘtiințăFără avertismente★ 1,4 K↓ —
- itcs-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when deciding what counts as evidence for an ITCS theory claim — proofs as the primary evidence, worked examples and separations that make a model concrete, and the rare, well-scoped illustrative computation or simulation — and how to keep any computational content checkable and subordinate to the mathematics.MediaFără avertismente★ 1,4 K↓ —
- nsdi-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of an NSDI submission — choosing traces, testbeds, and deployment evidence, sizing scale and failure-injection experiments, picking baselines that fight back, and reporting tail behavior so networked-systems reviewers can see where the design wins, loses, and breaks.DevOpsFără avertismente★ 1,4 K↓ —
- fse-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when revising an ESEC/FSE paper for a practitioner-grounded software-engineering contribution on the first page, research-question contracts, a threats-to-validity section that argues rather than recites, evidence proportional to the claim, double-anonymous wording, and disciplined use of the ACM-template page budget.RedactareFără avertismente★ 1,4 K↓ —
- coding-agent-rolloutalirezarezvani/claude-skillsRoll out Claude Code to a team: shared or managed settings, MCP and plugin approval, layered CLAUDE.md, adoption. Use whenever the user sets up Claude Code for their team or org, or asks if a rollout or settings file is right.InginerieFără avertismente★ 29,3 K↓ —
- osdi-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning or managing a full OSDI cycle — the December title-registration and submission deadlines on HotCRP, the silent no-rebuttal review window, March notification, the May artifact deadline, June shepherded final papers, and the July conference — including rejection retargeting to SOSP or NSDI.ProductivitateFără avertismente★ 1,4 K↓ —
- stoc-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a STOC (ACM Symposium on Theory of Computing) project calendar — backward planning to the early-November deadline, the STOC/FOCS alternating two-deadline year that theory groups schedule around, full-version and camera-ready milestones, and the June TheoryFest endpoint.ProductivitateFără avertismente★ 1,4 K↓ —
- nsdi-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an NSDI campaign across the spring and fall deadlines — sequencing abstract and paper gates, notification waits, one-shot revision windows, artifact evaluation, and the May symposium — so a networked-systems project always knows which of the two yearly gates it is really building toward.ProductivitateFără avertismente★ 1,4 K↓ —
- focs-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a FOCS (IEEE Symposium on Foundations of Computer Science) cycle end to end — working backward from the April 1 deadline, managing the live post-submission summer of the 2026 cycle, coordinating with the STOC beat, preparing the November conference, and scheduling a FOCS 2027 attempt.ProductivitateFără avertismente★ 1,4 K↓ —
- podc-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ACM PODC campaign end to end — running the single annual cycle backward from the February deadline through abstract registration, lightweight double-blind review, the late-April notification, the May camera-ready, and the arXiv full version — and coordinating the regular-paper-vs-Brief-Announcement decision along the way.ProductivitateFără avertismente★ 1,4 K↓ —
- icml-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning or sequencing an ICML manuscript workflow end to end - from topic selection and drafting through OpenReview submission, double-blind review, author response, camera-ready, PMLR publication, public original-submission release, and rerouting decisions. Use when you need the next ICML skill, the official page to reopen, or the blocking gap for the current stage.ProductivitateFără avertismente★ 1,4 K↓ —
- itcs-workflowbrycewang-stanford/Awesome-Journal-SkillsUse to plan an ITCS campaign end to end on its single annual cycle — backward from the early-September deadline through the no-rebuttal review, the November notification, the LIPIcs camera-ready, and the January conference with its Graduating Bits session.ProductivitateFără avertismente★ 1,4 K↓ —
- vis-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an IEEE VIS project timeline from area fit through the abstract and full-paper deadlines, the two-phase review, the conditional-accept second round, the IEEE TVCG camera-ready, the Graphics Replicability Stamp, and presentation, with backward-planning offsets for a visualization paper and honest handling of the annual cycle and the second-round revision window.ProductivitateFără avertismente★ 1,4 K↓ —
- pnas-figuresbrycewang-stanford/Awesome-Journal-SkillsUse to finalize PNAS display items — column-width sizing (~9 / 11.4 / 18 cm), minimum font sizes, show-the-data with n and defined error bars, scale bars, colorblind-safe palettes, legend structure, image integrity, and color-mode notes. Enforces figure rigor before submission.MediaFără avertismente★ 1,4 K↓ —
- lancet-fitbrycewang-stanford/Awesome-Journal-SkillsUse when scoping a project and before any writing, to stress-test whether a study clears The Lancet's bar — clinically or public-health important, globally relevant, and likely to change practice or policy, often with an equity lens. Decides The Lancet vs a Lancet family title vs another general medical journal.TestareFără avertismente★ 1,4 K↓ —
- cell-rebuttalbrycewang-stanford/Awesome-Journal-SkillsUse after Cell reviews arrive to triage the decision, prioritize the (often substantial) new experiments by impact × feasibility, and draft a point-by-point response that is respectful, evidence-led, and closes the "completeness" gaps reviewers demand. Do not run before the experiments and revision are actually done.AlteleFără avertismente★ 1,4 K↓ —
- cell-databrycewang-stanford/Awesome-Journal-SkillsUse to build Cell's data and code deposition plan and the Data and Code Availability statement that lives inside STAR Methods Resource Availability — approved repositories, accessions/DOIs at submission, and Cell's three-bullet availability format with Mendeley Data as Elsevier's default.PlanificareFără avertismente★ 1,4 K↓ —
- chi-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ACM CHI submission cycle end to end — the single September deadline, two-round review with a five-week revise-and-resubmit window, December decisions, the TAPS and publication-ready chain, and the May conference — with owners and risk buffers for each stage.ProductivitateFără avertismente★ 1,4 K↓ —
- sci-databrycewang-stanford/Awesome-Journal-SkillsUse to build Science's data, code, and materials availability — mandatory deposition in approved repositories, accession numbers, a compliant data-availability statement, and materials/reagent sharing.ȘtiințăFără avertismente★ 1,4 K↓ —
migliora
dagoSte/squadra
InginerieActualizat alaltăieri
De la autor
Improve a project's development workflow from observed failures, repeated work and avoidable waits. Apply scoped, verified remedies and useful project instructions, then automatically commit owned changes when the project's required checks and reviews are complete. Use after recurring development friction or when asked to improve the process; do not add rules without evidence.
Instalare
npx skills add dagoSte/squadra --skill migliora -a claude-code
Se instalează în .claude/skills/migliora/ · 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ță77
Întreținere100
Licență100
Adopție50
Fișiere (1)
- SKILL.md