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 3 hours ago
48,362 skills
- 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.ProductivityNo warnings★ 1.4K↓ —
- 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.ProductivityNo warnings★ 1.4K↓ —
- 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.ProductivityNo warnings★ 1.4K↓ —
- 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.ProductivityNo warnings★ 1.4K↓ —
- 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.ProductivityNo warnings★ 1.4K↓ —
- 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.ProductivityNo warnings★ 1.4K↓ —
- where-to-start-situation-savegooseworks-ai/goose-skillsStep of the where-to-start playbook: saves the founder's answers and the agreed first move with the brand, so later visits and other playbooks don't ask again. Run where-to-start instead; not for direct use.OtherNo warnings★ 1.3K↓ —
- iclr-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICLR project timeline from topic selection through OpenReview submission, discussion, revision, decision, camera-ready, poster, video, and public artifact release. Use when sequencing milestones against the current cycle's OpenReview deadlines, budgeting time for the long public discussion phase, or assigning owners for anonymity audits and reviewer-verifiable evidence paths.ProductivityNo warnings★ 1.4K↓ —
- dac-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ACM/IEEE Design Automation Conference (DAC) Research-Manuscript submission for Softconf readiness, covering the two-stage abstract-then-manuscript deadline, the 6+1-page ACM double-column page budget with its references-only last page, the double-blind anonymization sweep, TPC conflict-of-interest declaration, and desk-reject triage before the mid-to-late-November cutoff.DesignNo warnings★ 1.4K↓ —
- 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.ProductivityNo warnings★ 1.4K↓ —
- edbt-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an EDBT project timeline across the multiple-cycle rolling model — choosing a submission cycle, backward-planning through the author-feedback phase and the in-cycle revise-and-resubmit window, and handling the cycle-to-conference roll — for a database-systems paper published open access on OpenProceedings.ProductivityNo warnings★ 1.4K↓ —
- ecai-workflowbrycewang-stanford/Awesome-Journal-SkillsUse to plan an ECAI campaign end to end — run the single-round year backward from the paper deadline through the abstract/registration step, summary-reject phase, rebuttal window, notification, and the open-access camera-ready, adapting to whether the edition is a standalone ECAI (FAIA/PAIS) or the joint IJCAI-ECAI 2026.ProductivityNo warnings★ 1.4K↓ —
- 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.ScienceNo warnings★ 1.4K↓ —
- 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.MediaNo warnings★ 1.4K↓ —
- cell-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when deciding which cell-* sub-skill to invoke next, or when sequencing a manuscript from significance test through reviewer rebuttal for Cell (Cell Press). Routes — it does not replace — the specialized skills.ProductivityNo warnings★ 1.4K↓ —
- cikm-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a CIKM project calendar across the May abstract/paper gates, June short-track gates, August notification and camera-ready, and the November conference, including the post-submission phase now live in the 2026 cycle, multi-track coordination, and fallback planning toward CIKM 2027 or sibling venues.ProductivityNo warnings★ 1.4K↓ —
- colm-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a COLM submission campaign across the calendar — working backward from the late-March abstract and paper deadlines through the May-June rebuttal, July decisions, August camera-ready, and October conference, coordinating co-authors, compute, and reciprocal-reviewing duties, and slotting COLM into a multi-venue LM-research pipeline.ProductivityNo warnings★ 1.4K↓ —
- corl-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a CoRL submission cycle end to end — the late-May abstract and paper deadlines, the summer review window, first-round rejection risk, the August one-page rebuttal and discussion period, autumn decisions, the October PMLR camera-ready, and the November conference — including what to do between milestones.ProductivityNo warnings★ 1.4K↓ —
- colt-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a COLT (Conference on Learning Theory) submission calendar backward from the single AoE paper deadline — proof-completion and verification milestones, writing and appendix-assembly passes, CMT logistics, the rebuttal window, decision aftermath, and PMLR camera-ready with conference presentation in early summer.ProductivityNo warnings★ 1.4K↓ —
- pnas-fitbrycewang-stanford/Awesome-Journal-SkillsUse before any writing begins to stress-test whether a result clears PNAS's bar — high quality and broad significance to a general scientific readership — and to make the realistic call between PNAS, Science/Nature, and a specialist field journal.TestingNo warnings★ 1.4K↓ —
- nejm-fitbrycewang-stanford/Awesome-Journal-SkillsUse this first, before any writing, to stress-test whether a clinical study clears NEJM's bar — practice-changing clinical impact, methodological rigor, and generalizability. Decides NEJM vs Lancet/JAMA vs a specialty journal.TestingNo warnings★ 1.4K↓ —
- minutes-briefsilverstein/minutesFast non-interactive briefing before any meeting — auto-detects your next calendar event, pulls relationship history, surfaces open commitments, and produces a one-page brief in under 30 seconds. Use this whenever the user says "brief me", "give me a quick brief", "what's coming up", "background on my next call", "who am I meeting next", "brief me on Sarah", "I have a call in 10 min", "quick rundown", or right before walking into a meeting. Different from /minutes-prep — brief is the fast hook-fireable version that doesn't ask questions and doesn't set goals. Use brief when speed matters; use prep when the user wants to think hard about goals first.ProductivityNo warnings★ 1.6K↓ —Also in 1 other repo
- color-palettejezweb/claude-skillsGenerate complete, accessible colour palettes from a single brand hex. Produces 11-shade scale (50-950), semantic tokens, dark mode variants, Tailwind v4 CSS output, WCAG contrast checks. Use whenever the user supplies a brand hex and asks for a palette, mentions setting up a design system, wants Tailwind theme colours from a brand colour, or asks to check colour accessibility / contrast.DesignNo warnings★ 1.1K↓ —
- expo-skill-evalexpo/skillsEvaluate Expo skills in this repo end-to-end - trigger accuracy, generated code quality, and runtime screenshots on iOS simulator and Android emulator via Expo Go (web optional). Use when the user wants to eval an Expo skill, test that a skill produces working code, benchmark a skill with device screenshots, or verify a skill's output renders correctly.OfficialTestingNo warnings★ 4K↓ —
scheduler-and-booking-design
rampstackco/claude-skills
From the author
Designing meeting schedulers and booking experiences that qualify leads, set up calls well, and convert at higher rates than a generic Calendly link. Availability logic, qualification gating, prep automation, follow-up sequencing. Honest about any-time-friction (no qualification, just a booking link), interrogation-gate (so much qualification it scares users off), and qualified-fast-path (just enough qualification to set up the call well) patterns. Triggers on scheduler design, meeting booking, demo scheduling, sales call scheduling, calendar tool, booking page, qualification flow. Also triggers when sales team complains about cold demos, when booking conversion is poor, or when scheduler is being scoped for the first time.
Install
npx skills add rampstackco/claude-skills --skill scheduler-and-booking-design -a claude-code
Installs to .claude/skills/scheduler-and-booking-design/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
What it can touch
Safety checks on SKILL.md
No warnings.
Why 88
Files (11)
- README.md
- SKILL.md
- references/availability-logic-patterns.md
- references/common-scheduler-failures.md
- references/prep-automation-patterns.md
- references/qualification-field-design.md
- references/reminder-sequence-patterns.md
- references/reschedule-and-no-show-handling.md
- references/routing-patterns.md
- references/scheduler-anti-patterns.md
- references/scheduler-decision-criteria.md