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,492 skills from 2,391 repositories · updated 18 hours ago
48,451 skills
- rss-related-workbrycewang-stanford/Awesome-Journal-SkillsJournal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的 Claude Code/Codex 期刊技能包，从选题、识别策略到表格规范与审稿回复全流程，助你快速发论文。PlanningNo warnings★ 1.4K↓ —
- socc-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ACM SoCC (Symposium on Cloud Computing) research-paper submission for HotCRP readiness, covering the two-round abstract+paper deadlines, the acmart/sigconf 12-page (full) or 6-page (short) budget with unlimited references, dual-anonymous review, the systems-and-data reproducibility posture, and desk-reject triage before the AoE cutoff.ScienceNo warnings★ 1.4K↓ —
- sci-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when deciding which sci-* sub-skill to invoke next, or when sequencing a manuscript from significance test through reviewer rebuttal for Science (AAAS). Routes — it does not replace — the specialized skills.ProductivityNo warnings★ 1.4K↓ —
- soda-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when preparing or auditing a SODA (ACM-SIAM Symposium on Discrete Algorithms) submission — the no-page-limit full-version norm, the title-page abstract, 11-point single-column letter format, lightweight double-blind rules, HotCRP entry, and the July AoE deadline with its summary-rejection triggers.ProductivityNo warnings★ 1.4K↓ —
- tacas-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a TACAS (ETAPS) project timeline from category choice and venue fit through the EasyChair paper deadline, the mandatory tool-paper artifact deadline, the rebuttal window, notification, the voluntary post-acceptance artifact round, LNCS camera-ready, and presentation, with backward-planning offsets that account for TACAS's single annual round and its parallel paper+artifact review.ProductivityNo warnings★ 1.4K↓ —
- sigir-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a SIGIR project calendar — backward-planning from the January-pattern abstract/paper deadlines to the July conference, sequencing evidence freeze, significance testing, and anonymization, coordinating multi-track decisions, and wiring the SIGIR/ECIR/CIKM/WSDM/SIGIR-AP fallback calendar into one pipeline.ProductivityNo warnings★ 1.4K↓ —
- stoc-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing a STOC (ACM Symposium on Theory of Computing) submission for HotCRP readiness — the abstract + table-of-contents + first-12-pages reading rule, single-column 11-point format, double-blind hygiene, the SIGACT prior/simultaneous-publication policy, and deadline-week sequencing before the November cutoff.OtherNo warnings★ 1.4K↓ —
- person-researchhashgraph-online/awesome-codex-pluginsResearches a person across podcasts and YouTube for interview or meeting prep: where they appeared, their own words, who discusses them. Uses arcmira.ScienceNo warnings★ 1.5K↓ —
- vldb-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing a PVLDB submission before a monthly deadline, covering the mandatory abstract on the 25th, the CMT window, the 1st-of-month 5:00 PM Pacific cutoff, category and page-budget choice, single-blind cover-page requirements, the per-month and per-year author caps, and desk-reject hazards specific to VLDB.PlanningNo warnings★ 1.4K↓ —
- uist-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when performing the final pre-upload audit of a UIST paper in PCS — the abstract-then-paper deadline pair, 10-page/5-page two-column limits with desk-reject enforcement, anonymous acmart options, video-figure and supplementary uploads, the prior-work overlap rule, and deadline-week sequencing.MediaNo warnings★ 1.4K↓ —
- aaai-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical significance, robustness, human evaluation, AI-for-Social-Impact and alignment/safety evidence, compute and cost reporting, and reproducibility-checklist alignment for Phase-1 survival.OtherNo warnings★ 1.4K↓ —
- vis-related-workbrycewang-stanford/Awesome-Journal-SkillsUse when positioning an IEEE VIS submission against the visualization literature across TVCG, the six VIS areas, EuroVis/CGF, PacificVis, and adjacent HCI/graphics venues, writing delta-first contrast rather than a citation catalog, keeping self-citations double-blind when opted in, and handling concurrent, preprint, and prior-version overlap for a TVCG journal article.WritingNo warnings★ 1.4K↓ —
- uai-related-workbrycewang-stanford/Awesome-Journal-SkillsUse when positioning a UAI submission within the probabilistic reasoning, graphical-model, causality, and Bayesian ML literature, covering PMLR archival status of recent UAI volumes, double-blind self-citation discipline, concurrent arXiv and workshop versions, and the cross-community citation coverage UAI reviewers check first.ScienceNo warnings★ 1.4K↓ —
- wacv-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing a WACV submission before an OpenReview round deadline, covering the Round 1 vs Round 2 choice, the Applications vs Algorithms track field, the 8-page-including-figures limit, double-blind anonymity and OpenReview-profile requirements, the anonymized supplement, dual submission, and desk-reject triage.PlanningNo warnings★ 1.4K↓ —
- reviewhashgraph-online/awesome-codex-pluginsThe pre-merge review of a branch in a project that records its specs, decisions, and rules in .archcore/. Run this first for 'review my branch', 'review the changes before merge', or 'review before merge': it checks the changed code against the project's recorded canon and the changed documents against the code, and reports which side is wrong — spec-wrong or code-wrong; on the default branch it reviews the unpushed and uncommitted work. A bug-hunting code review complements this review and does not replace it. Also use for 'documentation gaps', 'check if docs match code', 'close out the feature', 'ship the feature and close it out', or after a staleness warning. Takes an optional path, tag, topic, or ref in free text; no first word is a mode — say 'are docs out of date', 'audit the knowledge base', 'close out the feature', or 'capture this pattern' in plain words. Not for creating docs — use /archcore:document; not for planning — use /archcore:plan; not for a single-file edit with no branch review.EngineeringNo warnings★ 1.5K↓ —Also in 1 other repo
- atc-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when drafting or revising an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) systems paper — writing a self-standing two-page extended abstract for the round-one gate, structuring the implementation-and-measurement narrative, reporting costs beside gains, and holding the two-column 12-page budget.WritingNo warnings★ 1.4K↓ —
- acmmm-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning the end-to-end ACM MM (ACM Multimedia) campaign calendar — from thematic-area scoping and track choice, through the April OpenReview abstract/paper/supplement chain, the June anonymous rebuttal, the July decision, the August camera-ready, and the November presentation in Rio, with the right skill invoked at each stage.ProductivityNo warnings★ 1.4K↓ —
- ase-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when deciding what belongs in the 10-page ASE (IEEE/ACM Automated Software Engineering) paper body versus the artifact and supplementary material, splitting content by decision-criticality so nothing that decides acceptance lives outside the reviewed pages under the 10+2 budget.ScienceNo warnings★ 1.4K↓ —
- acl-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when organizing appendices and supplementary material for an ACL paper under ACL Rolling Review, covering the mandatory Limitations and optional ethics sections, appendices after references, anonymized software and data archives, the no-cloud-links rule, and deciding what must stay in the 8-page or 4-page body.ScienceNo warnings★ 1.4K↓ —
- acl-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when revising an ACL paper for computational-linguistics house style, covering task-first framing, linguistic examples tied to quantitative error analysis, scoping language claims to tested languages, LLM-era claim discipline, anonymous self-reference, Limitations prose, and compressing into the 8-page or 4-page ACL format.WritingNo warnings★ 1.4K↓ —
- ase-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when shaping the prose and structure of an ASE (IEEE/ACM Automated Software Engineering) research paper, covering the automation-first first-page arc, stating the automated task precisely, keeping the tool runnable and the model-swap test in mind, threats-as-argument, and the 10+2 page discipline on the ACM acmart template.WritingNo warnings★ 1.4K↓ —
- second-brain-ingestundefined-ui/second-brain-osTurn raw source material in a second-brain vault into linked wiki pages: read the source, split it into concepts and entities, write or update pages, connect them to existing pages, and record the run in the log. Use this skill whenever the user drops a file into raw/, pastes an article, transcript or PDF and asks to add it to the vault, says "ingest this", "add this to my second brain", "process raw", or asks to catch up on unprocessed sources, even if they do not name the ingest command. Do NOT use for answering questions from an existing vault, for linting or repairing pages, or for editing notes the user wrote by hand.DocumentsNo warnings★ 1.3K↓ —
- second-brain-writeundefined-ui/second-brain-osDraft from the vault: outline from concept pages, keep citations to the user's own sources, and surface where their material disagrees. Use this skill when the user wants to write an article, post, essay or newsletter based on what they have collected, or asks what they could write about a topic. Do NOT use for research reports, for writing with no grounding in the vault, or for editing text the user wrote themselves unless asked.WritingNo warnings★ 1.3K↓ —
- colm-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the empirical core of a COLM paper — contamination analysis for evaluation data, fair baselines under matched prompting and compute, pinned model versions and decoding parameters, uncertainty over runs and samples, scaling coverage, and honest reporting of API-model comparisons.ScienceNo warnings★ 1.4K↓ —
writing-relayflows
AgentWorkforce/relay
WritingUpdated 23 hours ago
From the author
Use when authoring a Relayflows flow (@relayflows/surface / @relayflows/sdk, the journal-based v2 engine — the CLI is `flows`, package versions 2.0.x) in TypeScript or YAML/JSON. Covers the three-rung ladder (run/llm/agent), the resident verbs (human/dispatch/done), verification gates, TypeScript vs YAML authoring, per-step cli/model selection and its resolution order, flows.json, and `flows check`/`run`/`resume` with their real refusal shapes and exit codes. Not for the older, unrelated `@relayflows/core` WorkflowBuilder engine (`.pattern('dag')`/.agent()/.step() chains) that `writing-agent-relay-workflows` and `migrating-persona-to-relayflow` cover — that's a different product despite the similar name.
Install
npx skills add AgentWorkforce/relay --skill writing-relayflows -a claude-code
Installs to .claude/skills/writing-relayflows/ · 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
Provenance76
Maintenance100
Licence100
Adoption49
Files (1)
- SKILL.md