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.743 de skill-uri din 2.355 de depozite · actualizat acum 11 minute
47.668 de skill-uri
- wsdm-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of a WSDM paper - offline ranking and recommendation metrics with bias controls, temporal-split protocols for interaction logs, baseline selection from recent WSDM/SIGIR/KDD editions, ablations that isolate the mechanism, efficiency reporting, and online-evidence framing.ȘtiințăFără avertismente★ 1,4 K↓ —
- aaai-related-workbrycewang-stanford/Awesome-Journal-SkillsUse when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across the broad AI scope, while staying inside AAAI's dual-submission and AI-as-source policy constraints and writing a related-work section legible to non-specialist reviewers.ȘtiințăFără avertismente★ 1,4 K↓ —
- aaai-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and final public artifact release.ȘtiințăFără avertismente★ 1,4 K↓ —
- wacv-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing WACV experiments, covering Applications-track systems evidence (latency, power, robustness under real constraints) versus Algorithms-track matched-baseline novelty, comparative assessment under the deployed condition, uncertainty over seeds and sessions, ablations, and evidence that survives the two-round review.DevOpsFără avertismente★ 1,4 K↓ —
- vldb-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of a VLDB paper, covering workload and dataset realism at scale, competitor tuning fairness, scalability curves versus single points, tail-latency and throughput reporting, ablations that isolate the mechanism, and the loss-case disclosure PVLDB reviewers look for first.ȘtiințăFără avertismente★ 1,4 K↓ —
- vis-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when revising an IEEE VIS paper for a task-grounded visualization contribution on the first page, a design rationale that ties each visual encoding and interaction to a task, evaluation matched to the contribution type, honest limitations, and disciplined use of the VGTC/TVCG 9+2 page budget for a paper that will be read as an IEEE TVCG journal article.RedactareFără avertismente★ 1,4 K↓ —
- ase-review-processbrycewang-stanford/Awesome-Journal-SkillsUse when reasoning about how an ASE (IEEE/ACM Automated Software Engineering) research submission is evaluated, covering double-anonymous review, the early-rejection stage before rebuttal, the Accept / Revision / Reject outcomes, the criteria-bound revision round, and how ASE's process differs from FSE's PACMSE Major Revision, ICSE's cycles, and ISSTA's rounds.InginerieFără avertismente★ 1,4 K↓ —
- cav-review-processbrycewang-stanford/Awesome-Journal-SkillsUse when reasoning about how a CAV (Computer Aided Verification) submission is evaluated, covering the two-stage reviewing process (two reviews then an early-reject filter, then two more reviews with a rebuttal), the partial double-anonymity by category, the accept/reject outcome, the optional non-conditional artifact evaluation, and how CAV differs from TACAS and FMCAD.InginerieFără avertismente★ 1,4 K↓ —
- atc-review-processbrycewang-stanford/Awesome-Journal-SkillsUse when reasoning about how an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) submission is evaluated — the two-round extended-abstract model, the round-one gate by two reviewers, the round-two read by 3-4 reviewers, double-blind reviewing, rebuttal, conditional acceptance with shepherding, and how ATC differs from OSDI/SOSP/NSDI.InginerieFără avertismente★ 1,4 K↓ —
- asplos-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ASPLOS campaign across the two-deadline cycle — sequencing evidence building, the September 9, 2026 submission gate, author-response windows, the December 21 notification, Major Revision resubmission six weeks later, artifact evaluation, and the April 2027 conference in Crete, with owners per risk.ProductivitateFără avertismente★ 1,4 K↓ —
- cikm-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when turning an accepted CIKM paper into its ACM proceedings version inside the short notification-to-camera-ready window, covering de-anonymization, the e-rights and TAPS pipeline into the ACM Digital Library, CCS concepts and metadata, GenAI-disclosure retention, artifact link publication, and Rome presentation logistics.ȘtiințăFără avertismente★ 1,4 K↓ —
- cell-star-methodsbrycewang-stanford/Awesome-Journal-SkillsUse to build Cell's mandatory STAR Methods — the Key Resources Table, the three Resource Availability subsections, Experimental Model and Subject Details, Method Details, and Quantification and Statistical Analysis, in the exact required order.AlteleFără avertismente★ 1,4 K↓ —
- doca-rmaxNVIDIA/skillsDOCA Rivermax (doca_rmax) receive streams for timing-precise media over IP (SMPTE ST 2110 video / audio, market data, scientific feeds) on a target BlueField DPU (DOCA Rivermax apps run only there), once the Rivermax libraries and license are installed; getting them is doca-setup / doca-public-knowledge-map territory. Trigger on "ST 2110 receive isn't getting frames", "sub-microsecond jitter on my media receiver", "NOT_SUPPORTED from doca_rmax_init", "no recv events after stream start", or "license check failing on a media receiver", even without naming Rivermax. Covers doca_rmax_in_stream sessions, the SDK + license precondition check, doca_rmax_get_*_supported capability queries, pairing with doca-eth queues and doca-flow steering, and DOCA_ERROR_* from Rivermax calls. Refuse and route elsewhere for programming the underlying queue (doca-eth), steering rules (doca-flow), PTP / clock sync (doca-firefly), or best-effort packet I/O.MediaFără avertismente★ 3,8 K↓ —
- openspec-apply-changeMemeMeow-Studio/MemeMeowImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.ProductivitateFără avertismente★ 1,3 K↓ —Apare și în 1 alt depozit
- openspec-exploreMemeMeow-Studio/MemeMeowEnter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.FinanțeFără avertismente★ 1,3 K↓ —Apare și în 1 alt depozit
- openspec-archive-changeMemeMeow-Studio/MemeMeowArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.ProductivitateFără avertismente★ 1,3 K↓ —
- openspec-apply-changeMemeMeow-Studio/MemeMeowImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.ProductivitateFără avertismente★ 1,3 K↓ —
- openspec-update-changeMemeMeow-Studio/MemeMeowUpdate an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.RedactareFără avertismente★ 1,3 K↓ —
- openspec-update-changeMemeMeow-Studio/MemeMeowUpdate an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.RedactareFără avertismente★ 1,3 K↓ —
- openspec-update-changeMemeMeow-Studio/MemeMeowUpdate an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.RedactareFără avertismente★ 1,3 K↓ —
- judge-group-closuresno-ai/sno-stationJudge which offered rows one nominated statement retires or replaces.AlteleFără avertismente★ 1,1 K↓ —
- run-paid-campaigns-weekly-readgooseworks-ai/goose-skillsStep of the run-paid-campaigns playbook: reads each platform's last mature results window against the allowable cost, as evidence for the week's moves. Run run-paid-campaigns instead; not for direct use.AlteleFără avertismente★ 1,3 K↓ —
- setup-offline-profilemicrosoft/power-platform-skillsUse when the user wants to enable offline mode for a Power Apps mobile app and create a Mobile Offline Profile in Dataverse — designs per-table row scope, relationships, columns, and sync frequency through a 3-gate approval flow.AlteleFără avertismente★ 1,1 K↓ —
- publish-pcf-companionmicrosoft/power-platform-skillsDeploy the dispatcher PCF for a third-party `.ppmplugin` control to a Power Platform environment via `pac pcf push`. The dispatcher PCF is the Studio-side control that dispatches the composite key `<name>/<receiver>` over the wrap shell's `SendMessagePlugin` bridge to the control's native module. Verifies deploy prereqs (Node.js 20+ with npm, .NET SDK, and active `pac auth`), then three confirmation gates — publisher prefix (2–8 chars; defaults to `pamext` or the last-used value from `.extension-state.md`), version bump (patch / minor / major / no-bump), target environment URL (from `pac org who`). Builds the PCF if needed, then pushes. Decoupled from /generate-pcf-companion so the engineer can scaffold and customize locally, then deploy when ready. Updates `.extension-state.md` with deployment history (timestamp, env URL, version, prefix used).DevOpsFără avertismente★ 1,1 K↓ —
nzism
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
SecuritateActualizat 10 oct. 2026
De la autor
Expert New Zealand Information Security Manual (NZISM) advisor for NZ government agencies and their supply chains. Use for NZISM control guidance, gap analysis, agency security obligations, classification framework (Unclassified through Top Secret), security risk management, system certification, and GCSB/NCSC NZ compliance. Triggers on: NZISM controls, NZ government security, GCSB compliance, agency cybersecurity obligations, NZ classification markings, Restricted/Confidential/Secret system scoping, agency security policies, third-party supplier security, Certification and Accreditation (C&A), and any question about NZ government information security requirements or the NZISM framework.
Instalare
npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill nzism -a claude-code
Se instalează în .claude/skills/nzism/ · 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ță76
Întreținere100
Licență100
Adopție49
Fișiere (4)
- SKILL.md
- references/classification-framework.md
- references/control-groups.md
- references/nzism-control-ids.md