Agent skills you can check before you install
Public SKILL.md skills from GitHub repositories with 50+ stars and from the vendors themselves, scanned and scored. Install any of them with one command in Claude Code, Cursor, Codex, GitHub Copilot or Gemini CLI.
49,409 skills from 2,375 repositories · updated 28 minutes ago
48,362 skills
- ecsitsmostafa/aws-agent-skillsAWS ECS container orchestration for running Docker containers. Use when deploying containerized applications, configuring task definitions, setting up services, managing clusters, or troubleshooting container issues.DevOpsNo warnings★ 1.2K↓ —
- eksitsmostafa/aws-agent-skillsAWS EKS Kubernetes management for clusters, node groups, and workloads. Use when creating clusters, configuring IRSA, managing node groups, deploying applications, or integrating with AWS services.DevOpsNo warnings★ 1.2K↓ —
- 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.EngineeringNo warnings★ 1.4K↓ —
- month-end-closealirezarezvani/claude-skillsUse when running, planning or speeding up a month-end (or quarter-end) close — building or reviewing the close checklist and calendar, reconciling a bank statement or sub-ledger to the general ledger, writing or reviewing flux (variance) explanations, or finding why the close takes too many days. Orders close tasks by dependency and finds the critical path, proves each reconciliation and ages what is left, and refuses to sign off material fluctuations explained with boilerplate.WritingNo warnings★ 29.2K↓ —
- iclr-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing ICLR experiments, including baselines, ablations, scaling laws, robustness, statistics, benchmarks, human evaluation, and compute reporting. Use when a reviewer questions whether a representation-learning or model gain is real, when you must isolate one mechanism with an ablation, or when preparing a small compute-matched control that can be posted inline during the public discussion period.OtherNo warnings★ 1.4K↓ —
- cav-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when deciding what belongs in a CAV (Computer Aided Verification) paper body versus its optional appendix and artifact, covering the LNCS page limits, the rule that reviewers are not obliged to read the appendix so decision-critical content stays in the body, where full proofs and benchmark tables live, and double-anonymous supplementary material for the anonymized categories.ScienceNo warnings★ 1.4K↓ —
- cscw-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the empirical work behind a CSCW paper — interview and ethnographic rigor, trace and log analysis, surveys, deployments, and mixed methods — matching each method's own validity standard and the ethics of studying real communities.DevOpsNo warnings★ 1.4K↓ —
- ndss-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of an NDSS paper — attack demonstrations, defense evaluations under adaptive adversaries, and Internet measurements — choosing between testbed, emulation, and live experiments and meeting NDSS's deployment-realism evidence bar.DevOpsNo warnings★ 1.4K↓ —
- edbt-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing EDBT empirical evaluations for database-systems work, covering real workloads and datasets, fair and tuned baselines, honest measurement across realistic scales, reproducible harnesses, and the higher bar of the Experiments & Analysis paper where the measurement itself is the contribution.DataNo warnings★ 1.4K↓ —
- goose-product-photosgooseworks-ai/goose-skillsMake product photos (studio, lifestyle or on a model) of a brand's real products with GooseWorks in this chat. Start brand work with brand_knowledge_browse and follow the next_step in every answer.MediaNo warnings★ 1.3K↓ —
- soda-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when deciding whether and how experiments belong in a SODA (ACM-SIAM Symposium on Discrete Algorithms) paper — SODA's scope includes experimental validation but theorems carry the decision, so this skill designs supporting numerics honestly and routes implementation-led work to co-located ALENEX or to SEA.ScienceNo warnings★ 1.4K↓ —
- uai-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when revising a UAI manuscript for probabilistic-inference readers, enforcing precise notation for distributions, graphs, and interventions, explicit assumption and identifiability statements, an 8-page main part that carries the whole argument while proofs sit in the appendix, and claims calibrated to what the theory and experiments show.WritingNo warnings★ 1.4K↓ —
- osdi-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of an OSDI submission — choosing mature baselines and realistic workloads, structuring the section around research questions, measuring scalability and tail behavior, quantifying the design's costs, and fitting the evidence into the 12-page reviewed body.DesignNo warnings★ 1.4K↓ —
- eccv-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the experimental program of an ECCV paper — benchmark selection that survives a September conference, matched-substrate baseline fairness in the foundation-model era, ablations that isolate the claimed mechanism, qualitative failure evidence, and run sequencing toward a March freeze.ScienceNo warnings★ 1.4K↓ —
- hri-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when drafting or revising an ACM/IEEE HRI full paper's structure and prose for an interdisciplinary audience — leading with the human-robot contribution and research questions, making hypotheses and measures explicit, describing the robot embodiment, keeping claims proportional to the study within the 8-page acmart budget, and writing so the chosen track's contribution type is unmistakable.WritingNo warnings★ 1.4K↓ —
- iccv-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing the experimental program for an ICCV paper against the early-March deadline, covering benchmark-drift audits across the two-year gap, baseline fairness in the foundation-model era, ablations that isolate mechanisms, qualitative and failure evidence, and sequencing runs so the decisive result lands before the deadline, not after.ScienceNo warnings★ 1.4K↓ —
- corl-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing experiments for a CoRL robot-learning paper — seeds and evaluation-episode counts, task-suite breadth, real-robot versus simulation evidence, sim-to-real gap measurement, baseline fairness across BC/RL/VLA families, generalization splits, and statistics for success-rate claims.ScienceNo warnings★ 1.4K↓ —
- openship-deployfcakyon/claude-codex-settingsThis skill should be used when the user asks to "deploy with OpenShip", "manage a self-hosted OpenShip instance", "debug an OpenShip deployment", or manage its domains, storage, backups, or upgrades through the CLI.DevOpsNo warnings★ 1.2K↓ —
- doca-upgradeNVIDIA/skillsChanging DOCA versions safely: upgrading or downgrading the host DOCA packages, refreshing the BlueField BFB, bumping the NGC DOCA container tag, or rolling back, with the discipline detect -> report -> ASK -> only then a guided upgrade. Trigger on "is there a newer DOCA", "I want the newest DOCA features, can I just apt upgrade in place", "should I move to the next release", "the upgrade stopped midway and dpkg is in a broken state", "my component is being deprecated, what now", or "roll me back", even without the word upgrade. Detect what is installed, find the newer release, report the gap, then STOP and ask for explicit confirmation; never upgrade automatically. Do not use it for a runtime error on an unchanged install (doca-debug). Version detection alone belongs to doca-version, first-time install to doca-setup, any hardware / firmware / reboot step to doca-hardware-safety, and public-docs or sunset routing to doca-public-knowledge-map.EngineeringNo warnings★ 3.8K↓ —
- 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.DocumentsNo warnings★ 1.4K↓ —
- casefilehashgraph-online/awesome-codex-pluginsUse when tracking security investigations, bug bounty findings, CTF leads, audit evidence, exploit chains, dead ends, or reports in the Casefile ledger through Codex.SecurityNo warnings★ 1.5K↓ —
- 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.ScienceNo warnings★ 1.4K↓ —
- 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.MediaNo warnings★ 1.4K↓ —
- 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.DevOpsNo warnings★ 1.4K↓ —
anti-ui-slop
hashgraph-online/awesome-codex-plugins
DesignUpdated 17 hours ago
From the author
Stop coding agents from shipping generic UI. Use UIZZE's 800,000+ real web and iOS screens to build product-specific interfaces, define a design contract, cover required states, and run a hard finish gate. Use when designing, implementing, redesigning, critiquing, or pre-ship reviewing a web or iOS interface in Codex, Claude Code, Cursor, Copilot, or another coding agent. Trigger with "anti-ui-slop", "stop UI slop", "ground this UI in real screens", or "run the UI finish gate".
Install
npx skills add hashgraph-online/awesome-codex-plugins --skill anti-ui-slop -a claude-code
Installs to .claude/skills/anti-ui-slop/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
What it can touch
Instructions onlyNo network use seenLicence: APACHE-2.0
Safety checks on SKILL.md
No warnings.
Why 88
Security100
Provenance78
Maintenance100
Licence100
Adoption51
Files (16)
- CHECKSUMS.sha256
- LICENSE
- MANIFEST.json
- MODIFICATIONS.md
- NOTICE
- SKILL.md
- agents/openai.yaml
- reference/audit.md
- reference/craft.md
- reference/distill.md
- reference/ios.md
- reference/new-work.md
- +4 more