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 10 ore
48.451 de skill-uri
- strategy-memomohitagw15856/pm-claude-skillsWrite a strategy memo that commits to a bet and says what you won't do. Use when asked to write a strategy memo, articulate a strategy, make the case for a strategic direction, or align the team on where to focus. Produces a strategy memo — the strategic question, the diagnosis, the bet/approach, why now, explicit non-goals (what we're NOT doing), how we'll know it's working, and the risks.RedactareFără avertismente★ 1,5 K↓ —
- pmla-workflowbrycewang-stanford/Awesome-Journal-SkillsUse as the entry point for any PMLA (Publications of the Modern Language Association) manuscript. Routes to the right PMLA sub-skill based on where you are in the lifecycle and which venue fits — a regular blind-reviewed article or a special feature (Theories and Methodologies, The Changing Profession, Criticism in Translation, Little-known Documents). It dispatches; it does not draft content.ProductivitateFără avertismente★ 1,4 K↓ —
- pnas-citationbrycewang-stanford/Awesome-Journal-SkillsUse to convert references to PNAS's numbered citation style — cited in order of appearance, a numbered reference list, full author lists, abbreviated journal titles. Provides formats for article/book/chapter/dataset/preprint and an author-date → PNAS conversion table. Late-stage style pass.MarketingFără avertismente★ 1,4 K↓ —
- pldi-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a PLDI campaign across its annual clock — backward-planning from the November deadline through winter reviewing, the February response window, March notification, post-acceptance artifact evaluation, PACMPL production, and the June conference, with owners for each deliverable.ProductivitateFără avertismente★ 1,4 K↓ —
- brooks-healthhyhmrright/brooks-lintCombined codebase health dashboard that scores a project across all four quality dimensions — PR quality, architecture, tech debt, and test quality — in a single pass, drawing on twelve classic engineering books. Triggers when: user wants an overall quality assessment, asks "how healthy is this codebase?", "run all the checks", "I need a health score before the release", or wants to onboard a new team with a quality overview. Do NOT trigger for: server health checks, HTTP health endpoints, Kubernetes liveness/readiness probes, database health, or application uptime. Also do not trigger when the user specifically requests only one dimension — use the corresponding focused skill instead (brooks-review / brooks-audit / brooks-debt / brooks-test).TestareFără avertismente★ 1,6 K↓ —
- pnas-abstractbrycewang-stanford/Awesome-Journal-SkillsUse to write the PNAS abstract — a single self-contained paragraph of ~250 words, quantified and accessible to a broad scientific audience. Distinguishes the abstract (what/how/found, for scientists) from the Significance Statement (why-it-matters, for everyone). Late-stage polish.ȘtiințăFără avertismente★ 1,4 K↓ —
- pnas-rebuttalbrycewang-stanford/Awesome-Journal-SkillsUse after PNAS reviews arrive to triage the decision, prioritize experiments, and draft a point-by-point response that is respectful, evidence-led, and honest about limits. Do not run before the main text is actually revised.AlteleFără avertismente★ 1,4 K↓ —
- pnas-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when deciding which pnas-* sub-skill to invoke next, or when sequencing a manuscript from significance test through reviewer rebuttal for PNAS (Proceedings of the National Academy of Sciences). Routes — it does not replace — the specialized skills.ProductivitateFără avertismente★ 1,4 K↓ —
- red-green-proofalirezarezvani/claude-skillsTurns a suspected bug into a proven one. Verify the cause against reality before claiming it, write a test that FAILS on the current code, apply the fix, watch it pass — then revert the fix and confirm the test goes red again, because a test that passes both ways proves nothing. Invoked bare after a debugging conversation, it takes the target from context rather than asking. Use when fixing a bug, investigating an incident, hardening a flaky area, or when asked to "add tests that reveal the bug". Triggers on "/red-green-proof", "prove the bug", "red-green", "make the test fail first", "is that test load-bearing", "reveal the bug with a test".TestareFără avertismente★ 29,3 K↓ —
- nejm-rebuttalbrycewang-stanford/Awesome-Journal-SkillsUse after NEJM reviews arrive — often including a dedicated statistical reviewer and an editor letter — to triage the decision, answer statistical comments rigorously, and draft a point-by-point response that quotes each comment, the response, and the revised manuscript text. Do not run before the main text is actually revised.RedactareFără avertismente★ 1,4 K↓ —
- nejm-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when deciding which nejm-* sub-skill to invoke next, or when sequencing a clinical manuscript from significance test through response to reviewers for The New England Journal of Medicine. Routes — it does not replace — the specialized skills.ProductivitateFără avertismente★ 1,4 K↓ —
- figma-generate-designopenai/skillsUse this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the Figma screen to match code'. This is the preferred workflow skill whenever the user wants to build or update a full page, screen, or view in Figma from code or a description. Discovers design system components, variables, and styles via search_design_system, imports them, and assembles screens incrementally section-by-section using design system tokens instead of hardcoded values.OficialDesignFără avertismente★ 28,5 K↓ —
- okr-buildermohitagw15856/pm-claude-skillsCreate well-structured OKRs (Objectives and Key Results) for product teams, startups, and individuals. Use when asked to write OKRs, set quarterly goals, define key results, or review existing OKRs. Produces a complete OKR set with objectives, measurable key results, baselines, and a scoring guide.RedactareFără avertismente★ 1,5 K↓ —
- one-pagermohitagw15856/pm-claude-skillsDistil anything — a startup, product, project, or idea — into a single persuasive page. Use when asked to make a one-pager, a one-page summary, a leave-behind, a startup/product one-sheet, or a tl;dr brief. Produces a structured single page — headline + tagline, the problem, the solution, why-now/proof, and a clear ask/CTA — designed to be skimmed and remembered, ready to export as a typeset PDF.DocumenteFără avertismente★ 1,5 K↓ —
- nejm-abstractbrycewang-stanford/Awesome-Journal-SkillsUse to write the NEJM structured abstract — four headed sections (Background, Methods, Results, Conclusions), ≤250 words, with the trial registration number and funding source, leading the Results with the primary outcome reported as an effect size with a 95% CI. Late-stage polish skill.RedactareFără avertismente★ 1,4 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,4 K↓ —
- iros-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an IROS project timeline from venue fit through the spring paper deadline, the separate video deadline, the summer review silence, the June notification, the July camera-ready, IEEE Xplore publication, registration, and presentation, with backward-planning offsets for a real-robot paper on the fall IEEE/RSJ calendar.ProductivitateFără avertismente★ 1,4 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,4 K↓ —
- icdt-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICDT (International Conference on Database Theory) campaign end to end, running the two-submission-cycle calendar backward from a chosen cycle deadline through abstract registration, the first-cycle revision round, LIPIcs camera-ready, and presentation at the co-located EDBT/ICDT event.ProductivitateFără avertismente★ 1,4 K↓ —
- roastalirezarezvani/claude-skillsRoast an idea: a 5-angle panel (Critic, Champion, Analyst, Investigator, Customer) attacks it, then a Judge returns one GO / RESHAPE / KILL verdict with the cheapest test to de-risk it. Use whenever the user wants to pressure-test or validate a business idea, asks for a brutal second opinion before building, asks is this a good idea, says convene the panel, or runs /roast.TestareFără avertismente★ 29,3 K↓ —
- hpca-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an HPCA project timeline from venue fit through the two-step July registration and paper gate, the autumn review wait, the single rebuttal/revision window, notification, IEEE camera-ready, artifact evaluation, and the February/March talk, with backward-planning offsets for a hardware-evaluated paper.ProductivitateFără avertismente★ 1,4 K↓ —
- eccv-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when running an ECCV campaign end to end — the even-year calendar from February registration to the September conference, the retargeting triangle to CVPR and ICCV seen from the ECCV seat, where the 2026 cycle stands today, and backward planning a 2028 submission from the March deadline.ProductivitateFără avertismente★ 1,4 K↓ —
- fse-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ESEC/FSE research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the ACM Primary Article Template page budget, double-anonymous "heavy" anonymity, the open-science Data Availability statement, PACMSE publication, and desk-reject triage before the AoE cutoff.ȘtiințăFără avertismente★ 1,4 K↓ —
- chi-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ACM CHI Papers submission for PCS readiness, covering the September full-paper deadline, the anonymized single-column template, word-count norms instead of page limits, subcommittee designation, supplementary and video upload, anonymization of external links, and CHI's desk-reject triage before upload.MediaFără avertismente★ 1,4 K↓ —
cvpr-experiments
brycewang-stanford/Awesome-Journal-Skills
TestareActualizat 27 sept. 2026
De la autor
Use 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.
Instalare
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cvpr-experiments -a claude-code
Se instalează în .claude/skills/cvpr-experiments/ · 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