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.539 de skill-uri din 2.407 depozite · actualizat acum 3 minute
48.313 skill-uri
- 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↓ —
- cto-advisoralirezarezvani/claude-skillsCTO decisions: tech debt, architecture direction, scaling the engineering team, technology evaluation, DORA metrics. Use whenever the user asks whether to rewrite, how to grow the eng team or which tech to bet on.PlanificareFără avertismente★ 29,3 K↓ —
- hyperframes-cliActualizatheygen-com/hyperframesThe HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.OficialInginerieVerifică întâi★ 79,3 K↓ —
- pmf-strategykostja94/marketing-skillsWhen the user wants to validate product-market fit, measure PMF, or plan before scaling. Also use when the user mentions "PMF," "product-market fit," "product market fit," "Sean Ellis test," "very disappointed," "vitamin vs painkiller," "PMF validation," "premature scaling," or "validate before scale." For GTM after validation, use gtm-strategy.TestareFără avertismente★ 1,1 K↓ —
- ndss-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an NDSS submission calendar — choosing between the summer and fall cycles, backward-planning from the AoE deadline through early-reject, rebuttal, notification, camera-ready, and the Seoul symposium, and placing NDSS honestly inside the security big-four retargeting year.ProductivitateFără avertismente★ 1,4 K↓ —
- nejm-citationbrycewang-stanford/Awesome-Journal-SkillsUse to convert references to NEJM's Vancouver / ICMJE numbered style — numbered in order of appearance, limited author lists then et al., NLM journal abbreviations, and a capped reference count. Late-stage style pass.AlteleFără avertismente★ 1,4 K↓ —
- mind-workflowbrycewang-stanford/Awesome-Journal-SkillsUse as the entry point for any Mind (philosophy journal) article. Routes to the right Mind sub-skill based on where you are in the lifecycle and whether the piece is an article, discussion note, book review, or critical notice. Mind is analytic philosophy — argument, not data — so the router's first job is to confirm there is a sharp thesis and a sound argument. It dispatches; it does not draft content.ProductivitateFără avertismente★ 1,4 K↓ —
- kdd-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing a KDD submission for readiness in either cycle, covering Research vs ADS track declaration, OpenReview profile completeness for all authors, the ACM sigconf 8-content-page budget, double-blind checks, in-paper artifact references, resubmission declarations, and desk-reject triggers specific to ACM SIGKDD.ȘtiințăFără avertismente★ 1,4 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↓ —
- 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,4 K↓ —
- oma-brainstormNoufirst-fluke/oh-my-agentExplore goals, constraints, and alternative approaches before choosing a design. Use when the user requests ideation or design exploration.PlanificareFă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↓ —
- 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,4 K↓ —
- 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,4 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,4 K↓ —
- pods-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ACM PODS project timeline across its multiple submission cycles per year, from venue fit through the EasyChair abstract-then-paper deadlines, the 48-hour rebuttal, the accept/reject/revision decision and shepherded revision round, PACMMOD-track publication, the arXiv full version, and presentation — with backward-planning offsets for a theory paper and honest handling of cycle choice.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↓ —
- iccv-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when project-managing an ICCV campaign across the odd-year cycle, covering the autumn fork between CVPR and ICCV, the early-March registration and single submission deadline, May rebuttal week, late-June decisions, the October conference with international travel and visa lead times, and the ECCV/CVPR fallback ladder if the paper misses.ProductivitateFără avertismente★ 1,4 K↓ —
- product-analytics-setuprampstackco/claude-skillsHow to actually instrument product analytics correctly. Event taxonomy, property design, naming conventions, schema versioning, identity stitching, funnel design, retention cohorts, North Star metric selection, dashboard hygiene, instrumentation debt, and the failure modes that produce data nobody trusts. Triggers on product analytics setup, event taxonomy, tracking plan, instrumentation, schema versioning, North Star metric, retention cohorts, funnel design, naming conventions, instrument new feature, audit existing analytics, dashboard reconciliation, instrumentation debt, Mixpanel setup, Amplitude setup, PostHog setup, warehouse-native analytics. Also triggers when the team has data but cannot trust it, or when designing instrumentation for a new feature, or when auditing an existing setup that has drifted.DateFără avertismente★ 1 K↓ —
- icde-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an IEEE ICDE project timeline around the two-round-per-edition calendar, choosing between the June and November research deadlines, budgeting for a possible revise-and-resubmit window, and backward-planning a data-engineering systems paper from CMT submission through review, camera-ready, and IEEE Xplore publication.ProductivitateFără avertismente★ 1,4 K↓ —
- icdm-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICDM (IEEE International Conference on Data Mining) project timeline from venue fit through the abstract and full-paper deadlines, the long summer wait to the August notification, the no-rebuttal review, the possible short-paper acceptance branch, IEEE camera-ready, and in-person presentation on a single annual deadline.ProductivitateFără avertismente★ 1,4 K↓ —
figma-implement-design
openai/skills
OficialDesignActualizat 28 oct. 2026
De la autor
Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions "implement design", "generate code", "implement component", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`.
Instalare
npx skills add openai/skills --skill figma-implement-design -a claude-code
Se instalează în .claude/skills/figma-implement-design/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Fără descărcare: licența acestui skill (Personalizată sau neclară) nu ne permite să-i redistribuim fișierele. Comenzile de instalare le iau direct de pe GitHub.
La ce are acces
Doar instrucțiuniNu am văzut acces la rețeaLicență: Personalizată sau neclară
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 88
Securitate100
Proveniență100
Întreținere85
Licență45
Adopție69
Fișiere (6)
- LICENSE.txt
- SKILL.md
- agents/openai.yaml
- assets/figma-small.svg
- assets/figma.png
- assets/icon.svg