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.
48,622 skills from 2,355 repositories · updated 17 hours ago
47,548 skills
- 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.3K↓ —
- 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.3K↓ —
- 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.3K↓ —
- 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.3K↓ —
- 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.3K↓ —
- eacl-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an EACL project timeline through ACL Rolling Review, covering the single viable ARR cycle with no fallback, backward planning from the one deadline, the rebuttal window, the commitment decision to EACL, notification, and camera-ready through ACL Anthology publication, plus re-routing since the next chance is another conference.ProductivityNo warnings★ 1.3K↓ —
- 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.3K↓ —
- 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.3K↓ —
- 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.3K↓ —
- 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.3K↓ —
- 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.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.3K↓ —
- hri-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ACM/IEEE HRI full-paper submission for PCS readiness — the mandatory abstract-then-paper two-step deadline, choosing the correct one of the five tracks, the 8-page acmart anonymous format, the double-blind sweep across PDF and video, the human-participants ethics acknowledgment, and desk-reject triage before the AoE cutoff.DocumentsNo warnings★ 1.3K↓ —
- 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.3K↓ —
- 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.3K↓ —
- 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.3K↓ —
- 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.3K↓ —
- 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.3K↓ —
- 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.3K↓ —
- 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.ScienceNo warnings★ 1.3K↓ —
- 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.ProductivityNo warnings★ 1.3K↓ —
- 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.ProductivityNo warnings★ 1.3K↓ —
- 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.ProductivityNo warnings★ 1.3K↓ —
- 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.ProductivityNo warnings★ 1.3K↓ —
journey-mapping
rampstackco/claude-skills
OtherUpdated 6 days ago
From the author
Build customer journey maps and service blueprints that visualize the end-to-end user experience including touchpoints, emotions, friction, and underlying systems. Use this skill whenever the user wants to map a customer journey, build a service blueprint, identify friction across an experience, align teams on the user experience, or visualize touchpoints and pain points. Triggers on customer journey, journey map, service blueprint, user journey, experience map, touchpoint analysis, friction map, journey audit, end-to-end experience, customer experience map. Also triggers when the team has departmental views of users but no shared map of what the experience actually feels like.
Install
npx skills add rampstackco/claude-skills --skill journey-mapping -a claude-code
Installs to .claude/skills/journey-mapping/ · 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: MIT
Safety checks on SKILL.md
No warnings.
Why 88
Security100
Provenance76
Maintenance100
Licence100
Adoption49
Files (3)
- README.md
- SKILL.md
- references/journey-map-template.md